COMMITMENT ALLOCATION IS NOT INFLUENCING PLANNING
(Doc ID 1061765.1)
Last updated on APRIL 04, 2018
Applies to:Oracle Transportation Management - Version: 5.5.05.06 - Release: 5.5
Information in this document applies to any platform.
NOTE: This is not restricted to voyages.
Expect OTM to respect the Carrier Commitment configuration.
The issue can be reproduced at will with the following steps:
1 - Create 4 service providers :
2 - Create 6 voyages:
1. from VNSGN to USLAX - for SP1
2. from VNSGN to USSEA - for SP2
3. from VNSGN to USSPQ - for SP2
4. from VNSGN to USTIW - for SP3
5. from VNVUT to USLGB - for SP3
6. from VNSGN to USLGB - for SP4
3 - Create Rate Offering, Rate Record and Service which are compatible for all the above schedules with same cost.
4 - Commitment allocation is configured for the following lanes with 100% for SP2 for the lanes same as voyage schedules. Also a lane covering the source ports to destination ports is created with 100% to SP2.
5 - Plan 2 order releases which are bundled in to one so that it would be assigned to SP2, the carrier with the highest / only allocation.
6 - Instead of SP2, the shipment for primary leg is built with SP1 as carrier.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|