Collect From Store Customer Order Is Not Flowing Correctly To WMS
(Doc ID 3072763.1)
Last updated on FEBRUARY 21, 2025
Applies to:
Oracle Retail Integration Cloud Service - Version 24.1 to 24.1 [Release 24.1]Information in this document applies to any platform.
Symptoms
On : 24.1 version, Universal Service Mapper
Collect from Store Customer Order is not flowing correctly from WMS to SIOCS.
For customer orders designated as pick-up-in-store and sourced from the warehouse, USM fails to transmit the required store-bound order information to WMS. As a result, WMS incorrectly processes these as warehouse-to-customer orders. During shipping, USM cannot properly transform the order information, which prevents SIOCS from processing the transfer as a customer order.
Steps to recreate:
======
1. Create a CO with the following setup
"customerOrderNo": "SNB_10_WEB_ORDER_WHS",
"fulfillOrderNo": "SNB_10_WEB_ORDER_WHS",
"sourceLocationType": "WH",
"sourceLocation": 1910,
"fulfillLocationType": "S",
"fulfillLocation": 1003,
"partialDeliveryInd": "N",
2. Validate that the Order was created in WMS and it appears as a CO with a physical location but with customer details like Customer Address.
3. Ship the order in WMS using the LogFireToRibASNOutFromOblpnShipping_ServiceMappingDef.json flow.
4. Validate that the order reached SIOCS however it’s not linked with a PO.
5. Check table TSF_DELV_CARTON in SIOCS and see if the field CUSTOMER_ORDER_RELATED shows 3, meaning that is not linked with a CO.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |