Good morning everyone,
We have a unique case in our parts sales process for railway maintenance of way; our customers will place a larger order that will commonly have shortages/backorders. The first initial shipment would go to a railway depot/station on the line of the track. After that the machine will move down the track, therefore the shipping address will change for that order.
The customer will only be placing one order via EDI so everything must stay on one order to loop back to the exchange.
I cannot make this an "Order Type" and this applies to all of our BP's and Sales Offices.
My theory is that I could add a boolean to the Sales Order table to add "Is this a order where the location will move?" (the CSR's know this at input).
After the order is "Released to Warehousing" I need to leave the order in the "Released to Warehousing" state; I have backorders and cross-docking implemented, so I need to notify my CSR when something is received against that order to call and get an updated shipping address.
Then use the "UponTaskCompletion" workflow to release the lines available to the new address or some sort of step to verify the address is the same.
Has anyone ever encountered something like this?
I thought about having the lines that had shortages have the AD default back to our location so they wouldn't ship out accidentally, but that would be an update line as well.
Any help, directions towards work flows, etc. would be helpful.
