[raajamanikandan]

We are running an RIQ with the 'Date Deliver By' as November 20, I have a Voyage schedule setup for the Ocean Primary leg for the next 4 weeks.
When we run the RIQ with the above date, the system inserts the 'Date Available By' as the current date and gives me the immediate next available schedule instead
of the schedule which will meet my 'Date Deliver By' of Nov 20'.

If I run the same query with the date available by as Nov 05, it is fetching me the right rate and schedule.

Even if I insert an RIQ xml with the 'Date Deliver By' as Nov 20, am getting the same wrong immediate available schedule.

**************************************
When I enter the 'Deliver By Date' and leave the 'Available By Date' blank, OTM is inserting the current date in 'Available By Date',
is this the functionality?, shouldnt it calculate the 'Available by Date' based on the 'Deliver By Date'?

This is a very important functionality for the customer is doing an RIQ when they create the PO, at this point they do not know
what is the cargo available date from the supplier, after getting the schedule from OTM based on the 'Deliver By Date', they send
this info to the supplier and ask them to plan accordingly ie plan the ship date based on the ETD date which OTM has calculated
for them using the 'Deliver By Date'. We need to explore how to get this working.

[raj73]

Please try setting HOLD AS LATE AS POSSIBLE & MINIMIZE WAIT TIME IN SERVICE TIME CALCULATION to TRUE in the planning-parameter-set that is attached to your Domain and perform RIQ with Route-and-Rates. Please check the start_time and end_time from the result. Hope this would help.

[raajamanikandan]

Thanks Raj, I have tried this, it works fine if we have a normal Look Up Rate Service set up, but if I have a Voyage Schedule setup for the ocean leg of the multileg shipment, it is just not fetching any rates if the HOLD AS LATE AS POSSIBLE parameter is set to TRUE, any ideas as to why it is not.

With the default parameter this voyage schedule rate service works just fine.

[raj73]

I guess this is something to do with your rate-service setup and maybe something in particular with Type=Voyage schedule as you have mentioned that Type= Lookup works fine.

Have you setup the Voyage-service-Type to link the voyage-schedule to atleast one rate-service (and associated to rate-offering with valid rate-records)?

[raajamanikandan]

Yes Raj, have the same rate service work just fine when i do not have the HOLD AS LATE AS POSSIBLE paramater set to TRUE and I use the default parameter.

[raj73]

This behaviour appears to be a bit strange. Maybe, worth raising this as an issue with OTM support.