Metadata for Classic Planning applications can be loaded for Account, Period, Year, Scenario, Version, Currency, Entity, user-defined dimensions, attributes, UDAs, and Smart Lists. Values can also be loaded for exchange rates. However, because exchange rate values are loaded into the Planning relational tables, not directly into Essbase, the procedure for loading metadata still applies.
The utility loads one record at a time. If a record fails to load, a message is written to the exception file, and the load process resumes with the next record. When new members are added, unspecified properties assume the default value or inherit the parent member's property as appropriate. If a member exists and no property value is specified, the property is left as is.
To load metadata:
When loading metadata, the load file must contain a header record that lists the dimension, such as Account, and the member properties used by subsequent metadata records. For example, for Account, you can specify which account to load, a default alias, the operation to perform, and so on. Header records are case sensitive. They can appear in any order.
The next lines in the .CSV load file contain metadata records, listed in the order designated by the header record. Each metadata record contains a comma-separated list of property values that correspond to the header record entries. For detailed information on the properties available for each Planning member, see Dimension Properties.
Example: This load file loads an Entity dimension with the required header record and three data records. The header record specifies the member to be loaded (Entity), the parent member (Parent) into which to load the member, and the Data Storage property to assign to the member.
Entity, Parent, Data Storage e1, Entity, e2, , e1, e2, Shared
Using this load file would result in this outline, assuming that no other members exist:
Entity e1 e2 e1(Shared)
The first data record (e1, Entity) loads Entity member e1 as a child under the root member Entity. Unspecified values assume the default. For example, if data storage is not specified, it assumes the default value, Never Share. The next data record (e2, ,) loads Entity member e2 under the dimension root member because no parent is specified, and sets data storage to Never Share. The last data record (e1, e2, Shared) loads a shared member of e1 under member e2, and sets data storage to Shared.
When loading the Currency dimension with the Default Currency Symbol, if a currency is added without a symbol specified, the symbol is set to that of a pre-defined currency of the same name (or, if the name does not match a pre-defined currency, to the currency code of the currency being added).
Test the load file and run the utility.
Locate the Outline Load utility, installed in the planning1 directory.
For the full path to the planning1 directory, see About EPM Oracle Instance.
To confirm that the load file parses without any errors, run the utility using /N, and check the log file to be sure no error messages were generated. For example:
C:\EPM_ORACLE_INSTANCE\Planning\planning1>OutlineLoad /A:test /U:admin /M /N /I:c:\outline1_ent.csv /D:Entity /L:c:/outlineLoad.log /X:c:/outlineLoad.exc
You can then run the utility from the command prompt, using the case-sensitive command, one space, and the appropriate parameters.
For detailed information on the parameters available for the Outline Load utility, see Dimension Properties.