269356 - Revision history

Middletong at 11:49, 29 April 2010

2010-04-29T11:49:16Z

← Older revision		Revision as of 13:49, 29 April 2010
Line 232:		Line 232:

	\|}		\|}

	~~Back to [[CONPRD Release - 24/02/2010]]~~

Middletong at 10:21, 29 March 2010

2010-03-29T10:21:09Z

← Older revision		Revision as of 12:21, 29 March 2010
Line 232:		Line 232:

	\|}		\|}

			Back to [[CONPRD Release - 24/02/2010]]

Middletong: /* FUNCTIONAL DESCRIPTION */

2010-03-29T09:57:40Z

FUNCTIONAL DESCRIPTION

← Older revision		Revision as of 11:57, 29 March 2010
Line 155:		Line 155:

	The T_LOAD process contains hard-coded values for the location DHLBEHH. These will need to be changed to the new location ID to be confirmed by DHL. The following items will need to be changed.		The T_LOAD process contains hard-coded values for the location DHLBEHH. These will need to be changed to the new location ID to be confirmed by DHL. The following items will need to be changed.


	INT_XML_OUT2.PROCESS_XML_OUTBOUND_BEIG		INT_XML_OUT2.PROCESS_XML_OUTBOUND_BEIG
Line 170:		Line 171:

	The order confirmation section will be identified by the tag <ORDER_HEADER_CONFIRM>. Within this tag will be 5 further tags.		The order confirmation section will be identified by the tag <ORDER_HEADER_CONFIRM>. Within this tag will be 5 further tags.


	<CONF_DATE> Date of confirmation		<CONF_DATE> Date of confirmation

Middletong: /* FUNCTIONAL DESCRIPTION */

2010-03-29T09:57:18Z

FUNCTIONAL DESCRIPTION

← Older revision		Revision as of 11:57, 29 March 2010
Line 133:		Line 133:


	New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be		New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be:

Middletong: /* FUNCTIONAL DESCRIPTION */

2010-03-29T09:57:06Z

FUNCTIONAL DESCRIPTION

← Older revision		Revision as of 11:57, 29 March 2010
Line 134:		Line 134:

	New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be		New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be


	/webint/<dbname>/interface/MLS		/webint/<dbname>/interface/MLS
Line 148:		Line 149:

	/webint/<dbname>/interface/MLS/IN/failures		/webint/<dbname>/interface/MLS/IN/failures



	The inbound process (T_ORDER) will not require any changes as the procedure references the above parameters to determine the location and name of files for processing. Once these parameters have been changed the inbound flow should work as it does now.		The inbound process (T_ORDER) will not require any changes as the procedure references the above parameters to determine the location and name of files for processing. Once these parameters have been changed the inbound flow should work as it does now.

Middletong: /* FUNCTIONAL DESCRIPTION */

2010-03-29T09:56:37Z

FUNCTIONAL DESCRIPTION

← Older revision		Revision as of 11:56, 29 March 2010
Line 135:		Line 135:
	New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be		New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be

	/webint/<dbname>/interface/MLS		/webint/<dbname>/interface/MLS
	/webint/<dbname>/interface/MLS/IN
			/webint/<dbname>/interface/MLS/IN

	/webint/<dbname>/interface/MLS/IN/archive		/webint/<dbname>/interface/MLS/IN/archive

	/webint/<dbname>/interface/MLS/IN/failures		/webint/<dbname>/interface/MLS/IN/failures

	/webint/<dbname>/interface/MLS/OUT		/webint/<dbname>/interface/MLS/OUT

	/webint/<dbname>/interface/MLS/IN/archive		/webint/<dbname>/interface/MLS/IN/archive

	/webint/<dbname>/interface/MLS/IN/failures		/webint/<dbname>/interface/MLS/IN/failures

Line 148:		Line 154:

	INT_XML_OUT2.PROCESS_XML_OUTBOUND_BEIG		INT_XML_OUT2.PROCESS_XML_OUTBOUND_BEIG

	TRG_SCH_TRIP_XML_INT_BEIG		TRG_SCH_TRIP_XML_INT_BEIG

	TRG_SHA_XML_BEIG		TRG_SHA_XML_BEIG

	TRG_STS_XML_BEIG		TRG_STS_XML_BEIG


	The outbound file name will be changed from TMS_DAI to TMS_MLS.		The outbound file name will be changed from TMS_DAI to TMS_MLS.
Line 157:		Line 167:

	The order confirmation section will be identified by the tag <ORDER_HEADER_CONFIRM>. Within this tag will be 5 further tags.		The order confirmation section will be identified by the tag <ORDER_HEADER_CONFIRM>. Within this tag will be 5 further tags.

	<CONF_DATE> Date of confirmation		<CONF_DATE> Date of confirmation

	<CONF_USER> User		<CONF_USER> User

	<CONF_COMMENT_1> Y/N denoting whether T_LOAD file has been accepted.		<CONF_COMMENT_1> Y/N denoting whether T_LOAD file has been accepted.

	<CONF_COMMENT_2> Reason Code		<CONF_COMMENT_2> Reason Code

	<CONF_COMMENT_3> Description		<CONF_COMMENT_3> Description


	A new job will be created to process the incoming confirmation files. It is assumed that these file will go into the same inbound folder as the existing inbound order files.		A new job will be created to process the incoming confirmation files. It is assumed that these file will go into the same inbound folder as the existing inbound order files.

Middletong: /* Solution */

2010-03-29T09:54:52Z

Solution

Middletong: /* Solution */

2010-03-29T09:53:37Z

Solution

← Older revision		Revision as of 11:53, 29 March 2010
Line 31:		Line 31:
	The inbound file identifier will require to be re-named to MLS_TMS_BEIG_ORD_*		The inbound file identifier will require to be re-named to MLS_TMS_BEIG_ORD_*

	Changes to “T_LOAD” (TMS to WMS) outbound message flow:		'''Changes to “T_LOAD” (TMS to WMS) outbound message flow:'''

	Database object: PROCESS_XML_OUTBOUND_BEIG will need to be changed to reflect the new order pickup/startup location: formerly DHLBEHH, the new warehouse location needs to be advised.		Database object: PROCESS_XML_OUTBOUND_BEIG will need to be changed to reflect the new order pickup/startup location: formerly DHLBEHH, the new warehouse location needs to be advised.
	The outbound filename hardcoded into PROCESS_XML_OUTBOUND_BEIG will need to have it’s name suffix changed from TMS_DAI_... to TMS_MLS_...		The outbound filename hardcoded into PROCESS_XML_OUTBOUND_BEIG will need to have it’s name suffix changed from TMS_DAI_... to TMS_MLS_...
Line 37:		Line 38:
	(It is assumed by the estimate author that the warehouse location will not change again; hence the use of hardcoded values has been continued, rather than the use of dynamic or new system-parameter values.)		(It is assumed by the estimate author that the warehouse location will not change again; hence the use of hardcoded values has been continued, rather than the use of dynamic or new system-parameter values.)

	Changes to “T_ORDER” (WMS to TMS) inbound message flow:
			'''Changes to “T_ORDER” (WMS to TMS) inbound message flow:'''

	Database object: PROCESS_BEIG_ORD_XML_IN does not require to be changed to facilitate the new ‘MLS’ file name in regards to file input. The control of the inbound files is completed via name recognition, which is addressed in; “Changes to System Parameters” (previous). It is expected that a new SOURCE_SYSTEM of ‘WBWMSBEIG’ will replace the existing value of ‘HHWMSBEIG’. The value WBWMSBEIG will need to be added to MTS Standing Data.		Database object: PROCESS_BEIG_ORD_XML_IN does not require to be changed to facilitate the new ‘MLS’ file name in regards to file input. The control of the inbound files is completed via name recognition, which is addressed in; “Changes to System Parameters” (previous). It is expected that a new SOURCE_SYSTEM of ‘WBWMSBEIG’ will replace the existing value of ‘HHWMSBEIG’. The value WBWMSBEIG will need to be added to MTS Standing Data.

Line 50:		Line 53:

	Addition of email outbound message flow:		Addition of email outbound message flow:

	When a file (or files) are rejected by the Partner Logistics WMS and a corresponding T_CONF message is sent back with an “Accepted” = “N” flag on an order, an email will be collated with all the orders and errors for that inbound file handling process.		When a file (or files) are rejected by the Partner Logistics WMS and a corresponding T_CONF message is sent back with an “Accepted” = “N” flag on an order, an email will be collated with all the orders and errors for that inbound file handling process.

Line 55:		Line 59:

	It is envisaged that all the error messages for a particular T_CONF message will be bundled into one email message summarising an individual message run. Suggested format is as follows:		It is envisaged that all the error messages for a particular T_CONF message will be bundled into one email message summarising an individual message run. Suggested format is as follows:


	Ie:		Ie:

Middletong: /* Solution */

2010-03-29T09:52:02Z

Solution

← Older revision		Revision as of 11:52, 29 March 2010
Line 19:		Line 19:
	It is assumed for this estimate that data will be passed through the ESI data interface, and will be presented in OBS’s ‘standard’ XML format (xsd v2.3).		It is assumed for this estimate that data will be passed through the ESI data interface, and will be presented in OBS’s ‘standard’ XML format (xsd v2.3).

	Changes to System Parameters:		'''Changes to System Parameters:'''

	The following system Parameters will need to be changed from DAI to MLS:		The following system Parameters will need to be changed from DAI to MLS:

Middletong: /* FUNCTIONAL DESCRIPTION */

2010-03-29T09:51:09Z

FUNCTIONAL DESCRIPTION

← Older revision		Revision as of 11:51, 29 March 2010
Line 98:		Line 98:
	To accommodate the change from DAI to MLS the following parameter’s values will need to be changed from referencing DAI to referencing MLS. (Current values taken from CONTST). The changes required are highlighted in red.		To accommodate the change from DAI to MLS the following parameter’s values will need to be changed from referencing DAI to referencing MLS. (Current values taken from CONTST). The changes required are highlighted in red.

	~~<b/r>~~

	BEIG_INBOUND_PATH /webint/contst/interface/'''DAI'''/IN		BEIG_INBOUND_PATH /webint/contst/interface/'''DAI'''/IN
Line 113:		Line 113:

	INBOUND_BEIG_IDENTIFIER '''DAI'''_TMS_BEIG_ORD_*		INBOUND_BEIG_IDENTIFIER '''DAI'''_TMS_BEIG_ORD_*



	New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be		New inbound and outbound directories will be created on the server to store the received and sent files. The new folders will be

← Older revision		Revision as of 11:54, 29 March 2010
Line 66:		Line 66:

	To: PlanningFrozenHamsHall@dhl.com		To: PlanningFrozenHamsHall@dhl.com

	From: MTS_OWNER (Do Not Reply)		From: MTS_OWNER (Do Not Reply)

	Subject: T_CONF: MLS_TMS_BEIG_ORD_xxxxxxxxxxxxxxxxxx.XML		Subject: T_CONF: MLS_TMS_BEIG_ORD_xxxxxxxxxxxxxxxxxx.XML

	Trip MAN-00111111		Trip MAN-00111111

	Order yyy – Failed, Reason Code 00, Reason Text:		Order yyy – Failed, Reason Code 00, Reason Text:

	Order zzz – Failed, Reason Code 00, Reason Text:		Order zzz – Failed, Reason Code 00, Reason Text:

	Trip MAN-00222222		Trip MAN-00222222

	Order yyy – Failed, Reason Code 00, Reason Text:		Order yyy – Failed, Reason Code 00, Reason Text:

	Order zzz – Failed, Reason Code 00, Reason Text:		Order zzz – Failed, Reason Code 00, Reason Text:

	This is an automated email, please do not reply.		This is an automated email, please do not reply.


	'''Email 2'''		'''Email 2'''

	To: PlanningFrozenHamsHall@dhl.com		To: PlanningFrozenHamsHall@dhl.com

	From: MTS_OWNER (Do Not Reply)		From: MTS_OWNER (Do Not Reply)

	Subject: T_CONF: MLS_TMS_BEIG_ORD_yyyyyyyyyyyyyyyyyy.XML		Subject: T_CONF: MLS_TMS_BEIG_ORD_yyyyyyyyyyyyyyyyyy.XML

	Etc…		Etc…


	Only Trips with Failed Orders will be included in the email(s). Only failed orders will be displayed in the message.		Only Trips with Failed Orders will be included in the email(s). Only failed orders will be displayed in the message.