Crossdock

From CTMS
Revision as of 13:36, 29 December 2008 by Crisfordm (talk | contribs) (New page: Within MTS there are 2 types of Cross Docks, one that is created via the Bookings functionality where multiple orders will be created, and the second where a single Order is cross dock...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Within MTS there are 2 types of Cross Docks, one that is created via the Bookings functionality where multiple orders will be created, and the second where a single Order is cross docked via one or more locations. This item is focussing on the second type of crossdock.

An example of a crossdock is where an Order is scheduled to be delivered from A to B. A and B are 200 miles apart, there is another depot (called C) that is approx 100 miles from each location. A decision is therefore made to move Order from A to C and to then move it from B to C (normally on a different Trip). This would potentially allow the first Trip to go and collect some additional Orders or to take an Order back from C to A.

This module's main feature is to allow the user to schedule an [Order[Orders]] to be delivered via one or more locations

Main modules used in Cross Docks are ORDERS (Oracle Form) TRIPSUM (Oracle Form) TRIPPLAN (Oracle Form) TRM (database Package)

If an Order is Scheduled from its collection point to a cross dock location it will be set to a status of SCHED_COLL.