Integration Process Description

At a high level, this is how you integrate Oracle General Ledger data from the Oracle ERP Cloud with your Oracle Fusion Cloud Enterprise Performance Management application:

  1. In Data Integration, configure the Oracle ERP Cloud connection information, and then register the Oracle ERP Cloud as a data source.

    For more information, see Configuring a Source Connection.

  2. Register the Cloud EPM application that requires the data from the Oracle ERP Cloud (GL Balances).

    For more information, see Registering Cloud EPM Applications.

  3. Register the Oracle General Ledger application in the Oracle ERP Cloud from which to load data to one or more Cloud EPM applications and import the Oracle General Ledger application.

    The import application process brings over the Oracle General Ledger data into the Cloud EPM system as Oracle Essbase cubes. Each Essbase application represents a chart of accounts definition from the source Oracle ERP Cloud.

    For more information, see Registering Oracle Cloud ERP Applications.

  4. Create the integration between the source application and the target Cloud EPM application.

    For more information, see Creating an Integration with the Oracle ERP Cloud (GL Balances).

  5. Map the dimensions between the Cloud EPM application and the dimensions in the segments in the Oracle General Ledger segments.

    For more information, see Mapping Dimensions.

  6. Map members to convert the chart of accounts values from the Oracle General Ledger to dimension members in the Cloud EPM during the transfer.

    For more information, see Mapping Members.

  7. On the Options page, select any filters and application options.

    A default filter is provided that includes all dimensions of the Essbase cube. The cube may have duplicate members so fully qualified member names are required. The Essbase cubes work off the Oracle General Ledger segments, and there is a one-to-many relationships of Chart of Accounts to ledgers in the Oracle General Ledger.

    Data Integration creates filters when an integration is created. You can modify the filters as needed but cannot delete them. (If the filters are deleted, Data Integration recreates the default values). For information about these filters, see Defining Oracle General Ledger Filters.

  8. Optional: Define adjustment periods from the source Oracle General Ledger when loading balances to a Cloud EPM application.

  9. Run the integration job using any filters.

    This process extracts and loads data from the Oracle General Ledger to the Cloud EPM.

  10. Optional: Write back Cloud EPM data to the Oracle General Ledger in the Oracle ERP Cloud.

    To write back data to the Oracle General Ledger from a Cloud EPM source system, set up and run the integration. In this case, the filters are applied against the Cloud EPM application.

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