Crossdock: Difference between revisions
(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...) |
m (Minor formatting change) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Within | Within CTMS 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 | 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 approximately 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 | This module's main feature is to allow the user to schedule an [[Order]] to be delivered via one or more locations. | ||
Main modules used in Cross Docks are | The Main modules used in Cross Docks are | ||
ORDERS (Oracle Form) | * [[ORDERS]] (Oracle Form) | ||
TRIPSUM (Oracle Form) | * [[New Order]] (Oracle Form) | ||
TRIPPLAN (Oracle Form) | * [[TRIPSUM]] (Oracle Form) | ||
TRM ( | * [[TRIPPLAN]] (Oracle Form) | ||
* [[PLANNING]] (Oracle Form) | |||
* TRM (Database Package) | |||
If an Order is | If an Order is scheduled from its collection point to a cross dock location it will be set to a status of SCHED_COLL. | ||
Latest revision as of 09:56, 9 May 2024
Within CTMS 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 approximately 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
- ORDERS (Oracle Form)
- New Order (Oracle Form)
- TRIPSUM (Oracle Form)
- TRIPPLAN (Oracle Form)
- PLANNING (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.
