Cargo Due Date Feature
From UG
(→Requirements) |
(→Requirements) |
||
| Line 25: | Line 25: | ||
* Logged into history - internal CT record updates log & portal shipper/planner history view | * Logged into history - internal CT record updates log & portal shipper/planner history view | ||
| - | This date needs to | + | This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here [http://ct.jaguarfreight.com/mantis/view.php?id=2229 2229]) |
Date can be changed often, it is the same functionality as: [[Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status]] and it cannot be changed 72 hrs before the set date | Date can be changed often, it is the same functionality as: [[Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status]] and it cannot be changed 72 hrs before the set date | ||
Revision as of 21:17, 24 May 2011
Contents |
Info
Related mantis:
- 0002896: [Truck Optimization] ...... <proj>
- 0002489: [KPI] (External KPIs) Implement phase 1
Glossary
Business Needs
Core need
This feature would allow for better optimization, by knowing the number of days to put off picking up shipments; to be able to add more pickups, in the future, to maximize the trucks capacity.
Requirements
This date feature should not be hard coded; it should be allowed to be managed in CT2 >> Admin >> Client App Admin - TMS tab, as an option to display or not to display. (This would be to allow for the scalability of our current TMS solution, for us to provide to other client companies.)
This feature is for Non Jag users that have role, Planner set in their non jag user profile - see Cybertrax_2.1_Client_(requirements)#Core_Planner_Functionality.
The Cargo Due Date set, needs to be displayed:
- CT record, internal application, already has this field on the Gen Tab CT_bo#Cargo_due
- Logged into history - internal CT record updates log & portal shipper/planner history view
This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here 2229)
Date can be changed often, it is the same functionality as: Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status and it cannot be changed 72 hrs before the set date
Allow the Approved for date to the same as the due date
Functionality
Add/Display a Datebox to client app planner role for when user sets:
OR
- Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status
- Do not display if/when user sets: Cybertrax_2.1_Client_(requirements)#Hold_Without_Approved_For_Pick_Up_On_Date_Status
- Display when the status is changed to Cybertrax_2.1_Client_(requirements)#Approve_Status OR
Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status.
- System should only allow the due date to be = or > than the CT_bo#Cargo_available & [CT_bo#Approved_For_Delivery_By_Date]] & CT_bo#Approved_On
KPI Reporting will be required to report/analyze on
- Created date to approval date
- Approval date to due date
- Actual delivery date vs due date (on time performance, variations etc) (this one is an internal requirement EA did not request it
but it has significant value)
