Crossdock - Revision history

Anw: Minor formatting change

2024-05-09T07:56:04Z

Minor formatting change

← Older revision		Revision as of 09:56, 9 May 2024
Line 1:		Line 1:
	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.		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 ~~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.		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.		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		The Main modules used in Cross Docks are
	~~<ul>~~		* [[ORDERS]] (Oracle Form)
	~~<li>~~[[~~ORDERS~~]] (Oracle Form)~~</li>~~		* [[New Order]] (Oracle Form)
	~~<li>~~[[TRIPSUM]] (Oracle Form)~~</li>~~		* [[TRIPSUM]] (Oracle Form)
	~~<li>~~[[TRIPPLAN]] (Oracle Form)~~</li>~~		* [[TRIPPLAN]] (Oracle Form)
	~~<li>~~TRM (Database Package)~~</li>~~		* [[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.		If an Order is scheduled from its collection point to a cross dock location it will be set to a status of SCHED_COLL.

Crisfordm at 11:40, 29 December 2008

2008-12-29T11:40:23Z

← Older revision		Revision as of 13:40, 29 December 2008
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>

Crisfordm at 11:40, 29 December 2008

2008-12-29T11:40:07Z

← Older revision		Revision as of 13:40, 29 December 2008
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.

Crisfordm at 11:39, 29 December 2008

2008-12-29T11:39:34Z

← Older revision		Revision as of 13:39, 29 December 2008
Line 3:		Line 3:
	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.		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		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)		<ul>
	TRIPSUM (Oracle Form)		<li>ORDERS (Oracle Form</li>
	TRIPPLAN (Oracle Form)		<li>TRIPSUM (Oracle Form)</li>
	TRM (~~database~~ Package)		<li>TRIPPLAN (Oracle Form)</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.

Crisfordm: 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...

2008-12-29T11:36:50Z

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...

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 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.