Bulk Import Troubleshooting Issues

Callback Integration Is Not Triggered on Failure of the Child ESS Job "Load Interface File for Import"

When the child ESS job "Load Interface File for Import" fails, the Oracle Integration callback integration is not triggered. There is no current workaround for this issue. This is a known limitation with the Oracle ERP Cloud application.

How to Pass an Interface Request ID to an Import Job in a Bulk Import Process

To add a request ID ({req_id}) as a parameter in the manifest file/properties file, pass the request ID in a parameter list as {req_id}. This dynamically retrieves the load request ID in Oracle ERP Cloud and enables the import process to continue.

Bulk Data Import Implementation Recommendations

If you want to use the bulk data import feature with Oracle ERP Cloud, it is recommended that you select the Import Bulk Data into Oracle ERP Cloud option on the Actions page of the Adapter Endpoint Configuration Wizard, and not use the web service APIs.

However, if you instead directly use the ERPIntegrationService web service (and importBulkData operation) for bulk data imports, ensure that the properties for the jobOptions parameter are set to values. For example:

<jobOptions>ExtractFileType=ALL,InterfaceDetails=TO_DETERMINE<jobOptions>

The jobOptions parameter is required for all FBDI imports and is required to receive callbacks.

Note that if you select the Import Bulk Data into Oracle ERP Cloud option on the Actions page of the Adapter Endpoint Configuration Wizard, this task is not required.

Create a Job Property File for the importBulkData Operation

You can generate the job property file for each job to further simplify the request payload of the importBulkData operation.

See the following documentation for details:

See Using External Data Integration Services for Oracle ERP Cloud of External Data Integration Services for Oracle Cloud: Overview.
1. Scroll to the bottom and see the Oracle Support Services link under Related Topics: Using External Data Integration Services for Oracle ERP Cloud.
2. Scroll to the Attachments section at the bottom of the link and see Appendix 12: Creating a Job Property File for the importBulkData Operation in the Using External Data Integration Services guide appropriate to your Oracle Fusion Applications release.
See Oracle Integration and ERP Cloud - How to get Job Name and Parameters of ERP Bulk Import Jobs.

Error Response Received When Invoking a Bulk Import with the Oracle ERP Integration WSDL

If you receive an error when trying to perform a bulk import using the importBulkData operation of the ERP Integration Service WSDL, ensure that you are correctly using the Oracle ERP Cloud Adapter to perform this task.

See Invoke a File-Based Data Import (FBDI) Job.

Import Bulk Data into ERP Cloud Application Option Must Be Reselected in an Imported Integration

If you import an integration using the bulk data import feature into another instance, the Import Bulk Data into ERP Cloud Application option on the Actions page of the Adapter Endpoint Configuration Wizard is not selected. Instead, the initial option on this page is selected. You must open the Adapter Endpoint Configuration Wizard in edit mode, reselect the Import Bulk Data into ERP Cloud Application option, save your changes, and activate the integration. If you later re-import this integration into another instance, the Import Bulk Data into ERP Cloud Application option is correctly selected. This issue only occurs with the initial import.

Jobs Not Appearing in the Import Jobs List on the Operations Page

If you selected Import Bulk Data into ERP Cloud Application on the Actions page, you can specify the import job to import on the Operations page of the Adapter Endpoint Configuration Wizard. If the job does not appear in the Import Job Name list, the causes may be as follows:

Only File-Based Data Imports (FBDI)-compliant jobs are visible. FBDI jobs are described in File-Based Data Imports of File-Based Data Import (FBDI) for Financials.
Your user account may not have the correct roles. See Assign Required Roles to an Integration User.

See Import Bulk Data into ERP Cloud Application.

Receive a Callback from an ExportBulkData Operation

To receive a callback from an ExportBulkData operation, you can also configure events in the callback integration. An event is a good alternative if there are issues when using the ExportBulkData callback operation in the callback integration. Both methods are supported.

Configure the Callback for the ExportBulkData Operation

ExportBulkData operation behavior is different from ImportBulkData operation behavior. The approach used with ImportBulkData to configure a callback integration does not work with ExportBulkData.

To consume the callback received from ExportBulkData, you must configure the integration as follows:

Create an integration with an event as a trigger.
Subscribe to an Oracle ERP Cloud integration outbound event with the Oracle ERP Adapter. Do not add any filter; use the default.

Parse the payload to get the document ID.

{
 "JOBS": [
  {
   "JOBNAME": "TEST PO Extract Extract Job",
   "JOBPATH": "/oracle/apps/ess/custom/int",
   "REQUESTID": "9519",
   "STATUS": "SUCCEEDED",
   "DOCUMENTNAME": "ExportBulkData_TESTPOEXTACT_9519"

  },
  {
   "JOBNAME": "Upload Interface Error and Job Output File to Universal Content Management",
   "JOBPATH": "/oracle/apps/ess/financials/commonModules/shared/common/interfaceLoader",
   "REQUESTID": "9520",
   "STATUS": "SUCCEEDED",
   "DOCUMENTNAME": "ExportBulkData_TESTPOEXTACT_9519"
  }
 ],
 "SUMMARYSTATUS": "SUCCEEDED",
 "DOCUMENTID": "10174",
 "DOCUMENTNAME": "ExportBulkData_TESTPOEXTACT_9519"
}

Use the SOAP Adapter to download the file from Universal Content Manager (UCM) using the above document ID.
Continue using the SOAP Adapter because it supports attachments.
In the integration that invokes the ExportBulkData operation, open the mapper.
Add EnableEvent=Y in the jobOptions element of the exportBulkData operation.

Oracle ERP Cloud Callback About the Bulk Import Issue

If Oracle Integration does not receive an Oracle ERP Cloud callback about the bulk import, it is likely due to an incomplete prerequisite to using the adapter.

See Upload Files in Bulk and Insert Data into Oracle ERP Cloud Application Tables for New Integrations.