Process Description

At a high level, these are the steps you complete in Data Integration to prepare to load budget revisions from EPM Planning Financials to Budgetary Control:

  1. Complete the setup integration steps between Planning and Planning Budget Revisions and Budgetary Control.

    For more information, see https://docs.oracle.com/en/cloud/saas/planning-budgeting-cloud/epbca/fin_budget_adjustment_setup_102x2f7be273.html.

  2. Register your application with OEP_FS as an input cube.

    This step enables you to register the Planning Budget Revision application, which stores the preparations or revisions made to the budget and then is loaded to Budgetary Control. This application name is appended with a "BAR" in the name, for example, "PRCVisionCityControlB_BAR"

  3. Register Budgetary Control as a data source, specify the connection to use, and then import the Budgetary Control balance Essbase cubes into Data Integration.

    The Import Applications button brings over Budgetary Control balance Essbase cubes into Data Integration as Budgetary Control target applications. A control budget dimension member within each Budgetary Control target application represents a control budget in Budgetary Control used to load and write back data from and to the Oracle Enterprise Performance Management Cloud.

    See Registering Budgetary Control as a Data Source and Importing Applications.

  4. Register the budget adjustment revision by selecting Data Export category, then select the Budget Adjustment Revision type and then select the Budgetary Control Essbase cube for the application.

    This type of application is appended with a "BAR" in the application name, for example, "PRCVisionCityControlB_BAR."

    See Registering a Budget Adjustment Request.

  5. Register the Planning Budget Revision as a data source, which stores the preparations or revisions made to the budget and then is loaded to Budgetary Control.

    See Registering the Planning Budget Revision.

  6. Optional: If you migrate an application using Migration from another environment, then you must import the Control Budget information from the source. In this case, select the Budgetary Control Essbase application and select Refresh Member option from the action menu.

  7. On the General page, create the integration between the Planning Budget Revision source application and the Budget Adjustment Request.

    See Integrating the Planning Budget Revision and Budget Adjustment Request.

  8. On the Map Dimensions page, create an import format by mapping the dimensions from the Planning Budget Revision source to the Budget Adjustment Request.

    In this step you map the Planning Budget Revision dimensions to the Budget Adjustment Request dimensions.

    See Mapping the Planning Budget Revision and the Budget Adjustment Request Dimensions.

  9. Optional: Map additional attribute columns to which you can import values from the selected EPM Planning Financials source.

    For more information, see Mapping Custom Budget Revision Attributes.

  10. On the Options page, select the period mapping.

    Period mappings define the mapping between EPM Planning Financials and Budgetary Control. You can define period mappings in two ways:

    • Default Period Processing

    • Explicit Period Processing

    Select default period processing when EPM Planning Financials and Budgetary Control use consistent period definitions and period naming. For example, when a monthly calendar is used in both systems and the names of the periods like Jan-20 match both systems, then you use the Period Mapping Type of Default in the integration. No additional mapping is required.

    Use explicit period processing when EPM Planning Financials and Budgetary Control period definition or period naming conventions are different. In this case, you are required to select a calendar that is associated with an explicit source period mapping.

    See Defining Budget Adjustment Options.

Note the following about the EPM Planning Financials Budget Revisions to Budgetary Control integration:

  • You cannot use Member Mapping for the EPM Planning Financials to Budgetary Control. You can only use an import expression to add a prefix or assign constant values for extra dimensions.

  • You cannot execute the EPM Planning Financials to Budgetary Control integration from the Run Integration page in Data Integration. The run integration step is invoked only from EPM Planning Financials when performing a Funds Check or Funds Reservation action.

  • You cannot view the results of the EPM Planning Financials to Budgetary Control integration in the Workbench.