In a test environment, run load files, and then open the appropriate data form in Public Sector Planning and Budgeting to ensure that the files load the correct metadata and data (see Verifying Data Loads.)
Important: Run the load files for metadata first, and then those for data. See Required Data Load File Run Order.
Test load files by running commands using this syntax
OutlineLoad /A:<application> /U:<user name>/I:<.csv file>/D:<dimension> /L:<log file>/N [/S:<server>] [/M] /X:<exception file>
/A:— Application name
/U:— User name of administrative user who can access Essbase and Planning.
/M:— Properties for each dimension to load
/N:— If the file parses without loading data
/I:— CSV load file that contains the header record and metadata records
/D:— Dimension to load
/C: —Refresh the database
/L:— Name of the log file to report load status. Default is stdout.log
/X:— Name of the file to report exceptions during the load. Default is stderr
/S:— Server hosting the application
Omit components as necessary. For example, if you do not want to refresh the database, remove /C/.
For all command parameters, see Chapter 5 of the Oracle Hyperion Planning Administrator's Guide.
For example: OutlineLoad /A:PO /U:jtadmin /I:<directory>\employee.csv/D:Employee /L:c:/employee_load.log /N/S:localhost /M/X:c:/employee_load.exc:
Loads data to the Position-Only (PO) application
Logs on to the application usingjtadmin
Loads data to the application on the localhost server
Loads the Employee data specified in employee.csv
Writes errors to employee_load.log
Parses to ensure that the file is correctly defined
Writes exception details to employee_load.exc