Solution Overview

The technical aspects involved in the integration between Oracle Supply Chain Management 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 subscribe to business events raised by various modules in Oracle Supply Chain Management. This integration subscribes to the Item Publication, Item Create, and Item Update Events.

• REST Adapter to invoke ERP SCM UnitOfMeasureConversions REST API to get the UOM Conversion for the Item’s PI Ratio.

• REST Adapter to receive and send item and storeroom records across Oracle Integration Cloud integration flows and used to invoke the Common Error Handler Oracle Integration Cloud integration flow.

• SOAP Adapter to interact with Oracle UCM Generic Web Service to get files in Oracle UCM.

• SOAP Adapter to invoke the ERP BI Report SOAP service, to fetch the item quantity and price.

• Oracle Utilities adapter to invoke WACS REST APIs, to synchronize storerooms and stock item details.

• Oracle Utilities Adapter to invoke WACS Health check SOAP service.

• The integration pattern used for the solution is:

• One-way Asynchronous

• Two-way Asynchronous

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_ERPSCM_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_ERPSCM_Email_ID lookup.

Two-way Asynchronous

The two-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 the target application to send the request message.

4. Transforms the success or error response message.

5. In case of any error, the global fault handler catches them.

6. 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.

7. The email notification is optional in most cases. Configure the notification.error.flag property name in the OUTL-BRT-WACS_ERPSCM_ConfigProps lookup to 'true' and notification.type.email property to 'email' to receive email notification when errors are encountered.

8. The recipient(s) of the email notification is/are configured in the OUTL-BRT-WACS_ERPSCM_Email_ID lookup.