When Planning an Order thru a Xdock Max Freight Idle Time Is Ignored When Using a Network
(Doc ID 2106560.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.0 and laterOracle Transportation Management Cloud Service - Version 6.3.4 and later
Information in this document applies to any platform.
Symptoms
When planning an order thru a xdock, max freight idle time is ignored.
The time between the resulting two shipments is more that 1 day as has been setup on the xdock location role.
Scenario details:
- final destination has a calendar that accept delivery only on the day 6 of week
- XDOCK has a Max Freight Idle Time set to 1 day
When an Order Release is plan from location A to B thru a xdock on Day 1 (using an Itinerary that has one leg with a network) will result 2 shipment:
- A to XDOCK >> start date is Day 1 and delivery Date is on the same day
- XDOCK to B >> start date is Day 6 and delivery date is the same day
The expect result is:
- A to XDOCK >> start date is Day 5 (or 6 depending the transit time) and delivery Date is on the same day
- XDOCK to B >> start date is Day 6 and delivery date is the same day
Cause
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
| Symptoms |
| Cause |
| Solution |