How should the import file be organized?
The different import files can be:
-
Files with separators
These are files that have been created by Business Objects™ applications or Microsoft Excel™, for example.
Each field is separated by a character, for example a comma or tab.
-
Fixed length files
The data in these files is organized in columns whose length is fixed.
The import file can contain:
- Zero or a number of row headers to be ignored during the data import.
- A first row describing the column headers in the import file and the list of dimensions to be imported.
- The rows containing the data to be imported.
Example:

Compulsory and optional dimensions
This section describes the compulsory and optional dimensions for the different types of data import.
- The following dimensions must be entered
when importing single packages
- Account (code: AC)
- Flow (code: FL)
-
The following dimensions must be entered when importing multiple packages
- Account (code: AC)
- Flow (code: FL)
- Category (code: CA)
- Data Entry Period (code: DP)
- Reporting Unit (code: RU)
-
The following dimensions must be present in the import file structure, but do not necessarily need to contain data
- Audit ID (code: AU)
- Period (code: PE)
- Currency (code: CU)
-
Optional dimensions
- Original Reporting Unit (code: ORU)
- Partner 1 (code: PA)
- Partner 2 (code: SH)
- Technical Origin (code: TO)
- Geographical Origin (code: GO)
- Ledger (code: LE)
- Journal Entry Number (code: NU)
- User-defined dimensions
Assigning a default member
Regardless of whether you are importing data into multi-packages or into one package only, a default member will be assigned if one of the compulsory dimension rows does not contain any members:
| Dimension row | Default member assigned |
|---|---|
| Audit ID | Original package audit ID (S level). |
| Currency | Package data entry currency defined in the RU Organizer module. |
| Period (single-period category scenario) | Period defined for this category scenario. |
| Period (multi-period category scenario) | First period defined for this category scenario. |
Column headers
The column headers contain the dimension code for the rows of data in the import file:
- If the rows of data contain alphanumeric codes, the dimension must be identified by a D_ <dimension code> in the column header.
- If the rows of data contain numerical data, the dimension must be identified by a ZD_ <dimension code> in the column header.
The amount column name must be P_AMOUNT and the comment column must be P_COMMENT.
