The new cross-docking functionality is very useful. However it doesn't support Goods In Transit orders as a supply source. This is a significant gap for my current client. Knowing how many of our clients are now embracing Landed Cost I can see it coming up regularly. So please extend it to support goods in transit. We are using using marking with our cross-docks. So ideally it would support marking to a PO and automatically associate the planned cross dock with the relevant goods in transit order(s) that would be great, but as a minimum if we could mark to a GIT order, and that be handled on the HHT, it would be a big step forward
Comments
Not sure what the status is on this from but here are some of my own observations as the planned cross dock partially works as detailed in scenario 1, this should be on the roadmap to fix.
Scenario 1.
- Purchase order is created
- Sales order created
- Automatic Released to WH runs (including Planned Cross dock)
- Load is created and planned crossdocking is created
- Now a voyage is created for the PO
- PO invoice posted
- Voyage line status is GIT
- At this point you will notice that 2 GIT orders are created, 1 for the planned cross dock amount and 1 for the remaining inventory.
- Receiving the 2 individual GIT orders results in crossdocking work created as per usual .
Scenario 2.
- Purchase order created
- Voyage created
- Sales order created
- Automatic Release to WH run with cross docking
- No planned crossdocking created.
Category: Warehouse Management
Administrator on 8/2/2023 9:38:48 AM
Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Per Lynnerup
PM, Microsoft