SOP All TO cleanup/ discrepancy triage requests SOP

Name: 
Summary:  This SOP details the type of cleanup and issue triage requests we get from business
on an almost-daily basis. This SOP contains all the workarounds for TOR-1. These the
contents of this document

Contents
Transfer Orders – TOR-1......................................................................................................................................................
Close tripped TO shipments in OMS...........................................................................................................................
Close untripped TO item in OMS..................................................................................................................................
Duplicate TO orderlines cleanup..................................................................................................................................
Full Refresh...........................................................................................................................................................................
Duplicate shipments cleanup in DW...........................................................................................................................

Created  Geetika Bajaj

by
Architect  
Approver
Status: 
Estimated Each process below is different and can take from 15 – 60 mins
Execution
Time 

 
 Transfer Orders – TOR-1

These are the requests we get for Transfer Orders :

Close tripped TO shipments in OMS

If there are any discrepancies for tripped TOs between OMS and the source system, business will
reach out the L2 support team through an email or by creating a PBI in DirtyFingerNail feature.
If the orderline is tripped, it means that a shipment for it has already been created in OMS. We
don’t allow for cancelling a shipment by design in AFI. So instead, we manually receive the
orderline to close it. Tripped items can have the following statuses in OMS : InTransit, Partially
Received.
For tripped shipments, we need to change the status of the shipment from ‘Shipment Shipped
(1400)’ to ‘Included in Receipt (1600)’
Please use the below sheet to create the input for the multiApi call. Sheet ‘Workaround Steps’
contains detailed steps for closing the tripped TO items.

OMS_SOP_TOR1_TO_
Shipment Closing.xlsx

Close untripped TO item in OMS

If there are any discrepancies for untripped TOs between OMS and the source system, business
will reach out the L2 support team through an email or by creating a PBI in DirtyFingerNail
feature.
If the orderline is still untripped, it means that a shipment for it is not yet created in OMS.
Closing such orderlines can be done by directly going into order console and cancelling the
orderline. Untripped items can have the following statuses in OMS : OnOrder, Planned, Created
If there are too many untripped items to be closed in OMS, please use the below sheet to create
the input for the multiApi call. Sheet ‘Workaround Steps’ contains detailed steps for closing the
untripped TO items

OMS_SOP_TOR1_TO_
Untripped Closing.xlsx
Duplicate TO orderlines cleanup
There is an open bug in OMS due to which duplicate orderlines are getting created in OMS.
Example: TO# ABCDE will have 2 orderlines with the same itemID. Vivek opened a case with
IBM to understand how why multi-threading will cause this. The case is still open.
Meanwhile, we manually look for duplicate TO items in OMS - cancel the orderliness and
remove the orderliness from OMS.
Once this is complete, we request White, Justin JuWhite@Ashleyfurniture.com to delete the
duplicate orderliness from DW as well. below folder has the steps that can be followed to
sequentially cleanup duplicate TO orderlines in OMS and DW

Duplicate TO Item Cleanup SOP.zip

Full Refresh
We don’t manually trigger TOR-1 full refresh generally. A full refresh is sent to OMS every
morning Monday- Saturday. Please reach out to Ray, Christopher CRay@Ashleyfurniture.com if
a manually full refresh needs to be triggered.

Duplicate shipments cleanup in DW

There is an open issue in OMS which is causing duplicate shipments to get created in OMS and
DW. We have noticed that the shipments in OMS get automatically cleaned up on their own. But
the duplicate shipments have to be manually cleaned from data warehouse. Please use the below
script to clean up the duplicate shipments from DW. Script needs to be sent to White, Justin
JuWhite@Ashleyfurniture.com

DELETE FROM [Wholesale_OMS_Enh].[Shipment] WHERE SHIPMENTKEY IN ('', '', '');

DELETE FROM [Wholesale_OMS_Enh].[ShipmentLine] WHERE SHIPMENTKEY IN ('', '', '');

TO_Cleanup.txt