Set up the Oracle General Ledger source system and connection information, and then initialize the source system.
The initialize process brings over the Oracle General Ledger data into the Oracle Enterprise Performance Management Cloud system as Oracle Essbase cubes. Each Essbase target application represents a chart of accounts definition from the source Oracle General Ledger.
Create the EPM Cloud target application that requires the Oracle General Ledger data from the Oracle General Ledger source system.
Create the target application that requires data from one or more source systems.
If you are loading data from an Oracle General Ledger application to an EPM Cloud application, add the EPM Cloud as the target application type (for example, add Planning as the target application type.)
Set up the integration mapping between Oracle General Ledger and the EPM application dimensions in Data Management by building an import format.
See Working with Import Formats in this section.
Define the location used to associate the import format with the Oracle General Ledger segments.
See Defining Locations in this section.
Create category mapping for scenario dimension members in the EPM application to which Oracle General Ledger balances are loaded.
See Defining Category Mappings in this section.
Define data load mapping to convert the chart of accounts values from the Oracle General Ledger to dimension members during the transfer.
See Data Load Mapping in this section.
Define a data rule with the necessary filters and execute the rule.
A default filter is provided that includes all dimensions of the Essbase cube. The cube may have duplicate members so fully qualified member names are required. The Essbase cubes work off the Oracle General Ledger segments, and there is a one to many relationships of Chart of Accounts to ledgers in the Oracle General Ledger.
Data Management creates filters when a rule is created. You can modify the filters as needed but cannot delete them. (If the filters are deleted, Data Management recreates the default values). For information about these filters, see Adding Filters for Data Load Rules.
The process extracts and loads the data from Oracle ERP Cloud to Data Management.
Optional: Write back the data to the Oracle ERP Cloud.
To write back data to Oracle ERP Cloud from an Planning or Planning Modules source system, set up a data rule. In this case, the filters are applied against the Planning or Planning Modules application.
Optionally, you can write back budget data from a Planning to a flat file using a custom target application. This output file may be used to load data to any other application.