Writing Back Cloud EPM Budget Balances to the Budgetary Control Process Description

If you want to report budget-to-actual from the General Ledger, you need to write back your budget to Oracle General Ledger. If you want to validate spending online, you need to write back your budget to Budgetary Control.

Use this procedure to write back original and revised budget prepared using thePlanning feature to Oracle General Ledger.

This procedure is not for writing back budget revisions prepared using the Budget Revisions feature in the Oracle Fusion Cloud Enterprise Performance Management which automatically updates budget in both General Ledger and EPM type control budget in Budgetary Control through other procedure. For more information, see Setting Up Budget Revisions and Integration with Budgetary Control.

This procedure synchronizes the budget written back to an EPM type control budget in Budgetary Control with the budget in Oracle General Ledger, making it possible to skip the Writing Back Budgets to the Oracle ERP Cloud in Administering Data Management for Oracle Enterprise Performance Management Cloud procedure for the portion of your enterprise-wide budget that you write back to Budgetary Control.

For more information, see Using Financials for the Public Sector.

For Planning users, watch this tutorial video to learn about writing back Cloud EPM budgets to the Oracle General Ledger:

Tutorial Video

For Planning Modules users, see the Tutorial Video.

At a high level, here are the steps for writing back Cloud EPM budgets to the Budgetary Control::

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

   See Configuring a Connection to a Budgetary Control Source.

   Note:

   If you have already registered a source system to connect to the Budgetary Control application in Loading Budgetary Control to the Oracle Fusion Cloud EPM Process Description topic (see Loading Budgetary Control Budget Consumption Balances to the Cloud EPM Process Description), you must reuse the same source system.

   Note:

   Drill through is not supported in this release.

2. Select the Budgetary Control target application to which to write back budgets from the Cloud EPM source system.

   A Budgetary Control application is downloaded with the target application type Oracle Essbase.

   As a rule, when writing back to a Budgetary Control application, do not change, add, or delete any dimension details on the Target Application screen.

   See also: Registering Target Applications.

3. Map the dimensions between the Planning application and the Budgetary Control target application by building an import format.

   See also: Working with Import Formats.

4. Create a location to associate the import format for a Cloud EPM application with a Budgetary Control application.

   See also: Defining Locations.

5. Create category mapping for scenario dimension members in the Planning application and from which the budget is written back to the Budgetary Control.

   See also: Defining Category Mappings.

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

   See also: Data Load Mapping.

7. Create a data load rule (integration definition) to to map dimension members between the Planning application and Budgetary Control.

   See also: Adding Data Load Rules.

8. View the Cloud EPM budgets loaded to Budgetary Control.

   See also: Viewing the Cloud EPM Budgets Loaded to Budgetary Control.

9. Optionally, you can write out budget data from the Planning to a flat file using a custom target application. This output file may be used to load data to any other application.

   See also: Creating a Custom Target Application.