Cargo Due Date Feature

From UG

Revision as of 20:10, 6 June 2011 by Denise (Talk | contribs)
Jump to: navigation, search


Contents

Info

Related mantis:

  • 0002539: [OSDS] ..... <proj>
  • 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)
  • Allow the Approved for date to the same as the cargo due date, but it cannot be in the past
  • This date will also be required for KPI reporting/analysis.

Functionality

  • Provide option to turn on/off the Cargo Due Date Field on each planner role
  • This cargo due date field is a Datebox

OR

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status.

  • If super planner sets the cargo Due Date, the system should not allow basic planner user to change
Personal tools