We can put Integrations inside a package using below two methods:
Select a pattern
Here we will see how to do package migration from one instance to another instance.
To migrate mutiple integrations in a package, the integrations must be defined inside a package name. If we forget to put package name while creating the integration then we can give the package name after the integration development also.
Check below blog how to add the package name after the development:
oic-add-package-name-for-integration
Steps in detail:
To show it, I have created here two scheduled integrations and put same Package name as test.package.
Package Migration done.
We can migrate Integrations from one OIC instance to another in following two ways:
Command:
aws s3 ls s3://bucket_name/directory_path/ -- recursive | wc - l
aws s3 mv s3://bucket_name/from-director_path/ s3://bucket_name/to_directory_path/ --recursive --exclude "*" --include "filename_pattern*.csv"
This command we are running at aws EC2 to move the aws s3 files from one bucket location to another location.
Use case:
Here we will show you how to group data Name element . In the below, we can see Name value is duplicated that we will take distinguish name values using for each group XSLT element.
We will use for-each-group element on Input and group by Name.
Input:
{"Input":[{
"Name": "Sanddy",
"Title":"Title"
},
{
"Name": "Sanddy",
"Title":"Title"
},
{
"Name": "Sanddy2",
"Title":"Title"
}
}]}
Output:
{"Output":[{
"Greeting": "Hi Sanddy"
},
{
"Greeting": "Hi Sanddy"
}]
}
One sample code:
<xsl:template match="Person">
<xsl:for-each-group select="Student/Info" group-by="@Country">
<Country name="{current-grouping-key()}">
</country>
</xsl:for-each-group>
</xsl:template>
POC with Screenshots:
Usecase: Here, we will see how to get custom fusion accounting hub callback from ERP.
Highlevel steps:
Detailed Steps:
Step1: We have 2 integrations,
Request:
{
"base64FileReference" : "ref",
"sourceFileName": "name",
"archiveDirectory": "",
"importRequestId": "",
"importRequestStatus":"",
"childRequestId":"",
"childRequestStatus":"",
"logDirectory":"",
"logFileName":"",
"deleteBaseDirectory": "",
"directoryAdapter":""
}
Response:
{
"archiveComplete":"Y",
"logComplete": "Y",
"ExceptionCode":"",
"ExceptionReason":"",
"ExceptionDetails":""
}
Implementation steps:
If childRequestId !="" then call ERP cloud adapter to submit create accounting execution report.
Service: ErpIntegrationService
Operation: submitESSjobRequest.
And map the all parameters to run the accounting execution report.
jobPakageName: "/oracle/apps/ess/financials/subledger/Accounting/shared"
jobDefinitionName: "XLAFSNAPRPTRPT"
paramList: childRequestID,D,N,N
Submit a ESS job to create BI bursting callback or control report. Operation: submitESSJobRequest service: ErpIntegrationService
Create a custom report file name: like ReportFileName: concat("Oracle_Control_Report_FAH_",current-date(),hours-from-dateTime(current-dateTime()),".",minutes-from-dateTime(current-dateTime()),".",seconds-from-dateTime(current-dateTime()),".log")
Call a subIntegration like moveCustomReport with below parameters: where we will check ess job completion staus and then download and move the report.https://soalicious.blogspot.com/2022/08/oic-to-erp-improved-custom-callback.html
screenshots:
for submitting create accounting execution report:
ERP BI SQL Query for custom import callback.
https://soalicious.blogspot.com/2022/04/erp-bi-sql-query-for-custom-import.html
The new offering OIC allows very easily to receive or subscribe to the business events raised from the ERP or other Oracle Fusion based cloud services and forward them to others external applications.
There several business events that we can raise from ERP. Below are some of them from the standard list:
Screenshots: Receive events for Purchase order event raised with the ERP.
1. Export 11g OSB code and import in 12c Jdeveloper. Steps to import OSB project in Jdeveloper: File⇾Import⇾Service Bus Resources⇾ Se...
