Consider these points when working with load files:
For each dimension in the application, you create a load file with fields corresponding to the dimension properties. Each load file can contain members for only one dimension. You can define multiple members for each dimension.
The required fields are different for each dimension being loaded. See Dimension Properties.
The member name must be included as a field in the load file. If the member property value is not specified, the application default value for the property is used.
When adding new members, unspecified values assume a default value or are inherited from the parent member's property value as appropriate. If the member exists and no value is specified, it is left as is.
When you load a member that already exists in the Planning application (for example, to change a property), if the member already exists in the application and a parent is not specified in the load file, the member is left under the existing parent. If a new parent is specified, the member is moved under the new parent.
The planning unit hierarchy load behavior differs from other dimension loads in that the import file specifies a complete replacement of the hierarchy instead of incremental changes, as is the case when loading other dimensions. Loading planning unit hierarchies first deletes all members of the planning unit hierarchy, and then adds each member specified in the input file as a new member. It is important to keep in mind that a planning unit hierarchy load deletes an existing member and its children from the hierarchy if the member is not specified in the input file.
To specify a null value, you can use the reserved value, <none>, for example, to delete an attribute assignment.
Only one dimension can be loaded per load file.
Column headers in the load file are case-sensitive.
The records are loaded one by one. If a record fails to load, its associated exception is written to the exception file and the load process resumes with the next record.
If errors are logged when loading a year, and the year was loaded into the application, its properties may not be what was specified for it in the load file. Correct the load file record and reload the year to set its properties correctly.
Parent members must exist or be loaded before their child members. In most cases, the load file must be sorted in parent-child order, either explicitly or by using /H.
Data values containing commas and quotation marks must be enclosed in quotation marks. These examples show how commas and quotation marks are interpreted.