The files must contain at least the following information:

1. Dimensionlevel
   Indicates which dimension level the value should be created on. Example:
   Dim1 = Department dimension level
   Dim2 = Project dimension level
2. Dimension relation
   Value, which indicates which relation / dependence the value has to another dimension value
3. ID: Unique key to the dimension
   The value must never change and must be unique across dimensions and levels. Used to decide if it is a new dimension or one to be updated
4. Description
   The value displayed for the user. Typical name of project and project number - eg "Sales Project - 12001"
5. Booking value
   Value to be exported to the ERP system for proper posting.
6. Active
   Value, which shows that the delivered value is active

Depending on configuration and desires, there may be configurations where there are dependents between the dimensions and no dependents. These dependents can be combined in different ways.

Dimensional levels without dependancy

1. Department = Dim1 level
2. Project = Dim2 level

The file for Acubiz should not contain header lines - only user data:

Example of file content

Dim1;Dim1;100;Sales Department - 100;100;1
Dim1;Dim1;120;Finance Department - 120;120;1
Dim1;Dim1;130;Marketing Department - 130;130;1
Dim2;Dim2;5001;Sales Project - 5001;5001;1
Dim2;Dim2;5002;Finance Project - 5002;5002;1
Dim2;Dim2;5003;Marketing Project - 5003;5003;1

Se attached "DimData_Basic_2_DimLevels.txt"

Dimension with dependence

Same structure with 2 levels, but where there are dependancy between the dimensions. Meaning that only projects associated with a single department are displayed for the user

1. Department = Dim1 level
2. Project = Dim2 level (Dependancy to department Dim1)

If "Sales department - 100" is selected, then only "Sales Project - 5001" can be selected in the project level

The file for Acubiz should not contain header lines - only user data:

Example of file content

Dim1;Dim1;100;Sales Department - 100;100;1
Dim1;Dim1;120;Finance Department - 120;120;1
Dim1;Dim1;130;Marketing Department - 130;130;1
Dim2;100;5001;Sales Project - 5001;5001;1
Dim2;120;5002;Finance Project - 5002;5002;1
Dim2;130;5003;Marketing Project - 5003;5003;1

Active dimensions:

By default, an "active list" are delivered to Acubiz containing only active dimension values. This means that Acubiz keeps track of the dimensions to be closed/deactivated in Acubiz.

In the above example, the following happens with data in AcubizEMS:

1. Department 100: Is included in the file and does not exist in Acubiz = Created
2. Department 120: Is included in the file and exists in Acubiz. Name is changed = Updated
3. Department 130: Is included in the file and exists in Acubiz = No change
4. Project 5001: Is included in the file and does not exist in Acubiz = Created
5. Project 5002: Is included in the file and exists in Acubiz = No change
6. Project 5003: Is included in the file and exists in Acubiz = No change
7. Project 5004: Is not included in the file and exists in Acubiz = Deactivated

The file must not contain

There are certain characters that can not be used - eg, the Seperator, &, <TAB>, + and other special characters (*,;%% & "). These will cause problems for the user and must be sorted / replaced by other characters before loading in Acubiz. We handle unauthorized characters, but this means that the individual values gets an editing date for each upload and is therefore marked as new. The values are therefore updated in apps at each login and are performanceally inappropriate. There may be other information that may be required depending on your configuration.

A further clarification must be made based on your configuration