Writing Back Budgets to the Oracle General Ledger

If you want to report budget-to-actual from the Oracle General Ledger, you need to write back your budget to the 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 budgets prepared using the Planning feature to the Oracle General Ledger.

This procedure is not for writing back budget revisions prepared using the Budget Revisions feature in the Oracle Enterprise Performance Management Cloud, which automatically updates budget in both General Ledger and EPM type control budget in the Budgetary Control through another procedure.

The write back to Oracle General Ledger is also automatically performed for you when you write back the budget to the Budgetary Control for the EPM type control budget, but obviously only 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 EPM Cloud budgets to the Oracle General Ledger:

Tutorial Video

For Planning Modules users, see the Tutorial Video.

To write back to the Oracle General Ledger:

1. From the Data Integration home page, and then Actions, select Applications.

2. From the Application page, click to the right of the EPM Cloud source application, and then select Application Detail.

3. Select the Options tab.

4. From the Balance Type drop-down, select Budget.

5. In Journal Source, enter a description of the journal source that matches the journal source defined in Oracle ERP Cloud.

6. In Journal Category, enter a description of the journal category that the matches the journal category in Oracle ERP Cloud.

7. From the Data Integration home page, click , then on the Create Integration page, create the integration between the source data to the target and then click Save and Continue.

   1. In Name and Description, enter a name and description for the new integration.

   2. In Location, enter a new location name, or pick an existing location to specify where to load data.

   3. From the Source () drop-down, select the name of the EPM Cloud application from which to write back data.

   4. From the Target () drop-down, select the Oracle ERP Cloud application.

   5. From Category, select the category mappings for categorizing and mapping source system data to a target Scenario dimension member.

      The categories listed are those that you created in the setup, such as "Actual." For more information, see Managing Category Mappings.

   6. Optional: Select any applicable location attributes for the integration. For more information, see Selecting Location Attributes.

   7. Click Save and Continue.

8. On the Map Dimensions page, map the dimensions in the Oracle ERP Cloud source application to the dimensions in the EPM Cloud application.

   If you are adding new dimensions or editing an existing dimension, complete the following:

   • In Column, specify the field number from the file to import.

   • In Select Source Dimension, specify the name of the source dimension to assign to the target application.

     Multiple source columns of the same dimension can be mapped to target dimensions. For example, you can map four "Account" source columns.

   • Add a source or target expression: assign an expression that operates on values directly from the source or target.

     See Using Source Expressions and Using Target Expressions.

   Be sure to map a source for the target dimension "Ledger."

   You can map a dimension like "Entity" to the ledger and define any necessary data load mapping to convert to the Oracle General Ledger name. If you are writing back to a single ledger, enter the name of the ledger in the expression column.

   Optional: If you want to populate any additional reference data and/or attribute data for each journal, use the Attribute columns to map the columns.

   Attribute columns, Attribute1 to Attrbute10, are reserved for REFERENCE1 TO REFERENCE10. In this case, you need to also add the REFERENCE column as a dimension and map it to the ATTR column in the target application. For example, when you want to populate REFERENCE3, then insert dimension details and give it an appropriate name, assign the type of Attribute, and then assign data column ATTR3. (ATTR11 to ATTR30 are reserved for ATTRIBUTE1 TO ATTRIBUTE20. Attribute1 is stored in ATTR11, Attribute2 is stored in ATTR12 and so on.)

   For more information, see Mapping Dimensions.

9. From Map Members page, map any members from the source to target.

   To map all members to the Oracle ERP Cloud "as is" without any modification, select All for the Mapping Type, click Add, and on the Add Map Member page, in Source, enter: *, and in Target, enter: *.

   For more information, see Mapping Members.

10. Click Save and Continue.

11. From the Data Integration home page, and then from the Actions menu, select Period Mapping.

    The period mapping is used to convert periods to Oracle General Ledger accounting calendar periods for the transfer.

12. Select the Application Mapping tab.

13. From Application Mapping page, then Target Application, select the Oracle General Ledger application from the Oracle ERP Cloud to which to write back data.

14. Click to add a separate row for each period that is to receive actual amounts and complete the following.

    Note:

    When specifying the period, the starting and ending periods should be within a single fiscal year. Providing date ranges that cross fiscal year results in duplicate data.

15. Define a Period Key, Target Period Month and Target Period Year.

    • Period Key—Specify the last day of the month to be mapped from the target system.

      Use the date format based on the locale settings for your locale. For example, in the United States, enter: the date using the MM/DD/YY format.

    • Target Period Month—The values in this field need to match the accounting calendar for the ledger in the Oracle General Ledger, which receives the transferred amounts.

    • Target Period Year—Use values that corresponds to the accounting period (as defined in the Target Period Month column).

    When you select a value, information about the period key, prior period key, period name, and the target period month are populated automatically.

16. Click Save.

17. Run the integration.

    For more information, see Running an Integration.