If your Capital Asset Planning application is new, you may want to load information, such as the existing account structure and properties, from enterprise systems:
If you are using Performance Management Architect application administration, load information using a flat file (see the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide).
If you are using Classic application administration, you can use Oracle's Hyperion® Data Integration Management Adapter for Planning (see Loading Information Using DIM Adapter for Planning).
You can also:
Manually enter information into Capital Asset Planning.
Load metadata and data that generates data and rules files for loading metadata and data through Oracle Essbase Administration Services. See the Oracle Hyperion Planning Administrator's Guide or online help.
To load information—data and metadata—using DIM Adapter for Planning:
Load metadata (for example, entities and accounts) into Capital Asset Planning.
Load Account and user-defined dimensions from any flat file or ODBC-compliant database. Load members, shared members, and attribute values into dimensions. Oracle recommends that you first load a small sample of accounts. Verify the results, make any needed changes, and then load the entire dimension.
See Capital Asset Planning Structure for a list of Capital Asset Planning accounts and their properties.
Refresh the application to update the Oracle Essbase outline.
Set up the data load dimension and dimension driver members.
The data load dimension is the dimension to which you are loading data, and corresponds to the target table in the DIM Adapter for Planning. The driver dimension is the dimension to which you are loading data in an Essbase database. See “Loading Data” in the Oracle Hyperion Planning Administrator’s Guide.
Load data and member properties into the Essbase database for the Capital Asset Planning application.
The outlines must match; you can specify only the members and parent member names.
Refresh the application to update the data.
Each time you modify the application structure, reload the data.