Registering Oracle ERP Cloud General Ledger Applications

When integrating Oracle General Ledger data from the Oracle ERP Cloud with your Oracle Fusion Cloud Enterprise Performance Management application, you use Applications to specify the Oracle ERP Cloud General Ledger applications as a data source application type and then import the applications so that they can be used as sources in the Cloud EPM target applications. When you import the applications, the system brings over the source Oracle ERP Cloud General Ledger data into the Cloud EPM system as Oracle Essbase cubes. Each Essbase application represents a Ledger definition from the source Oracle ERP Cloud General Ledger.

Note:

Data Integration does not allow you to register a Oracle ERP Cloud application which has the same name as a Cloud EPM application. To avoid any issues, rename the Cloud EPM.

To define an Oracle ERP Cloud application as data sources:

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

  2. On the Applications page, click Image shows the Add icon. (Add icon).

  3. From Category, select Data Source.

  4. From Type, select Oracle ERP Cloud.

  5. From Connection, select Fusion.

  6. In Application Filter, specify any filters for the load.

    Application filter is used to filter the name of application to import from the Oracle ERP Cloud. For example, you can filter on a specific application name such as Vision USA or wild card Vision%.

  7. Click Import Applications to register the application and initialize the Oracle ERP Cloud application.

    Note:

    In some cases, customers may have multiple instances of their Fusion ERP, for example, one for test, and one for production. When setting up an integration to these sources, if the ledgers are named the same, and are identical in both sources, only a single connection can be used.

    For example, when customers set up an integration to the test instance with ledgers named Ledger1 and Ledger2, and now need to pull data from the production instance with Ledger1 and Ledger2, they can just change the connection information for the connection and the integration will use those connection details with the selected integration. Adding a new connection will not be referenced when running the integration – only the original connection, but with the updated connection information.