Anw: /* CALIDUS EPOD Export Mechanism */

2013-03-20T11:28:42Z

CALIDUS EPOD Export Mechanism

← Older revision		Revision as of 13:28, 20 March 2013
Line 427:		Line 427:

	The files to be picked up will be named as follows:		The files to be picked up will be named as follows:
	* <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.~~csv~~		* <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.xml
	where		where
	* <SENDER> is the system sending the file - expected to be "epod"		* <SENDER> is the system sending the file - expected to be "epod"

Anw: v0.4 - amendments following supplier discussions

2013-02-20T10:58:09Z

v0.4 - amendments following supplier discussions

← Older revision		Revision as of 12:58, 20 February 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|EPOD Vigo Interface}}		{{#vardefine:Doc_Title\|EPOD Vigo Interface}}
	{{#vardefine:Version\|0.3}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|~~18th~~ February 2013}}		{{#vardefine:Date\|20th February 2013}}
	{{#vardefine:Reference\|305796}}		{{#vardefine:Reference\|305796}}
	{{#vardefine:Year\|2013}}		{{#vardefine:Year\|2013}}
Line 39:		Line 39:
	* Sending of data to ''CALIDUS'' ePOD will be through a new Partnerlink CSV format.		* Sending of data to ''CALIDUS'' ePOD will be through a new Partnerlink CSV format.
	* Receiving data from ''CALIDUS'' ePOD will be through the OBS XML format.		* Receiving data from ''CALIDUS'' ePOD will be through the OBS XML format.
	* The mechanism of sending and receiving data will be through Flat File transfer via ~~FTP.~~		* The mechanism of sending and receiving data will be through Flat File transfer via a shared folder on the Vigo system
	* The sending of data to ''CALIDUS'' ePOD will be through a manual option within the Vigo system ("Send to ePOD").		* The sending of data to ''CALIDUS'' ePOD will be through a manual option within the Vigo system ("Send to ePOD").
	* The Vigo system must merge of Delivery and Collection manifests into a single Consolidated Manifest when sending data.		* The Vigo system must merge of Delivery and Collection manifests into a single Consolidated Manifest when sending data.
Line 66:		Line 66:
	* Customers		* Customers

	A number of actions are outstanding from this meeting regarding the production of this interface specification, as follows:		{{Note}} A number of actions are outstanding from this meeting regarding the production of this interface specification, as follows:
	* Partnerlink to provide a list of existing Partner Codes in use.		* Partnerlink to provide a list of existing Partner Codes in use.
	* Partnerlink to provide a document of the standard Reason Codes in use.		* Partnerlink to provide a document of the standard Reason Codes in use.
	* Partnerlink to update the spreadsheets (provided to map the import to and Export from ePOD) to indicate Vigo Table and Field Names, for inclusion in this document.		* Partnerlink to update the spreadsheets (provided to map the import to and Export from ePOD) to indicate Vigo Table and Field Names, for inclusion in this document.
	Until these actions are completed, the document will remain in draft form, unless authorised by the customer.		Until these actions are completed, the document will remain in draft form, unless authorised by the customer.

	<!-- NEW PAGE -->		<!-- NEW PAGE -->
	= Set-up =		= Set-up =
Line 76:		Line 77:
	== Pre-requisites ==		== Pre-requisites ==
	* A working Vigo TMS and ''CALIDUS'' EPOD system must be in place.		* A working Vigo TMS and ''CALIDUS'' EPOD system must be in place.
	* The two systems must be able to connect via ~~FTP~~, either through an internet or LAN connection.		* The two systems must be able to connect via a shared folder, either through an internet or LAN connection. This must be accessible directly, without user and password information, through a shared user-name on the two servers or domain. This will be co-ordinated and configured by the Partnerlink IT team.

	== Menu Structure ==		== Menu Structure ==
Line 116:		Line 117:
	<tr><td>3</td><td>Reference 2</td><td>C</td><td>16</td><td>Ref2</td><td> </td></tr>		<tr><td>3</td><td>Reference 2</td><td>C</td><td>16</td><td>Ref2</td><td> </td></tr>
	<tr><td>4</td><td>Reference 3</td><td>C</td><td>16</td><td>Ref3</td><td> </td></tr>		<tr><td>4</td><td>Reference 3</td><td>C</td><td>16</td><td>Ref3</td><td> </td></tr>
	<tr><td>5</td><td>PartnerJobID</td><td>C</td><td>14</td><td>tracking_code</td><td>Is used to form the pallet ID of the pallets to be delivered (this field plus 2-digit count from 01 to Total Pallets)</td></tr>		<tr><td>5</td><td>PartnerJobID</td><td>C</td><td>14</td><td>tracking_code</td><td>Is used to form the pallet ID of the pallets to be delivered (this field plus 2-digit count from 01 to Total Pallets). Stored in new reference field.</td></tr>
	<tr><td>6</td><td>Job Date</td><td>C</td><td>8</td><td> </td><td> </td></tr>		<tr><td>6</td><td>Job Date</td><td>C</td><td>8</td><td> </td><td> </td></tr>
	<tr><td>7</td><td>Collection Name</td><td>C</td><td>30</td><td>col_name</td><td>Collection details - required for POD note (Consignor address)</td></tr>		<tr><td>7</td><td>Collection Name</td><td>C</td><td>30</td><td>col_name</td><td>Collection details - required for POD note (Consignor address)</td></tr>
Line 188:		Line 189:

	== Sending Mechanism ==		== Sending Mechanism ==
	The files can be		The files can be :
	* Sent by the Vigo TMS via FTP to an FTP service hosted by OBS		* Sent by the Vigo TMS via FTP to an FTP service hosted by OBS.
	* Pulled by ''CALIDUS'' ePOD via FTP from an FTP service hosted by Vigo		* Pulled by ''CALIDUS'' ePOD via FTP from an FTP service hosted by Vigo.
	* Copied by ''CALIDUS'' ePOD from a shared folder on the Vigo TMS		* Copied by ''CALIDUS'' ePOD from a shared folder on the Vigo TMS.
	* Copied by ''CALIDUS'' ePOD ~~from~~ a shared folder on the ~~''CALIDUS'' ePOD system~~.		* Copied by Vigo to a shared folder on ''CALIDUS'' ePOD.
			{{note}} It is expected that this transfer will be via file transfer though a shared folder on the Vigo TMS.

	Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).		Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).
Line 230:		Line 232:
	* Entered Trailer ID (at Job level).		* Entered Trailer ID (at Job level).
	* Clause information (per pallet)		* Clause information (per pallet)
			* External Reference ID (at Job level, containing the PartnerJobID.
	{{Note}} Trailer ID and Clause modifications are out of scope of the existing solution being provided, but have been added here so that the systems can be prepared to handle this functionality when it becomes available.		{{Note}} Trailer ID and Clause modifications are out of scope of the existing solution being provided, but have been added here so that the systems can be prepared to handle this functionality when it becomes available.

Line 292:		Line 294:
	<tr><td>EPL_SERVICE_LEVEL</td><td> </td><td> </td><td>N/A</td></tr>		<tr><td>EPL_SERVICE_LEVEL</td><td> </td><td> </td><td>N/A</td></tr>
	<tr><td>EPL_TRAILER_ID</td><td>To be used if the vehicle being used to fulfil the job is a Tractor unit, and a trailer ID has been entered by the user.</td><td> </td><td>x</td></tr>		<tr><td>EPL_TRAILER_ID</td><td>To be used if the vehicle being used to fulfil the job is a Tractor unit, and a trailer ID has been entered by the user.</td><td> </td><td>x</td></tr>
			<tr><td>EPL_EXT_REF</td><td>An external reference for the host system if required. For Partnerlink, this will be the PartnerJobID.</td><td>PartnerJobID</td><td>As Sent</td></tr>
	<tr><td>EPL_LAST_CHANGED_DATE</td><td> </td><td> </td><td>N/A</td></tr>		<tr><td>EPL_LAST_CHANGED_DATE</td><td> </td><td> </td><td>N/A</td></tr>
	<tr><td>EPL_LAST_CHANGED_TIME</td><td> </td><td> </td><td>N/A</td></tr>		<tr><td>EPL_LAST_CHANGED_TIME</td><td> </td><td> </td><td>N/A</td></tr>
Line 381:		Line 384:
	<EPL_SERVICE_LEVEL></EPL_SERVICE_LEVEL>		<EPL_SERVICE_LEVEL></EPL_SERVICE_LEVEL>
	<EPL_TRAILER_ID></EPL_TRAILER_ID>		<EPL_TRAILER_ID></EPL_TRAILER_ID>
			<EPL_EXT_REF></EPL_EXT_REF>
	<EPL_LAST_CHANGED_DATE>20120314</EPL_LAST_CHANGED_DATE>		<EPL_LAST_CHANGED_DATE>20120314</EPL_LAST_CHANGED_DATE>
	<EPL_LAST_CHANGED_TIME>9420098</EPL_LAST_CHANGED_TIME>		<EPL_LAST_CHANGED_TIME>9420098</EPL_LAST_CHANGED_TIME>
Line 413:		Line 417:

	== ''CALIDUS'' EPOD Export Mechanism ==		== ''CALIDUS'' EPOD Export Mechanism ==
	The files can be		The files can be:
	* ~~Sent~~ by the Vigo TMS via FTP to an FTP service hosted by OBS		* Pulled by the Vigo TMS via FTP from an FTP service hosted by OBS.
	* ~~Pulled~~ by ''CALIDUS'' ePOD via FTP ~~from~~ an FTP service hosted by Vigo		* Sent by ''CALIDUS'' ePOD via FTP to an FTP service hosted by Vigo.
	* Copied by ''CALIDUS'' ePOD ~~from~~ a shared folder on the Vigo TMS		* Copied by ''CALIDUS'' ePOD to a shared folder on the Vigo TMS.
	* Copied by ~~''CALIDUS'' ePOD~~ from a shared folder on the ''CALIDUS'' ePOD system.		* Copied by the Vigo TMS from a shared folder on the ''CALIDUS'' ePOD system.
			{{note}} It is expected that this transfer will be via file transfer though a shared folder on the Vigo TMS.

	Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).		Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).

	The files to be picked up will be named as follows:		The files to be picked up will be named as follows:

	* <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.csv		* <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.csv

	where		where

	* <SENDER> is the system sending the file - expected to be "epod"		* <SENDER> is the system sending the file - expected to be "epod"
	* <RECEIVER> is the system receiving the file - expected to be "vigo"		* <RECEIVER> is the system receiving the file - expected to be "vigo"
Line 447:		Line 449:
	\|Ref2=EPOD Export Mapping v0.5.xlsx		\|Ref2=EPOD Export Mapping v0.5.xlsx
	\|RefV2=0.5		\|RefV2=0.5
	\|RefDate2=25/01/2013		\|RefDate2=20/02/2013
	\|Ref3=EPOD XSD.zip		\|Ref3=EPOD XSD.zip
	\|RefV3=N/A		\|RefV3=N/A

Anw: v0.3 - amendments following supplier discussions

2013-02-18T12:07:39Z

v0.3 - amendments following supplier discussions

Show changes

Anw: v0.2 - Ready for customer review

2013-01-30T15:26:40Z

v0.2 - Ready for customer review

Show changes

FS 305796 EPOD Vigo Interface - Revision history

Anw: /* CALIDUS EPOD Export Mechanism */

Anw: v0.4 - amendments following supplier discussions

Anw: v0.3 - amendments following supplier discussions

Anw: v0.2 - Ready for customer review