Tweet
We build 4 related shipments(each having 1 pickup & 1 delivery stop) for our itnernational to US destination orders through Optimization. When we enter an actual departure date on the first leg we expect to see the estimated dates on the 3 related legs to be updated. This works just fine if the departure date on say leg 1(departed delivery location) is later than the planned arrival at stop 1 of the second leg.
However it does not work when the actual departure date on say leg 1(departed delivery location) is earlier than the planned arrival at stop 1 of the second leg.
We for good reasons are building shipments for containers in OTM after the fact and need to back date the actuals to reflect when the container actually left. This is causing extreme problems with visibility downstream as the final destination ETA doesn't change and product is arriving ahead of what the ETA dates in OTM says.
Have a ticket with Oracle opened but not getting a resolution to our issue quick enough.
Any thoughts on configuration to make this happen where re-calculate of estimate dates happens either way. thanks
We're on 5.5 CU4 RU3.
However it does not work when the actual departure date on say leg 1(departed delivery location) is earlier than the planned arrival at stop 1 of the second leg.
We for good reasons are building shipments for containers in OTM after the fact and need to back date the actuals to reflect when the container actually left. This is causing extreme problems with visibility downstream as the final destination ETA doesn't change and product is arriving ahead of what the ETA dates in OTM says.
Have a ticket with Oracle opened but not getting a resolution to our issue quick enough.
Any thoughts on configuration to make this happen where re-calculate of estimate dates happens either way. thanks
We're on 5.5 CU4 RU3.