Loading Budgetary Control Budget Consumption Balances to the EPM Cloud Process Description

Describes how to load commitments, obligations, and other anticipated expenditures from Budgetary Control to use in your Planning and Planning Budget Revisions applications.

You can load commitments, obligations, expenditures and other anticipated expenditures from Budgetary Control to use in your Planning and Planning Budget Revisions applications.

At a high level, these are the steps to load commitments, obligations, and other anticipated expenditures from Budgetary Control to the Oracle Enterprise Performance Management Cloud:

1. Register, configure, and initialize a source connection for Budgetary Control.

   The initialize process brings over Budgetary Control balance Essbase cubes into Data Management as Budgetary Control target applications. A control budget dimension member within each Budgetary Control target application represents a control budget in Budgetary Control from and to which the EPM Cloud loads data and writes back.

   See Configuring a Connection to a Budgetary Control Source.

   Note:

   Drill through is not supported in this release for the Budgetary Control integration with the EPM Cloud.

2. Create the EPM Cloud target application to represent the Planning and Budgetary Control application to be integrated.

   As a rule, when loading and writing back data between the Planning application and the Budgetary Control application, you can use the system-generated target application that represents the Planning application in the EPM Cloud and the target applications generated from source system initialization that represents the Budgetary Control balances Essbase cube, instead of creating your own. Do not change, add, or delete any dimension details for these system-generated target applications on the Target Application screen.

   See Registering Target Applications.

3. Create an import format to map the dimensions from the Budgetary Control application to those of the Planning application to which commitment, obligation and expenditure amounts are loaded.

   See Working with Import Formats in this section.

4. Create a location to associate the import format with the Budgetary Control.

   See Defining Locations in this section.

5. Create category mapping for scenario dimension members in the Planning application to which Budgetary Control balances are loaded.

   See Defining Category Mappings in this section.

6. Create data load mappings to map the dimension members between the Budgetary Control application and the Planning application.

   See Data Load Mapping in this section.

7. Create a data load rule (integration definition) to execute the data load and transfer commitment, obligation and expenditure amounts to the EPM Cloud application from the Budgetary Control application.

   See Adding Data Load Rules.