OIC Outbound Best-Practices & Guidelines
Updated: Mar 3
In this blog post, I will delineate optimal strategies and recommendations for outbound integrations.
When dealing with data exceeding 10 MB, attempting to execute the Run Report Action utilizing the XMLP webservice may result in failure due to size constraints. Consequently, it is imperative to implement the following technique:. Here is a high-level overview of the approach to automating data extractions in Oracle ERP Cloud using Oracle Integration Cloud (OIC).
Flow 1 :
1. Create a custom ESS Job for a specific report.
2. Invoke ERP Integration Service ->Export Bulk Data Operation and Submit the ESS Job using Export Bulk Data Operation
Flow 2:
3. Listen to Callback Event/message and Capture the document Id
4. Use Document Id and Download the file from UCM using SOAP adapter, which has MTOM
feature to accept attachments in response of 1GB.
The callback flow, denoted as flow2, will be tailored to a specific component or object. In the context of callback integration, when selecting ERP integration outbound events, we will establish a filter condition to exclusively handle the processing of the designated object extract, exemplified as follows:
The below XPath Expression will Process the output of ESS Job "payables Transactions Extract"
<xpathExpr xmlns:ns0="http://xmlns.oracle.com/apps/financials/commonModules/shared">$inputVariable/ns_0.JOBS/ns_0.JOBNAME='Payables Transactions Extract'</xpathExpr>
High-Level-Flow Diagram.
·
Outbound Extract of data Within 10mb/Transactional Data for validation using BIP report:
Directly Call BIP report using XMLP webservice and operation as RUN REPORT.
I hope this helps. Happy learning.
