1. Administering Data Integration for Oracle Enterprise Performance Management Cloud
  2. Frequently Asked Questions (FAQ) about Data Integration

E Frequently Asked Questions (FAQ) about Data Integration

This FAQ provides links to resources for frequently asked questions about administrative tasks in Data Integration.

Frequently Asked Questions

Note:

For a range of Frequently Asked Questions (FAQs) along with their answers, covering various topics related to Oracle Enterprise Performance Management Cloud, as found in multiple EPM Cloud documentation resources, see: Frequently Asked Questions in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators

What to do if the EPM Integration Agent fails to start with a 401 Unauthorized error?

The CLOUD_DOMAIN parameter is required except for any of the Gen 2 data centers. When using the EPM Integration Agent with Gen 2 data centers, this error can be resolved by removing the domain in the CLOUD_DOMAIN field. For other domains, the CLOUD_DOMAIN parameter must be specified in the agentparams.ini file. For details, see Configuring the EPM Integration Agent Startup Parameters.

What to do if the EPM Integration Agent does not extract data?

In some cases, this may be caused by entering the JDBC URL incorrectly. Ensure that the URL is entered in the format described in Extracting Data from On-premises Data Sources.

EPM Integration Agent - Teradata DB - ERROR [AIF]: Unexpected Error In ImportData: EPM Agent Failed To Extract Data

When trying to import data using the EPM Integration Agent connected to a Teradata database, the EPM Integration Agent fails to extract data. The error occurred due to an incorrect JDBC URL syntax.

Use the following JDBC URL for a Teradata Database: jdbc:teradata://database=<DB_Name>. Then update this line in the agentparams.ini file: CUSTOM_CLASS_PATH=C:\Oracle\EPMAgent\lib\*

For details, see Configuring the EPM Integration Agent Startup Parameters.

How to Resolve a Fetch of Driver Member Failure Error when Exporting Data to Financial Consolidation and Close?

This error may occur when the member is not valid or has no mapping. To resolve this error, define a valid member name, then define the data load mapping in the data file.

Fusion ERP GL Data Load Fails with Error: "Client Commands are Currently Not Being Accepted"

During a data load from the Fusion ERP General Ledger, the load fails with following errors:

INFO [AIF]: isHarnessTest():: harness flag enable ? false
INFO [AIF]: getOlapserver() :: = fa.oracleoutsourcing.com:11448
INFO [AIF]: ExtractBalanceData:Error::Cannot open cube view. Essbase Error(1051544): message on contacting or from application:
INFO [AIF]: [Wed Mar 9 02:02:53 2022]Local////140107914331904/Error(1013204)
INFO [AIF]: Client Commands are Currently Not Being Accepted

or

INFO [AIF]: ExtractBalanceData:Error::Cannot perform cube view operation. Essbase Error(1024015): Request [MdxReport] from user [FUSION_APPS_GL_ESSBASE_APPID] was terminated by an admin user

This error occurred because a Publish Hierarchy job was scheduled to run at the same time. Publish Hierarchy locks the cube for update. This causes the issue with the balance extract ESS job.

To fix this error, change the process timings to ensure that data load from the Fusion GL to EPM Cloud and the Fusion the Publish Hierarchy job do not overlap.

How to address source initialization errors when integrating with Oracle General Ledger in Data Management?

When integrating applications such as Oracle General Ledger created in the Oracle ERP Cloud with an EPM Cloud application, you first create and register the source system specifying the application type: Oracle ERP Cloud. For details, see Registering Oracle ERP Cloud Source Systems in Administering Data Management for Oracle Enterprise Performance Management Cloud

Find additional helpful information in Administering Data Integration for Oracle Enterprise Performance Management Cloud:

When attempting to initialize the Fusion GL Application as a Source System in Data Management, it fails with an error.

The required "Integration User" privileges in the Oracle ERP Cloud used for the Oracle General Ledger and EPM Cloud integration are missing.

The roles required in Oracle ERP Cloud for the "Integration User" used for the GL to EPM Cloud are the following:

  • GL_RUN_TRIAL_BALANCE_REPORT_PRIV – To Import Data from GL to EPM
  • GL_ENTER_BUDGET_AMOUNTS_FOR_FINANCIAL_REPORTING_PRIV – To Write-back data from EPM to GL
  • FUN_FSCM_REST_SERVICE_ACCESS_INTEGRATION_PRIV – Privilege to execute REST API used to perform the integration

Note:

If you are using a custom role or one of the roles not listed below, then you must add the FUN_FSCM_REST_SERVICE_ACCESS_INTEGRATION_PRIV to the role for the integration to work.

If you are using one of the following pre-defined roles for the "Integration User," then no further action is required.

  • For Import Data

  • General Accountant

  • Journal Management

  • Period Close Management

  • For Import and Write-back Data

  • General Accountant

  • Financial Analyst

For more information, see Security Role Requirements for Oracle ERP Cloud Integrations.

Data Management Load Issue Error "ERROR [AIF]: Server returned HTTP response code: 401"

Exporting actual data from Financial Consolidation and Close to EPBCS is failing.

This error occurs when Data Management or Data Integration is unable to consider changes in the target application.

To fix this issue, refresh members in the target application. To do this, in Data Integration, go to Applications, select the target application, then click Image shows Select icon. to the right of the application, and then select Refresh Members. Then perform the load again.

For more information, see Refreshing Members.

In Data Management, An ERROR_INVALID_PERIOD Error Is Thrown When Executing The Data Load Rule

When pulling data from the Financials General Ledger into Data Management, the "Transformation" step fails with the following error: ERROR_INVALID_PERIOD.............. Invalid period specified in the file. This error occurs even though the periods were mapped correctly and data was successfully loaded into the previous period.

The step failed because the Period was not open on the Financials side from which they were extracting data.

To fix this issue:

  1. Log into the Financials General Ledger/data source.

  2. Open the period, for example, as shown below:

    Image show Edit Accounting Period Statuses page

  3. Execute the data load rule again in Data Management.