288788 - Revision history

DuttonT: /* Import into EFX (at brief) */

2011-07-06T10:40:25Z

Import into EFX (at brief)

← Older revision		Revision as of 12:40, 6 July 2011
Line 76:		Line 76:


	[[Image:288788_2a]]		[[Image:288788_2a.png]]

DuttonT: /* Import into EFX (at de-brief) */

2011-07-06T10:39:40Z

Import into EFX (at de-brief)

← Older revision		Revision as of 12:39, 6 July 2011
Line 416:		Line 416:
	The EFX debrief schema XSD is included below		The EFX debrief schema XSD is included below

	[[Image:~~288788_2~~.png]]		[[Image:288788_6a.png]]


	An example of the XML is shown below		An example of the XML is shown below

	[[Image:~~288788_1~~.png]]		[[Image:288788_7a.png]]


Line 494:		Line 494:

	\|}		\|}


	== Other Comments ==		== Other Comments ==

DuttonT: /* Import into EFX (at de-brief) */

2011-07-06T10:38:10Z

Import into EFX (at de-brief)

← Older revision		Revision as of 12:38, 6 July 2011
Line 397:		Line 397:


	[[Image:]]		[[Image:288788_5a.png]]

	A trip import message will be created for each order at trip COMPLETED status and only one order will be sent in each message.		A trip import message will be created for each order at trip COMPLETED status and only one order will be sent in each message.
Line 405:		Line 405:

	This means that once the first pre-advise for the order is sent as described in section 2.1 and the status and EFX number received described in section 2.2, all following messages from C-TMS to EFX will contain the unique EFX number.		This means that once the first pre-advise for the order is sent as described in section 2.1 and the status and EFX number received described in section 2.2, all following messages from C-TMS to EFX will contain the unique EFX number.


	== Import into EFX (at de-brief) ==		== Import into EFX (at de-brief) ==

DuttonT: /* Export from EFX */

2011-07-06T10:37:26Z

Export from EFX

← Older revision		Revision as of 12:37, 6 July 2011
Line 310:		Line 310:
	C-TMS will be developed to read in the XML export message exactly as created by EFX and the assumption is that ESI Link will push the files to the C-TMS server. The EFX schema XSD is included below.		C-TMS will be developed to read in the XML export message exactly as created by EFX and the assumption is that ESI Link will push the files to the C-TMS server. The EFX schema XSD is included below.

	[[Image:]]		[[Image:288788_3a.png]]

	An example of the XML file is shown below		An example of the XML file is shown below

	[[Image:]]		[[Image:288788_4a.png]]

	Note that the response message contains the status ACCEPTED and an EFX number. If for whatever reason EFX rejects the trip import message, the export message back to C-TMS will contain the value REJECTED. The interface errors form in C-TMS will allow any REJECTED messages to be identified.		Note that the response message contains the status ACCEPTED and an EFX number. If for whatever reason EFX rejects the trip import message, the export message back to C-TMS will contain the value REJECTED. The interface errors form in C-TMS will allow any REJECTED messages to be identified.
Line 381:		Line 381:

	\|}		\|}


	== Import into EFX (at de-brief) ==		== Import into EFX (at de-brief) ==

DuttonT: /* Import into EFX (at brief) */

2011-07-06T10:35:47Z

Import into EFX (at brief)

← Older revision		Revision as of 12:35, 6 July 2011
Line 62:		Line 62:
	* A carrier has been assigned to the trip (means the carrier code is not the value ‘EFX’ and the carrier is determined to be third party and not own fleet).		* A carrier has been assigned to the trip (means the carrier code is not the value ‘EFX’ and the carrier is determined to be third party and not own fleet).
	* A cost value is assigned to the trip		* A cost value is assigned to the trip


	'''(Note that to maintain the functionality to tender to EFX, in C-TMS the carrier code will be assigned to the value EFX for the trip temporarily and as the trip status changes to TENDERED, the import trip message will be generated. This process is assumed to be out of scope for Openfield). '''		'''(Note that to maintain the functionality to tender to EFX, in C-TMS the carrier code will be assigned to the value EFX for the trip temporarily and as the trip status changes to TENDERED, the import trip message will be generated. This process is assumed to be out of scope for Openfield). '''
Line 69:		Line 70:


	[[Image:]]		[[Image:288788_1a.png]]


Line 75:		Line 76:


	[[Image:]]		[[Image:288788_2a]]


Line 303:		Line 304:

	\|}		\|}


	== Export from EFX ==		== Export from EFX ==

DuttonT: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Develop EFX Solution|Reference=FS 288788 DK-8H2HQC |Version=1.1|Date=|Sysver=10.6|Client=DHL MTS}} == Client Requirement == '''Change R...

2011-07-06T10:33:18Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Develop EFX Solution|Reference=FS 288788 DK-8H2HQC |Version=1.1|Date=|Sysver=10.6|Client=DHL MTS}} == Client Requirement == '''Change R...

Show changes