The Integration blog covers the latest in product updates, best practices, customer stories, and more.

ERP bulk import using ERPImportBulkData event.


File Based Data Integration (FBDI) using ERP Cloud Adapter is one of the widely used features. However, the pre-requisite for enabling this capability - filing a SR against ERP Cloud to get the required certificates could be a daunting one. ERP Cloud Adapter has simplified the FBDI integration significantly by removing this pre-requisite. Please refer to the documentation for the complete description.

This new design is applicable only for all new integrations and user also needs to specify the event URL. If the event URL is not specified then the implementation will fall back to old design.

The existing integrations or the older integrations which are already using bulk import will remain as it is.

These existing integrations will not be based on ERPImportBulkData event.

The details are in the documentation link


With this new design there is no longer need for the pre-requisites for new integrations as mentioned in below link.


However, since this new design is based on ERPImportBulkData event the pre-requisites for events which is CSF key creation is required.

Advantages of the new design

This simplifies setup for OIC customers required to invoke FBDI based jobs through ERP Cloud Adapter, since the pre-requisite is now only CSF creation which is simplified.
Even if the OIC server is busy/down the ERP cloud application tries to send the ERPImportBulkData event for sometime, so as soon as the OIC server is up these events can be picked up for processing.

Pre-requisites for ERP Connection

To use the new design user needs to specify the event URL. If the event URL is not specified then ERP adapter will use the old design.

Design time changes while configuring the bulk import for new integrations


Actions page remains as it is

Operations page remains as it is as seen below screenshot.



Response Page for new integrations

Response page is now changed.When user selects "Enable Callback"

The text fields callback integration identifier and callback integration version are no longer available.

These fields are removed because the callback is now based on ERPImportBulkData event and not on callback URL.


Design time changes for callback

For all new callback integrations there is a design change. The existing/old callback integrations based on callback URL or the "onjobCompletion" payload will remain as it is.

Since the callback is now based on ERPImportBulkData event

User needs to select the specific import job for which to process the ERPImportBulkData event.


1. During bulk import configuration of request, user selects "Enable Callback" however, the callback identifier and callback version fields are not visible.

Solution: This is as per the new design. For all new integrations the bulk import feature is now based on events hence customer need not provide any callback integration information. Once the import job completes, the ERPImportBulkData event will be raised. The callback integration is subscribing to this event by default(User need not select any event while configuring callback integration. It it automatically done in the ERP wizard). The event will be consumed by the callback integration.

2. Where to select ERPImportBulkData event in callback integration.

Solution: While configuring the callback integration user just have to select the option "Receive Callback Message upon completion of FBDI bulk import job submitted via another integration" User then has to select the particular import job for which the callback is to be received. Automatically, this callback integration will subscribe to ERPImportBulkData event.

3. OIC does not receive ERPImportBulkData event.

Solution: Since all new integrations for bulk import are now based on event, there is a pre-requisite of creating a CSF key as mentioned in 


4. Logs for troubleshooting.

Please enable logging in OIC.

Set oracle.soa-=TRACE 1

Also ensure tracing is enabled during activation of the flows.

Please review the OIC logs after reproducing the issue and contact Oracle support if the problem still exists.

5. What happens to the existing integrations based on bulk import

Solution: All the existing bulk import integrations and callback integration will continue to work on the older design. This old design is based on supplying callback integration details which forms the callback URL. The callback integration is invoked and onJobCompletion payload is processed by the callback integration.

6. CASDK-0061:
Received SOAPAction does not match deployed endpoint, configured: http://xmlns.oracle.com/fa/event/onEvent , received --> "onJobCompletion" - make sure you set the SOAP Action in your SOAP client.


Here there is a mismatch in the design. The callback integration is based on new design i.e. the event however, user has specified this callback integration in an older/existing bulk import integration based on callback URL

User should not specify new callback integration in older bulk import integration.

Ensure that both bulk import and callback integration are based on only one design either the old based on "onJobCompletion" or the new based on event.