Validity Dates at a Rate Level

[Former Member]

Dear TM Experts,

We have a requirement to be able to change the validity of freight rates for selected OD pairs. Based on the 'Dates & Values' on rate table however it appears that multiple rates share a validity. Here is our requirement in the form of an example.

Validity: 01 Jul 2014 to 31 Dec 2014

Rates: Chicago IL to Houston TX - $500 USD

           Chicago IL to Wichita KS - $440 USD

If the rate to Wichita changes from $440 to $450 but effective from 01 Oct 2014 to 31 Dec 2014 (with Houston's rate & validity unchanged while Wichita's rate is still $440 until new date comes into effect), how do we achieve this? If this is not standard in TM is there a creative way to implement this with any enhancements? Any pointers are much appreciated.

Best Regards,

KC

[vikas_gupta22 · Accepted solution]

Hi Krishna,

There are couple of standard options to use in this case. You can select one of them, basis your client requirements.

1) One rate table with differing validity.

a) In the beginning create a rate table with validity 01.06.2014 till 31.12.2014

b) When business wants to revise rates for a set of origin-destination from 01.09.2014, they would need to change the validity of the existing rate table from 01.06.2014 till 31.08.2014 and then copy this validity to create another validity from 01.09.2014 till 31.12.2014. In this new rate table validity, they can change the rates as needed.

Note: Both validity have to be in 'Released' status. (screenshots attached)

2) Create different rate tables for each origin and destination pairs. Use rate table determination condition at TCCS charge type level based on origin destination pair for appropriate rate table determination. You can play with validity and values for each of these rate tables as needed. However this option will increase maintenance manifold.

3) Include 'calculation date' as additional scale item in the rate table. This option will also increase data maintenance.

I would prefer 1st option.

Thanks,

Vikas.

[Former Member · Accepted solution]

Thanks Vikas. Looks like we have to create multiple validity periods for both old and new rates. It will be two validity periods in the above example but if there is a partial overlap then there will be 3 validity periods at most.

[former_member194187]

Hi,

We had similar requirement from one of our customers.

Considering various 'if- else' situation with using standard rate table structure, we found that use of std rate table is not meeting customer requirement.

Finally we gone for custom rate table solution

Regards,

Sunish