285989 - Revision history

DuttonT: /* Solution */

2011-06-28T13:35:36Z

Solution

← Older revision		Revision as of 15:35, 28 June 2011
Line 77:		Line 77:
	# IF KNOWN ITEM		# IF KNOWN ITEM
	## Deliver To will be derived from the Asset Details table.		## Deliver To will be derived from the Asset Details table.


	# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)		# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)
	# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)		# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)

DuttonT: /* Solution */

2011-06-28T13:35:00Z

Solution

DuttonT: /* Solution */

2011-06-28T13:34:37Z

Solution

DuttonT: /* Solution */

2011-06-28T13:33:42Z

Solution

DuttonT: /* Solution */

2011-06-28T13:32:42Z

Solution

← Older revision		Revision as of 15:32, 28 June 2011
Line 48:		Line 48:
	On receipt of POCPOD messages from Microlise the following processes will need to be added to existing logic:		On receipt of POCPOD messages from Microlise the following processes will need to be added to existing logic:

	#
	# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):		# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):
	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.
Line 71:		Line 71:
	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''

	#
	# No Customer references will be captured. A new unique OMS reference will be generated by C-TMS.		# No Customer references will be captured. A new unique OMS reference will be generated by C-TMS.
	# <nowiki>Customer will be derived using the Customer Group set up for the <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>		# <nowiki>Customer will be derived using the Customer Group set up for the <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>
Line 81:		Line 81:
	## Deliver To will be derived from the Asset Details table.		## Deliver To will be derived from the Asset Details table.

	#
	# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)		# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)
	# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)		# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)

DuttonT: /* Solution */

2011-06-28T13:32:03Z

Solution

← Older revision		Revision as of 15:32, 28 June 2011
Line 48:		Line 48:
	On receipt of POCPOD messages from Microlise the following processes will need to be added to existing logic:		On receipt of POCPOD messages from Microlise the following processes will need to be added to existing logic:

			#
	# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):		# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):
	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.
Line 71:		Line 71:
	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''

			#
	# No Customer references will be captured. A new unique OMS reference will be generated by C-TMS.		# No Customer references will be captured. A new unique OMS reference will be generated by C-TMS.
	# <nowiki>Customer will be derived using the Customer Group set up for the <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>		# <nowiki>Customer will be derived using the Customer Group set up for the <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>
Line 81:		Line 81:
	## Deliver To will be derived from the Asset Details table.		## Deliver To will be derived from the Asset Details table.

	# ~~<nowiki>Collect Times will be set to <STOP_ACTUAL_ARRIVAL_DATE> and <STOP_ACTUAL_DEPARTURE_DATE> sent in the Microlise Message.</nowiki>~~		#
	# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)		# Delivery Times will be set to the above + a parameterised number of Days i.e. 5 days. (MIC_DEL_DAY_OFFSET)
	# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)		# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)

DuttonT: /* Solution */

2011-06-28T13:31:07Z

Solution

← Older revision		Revision as of 15:31, 28 June 2011
Line 50:		Line 50:

	# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):		# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):

	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.

Line 60:		Line 59:

	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :


	## Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
Line 68:		Line 65:

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :


	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’

DuttonT: /* Solution */

2011-06-28T13:30:13Z

Solution

DuttonT: /* Solution */

2011-06-28T13:29:30Z

Solution

← Older revision		Revision as of 15:29, 28 June 2011
Line 50:		Line 50:

	# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):		# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):

	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.

Line 57:		Line 58:
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :

	#
	### Create New OMS reference on C-TMS		### Create New OMS reference on C-TMS
	### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
Line 67:		Line 69:
	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :

	#
	### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’

DuttonT: /* Solution */

2011-06-28T13:28:29Z

Solution

← Older revision		Revision as of 15:35, 28 June 2011
Line 51:		Line 51:
	# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):		# If known order and known asset is received, (i.e. known asset is being delivered or planned return collection):
	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.

	# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :		# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :
	## Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
Line 57:		Line 56:
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :
	## Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
Line 63:		Line 61:
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )

← Older revision		Revision as of 15:34, 28 June 2011
Line 52:		Line 52:
	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.

	## If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :		# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :
	### Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
	### Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.		## Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	### If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :
	#### Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
	####Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		##Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	#### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	#### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :
	### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''

← Older revision		Revision as of 15:33, 28 June 2011
Line 52:		Line 52:
	## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.		## Update Asset Table and Asset History accordingly, i.e. current location, arrival date/time.

	# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :		## If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :
	## Create New OMS reference on C-TMS		### Create New OMS reference on C-TMS
	## Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.		### Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		### If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :
	## Create New OMS reference on C-TMS		#### Create New OMS reference on C-TMS
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		####Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		#### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		#### Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip

	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''

← Older revision		Revision as of 15:30, 28 June 2011
Line 54:		Line 54:

	# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :		# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :
	### Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
	### Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.		## Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :


	### Create New OMS reference on C-TMS		## Create New OMS reference on C-TMS
	### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :


	### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	### Send Message to WCS to trigger unload at last DHL Depot on Trip		## Send Message to WCS to trigger unload at last DHL Depot on Trip

	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''
Line 82:		Line 82:
	# <nowiki>Collect From will be set to <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>		# <nowiki>Collect From will be set to <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>
	# IF UNKNOWN ITEM:		# IF UNKNOWN ITEM:
	### Deliver To will be set to a derived value based on the Collect From’s Customer Group, Envisaged this will be one of three DHL depots: DHLMILT, DHLHATF, DHLCIRN		## Deliver To will be set to a derived value based on the Collect From’s Customer Group, Envisaged this will be one of three DHL depots: DHLMILT, DHLHATF, DHLCIRN
	# IF KNOWN ITEM		# IF KNOWN ITEM
	### Deliver To will be derived from the Asset Details table.		## Deliver To will be derived from the Asset Details table.

	# <nowiki>Collect Times will be set to <STOP_ACTUAL_ARRIVAL_DATE> and <STOP_ACTUAL_DEPARTURE_DATE> sent in the Microlise Message.</nowiki>		# <nowiki>Collect Times will be set to <STOP_ACTUAL_ARRIVAL_DATE> and <STOP_ACTUAL_DEPARTURE_DATE> sent in the Microlise Message.</nowiki>
Line 90:		Line 90:
	# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)		# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)
	# IF UNKNOWN ITEM:		# IF UNKNOWN ITEM:
	### DU Type will be set to parameter MIC_DEF_DU_TYPE (‘LRC’)		## DU Type will be set to parameter MIC_DEF_DU_TYPE (‘LRC’)
	# IF KNOWN ITEM		# IF KNOWN ITEM
	### DU Type will be derived from the Asset Details table.		## DU Type will be derived from the Asset Details table.
	# DU Qty will be set to total number of assets received on message assumption is 1		# DU Qty will be set to total number of assets received on message assumption is 1
	# Schedule and RPE will be derived as per system standards		# Schedule and RPE will be derived as per system standards

← Older revision		Revision as of 15:28, 28 June 2011
Line 53:		Line 53:

	# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :		# If unknown order and known asset is received (i.e. known asset is being collected (ad-hoc)) :
	## Create New OMS reference on C-TMS		### Create New OMS reference on C-TMS
	## Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.		### Update Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip
	# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :		# If unknown order and unknown asset is received (i.e. unknown asset is being collected (ad-hoc)) :

	#		#
	## Create New OMS reference on C-TMS		### Create New OMS reference on C-TMS
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip

	# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :		# If known order and unknown asset is received (i.e. unknown asset is being collected on planned order (i.e. Return Collection) :

	#		#
	## Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )		### Create New Asset on Asset Table and Asset History accordingly, i.e. In Transit, departure date/time.(assumption is Location Id of Collection will drive Origin and therefore where the ‘To loc’. DU Type will be assumed to be ‘LRC’, and Asset Status will be set to status NEW. )
	## Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’		### Automatically schedule new order onto trip id within Microlise Message to the last DHL Depot on Trip. – This will leave order in a status of ‘SCHED_COLL’
	## Send Message to WCS to trigger unload at last DHL Depot on Trip		### Send Message to WCS to trigger unload at last DHL Depot on Trip

	'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''		'''The following assumptions have been made to collate all information required for creating new orders in C-TMS:'''
Line 80:		Line 80:
	# <nowiki>Collect From will be set to <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>		# <nowiki>Collect From will be set to <STOP_LOCATION_ID> sent in the Microlise Message.</nowiki>
	# IF UNKNOWN ITEM:		# IF UNKNOWN ITEM:
	## Deliver To will be set to a derived value based on the Collect From’s Customer Group, Envisaged this will be one of three DHL depots: DHLMILT, DHLHATF, DHLCIRN		### Deliver To will be set to a derived value based on the Collect From’s Customer Group, Envisaged this will be one of three DHL depots: DHLMILT, DHLHATF, DHLCIRN
	# IF KNOWN ITEM		# IF KNOWN ITEM
	## Deliver To will be derived from the Asset Details table.		### Deliver To will be derived from the Asset Details table.

	# <nowiki>Collect Times will be set to <STOP_ACTUAL_ARRIVAL_DATE> and <STOP_ACTUAL_DEPARTURE_DATE> sent in the Microlise Message.</nowiki>		# <nowiki>Collect Times will be set to <STOP_ACTUAL_ARRIVAL_DATE> and <STOP_ACTUAL_DEPARTURE_DATE> sent in the Microlise Message.</nowiki>
Line 88:		Line 88:
	# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)		# Product Type will be defaulted to a system parameter: MIC_DEF_PRODUCT (‘AMBIENT’)
	# IF UNKNOWN ITEM:		# IF UNKNOWN ITEM:
	## DU Type will be set to parameter MIC_DEF_DU_TYPE (‘LRC’)		### DU Type will be set to parameter MIC_DEF_DU_TYPE (‘LRC’)
	# IF KNOWN ITEM		# IF KNOWN ITEM
	## DU Type will be derived from the Asset Details table.		### DU Type will be derived from the Asset Details table.
	# DU Qty will be set to total number of assets received on message assumption is 1		# DU Qty will be set to total number of assets received on message assumption is 1
	# Schedule and RPE will be derived as per system standards		# Schedule and RPE will be derived as per system standards
Line 104:		Line 104:

	The Order Creation process will also have to be modified so that when new assets are encountered they are generated automatically based on scan location = origin, selected type = Du Type, created by etc should be WCS user etc.		The Order Creation process will also have to be modified so that when new assets are encountered they are generated automatically based on scan location = origin, selected type = Du Type, created by etc should be WCS user etc.


	== Scope ==		== Scope ==