TMS problems 2011
From UG
| Line 6: | Line 6: | ||
| align="center" style="background:#f0f0f0;"|'''Id''' | | align="center" style="background:#f0f0f0;"|'''Id''' | ||
| align="center" style="background:#f0f0f0;"|'''Status''' | | align="center" style="background:#f0f0f0;"|'''Status''' | ||
| + | | align="center" style="background:#f0f0f0;"|'''Descr''' | ||
|- | |- | ||
| - | | [[#tms1]] || open | + | | [[#tms1]] || open || Earliest and Latest Available Dates problem |
|- | |- | ||
| [[#tms2]] || open | | [[#tms2]] || open | ||
| Line 16: | Line 17: | ||
== tms1 == | == tms1 == | ||
| - | === Earliest and Latest Available | + | === Earliest and Latest Available Dates problem === |
| - | + | CT2 to TMS mapping is incorrect, also the whole way we use these dates is not well thought through. | |
| - | === Solution === | + | 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 | ||
| + | |||
| + | 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 | ||
| + | |||
| + | |||
| + | === Solution and Notes === | ||
Revision as of 21:19, 15 March 2011
Contents |
Intro
| Id | Status | Descr |
| #tms1 | open | Earliest and Latest Available Dates problem |
| #tms2 | open | |
tms1
Earliest and Latest Available Dates problem
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
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
