Oracle® Retail Merchandising and WMS Cloud Implementation Guide Release 19.0 F25718-02 |
|
![]() Previous |
![]() Next |
WMS Cloud
WMS Cloud provides visibilities to errors that may occur in the integration in two screens - Input Interfaces and Output Interfaces. The Inbound Interfaces screen will provide visibility to errors that occur in integration from Merchandising or SIOCS applications into WMS Cloud.
For data inbound to WMS Cloud, the APIs will respond back with appropriate error messages in the response if the message fails validation. These error messages can also be seen in the "Stage Record" tab of "Input Interfaces" screen as shown below. Both failed and successful messages are visible in this screen.
If there are issues with the data sent in the interface, appropriate changes need to be made to the data and data needs to be resent. However, if the issue is that dependent data is missing, for example, a purchase order is sent for an item that doesn't exist in WMS Cloud, then once the data is corrected the record can be reprocessed from the Input Interfaces view by selecting the appropriate record and clicking the "Reprocess selected records" button.
For data sent from WMS Cloud to Merchandising, SIOCS, and OROB, the status of the messages sent from WMS cloud can be seen in the Output Interfaces view. Like the Input Interfaces view, both successful and failed messages are visible in this screen.
If messages appear with Failed status, then the details of the errors can be viewed by clicking on the Interface Logs button, as seen below. Depending on the error, this view will also allow the message to be resent by clicking on the Resend button.
USM can also be used to view any errors that may occur during the transfer of data.
Starting in the Home tab, which is the landing page for USM, it gives the overall status of the system. It also gives the number of available mappings, total service activity count and also number of successful and failed activities.
The Monitoring tab gives information on the success or failure of a particular flow, including the start and end time of the source operation and the status of the mapping operation. Then, for the highlighted flow in the table, you will be able to see the data before and after the mapping to help with tracking down errors.
Additionally, the System Logs tab gives detailed information on errors on every flow individually. You can see the success or failure message by clicking on the respective flow and viewing the logs for it below.