Writing Back Budgets to the Oracle ERP Cloud

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 Planning in the Oracle Enterprise Performance Management Cloud to Oracle General Ledger.

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

The write back to Oracle General Ledger is also automatically performed for you when you write back budget to Budgetary Control. for EPM type control budget, but obviously only for the portion of your enterprise-wide budget that you writes back to Budgetary Control.

For more information, see Using Financials for the Public Sector

To write back to the Oracle General Ledger:

1. Create an import format to map dimensions to the Oracle General Ledger:

   1. On the Setup tab, under Integration Setup, select Import Format.

   2. Click Add.

   3. In Name, enter the name of the import format.

   4. In Source, select the name of the EPM Cloud application from the drop-down.

   5. In Description, enter a description that can be used to identify the import format.

   6. In Drill URL leave blank.

   7. In Target drop-down, select the Oracle General Ledger application.

   8. In Target drop-down, select the EPM application.

   9. Click Save to save the import format and see the lower portion populated.

   10. Scroll down to the lower region of the Import Format screen to map EPM Cloud dimensions to the general ledger dimensions.

   11. 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.

   12. Click Target Options, select Budget Name.

   13. In Expression, leave blank.

       If the target is the budget name, enter the value of the accounting scenario that you plan to use.

2. Create a location.

   The location is used to execute the transfer of budget amounts to the Oracle General Ledger. The import format is assigned to the location. If you are using multiple import formats, you also need to define multiple locations.

   1. On the Setup tab, under Integration Setup, select Location.

   2. Click Add.

   3. In Name, enter a name for the location.

      The location name is displayed when you initiate the transfer from the EPM Cloud to the Oracle General Ledger.

      The location name is displayed when you initiate the transfer from the EPM application to the Oracle General Ledger.

   4. In Import Format, select the name of the import format you to use during the transfer.

      Note:

      The Source and Target field names are populated automatically based on the import format.
   5. In Parent Location, enter the parent assigned to the location.

      Parent mappings are used to share mappings with other locations. Enter mappings at the parent location, and the related locations can use the same mappings. Multiple locations can share a parent. This feature is useful when multiple locations use one chart of accounts. Changes to a child or parent mapping table apply to all child and parent locations.

   6. In Source, the source is populated automatically.

   7. In Functional Currency, specify the currency of the location.

   8. Optional: In Logic Account Group, specify the logic account group to assign to the location.
   9. Optional: In Check Entity Group, specify the check entity group to assign to the location.
   10. Optional: In Check Rule Group, specify the check rule group to assign to the location.

   11. Save the location.

   See Defining Locations.

3. Create period mappings.

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

   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.

   1. On the Setup tab, under Integration Setup, select Period Mapping.

   2. Click Add and add a separate row for each period that is to receive budget amounts.

      Use the period names from the accounting calendar used by the ledger in the general ledger.

   3. Define a Period Key.

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

      • 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).

      See Defining Period Mappings.

4. Define the data load rule.

   A data load rule is used to submit the process to transfer balances from the EPM Cloud application to the Oracle General Ledger. The data load rule is created once but used each time there is a transfer.

   1. On the Workflow tab, under Data Load, select Data Load Rule.

   2. From the POV Bar, select the location to use for the data load rule.

      Data load rules are processed within the context of a point of view. The default point of view is selected automatically. The information for the point of view is shown in the POV bar at the bottom of the screen.

   3. Click Add.

   4. In Name, enter the name of the data load rule.

   5. In Category, leave the default category value.

   6. In Description, enter a description to identify the data load rule when you launch the request to transfer general ledger balances.

   7. In Target Plan Type, select a plan type.

   8. In Period Mapping Type, select the period mapping type for each data rule.

      Valid options:

      • Default—The Data Rule uses the Period Key and Prior Period Key defined in Data Management to determine the Source General Ledger Periods mapped to each Data Management period included in a Data Rule execution.

      • Explicit—The Data Rule uses the Explicit period mappings defined in Data Management to determine the source GL Periods mapped to each Data Management Period included in a Data Rule execution. Explicit period mappings enable support of additional GL data sources where periods are not defined by start and end dates.

   9. Click Save.
5. Add Source Option filters to the data load rule for write-back.

   1. On the Workflow tab, under Data Load, select Data Load Rule.

   2. From the POV Bar, select the location to use for the data load rule.

      Data load rules are processed within the context of a point of view. The default point of view is selected automatically. The information for the point of view is shown in the POV bar at the bottom of the screen.

   3. Select the data load rule to which to add a filter.

   4. Select the Source Options tab.

   5. In the Source Filters area, click .

   6. Select the Dimension Name.

   7. In Filter Condition specify the filter condition:

      • Enter a member name or filter condition in the Filter Condition text box.

      • Click to display the Member Select screen and use a member selector to specify functions for filtering. Then, click OK.

      To use the member selector:

      1. In the list of available dimensions and members on the left, select a member and click .

      2. To deselect a member from the list of members, click .

      3. To add special options for the member, click and select an option.

         In the member options, "I" indicates inclusive. For example, "IChildren" adds all children for the member, including the selected member, and "IDescendants" adds all the descendants including the selected member. If you select "Children", the selected member is not included and only its children are included.

         The member is moved to the right and displays the option you selected in the Selection Type column. For example, "Descendants" displays in the Selection Type column.

         Tip:

         To clear all members from the list of selections, click .

      4. Click OK twice to continue defining the source filter details.

      The selected member is displayed in Oracle Essbase syntax in the Filter Condition field.

6. Execute the data load rule to write back.

   1. On the Workflow tab, under Data Load, select Data Load Rule.

   2. From the POV Bar, verify the location and period to use for the data load rule.

   3. Select Execute to submit a request to transfer budget amounts to the Oracle General Ledger.

   4. In Import from Source, select to import the budget information from Planning.

   5. In Recalculate, leave blank.

   6. In Export to Target, select to export the information to the Oracle General Ledger.

   7. In Start Period, select the earliest general ledger period to transfer.

      The list of values includes all the general ledger periods that you have defined in the period mapping. This is typically the first period of the year for the initial budget load, and then the current period or a future period during the year if there are updates to the budget that are to be transferred to the Oracle General Ledger.

   8. In End Period, select the latest General Ledger period to transfer.

      The list of values includes all the general ledger periods you have defined in the period mapping.

   9. In Import Mode, select Replace to overwrite existing budget information in Oracle General Ledger for the period range you selected (from the start period and end period options).

      Select Append to add information to existing Oracle General Ledger budget amounts without overwriting existing amounts.

   10. Click Run.