TMS problems 2011
From UG
Contents |
Intro
| Id | Status |
| #tms1 | open |
| #tms2 | open |
tms1
Problems related to Earliest and Latest Pick Up Dates
Descr:
CT2 to TMS mapping is incorrect, also the whole way we use these dates is not well thought through.
This leads to several sub-problems:
A] no overlap in pick up windows for shipments in the load so load can’t be created
B] Corrupt XML files were sending multiple e-mails to shipper users every 5 mins (FIXED? good fix?)
C] status messages info is not updating
Solution and Notes:
Workaround#1 (through UI, very time consuming): To set up Appointment on the load before tendering
Quick programming fix: 0002797: [EDI to TMS] (Shipment_Import) Change Mapping of the Earliest & Latest Available Date
Notes from Denise:
1. Earliest & Latest Pickup Date is set in the shipment, which is currently mapped to the created on date &/or the date that the planner put on hold for approval with a 9am to 5pm window. Mantis 2797 was created to allow for CT admin users to set the amount of time between the Earliest & Latest Pickup dates that will pass on our shipment import into the TM. This solution was provided to cut down on current manually workarounds for dates.
2. Corrupt XML files were sending multiple e-mails to shipper users every 5 mins, this was due to users creating a load with 1 shipment, then selecting other shipment records, adding them to this already created load but these shipments have a variation of earliest & latest pickup dates. Then the TM takes all of the dates into consideration, automatically sets the earliest and latest available date for the load and being the dates were so out of range, their system was unable to understand how to handle.
Therefore Descartes provided a workaround for this and for the users to:
a. No longer use the create load option & select to select the consolidate option
b. Set a pickup appointment to the date of when the load will be picked up
c. Use the resequence option, which will have the TM re-order the dates for the TM to suggest a better window for the loads earliest and latest available date
tms2
FSC problems
Descr:
“Allocated shipment costs”/”Load costs” report is incorrect/FSC problems.
This is because Fuel surcharge (FSC) on Loads calculates incorrectly due to using wrong week on “Fuel price” weekly table.
Because it is a function of “Latest Available Date(LAD)” which is set incorrectly by Portal (to created on date)
Solution and Notes:
Quick fix: 0002797: [EDI to TMS] (Shipment_Import) Change Mapping of the Earliest & Latest Available Date
Note from Denise:
1. As there are issues with the dates, the TM currently applies the FSC incorrectly for every load, as it is based upon the Earliest & Latest Available dates set by the TM’s logic it is not an accurate way of rating the FSC as not all loads are picked up according the latest available date set by the TM. Therefore the following workaround was set: a. Change every shipment records earliest & latest pickup date to the date in which the load will be picked up and this is to ensure proper application of that weeks FSC
tms3
Addresses have duplicates
Descr:
Duplicates of addresses create: Extra “dummy” stop which leads to no updates on one of the CT in such load in CT2 DB
Solution and Notes:
a) Eliminate address duplicates in CT2
b) Descartes quick fix: TBD
Denise:
1. Due to CT address book issues IE – multiple addresses for the same company – when a user selects 2 or more shipments that have the same street address, yet has a variation in the company name, the TM creates 2 separate delivery stops for the load. When that happens, the TM does not set an estimated delivery time for the 2nd stop and leave that xml attribute blank, therefore these xml files are incomplete/corrupt and CT does not accept the update of pickup trucker, delivery trucker & est. pickup & delivery dates. Descartes feels this is a design bug on their end and will correct it, but in the interim as we clean up our address book, they have mapped the 1st stops estimated delivery date to the 2nd stops estimated delivery date, making their xml files complete & when we receive them, they will continue to update each CT record the same.
tms4
Not all approved shipments have Shipment Import file sent to TM
Descr:
Solution and Notes:
0002750 Bug: Not all approved shipments have Shipment Import file sent to TM
tms5
Summary TBD
Descr:
Solution and Notes:
tms6
Summary TBD
Descr:
Solution and Notes:
tms7
Summary TBD
Descr:
Solution and Notes:
