on ‎2020 Nov 20 4:59 PM
Hello Experts,
We are looking for guidance to mitigate the problem we are facing with our SAP ECC and TM integration when users are updating shipto party address on the delivery in ECC:
1. In ECC, user are updating the shipto party address e.g. street no. or house no. directly in the delivery when they realize it is incorrect.
2. This update is causing 2 issues on TM side:
a. This address update is creating one time location (1010 type) and this increases one time location for same shipto party in the system. Standard integration between ECC and TM is not picking up correct location (1010 type) created via CIF and instead uses this one time location in DTR/FU. So how do we stop this behavior and why is this behavior in TM. We were hoping, existing shipto location created from CIF is picked up instead of selecting one time location and destination location address in DTR/FU document is updated instead of using one time location.
b. If this address update from ECC is coming after FU is planned and FO exist then standard is removing the connection between FO and FU and is creating new FU. This is causing lot of confusion for load planner user as well as carrier because they does not have any visibly or informed in any way. Is this the standard behavior and how do we stop disconnect between FO and FU when shipto party is updated from ECC. Our expectation is that if FU is already planned then address is updated to all the document and updated address is communication to carrier via collobration portal.
So kindly review this request and share your feedback.
Regards
Sagar
Request clarification before answering.
hello Hari,
Unfortunately, no solution was found from the standard and we had to implement custom code to manage it. I would advice to open a ticket with SAP to confirm the standard behavior.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 13 | |
| 7 | |
| 4 | |
| 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.