Booking Entry - Revision history

Anw: Categorisation

2024-06-10T11:55:28Z

Categorisation

← Older revision		Revision as of 13:55, 10 June 2024
Line 80:		Line 80:
	Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..		Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..

			<noinclude>
	[[Category:Order Management\|150]]		[[Category:Order Management\|150]]
	[[Category:C-TMS Modules\|A-150]]		[[Category:C-TMS Modules\|A-150]]
	[[Category:C-TMS User Guide\|BA-150]]		[[Category:C-TMS User Guide\|BA-150]]
	[[Category:TEST\|A-150]]		[[Category:TEST\|A-150]]
			</noinclude>

Anw: Merged from training document

2024-06-10T10:16:34Z

Merged from training document

@@ Line 14: / Line 14: @@
 <center>[[Image:booking_detail.jpg|800px]]</center>
 Note that bookings can be imported through the Imports functionality:
@@ Line 40: / Line 41: @@
 See [[Create Transport Instructions]] for more details.
@@ Line 51: / Line 60: @@
 === Variance Filter ===
 This filter allows the records displayed in the Bookings screen to be restricted to those that have a discrepancy between the demand quantity and the quantity that was used to create Orders via Create TI’s. This allows a planner to easily and quickly identify any offending Product Summary records and subsequently determine why the demand has not flowed onto Orders, whether it be because there were no more appropriate Slots or violation of any other of the Create TI’s constraints.

Anw: Added BOOKING

2024-06-10T10:01:14Z

Added BOOKING

← Older revision		Revision as of 12:01, 10 June 2024
Line 14:		Line 14:

	<center>[[Image:booking_detail.jpg\|800px]]</center>		<center>[[Image:booking_detail.jpg\|800px]]</center>

			Note that bookings can be imported through the Imports functionality:
			* [[Imports_Details#BOOKING\|BOOKING]]

Anw: Merged from training document

2024-06-10T09:50:47Z

Merged from training document

← Older revision		Revision as of 11:50, 10 June 2024
Line 4:		Line 4:

	<center>[[Image:booking_1.jpg\|800px]]</center>		<center>[[Image:booking_1.jpg\|800px]]</center>

			To display the data for this schedule click the '''?''' button to the immediate right of the schedule name dropdown box. Alternatively, select a different schedule using the dropdown and click '''?''' to action the search.

			This will display all Booking records related to this schedule; information detailed will be as per the input data, with the main fields being Source, Destination, Delivery Date (Based on Schedule Name), Product Type, DU Type and Sum (Quantity).

			Note that the Quantity fields can be configured to display differently based on a C-TMS system parameter for a format mask e.g. 9999.000 or 99999.000.

			Double clicking a record will display further detail in a popup window:

			<center>[[Image:booking_detail.jpg\|800px]]</center>

Anw: test

2024-05-17T06:26:30Z

test

← Older revision		Revision as of 08:26, 17 May 2024
Line 52:		Line 52:
	[[Category:C-TMS Modules\|A-150]]		[[Category:C-TMS Modules\|A-150]]
	[[Category:C-TMS User Guide\|BA-150]]		[[Category:C-TMS User Guide\|BA-150]]
			[[Category:TEST\|A-150]]

Anw: Minor correction

2024-05-09T15:11:28Z

Minor correction

← Older revision		Revision as of 17:11, 9 May 2024
Line 4:		Line 4:

	<center>[[Image:booking_1.jpg\|800px]]</center>		<center>[[Image:booking_1.jpg\|800px]]</center>


	== Key Functionality ==		== Key Functionality ==

	=== Auto Summary ===		=== Auto Summary ===
			Summarises SKU level demand that is to be delivered, from one location to another on a particular date, from the SKU level Product Quantity data into DU level Product Summary records. For example, 730 Non Perishable SKU’s may summarise into 8 Non Perishable Despatch Units. This results in 730 SKU level records being transposed by the Auto Summary function into a single manageable record of 8 DU’s. The demand that is summarised by the Auto Summary function can be supplied via a Bookings inbound interface file.

	Summarises SKU level demand that is to be delivered, from one location to another on a particular date, from the SKU level Product Quantity data into DU level Product Summary records. For example, 730 Non Perishable SKU’s may summarise into 8 Non Perishable Despatch Units. This results in 730 SKU level records being transposed by the Auto Summary function into a single manageable record of 8 DU’s. The demand that is summarised by the Auto Summary function can be supplied via a Bookings inbound interface file.

	=== Copy Bookings ===		=== Copy Bookings ===
			Enables Product Summary records to be copied from one schedule date to another. This allows data to be copied as contingency if the inbound Bookings interface fails and therefore no demand for a particular schedule date is received.

	Enables Product Summary records to be copied from one schedule date to another. This allows data to be copied as contingency if the inbound Bookings interface fails and therefore no demand for a particular schedule date is received.

	=== Manual Booking Manipulation ===		=== Manual Booking Manipulation ===
			Provides the facility to manually add, edit and delete Product Summary records. Enables Product Summary records to be manipulated to cater for situations where a Product Summary record may need to be, for example, deleted as a store is unable to receive its demand or edited to handle a late request by a store for increased demand.

	Provides the facility to manually add, edit and delete Product Summary records. Enables Product Summary records to be manipulated to cater for situations where a Product Summary record may need to be, for example, deleted as a store is unable to receive its demand or edited to handle a late request by a store for increased demand.

	=== Manual Advance & Left Off’s ===		=== Manual Advance & Left Off’s ===
			Allows demand to be advanced or brought forward from one day to another or demand that could not be delivered, i.e. left off, to be added into the next days schedule. Complete flexibility is included to allow advances to be split from, and left off’s to be added to, one or more future schedules.

	Allows demand to be advanced or brought forward from one day to another or demand that could not be delivered, i.e. left off, to be added into the next days schedule. Complete flexibility is included to allow advances to be split from, and left off’s to be added to, one or more future schedules.

	=== Create Transport Instructions ===		=== Create Transport Instructions ===
			Creates Transport Instructions or Orders, including [[Crossdock]]’s, from one location to another so that delivery is performed within Slot time constraints imposed by the destination location. Each delivery Slot is examined in priority order and filled according to the following constraints: Slot/Trailer capacity, Slot/Product compatibilities, Product Temperature compatibilities, Order Delivery Time, Trip Depart Time and Product Picking Rates. Transport Instructions form the input to the scheduling process. However, Create Transport Instructions also handles Post Schedule Order and Trip Manipulation to cater for late planning scenarios.

			See [[Create Transport Instructions]] for more details.

	Creates Transport Instructions or Orders, including [[Crossdock]]’s, from one location to another so that delivery is performed within Slot time constraints imposed by the destination location. Each delivery Slot is examined in priority order and filled according to the following constraints: Slot/Trailer capacity, Slot/Product compatibilities, Product Temperature compatibilities, Order Delivery Time, Trip Depart Time and Product Picking Rates. Transport Instructions form the input to the scheduling process. However, Create Transport Instructions also handles Post Schedule Order and Trip Manipulation to cater for late planning scenarios.

	=== Auto Advance ===		=== Auto Advance ===
			Automation of manual advance process where a predetermined list of stores can be configured to receive advances at the press of a button. The function not only creates advance demand for a schedule but also creates the associated Orders to remove the need to recreate Transport Instructions.

	Automation of manual advance process where a predetermined list of stores can be configured to receive advances at the press of a button. The function not only creates advance demand for a schedule but also creates the associated Orders to remove the need to recreate Transport Instructions.

	=== Reverse Transport Instructions ===		=== Reverse Transport Instructions ===
			Reverses out Orders created by Create Transport Instructions. The mode in which Reverse TI’s is called dictates whether Unscheduled, Scheduled, Advance Only, all Orders or only a specific quantity of DU’s from Orders are reversed. Reversal of Transport Instruction’s gives flexibility to allow an entire inappropriate plan to be reversed and recreated with alternative reference data or just a specific RDC, store, product type and DU combination to be reversed if created in error or just no longer required.

	Reverses out Orders created by Create Transport Instructions. The mode in which Reverse TI’s is called dictates whether Unscheduled, Scheduled, Advance Only, all Orders or only a specific quantity of DU’s from Orders are reversed. Reversal of Transport Instruction’s gives flexibility to allow an entire inappropriate plan to be reversed and recreated with alternative reference data or just a specific RDC, store, product type and DU combination to be reversed if created in error or just no longer required.

	=== Variance Filter ===		=== Variance Filter ===
			This filter allows the records displayed in the Bookings screen to be restricted to those that have a discrepancy between the demand quantity and the quantity that was used to create Orders via Create TI’s. This allows a planner to easily and quickly identify any offending Product Summary records and subsequently determine why the demand has not flowed onto Orders, whether it be because there were no more appropriate Slots or violation of any other of the Create TI’s constraints.

	This filter allows the records displayed in the Bookings screen to be restricted to those that have a discrepancy between the demand quantity and the quantity that was used to create Orders via Create TI’s. This allows a planner to easily and quickly identify any offending Product Summary records and subsequently determine why the demand has not flowed onto Orders, whether it be because there were no more appropriate Slots or violation of any other of the Create TI’s constraints.

	=== Actuals Filter ===		=== Actuals Filter ===
			Allows the Bookings screen to be filtered to show Actuals against intended delivery quantities. Discrepancies between these two values can then be easily identified and any trends in the schedule derived and corrective action taken.

	Allows the Bookings screen to be filtered to show Actuals against intended delivery quantities. Discrepancies between these two values can then be easily identified and any trends in the schedule derived and corrective action taken.

	=== View Detail ===		=== View Detail ===

	Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..		Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..

Anw: Minor formatting change

2024-05-09T15:07:00Z

Minor formatting change

← Older revision		Revision as of 17:07, 9 May 2024
Line 3:		Line 3:
	Each Transport Instruction details the quantity of one or more compatible product types at DU level to be delivered from one location to another at a particular time on a particular date, rather than Product Quantity records which detail the quantity of each individual SKU, to be delivered from one location to another on a particular date.		Each Transport Instruction details the quantity of one or more compatible product types at DU level to be delivered from one location to another at a particular time on a particular date, rather than Product Quantity records which detail the quantity of each individual SKU, to be delivered from one location to another on a particular date.

	<center>[[Image:booking_1.jpg]]</center>		<center>[[Image:booking_1.jpg\|800px]]</center>

	== Key Functionality ==		== Key Functionality ==

Middletong at 15:02, 9 August 2011

2011-08-09T15:02:47Z

← Older revision		Revision as of 17:02, 9 August 2011
Line 3:		Line 3:
	Each Transport Instruction details the quantity of one or more compatible product types at DU level to be delivered from one location to another at a particular time on a particular date, rather than Product Quantity records which detail the quantity of each individual SKU, to be delivered from one location to another on a particular date.		Each Transport Instruction details the quantity of one or more compatible product types at DU level to be delivered from one location to another at a particular time on a particular date, rather than Product Quantity records which detail the quantity of each individual SKU, to be delivered from one location to another on a particular date.

	[[Image:booking_1.jpg]]		<center>[[Image:booking_1.jpg]]</center>

	== Key Functionality ==		== Key Functionality ==
Line 47:		Line 47:
	Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..		Enables the Product Quantity data to be viewed to determine how the Auto Summary process transposed many records into few. This view identifies the actual volumetric data, whether it be SKU or product type weight and volume that was actually used in the Auto Summary calculations. Spurious Volumetric data can then be corrected to prevent miscalculations in the future..

	~~== Tips & Tricks ==~~


	~~== Recent Changes ==~~
	[[Category:Order Management\|150]]		[[Category:Order Management\|150]]
	[[Category:C-TMS Modules\|A-150]]		[[Category:C-TMS Modules\|A-150]]
	[[Category:C-TMS User Guide\|BA-150]]		[[Category:C-TMS User Guide\|BA-150]]

Anw at 11:37, 11 May 2011

2011-05-11T11:37:07Z

← Older revision		Revision as of 13:37, 11 May 2011
Line 52:		Line 52:
	== Recent Changes ==		== Recent Changes ==
	[[Category:Order Management\|150]]		[[Category:Order Management\|150]]
			[[Category:C-TMS Modules\|A-150]]
			[[Category:C-TMS User Guide\|BA-150]]

Anw at 10:50, 11 May 2011

2011-05-11T10:50:48Z

← Older revision		Revision as of 12:50, 11 May 2011
Line 51:		Line 51:

	== Recent Changes ==		== Recent Changes ==
			[[Category:Order Management\|150]]

← Older revision		Revision as of 08:26, 17 May 2024
Line 52:		Line 52:
	[[Category:C-TMS Modules\|A-150]]		[[Category:C-TMS Modules\|A-150]]
	[[Category:C-TMS User Guide\|BA-150]]		[[Category:C-TMS User Guide\|BA-150]]
			[[Category:TEST\|A-150]]