1. Administering Data Integration for Oracle Enterprise Performance Management Cloud
  2. Integrating Data
  3. Integrating Oracle ERP Cloud Data
  4. Registering a BI Publisher Report as an Oracle Enterprise Scheduler (ESS) Job
  5. Creating the Integration Definition Between EPM Cloud and the BI Publisher Report Extract

Creating the Integration Definition Between EPM Cloud and the BI Publisher Report Extract

After you built the Oracle Business Intelligence Publisher report and registered it as an ESS job, you define the integration definition between Oracle Enterprise Performance Management Cloud and the BI Publisher report extract.

To create the integration definition:

  1. In BI Publisher, run the BI Publisher report extract, and export it in CSV file format locally to your file system if registering for the first time.

    Image shows the BI Publisher report to be exported.

    You may want to rename the downloaded CSV output file as <Appname>.csv where <Appname> is the name of the intended application for the data source application in Data Integration, which represents the BI Publisher report.

    The the CSV file needs to be copied (uploaded) to the Data Integration inbox folder. For information about uploading files, see Using the File Browser.

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

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

  4. From Category, select Data Source.

  5. From Type, select Oracle ERP Cloud (Custom).

  6. From File, specify the name of BI Publisher report extract CSV file or click Image shows Browse icon and navigate to the folder where you saved the BI Publisher report extract CSV file, select it and then click OK.

  7. In Prefix, specify a prefix to make the application name unique.

    The prefix is concatenated with the application name to form a unique application name. For example, if you want to name an application with the same name as an existing one, you can assign your initials as the prefix.

  8. Click OK.

  9. Click Save.

    Image shows the Create Application page.

    When the application is registered, the system returns the message: "Application registered successfully" and the application is available on the Application page as shown below:

    Image shows the Application page.

    Data Integration registers the application and returns all the columns in Dimension Details.

  10. On the Application page, click Image shows the Select icon. next to data source application and then select Application Details.

  11. On the Application Details page, click the Options tab.

  12. Complete the following fields and click Save.

    1. Connection Name—Specify the source system name.

    2. Execution Method—Specify the method for executing the job.

      Valid options:

      • BIP Report—Executes the BI Publisher report in synchronous mode, which has a timeout limit of about 5 minutes within the Oracle ERP Cloud instance. This method is suitable for smaller data sets or for queries that execute quickly.

      • ESS Job—Executes the BI Publisher report in asynchronous mode, without encountering execution time restrictions.

        Note:

        If you encounter a timeout in Data Integration when using the ESS feature for a BI Publisher report, increase the batch timeout in Data Management. To do this, specify the maximum time a job can run in the Timeout field of the batch definition. For more information, see Working with Batch Definitions in Administering Data Management for Oracle Enterprise Performance Management Cloud.

    3. Report Name—Enter the name of the report and the complete report path when the execution method is BIP Report. For example, enter /Custom/MyReport.xdo. Leave this field when the execution method is ESS Job.

    4. ESS Job Path—Enter the path to the folder that contains the ESS job definition. The path begins with /oracle/apps/ess/custom/ for custom ESS jobs.

    5. ESS Job Name—Enter the ESS job name.

    6. Report Parameter List—Specify the report parameters of the custom query.

      Make sure you specify a random string such as "ABC" in Report Parameter List that will be passed to the bind parameter you created in the report definition. If you create a report with a query that doesn’t have bind parameters passed from the EPM Cloud, the process fails on the Oracle ERP Cloud side.

      If you need to identify report parameters, complete the following:

      1. Navigate to Oracle ERP Cloud, and from the Overview page, select the report and click Resubmit.

        Image shows resubmitting the report from the Overview page.

        A list of report parameters is generated.

        Image shows the list of parameters.

      2. Copy the report parameters shown in the Warnings window.

      3. Navigate to Data Integration and paste the report parameter list from the Warnings window into the Report Parameter List field of your custom query.

        Make sure you specify a random string such as "ABC" in the "Report Parameter List" that will be passed to the bind parameter you created in the report definition. If you create a report with a query that doesn’t have bind parameters passed from the EPM Cloud, the process will fail on the EPM Cloud side.

    Image shows Application Details page.

  13. Create a new integration and select the data source application as the source and the target application. Then create the remaining steps to create the integration.

    Image shows the Create Integration page.

    1. Set up the integration mapping between the Oracle ERP Cloud data source and the target application by building an import format, location, and dimension mappings.

      See Mapping Dimensions.

    2. Map members from the source to target.

      See Mapping Members.

    3. Select any source and target options.

      See Setting Data Integration Options.

    4. Run the integration.

      See Running an Integration.