Loading Data

When loading data with the Outline Load utility, there are two ways to specify driver members. You can load to driver members that are specified on the Planning Data Load Administration page, or you can specify driver members in the .CSV load file and run the utility with the /TR option.

If you load data with the /TR option, the .CSV file must list the driver member and all other members under the Point-of-View column, regardless of their location on the data form. For example, if Jan or Descendants (YearTotal) are columns in a data form, they must be specified in the Point-of-View column. When using /TR, you can load one value per row in the .CSV file. You can include multiple rows, but you can specify only one data value per row.

Caution!

Following these steps can affect data in the database. The Planning DIRECT_DATA_LOAD system property enables data to be loaded directly to Essbase. In the current release, this property is set to true by default, and data is loaded directly into Essbase. To prevent data from being loaded directly into Essbase, set DIRECT_DATA_LOAD to false.

To load data with the Outline Load utility:

Back up the application and application databases before loading information. See the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.
Set Planning System properties.
1. Log in to the Planning application.
2. Select Administration, then Application, then Properties, then click the System Properties tab.
3. Set the DIRECT_DATA_LOAD and DATA_LOAD_FILE_PATH properties:
  - If DIRECT_DATA_LOAD is set to True, or if you do not specify a value for this property, information is loaded directly into Essbase while the load file records are processed. For this method to work correctly, the outlines maintained in Planning and Essbase must be synchronized. The .CSV load file must not specify any Planning outline changes unless they have already been refreshed to Essbase.
  - If DIRECT_DATA_LOAD is set to False, the Outline Load utility processes the .CSV load file that you created to generate a data file (.TXT) and rule file (.RUL). This way, the Planning and Essbase outlines do not need to be synchronized because data is not loaded at this time. You can refresh the changes at a convenient time to propagate the metadata changes to Essbase, and then load data directly into Essbase (for example, using Oracle Essbase Administration Services).
    In most cases, set DIRECT_DATA_LOAD to False, and set DATA_LOAD_PATH to the location and name that will be used for the generated data and rules files, for example, C:/myDirectory/App1.txt. Ensure that these properties are set in the System Properties tab in the Manage Properties page.
4. Restart the Planning application server.
If you want to load to driver members that are specified in Planning, set the driver members as described in this step. Otherwise, skip to the next step.
1. Log on to the Planning application for which data will be loaded.
2. Select Administration, then Data Load Settings.
3. Select a dimension from the Data Load Dimension list (such as Account). This is the dimension for which you want to load data. For example, it may appear as a row in a Planning data form.
4. Select a dimension from the Driver Dimension list (such as Period).
5. Click the member selection icon to select members of the Driver Dimension (such as Jan, Feb, March). For example, these members may appear as columns in a Planning data form.
Generate a comma-separated load file containing these columns:
- Driver Member: The member into which data is loaded. You can have one driver dimension per load. Multiple members can be defined for the driver dimension. The value is passed as a string representing a numeric value, or, if a Smart List is bound to the member, as a Smart List value.
- Point-of-View: All other dimensions required to determine the intersection for which to load the data. (If you are using /TR, include all of the members except the driver member.) The data load automatically performs cross-product record creations based on the dimension parameters in the point of view (POV). The load file creates and loads the data record for each relevant cell intersection. The value is passed as a string. The POV accepts a comma-separated list of members, including member functions. For example, children(Q1) is expanded to Jan, Feb, Mar during the load. The corresponding records are generated based on the cross product of all member combinations and the data value.
- Data Load Cube Name: The name of the plan type to which data is being loaded. The value is passed as a string. Values include any plan types specified in the application, such as Plan1.
Example 1: In this example, Account was selected as the Data Load dimension on the application's Data Load Administration page. Period was selected as the Driver Dimension, and Jan was selected as the Driver member.
```
Account,Jan,Point-of-View,Data Load Cube Name
acct1,12,”Local,ent1,Current,Ver1,FY08”,Plan1
```
Example 2: In this example, Entity was selected as the Data Load dimension on the application's Data Load Administration page. Account was selected as the Driver Dimension, and Account members aUnspec, aSmart, aDate, and aText were selected as the driver members. This .CSV load file loads data into the intersection of e1, the point of view, and the Account driver members, aUnspec, aSmart, aDate, and aText.
```
Entity,Operation,Data Load Cube Name,aUnspec,aSmart,aDate,aText,Point-of-View
e1, ,Plan1,77,smart1,12-22-2008,textValue,"USD,Jan,Current, BUVersion_1, FY07"
```
Assuming these values for the driver members:
- aUnspec: Data Type Unspecified (numeric), value 77
- aSmart: Data Type Smartlist,value smartlist entry ‘smart1’
- aDate: Data Type Date,value 12-22-2008
- aText: Data Type Text,value ‘textValue’
If DIRECT_DATA_LOAD is set to False, the example would generate this data load file:
```
    Currency  Version  Scenario  Year  Entity  Period  Account  HSP_Rates 
77  USD  BUVersion_1  Current  FY07  e1  Jan  aUnspec  HSP_InputValue
1  USD  BUVersion_1  Current  FY07  e1  Jan  aText  HSP_InputValue
20081222  USD  BUVersion_1  Current  FY07  e1  Jan  Date  HSP_InputValue
1  USD  BUVersion_1  Current  FY07  e1  Jan  aSmart  HSP_InputValue 
```
Example 3: Specify drivers directly in the .CSV load file.
```
Value,Driver Member,Point-of-View,Data Load Cube Name
14,a1,"Jan,Local,e1,Current,Version1,FY08",Plan1
sl1_value2,a2,"Jan,Local,e1,Current,Version1,FY08",Plan1
OutlineLoad /A:acpt1 /U:admin /M /I:c:\outline1data.csv /TR /L:c:/OutlineLogs/outlineLoad.log /X:c:/OutlineLogs/outlineLoad.exc
```
Test the load file and run the utility.
1. Locate the utility, installed in the planning1 directory.
  For the full path to planning1, see About EPM Oracle Instance.
2. To confirm that the load file parses without any errors, run the utility using the /N parameter, and check the outline log file to be sure no error messages were generated. Running the utility with /N does not load data or metadata, but ensures that the .CSV load file parses successfully. For example, you could use this command line to check the load file for a Planning application called test:
  C:EPM_ORACLE_INSTANCE\Planning\planning1>OutlineLoad /A:test /U:admin /M /N /I:c:\outline1data3.csv /D:Entity /L:c:/outlineLoad.log /X:c:/outlineLoad.exc
3. You can then run the utility from the command prompt without /N, using the case-sensitive command, one space, and the appropriate parameters. For example:
  C:\EPM_ORACLE_INSTANCE\Planning\planning1>OutlineLoad /A:test /U:admin /M /I:c:\outline1data3.csv /D:Entity /L:c:/outlineLoad.log /X:c:/outlineLoad.exc
  If you are loading data without specifying driver members within Planning, you can run the utility including /TR. For example:
  C:\EPM_ORACLE_INSTANCE\Planning\planning1>OutlineLoad /A:test /U:admin /M /N /I:c:\outline1data3.csv /TR /D:Entity /L:c:/outlineLoad.log /X:c:/outlineLoad.exc
  For detailed information on the parameters available for use with the Outline Load utility, see Dimension Properties.