Oracle Transportation Management (MOSC)

MOSC Banner

Choosing of Rate Record in Bulkplan process

edited Apr 10, 2015 6:43AM in Oracle Transportation Management (MOSC) 3 commentsAnswered

Hello,

  

We have 2 Active Rate Records:

  

RateRecord 1 which has Expiration Date 31.01.2015 and 

RateRecord 1 which has Effective Date 01.02.2015

 

We planned Order Release on 02.02.15 which had early pick up date on 03.02.2015 03:00:00; and then OTM took record RR 1 which has expired date.

 

We haven't any constraints on order_release, itinerary ,etc

  

Why did OTM take RR1 in the bulk-plan process, which Expiration Date is over and why did it not use RR 2?

  

Rate Record is created from csv file. After created RR we use Clear Cache.

Thanks for the answers.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center