on 2021 Nov 22 3:32 PM
Hello,
I try to set up quantity discrepancy update from EWM to TM, both basic embedded in shipper outbound scenario Integrated by Advanced shipping and receiving (ASR).
my problem is that I loose information about originally order qty in TM.
Example:
Outbound delivery created for two palletes of material -> FU for 2pal created and planned in FO in TM -> delivery order for 2pal created in EWM -> 1pal picked only and GI posted in EWM -> FU and FO reduced to 1 pal on planned qty according to the picking, actual QTY fields keeps empty.
Is there any chance to keep originally ordered quantities and obtain the information about real quantities in the same time?
I set up discrepancy profile, but without an effect. SAP help talks just about transit warehouse scenario, nothing about discrepancies display in shipper scenario.
Thank you for any advice
Petr
Dear Petr,
thank you for your question in the SAP TM Community!
In the Advanced Shipping & Receiving process in the current solution updates are always made on the so-called document quantities.
The document quantities express in the current state of the process how much is planned to be shipped, or - in case you are already in the execution process - how much has actually been staged in the warehouse. The requirement to record the discrepancies between planning and execution has already reached us and we are currently evaluating whether we want to include such functionality on the roadmap. If this should be the case, the timeframe for this would be the planning of the S/4HANA 2023 release.
I hope I was able to help you with my answer!
Best regards,
Carsten Abel
Product Owner Logistics Integration, SAP Transportation Management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've found that this requirement, "to be able to easily visualize the changes/discrepancies between planned quantities in transportation planning vs actual quantities after warehouse integration", is a very common expectation of the system from the customers. In case this helps sway the evaluation towards actually including it in the roadmap.
User | Count |
---|---|
10 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.