Crossdock: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
The Main modules used in Cross Docks are | The Main modules used in Cross Docks are | ||
<ul> | <ul> | ||
<li>ORDERS (Oracle Form</li> | <li>[[ORDERS]] (Oracle Form</li> | ||
<li>TRIPSUM (Oracle Form)</li> | <li>[[TRIPSUM]] (Oracle Form)</li> | ||
<li>TRIPPLAN (Oracle Form)</li> | <li>[[TRIPPLAN]] (Oracle Form)</li> | ||
<li>TRM (Database Package)</li> | <li>TRM (Database Package)</li> | ||
If an Order is scheduled from its collection point to a cross dock location it will be set to a status of SCHED_COLL. | If an Order is scheduled from its collection point to a cross dock location it will be set to a status of SCHED_COLL. | ||
Revision as of 13:40, 29 December 2008
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 to be delivered via one or more locations.
The Main modules used in Cross Docks are
