Oracle Integration Cloud: make integration easier?

Oracle Integration Cloud

Oracle Integration Cloud has made Integration to SaaS and other systems easy by delivering various prebuild adapters for variety of sources and targets. Some of the most common adapters integrating with SaaS are ERP Adapter, HCM Adapter, FTP Adapter for your file interactions, On-Prem adapter and the list goes on.

Where adapters excel is exposing the services provided by various systems.

As the Integration Architect/Developer there is no need to understand all the technical details of the various systems.

A standard inbound pattern for Oracle ERP/HCM in OIC:

  1. Source systems supply data in agreed format.
  2. Convert the source data to FBDI format.
  3. Load and Import data into Oracle Cloud ERP/HCM
  4. Reporting and Error handling

Creating a FBDI or HDL is not always straightforward and this is where OIC Integrations becomes complex with iterations and various complex mappings and calculations to be done. You need to use XSLT, conditional mappings and various other bits for achieving the simplest of the transformations. By standard Oracle recommends the usage of creating the FBDI & HDL files at source or using an extra layer like ODI. In many cases there are costs associated with changing data at source and also lack of knowledge of the Oracle system. This is where DBaaS comes into picture sitting close to OIC, an adapter away and can take away the complexity.

I don’t need to argue the benefits of using plsql which all Oracle developers are well acquainted with, for doing the transformations. The ATP/ADW/DB adapters expose the DB into OIC, provide the capabilities to table operations like select/insert/update and invoking a procedure. Once the data is transformed in the DB this can plugged back into the Step 3 for loading and importing into Oracle ERP/HCM. Here are high level steps of OIC plus DBaaS Inbound Integration Pattern for Payables Invoices where headers and lines FBDI files need to be created from source.

High Level Steps for Main Integration

  1. Read the file from FTP location
  2. Perform trailers and other checks
  3. Insert data into ATP/ADW
  4. Invoke Create FBDI Child Integration
  5. Invoke Reporting Child Integration
Non è stato fornito nessun testo alternativo per questa immagine
Non è stato fornito nessun testo alternativo per questa immagine

Create FDBI child Integration looks like this.

High level steps

  1. Create FBDI using invoke procedure function of adapter
  2. Write the header and line files in staging
  3. Zip and Invoke Bullk Import via ERP Adapter
Non è stato fornito nessun testo alternativo per questa immagine

Reporting Child Integration is another local Integration which is invoking the BI Webservice and reading the data to build in the summary/status emails.

High level steps

  1. Verify the Bulk Import Status
  2. Invoke BI services to fetch the interface processing reports
  3. Email the report building in the necessary formats (Ex- html)

The use of local Integrations is another powerful feature which allows building reusable modular integrations.

Modularization is a key and powerful process in any technology.

This keeps the Integrations simple and easy to understand and debug incase of issues. And the beauty is, we are using Integrations are like another service or API which we call part of the solution.

In RTT, we use Oracle Integration Cloud also for integrate your ERP with e-commerce. Do you want to know more? Watch the webinar!

Duilio Paliferro, Solution System Integrator & Business Unit Manager

Puoi leggere anche Scegli l’Application Maintenance di RTT per partire tranquillo!