Solution Overview
The technical aspects involved in the integration between Oracle Assets and Oracle Utilities Work and Asset Cloud Service are:
• The integration layer consists of integration processes deployed on Oracle Integration Cloud.
• The integration processes interact with other applications using the following adapters:
• Oracle ERP Cloud Adapter to invoke Asset FBDIs and scheduled processes in Oracle Fusion Cloud ERP/Oracle Assets. This invokes:
• Fixed Asset Mass Additions FBDI
• Prepare Asset Transaction Data scheduled process
• Project Asset and Assignment FBDI
• Fixed Asset Mass Transfer FBDI
• Fixed Asset Mass Adjustment FBDI
• Fixed Asset Mass Retirements FBDI
• FTP adapter to interact with the Oracle Utilities Work and Asset Management FTP server to search, get, and rename the asset extract files.
• REST Adapter to interact with the Oracle Utilities Work and Asset Cloud Service Object Storage to search, get, and rename the asset extract files.
• REST Adapter to invoke ERPFA REST APIs to get the Asset Details and the Schedule Process/job status.
• REST Adapter to receive and send asset records across Oracle Integration Cloud integration flows and also used to invoke the Common Error Handler Oracle Integration Cloud integration flow.
• SOAP Adapter to invoke the ERP Integration Service for Post Mass Additions to Post the Fixed Asset data to Oracle Fusion Cloud ERP.
• SOAP Adapter to invoke the ERP BI Report SOAP service.
• The integration pattern used for the solution is:
• One-way Asynchronous for all flows.
One-way Asynchronous
The one-way asynchronous integration process:
1. Receives request message from the source application.
2. Transforms message from the source to the target format. Lookups are used for data translations.
3. Invokes target application to send the request message.
4. In case of any error, the global fault handler catches them.
5. The error instance can be re-submitted from Oracle Integration Cloud. Refer to the Error Handling section in Configuring Lookups, Error Handling, and Email Notifications for more details.
6. The email notification is optional in most cases. Configure the notification.error.flag property name in the OUTL-BRT-WACS_ERPFA_CONFIGPROPS lookup to ‘true’ and notification.type.email property to ‘email’ to receive email notification when errors are encountered.
7. The recipient(s) of the email notification is/are configured in the OUTL-BRT- WACS_ERPFA_EMAIL_ID lookup.
Refer to the Integration Flows section for more information about each integration process.