TMS
From UG
Contents |
Def
TMS - in general it is Transportation Management System.
In our case it is the Descartes TMS that we integrated with our CT2 system.
TMS Admin
Admin Requirements
Not to hard code specific CT2/TMS functionality, so as to allow management users the ability to set specifics. Full spec is under category: EDI to TMS
What can be managed here are the following:
- Automatic and manually forwarding the approved portal CT records to the TMS
- Setup the CT2 & TMS server addresses for exchange
- Users can un-check auto option and select dates from calendar
- Automatically accept updates sent to CT2 from the TMS
- This can be managed in number of seconds
- Option for FTP server to hold/store xml files received that have a future date is set and re-ck at a specif time - IE currently set to 12am
- Allowing management users to change/set the number of days, on the Shipment Import XML file, between the earliest pickup date and latest pickup date - IE currently set to 7days from the Approved On Date which = Earliest Pickup Date
Admin mock up
Below is outdated.
SOWs
SOW 1 Add Bill To Party parameter to Descartes TMS properties
Add Add Bill To Party parameter to Descartes TMS properties (Admin).
Relationship is one to one: only one Bill To Party value is active at one time for Desc TMS.
Please note that this value is selected when E0 parameter is selected or changed in TMS Admin. System will present a list of Bill To Party values in the system associated with selected E0. User would have to select one.
See also
See also
These are the original Analysis / Requirements wiki for EDI to TMS proj Mantis: 2183 & the phase 2 are found here: 2539