Thursday, November 17, 2016

Automate File Based Data Import using ErpIntegrationService

A lot of customers are past the point of adapting Oracle Cloud Applications and are moving to the next step of the lifecycle, being integrating Oracle Cloud Applications within their enterprise architecture. Oracle is currently providing a plethora of CRUD web services, REST and SOAP for integration.
But in some cases the only ability to interface data is still through File Based Data Imports (FBDI).

Using FBDI you generate an input file for import using predelivered Excel sheets by Oracle. These input files need to be uploaded to UCM. After which you start the Load Interface File for Import process to load the data into staging tables. After this you start the appropriate import process to load the data into the actual transaction tables. These are all manual steps.

With the ErpIntegrationService service you can now automate the process of
  • uploading the input file to UCM
  • initiate the Load Interface File for Import process 
  • initiate the import process

Where to start the full automation?
In order to automate this process from any backend system or middleware, you first need to extract the data and mimic the format that FBDI generates and in some cases zip the extract file.

Suppose we want to automate the import of Suppliers.
The FBDI template looks like this:

And generates following csv file:

In order to upload the extract (input file) to Oracle Cloud using the ErpIntegrationService you need to base64 encode the zip file that contains the csv input file.

Before you can invoke the importBulkData operation, you need to lookup the import process Path, Jobname and Parameters. These can be found via task Manage Custom Enterprise Scheduler Jobs for [module]. It is also a good practice to run the import process manually to see the actual parameter values.

Using follow request you can now initiate the

<soapenv:Envelope xmlns:soapenv="" xmlns:typ="" xmlns:erp="">


<env:Envelope xmlns:env="" xmlns:wsa="">
      <ns0:importBulkDataResponse xmlns:ns0="">
         <result xmlns="">1124309</result>


Initiated processes

Imported Supplier

A few pointers
The element notificationcode can have the following values:

First digit 0 No notification
1 Email
2 Bell
3 Email & Bell
Second digit 0 Send in any case
1 Send on success
2 Send on error

The element callbackURL can be used to provide a (local) endpoint to a web service that will be invoked upon completion of the load and import sequence. 
For more details on the implementation of this callback web service, please see the blog post of Jack Desai

No comments:

Post a Comment