CR does not forward change of delivery rule to LER/ODR
[control] [delivery] [delivery date] [delivery order] [delivery time]
Related:
- Unclear error log entry during delivery creationSymptom You distribute outbound or inbound deliveries from ECC to...
Symptom
Not in all business use cases a change of the delivery rule in the SalesOrder item is propagated down to the CustomerRequirement, the LogisticsExecutionRequisition and the OutboundDeliveryRequest.
We refer to one specific business use case here: For a partially fulfilled SalesOrder item the delivery rule is changed from “Multiple Deliveries” to “Single Delivery”. In this case the LogisticsExecutionRequisition was not updated with the changed delivery rule and the not yet fulfilled quantity was not automatically rejected from OutboundDeliveryRequest to LogisticeExecutionRequistion and finally to the CustomerRequirement. The CustomerRequirement delivery status was still “In process” where instead it should have been “Finished”, since no further delivery is possible.
Other terms
delivery control
Reason and Prerequisites
Any time when the CustomerRequirement does not perform an ATP check after the corresponding SalesOrder item was changed (e.g. in the case when the confirmed quantity is already requested from execution; or technically: after the LogisticsExecutionRequisition was released), the delivery rule is not propagated to LogisticsExecutionRequisition.
Solution
The correction was applied to the following Support Packages:
FP 2.0 SPS 0 with transport request H0EK002649
FP 2.0 SPS 1 with transport request MGGK020175
FP 2.5 with transport request AGPK016911