Unassigning An Order From A Shipment Results In Incorrect Behavior Of Commitment Allocation.
(Doc ID 1101784.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Transportation Operational Planning - Version 5.5.05.06 to 5.5.05.08 [Release 5.5]
Information in this document applies to any platform.
On OTM version 5.5.05.06 when using Commitment Allocation, if two orders are built onto one Shipment the allocation records are updated correctly. However if one of the two orders is unassigned the allocation count is reduced by 1, this is not correct because the shipment still exists (as it still has the other order on it).
Expect the count to remain unchanged.
The issue can be reproduced at will with the following steps:
1. Check Commitment Allocation Usage for a Lane.
2. Build a shipment from 2 orders (Order 123 and Order 456) on the Lane.
3. Check Commitment Allocation Usage for the Lane, Total Planned Count and planned count for the chosen Service Provider will have incremented by 1.
4. Unassign Order 123
5. Check Commitment Allocation Usage for the Lane. Note the count has incorrectly reduced by 1, even though the shipment still exists.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document