282438 - Revision history

DuttonT: /* AUTHORISED BY */

2011-05-16T09:56:38Z

AUTHORISED BY

← Older revision		Revision as of 11:56, 16 May 2011
Line 1,513:		Line 1,513:
	\|-		\|-
	\| '''''Dave Meir'''''		\| '''''Dave Meir'''''
	\| c-TMS Product Manager		\| C-TMS Product Manager
	\|		\|

	\|}		\|}

DuttonT: /* Loading Process */

2011-05-16T09:56:03Z

Loading Process

← Older revision		Revision as of 11:56, 16 May 2011
Line 1,383:		Line 1,383:

	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"
	! Field
	! Type		{\| style="border-spacing:0;"
	! <center>Length</center>		\| style="background-color:#c0c0c0;border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Field'''</center>
	! Value		\| style="background-color:#c0c0c0;border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Type'''</center>
			\| style="background-color:#c0c0c0;border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Length'''</center>
			\| style="background-color:#c0c0c0;border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Value'''</center>
			\|

	\|-		\|-

DuttonT: /* Loading Process */

2011-05-16T09:53:51Z

Loading Process

← Older revision		Revision as of 11:53, 16 May 2011
Line 1,344:		Line 1,344:


	~~123456789012345678901~~

	~~X-DOCK LOADING .~~

	~~Trip: XXX-00000000~~

	~~Bay: 123456789012~~

	~~Trailer:XXXXXXXXXXXX~~

	~~Store: XXXXXXXXXXXX~~

	~~Total: 30~~

	~~Store: 10~~

	~~Scan:~~

	~~_____________________~~

	~~Item/Type~~

	~~12345678/PALLET~~

	~~12345677/BOXED~~

	~~<nowiki>*12345676/CARTON</nowiki>~~

	~~12345675/BOXED~~

	~~<nowiki>*12345674/CARTON</nowiki>~~

	~~12345673/BOXED~~

	~~12345672/CARTON~~

	~~UP DN~~

	~~F1-Conf F2-Damaged~~


Line 1,393:		Line 1,354:
	[[Image:282438_3.png]]		[[Image:282438_3.png]]

	~~123456789012345678901~~

	~~X-DOCK LOADING .~~

	~~Trip: XXX-00000000~~

	~~Bay: 123456789012~~

	~~Trailer:XXXXXXXXXXXX~~

	~~Store: XXXXXXXXXXXX~~

	~~Total: 30~~

	~~Store: 10~~

	~~Missing:F1-Conf CLR~~

	~~Item/Type~~

	~~PALLET3~~

	~~BOX1~~

	~~CARTON2~~


	~~F5-Detail UP DN~~


Line 1,430:		Line 1,363:
	[[Image:282438_4.png]]		[[Image:282438_4.png]]

	~~123456789012345678901~~

	~~X-DOCK LOADING .~~

	~~Trip: XXX-00000000~~

	~~Bay: 123456789012~~

	~~Trailer:XXXXXXXXXXXX~~

	~~Store: XXXXXXXXXXXX~~

	~~Total: 30~~

	~~Store: 10~~

	~~Missing:F1-Conf CLR~~

	~~Item/Type~~

	~~12345678/PALLET~~

	~~12345677/BOXED~~

	~~12345676/CARTON~~

	~~12345675/BOXED~~

	~~12345674/CARTON~~

	~~12345673/BOXED~~

	~~12345672/CARTON~~

	~~F5-Summary UP DN~~

DuttonT: /* Loading Process */

2011-05-16T09:51:16Z

Loading Process

← Older revision		Revision as of 11:51, 16 May 2011
Line 1,340:		Line 1,340:
	'''Sample screen showing items scanned'''		'''Sample screen showing items scanned'''

	[[Image:~~Example~~.~~jpg~~]]
			[[Image:282438_2.png]]


	123456789012345678901		123456789012345678901
Line 1,387:		Line 1,389:

	'''Summary of missing items'''		'''Summary of missing items'''
	[[Image:~~Example~~.~~jpg~~]]

			[[Image:282438_3.png]]

	123456789012345678901		123456789012345678901
Line 1,423:		Line 1,427:

	'''Detailed screen showing missing items'''		'''Detailed screen showing missing items'''
	[[Image:~~Example~~.~~jpg~~]]
			[[Image:282438_4.png]]

	123456789012345678901		123456789012345678901

DuttonT: /* Loading Process */

2011-05-16T09:47:47Z

Loading Process

← Older revision		Revision as of 11:47, 16 May 2011
Line 1,340:		Line 1,340:
	'''Sample screen showing items scanned'''		'''Sample screen showing items scanned'''

			[[Image:Example.jpg]]

	123456789012345678901		123456789012345678901
Line 1,386:		Line 1,387:

	'''Summary of missing items'''		'''Summary of missing items'''
			[[Image:Example.jpg]]

	123456789012345678901		123456789012345678901
Line 1,421:		Line 1,423:

	'''Detailed screen showing missing items'''		'''Detailed screen showing missing items'''
			[[Image:Example.jpg]]

	123456789012345678901		123456789012345678901
Line 1,546:		Line 1,549:
	\| style="border-top:none;border-bottom:0.035cm solid #000000;border-left:0.035cm solid #000000;border-right:0.035cm solid #000000;padding:0cm;"\| User doing the task		\| style="border-top:none;border-bottom:0.035cm solid #000000;border-left:0.035cm solid #000000;border-right:0.035cm solid #000000;padding:0cm;"\| User doing the task

			\|}

DuttonT: /* WCS Functional Description */

2011-05-16T09:44:45Z

WCS Functional Description

Show changes

DuttonT: /* Close DUs not Received or not Loaded */

2011-05-16T09:42:29Z

Close DUs not Received or not Loaded

← Older revision		Revision as of 11:42, 16 May 2011
Line 709:		Line 709:

	=== Close DUs not Received or not Loaded ===		=== Close DUs not Received or not Loaded ===
	A new batch job process will be develop to run each day at say midday to clear-up any DUs that have been manifested but not received 7 days after plan and any DUs that have been received but not loaded for delivery after 7 days. The batch job will clear the current location of the DU (if set) and create a failed to receive or failed to load reason code respectively.

	The 7 days elapsed will be a system parameter so the business can easily change this to be a longer or shorter elapsed time. The batch job can be configured to run at any time during the day or night as required

	From the document reviews, it has been decided to remove this function from scope. If a DU is received late, it will need to be loaded and POD’d and invoiced.		From the document reviews, it has been decided to remove this function from scope. If a DU is received late, it will need to be loaded and POD’d and invoiced.

DuttonT: /* Load Completion */

2011-05-16T09:41:47Z

Load Completion

← Older revision		Revision as of 11:41, 16 May 2011
Line 705:		Line 705:

	This message will update C-TMS and the status of the trip on the Load Management screen will change to loaded. A new loading status field will be added to the SCH_TRIP table with values PENDING, LOADING or LOADED.		This message will update C-TMS and the status of the trip on the Load Management screen will change to loaded. A new loading status field will be added to the SCH_TRIP table with values PENDING, LOADING or LOADED.

	~~On receipt of this message C-TMS will process through all DUs that were planned to be delivered on this trip grouped at PO level.~~

	~~The function will use the join through SCH_HAULAGE_ACTITIVITY (SHA), SCH_TRIP_STOP (STS) and SCH_TRIP (ST) to obtain all of the PO information for the delivery trip (ST.LOCATION_ID = SO.TO_LOC).~~

	Any DU that has not been load scanned successfully (i.e. still in the despatch lane) will be processed and a split order created to handle the left off. The splitting functionality will be as described above and the split order will be created as a status SCHED_COLL to facilitate loading on the next schedule.

	~~Note that if all DUs for a specific PO where not loaded then rather than splitting DUs off then the entire PO will be automatically unscheduled from the delivery trip.~~

	~~Any DUs that were not in the despatch lane (held in QC, GRID) or never received will be updated and a non-conformance created to represent failed to load for the planned trip.~~

	Any DUs left off from loading will retain their current location in the despatch lane. When loading against a delivery trip on the following operational schedule day, the splitting functionality described in section 3.5.2.2 above will manage the allocation of the DU to the new trip.		Any DUs left off from loading will retain their current location in the despatch lane. When loading against a delivery trip on the following operational schedule day, the splitting functionality described in section 3.5.2.2 above will manage the allocation of the DU to the new trip.

DuttonT: /* Load Update Messages from WCS to C-TMS - Process 841 */

2011-05-16T09:40:35Z

Load Update Messages from WCS to C-TMS - Process 841

Show changes

DuttonT: /* Loading Management - Creation of Load Release message 442 */

2011-05-16T09:39:21Z

Loading Management - Creation of Load Release message 442

← Older revision		Revision as of 11:39, 16 May 2011
Line 536:		Line 536:
	== Loading Management - Creation of Load Release message 442 ==		== Loading Management - Creation of Load Release message 442 ==
	A new C-TMS form will be developed called Loading Management to enable despatch lane assignment more easily and also to allow loading release messages to be sent to WCS as message code 442.		A new C-TMS form will be developed called Loading Management to enable despatch lane assignment more easily and also to allow loading release messages to be sent to WCS as message code 442.


	The form will be called from the menu system for authorised users. The user will select the trip schedule corresponding to the trips to be loaded on that shift. All the trips planned for store delivery will be displayed, one row per trip. The trips will be displayed sequentially in start time order so the earliest dispatches first in the list.		The form will be called from the menu system for authorised users. The user will select the trip schedule corresponding to the trips to be loaded on that shift. All the trips planned for store delivery will be displayed, one row per trip. The trips will be displayed sequentially in start time order so the earliest dispatches first in the list.


	The user can highlight any trip using a mouse click and this will display all the corresponding PO’s planned for the trip showing the PO store destination on the right hand side panel.		The user can highlight any trip using a mouse click and this will display all the corresponding PO’s planned for the trip showing the PO store destination on the right hand side panel.


	The screen view below shows the proposed layout of the form. The Bay Number heading will be labelled Despatch Lane. Users will be able to quickly assign despatch lanes to each trip and a default will be available. This default will be offered based on a new field that will be added to the store location form. This will allow the normal despatch lane for a store to be defined. A column will be introduced to display the carrier (showing either a carrier code or own fleet as planned). A further column will be introduced to allow the trailer number for own fleet to be displayed and entered.		The screen view below shows the proposed layout of the form. The Bay Number heading will be labelled Despatch Lane. Users will be able to quickly assign despatch lanes to each trip and a default will be available. This default will be offered based on a new field that will be added to the store location form. This will allow the normal despatch lane for a store to be defined. A column will be introduced to display the carrier (showing either a carrier code or own fleet as planned). A further column will be introduced to allow the trailer number for own fleet to be displayed and entered.


	The Send Load Check heading will be labelled Release Loading. The Order panel on the right hand side of the form will display the POs and store destinations and a count of the DUs planned and the total RPE planned per PO and an overall total – this will give visibility of the forecasted planned load volume per trip.		The Send Load Check heading will be labelled Release Loading. The Order panel on the right hand side of the form will display the POs and store destinations and a count of the DUs planned and the total RPE planned per PO and an overall total – this will give visibility of the forecasted planned load volume per trip.

			[[Image:282438_1.png]]
	[[Image:]]


	The Release Loading check box will be used to send a ‘442’ message to WCS. One or many trips can be released for loading by setting the appropriate check boxes and updating the input.		The Release Loading check box will be used to send a ‘442’ message to WCS. One or many trips can be released for loading by setting the appropriate check boxes and updating the input.


	An additional column will be included that will define the loading status of each trip and will display as PENDING, LOADING and LOADED. PENDING will be while waiting for a release loading message, LOADING once the release loading message sent and finally LOADED once the final 841 Load complete message is received by C-TMS from WCS.		An additional column will be included that will define the loading status of each trip and will display as PENDING, LOADING and LOADED. PENDING will be while waiting for a release loading message, LOADING once the release loading message sent and finally LOADED once the final 841 Load complete message is received by C-TMS from WCS.


	A right click menu option will be added that will allow the Trip Sheet to be printed. This menu will allow the summary or the detail version to be printed (the detail version includes the store delivery manifest pages).		A right click menu option will be added that will allow the Trip Sheet to be printed. This menu will allow the summary or the detail version to be printed (the detail version includes the store delivery manifest pages).


	When creating and sending the trip 442 load release message, the function will firstly check the APP_REC table to see if the MESSAGE_TYPE of ‘442’ is currently active (ACTIVE = ‘Y’).		When creating and sending the trip 442 load release message, the function will firstly check the APP_REC table to see if the MESSAGE_TYPE of ‘442’ is currently active (ACTIVE = ‘Y’).


	The process will check next that the trip is at the correct status to be sent (‘PLANNED’ or ‘ACCEPTED’) and that all of the required information (Despatch Lane, Carrier ID and for own fleet trips the Trailer ID) is populated.		The process will check next that the trip is at the correct status to be sent (‘PLANNED’ or ‘ACCEPTED’) and that all of the required information (Despatch Lane, Carrier ID and for own fleet trips the Trailer ID) is populated.


	The process will also derive a list of stores (STS.LOCATION_ID) that this trip is planned to deliver to by joining all of the STS records to GEO_LOCATION (GL) where GL.DEPOT = ‘BRANCH’ (i.e. only stores visited on this trip and not suppliers or RDC’s). These will be retrieved in STS.STOP_NO sequence so the message will advise WCS of the stop sequence and so the required loading sequence.		The process will also derive a list of stores (STS.LOCATION_ID) that this trip is planned to deliver to by joining all of the STS records to GEO_LOCATION (GL) where GL.DEPOT = ‘BRANCH’ (i.e. only stores visited on this trip and not suppliers or RDC’s). These will be retrieved in STS.STOP_NO sequence so the message will advise WCS of the stop sequence and so the required loading sequence.


	The data to be written to the 442 message and will be formatted to the layout based on the type declaration (see TYPE TY_WCS_TRIP_LOAD_PREADV in the new DP_RDT_FAST_LOAD package).		The data to be written to the 442 message and will be formatted to the layout based on the type declaration (see TYPE TY_WCS_TRIP_LOAD_PREADV in the new DP_RDT_FAST_LOAD package).



Line 624:		Line 611:

	\|}		\|}


	The 442 message will then be sent to WCS using the DP_WCS_IF.SEND_EDI_TO_WCS procedure.		The 442 message will then be sent to WCS using the DP_WCS_IF.SEND_EDI_TO_WCS procedure.


	Note that the message release function is NOT using the WCS_OUT_CONTROL table because the 442 message is defined at the same data level as the form (Trip Level) and so it will have minimum/no effect on the interactive speed of processing.		Note that the message release function is NOT using the WCS_OUT_CONTROL table because the 442 message is defined at the same data level as the form (Trip Level) and so it will have minimum/no effect on the interactive speed of processing.


	The Trip screens will be modified to remove the option to send the load check message or will need amending in line with all of the above changes.		The Trip screens will be modified to remove the option to send the load check message or will need amending in line with all of the above changes.


	== Load Update Messages from WCS to C-TMS - Process 841 ==		== Load Update Messages from WCS to C-TMS - Process 841 ==