| Oracle® Retail and WMS Cloud Implementation Guide Release 16.0.040 F23400-02 |
|
 Previous |
 Next |
The following lists all the outbound interfaces from WMS Cloud available in USM, for integration into RMFCS or SIOCS, along with their interface names, template files, service definition files, orchestration files, supported message types, and payloads.
|
Note: These interfaces have the exact same Failure and Response templates. Namely:
|
You will be able to see the details available in these templates in the USM screens to help with resolving any issues in the integration. See also the Chapter 3, "Integration Errors".
This integration will be used for shipments from the warehouse to a store or to another warehouse. It also will be used for customer orders that are shipped to the customer directly.
Any inventory adjustments that will increment or decrement inventory in the warehouse will be sent via this integration point. This includes removing inventory from stock completely or moving it to and from an available status. The integration here will map to one of two inventory status codes in RMFCS - Available to Sell (ATS) or Trouble (TRBL). Within RMFCS, you can configure the TRBL status code to map to either the applicable inventory status (see the Oracle Retail Merchandising Foundation Inventory User Guide for more information). The determination of which will be used will be based on the values in reference codes 11 and 12 in the WMS Cloud Inventory History. If reference code 11 is PAS, then if reference value 11 is Yes, the from disposition for the adjustment will be mapped to ATS; otherwise to TRBL. Similarly, if reference code 12 is CAS, then if reference value 12 is Yes, the to disposition in this interface will be mapped to ATS; otherwise to TRBL.
This integration will be used when shipping inventory back to a supplier from the warehouse. All RTV shipments will use the inventory disposition code of ATS.
This integration will be used for receipts of purchase orders, transfers, or allocations into the warehouse. Both container level and detailed receipts will flow through this message to update RMFCS.
This integration will be used to communicate updates for stock orders - which can be either a transfer or allocation. Status updates are based on certain activity codes in the Inventory History table in WMS Cloud and map to the RMFCS codes as follows:
Table B-1 Status Update Codes
| WMS Cloud Code | Description | RMFCS Code | Description |
|---|---|---|---|
|
10 |
Container Detail Packed |
PP |
Pick Pending |
|
27 |
Order Cancellations |
SD |
Stock Decrease |
The following lists the inbound interfaces to interfaces used for integration into WMS Cloud from RMFCS or SIOCS, along with their interface names, template files, service definition files, orchestration files, supported message types, and payload name. Because of how WMS Cloud consumes data, for the following interface points, a full payload is used for sending updates from RMFCS, rather than just the data that changed: items, purchase orders, stock orders, vendors, and RTV requests, using the "FullRep" message type.
The following list of Interfaces have the exact same Failure and Response templates.
RibToLogFire_DefaultAllAction_FailureResponseDataMapping.template
RibToLogFire_DefaultAllAction_ResponseDataMapping.template
This integration will send new and updated store information from RMFCS to WMS Cloud. If a store is deleted in RMFCS, that will also be communicated to WMS Cloud.
Service Definition
RibToLogFireStores_ServiceMappingDef.json
Orchestration File
RibToLogFireStores_ServiceMappingOrchestration.smo
This integration will send new and updated supplier site information from RMFCS to WMS Cloud. If a supplier site is deleted, that will also be communicated to WMS Cloud.
Service Definition
RibToLogFireVendor_ServiceMappingDef.json
Orchestration File
RibToLogFireVendor_ServiceMappingOrchestration.smo
This integration will send new and updated external finisher information, including addresses, from RMFCS to WMS Cloud. If an external finisher or its address is deleted, that will also be communicated to WMS Cloud.
Service Definition
RibToLogFirePartner_ServiceMappingDef.json
Orchestration File
RibToLogFirePartner_ServiceMappingOrchestration.smo
RIB Payload
PartnerDesc
Template Files (Request)
RibToLogFirePartner_PartnerCre_RequestDataMapping.template
This integration will send new or updated items to WMS Cloud from RMFCS, including parent items, transaction level items, and reference items, as applicable. Only approved items are sent in this integration. For pack items, the component details for the pack are also integrated. See the Items section for key assumptions about items that are integrated to WMS Cloud.
|
Note: Item Delete is not currently supported in this integration. |
Service Definition
RibToLogFireItem_ServiceMappingDef.json
Orchestration File
RibToLogFireItem_ServiceMappingOrchestration.smo
RIB Payload
ItemDesc
Template Files (Request)
RibToLogFireItem_ItemCre_RequestResponseDataMapping.template
RibToLogFireItem_ItemUpcCre_RequestResponseDataMapping.template
RibToLogFireItem_ItemBomCre_RequestResponseDataMapping.template
This integration is used to map shipments inbound to a warehouse, which could be from a supplier or a store. Modifications to shipments or deletions of a shipment can also occur based on adjustments sent from a store or supplier.
Service Definition
RibToLogFireASNIn_ServiceMappingDef.json
Orchestration File
RibToLogFireASNIn_ServiceMappingOrchestration.smo
This interface is used to send new and updated purchase orders from RMFCS to WMS Cloud. Only approved orders with a warehouse as one of the destination locations will be sent to WMS Cloud. For more details about PO mapping rules, see the Purchase Orders section.
Service Definition
RibToLogFireOrder_ServiceMappingDef.json
Orchestration File
RibToLogFireOrder_ServiceMappingOrchestration.smo
Stock orders can be either transfers or allocations, including customer order related transfers. These orders are sent from RMFCS to WMS Cloud when the warehouse is either the shipping location or the receiving location on the stock order. Only approved stock orders will be integrated.
Service Definition
RibToLogFireStockOrder_ServiceMappingDef.json
Orchestration File
RibToLogFireStockOrder_ServiceMappingOrchestration.smo
This integration will send return to vendor transactions initiated in RMFCS that are requested to be shipped from a warehouse.
Service Definition
RibToLogFireRTVReq_ServiceMappingDef.json
Orchestration File
RibToLogFireRTVReq_ServiceMappingOrchestration.smo
