Orders Interface - Revision history

Anw: Initial Creation

2025-08-14T08:51:29Z

Initial Creation

← Older revision		Revision as of 10:51, 14 August 2025
Line 12:		Line 12:

	The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.

			=== Tesla Orders Details ===
			{{:EDI Errors - Tesla Orders Tab}}

	=== LogiNext Details ===		=== LogiNext Details ===

Anw: ER047-005 - 528318 - Added LogiNext information

2025-07-08T11:28:02Z

ER047-005 - 528318 - Added LogiNext information

← Older revision		Revision as of 13:28, 8 July 2025
Line 13:		Line 13:
	The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.

			=== LogiNext Details ===
			{{:Interface Errors - LogiNext Details}}
	[[Category:C-TMS Admin\|150]]		[[Category:C-TMS Admin\|150]]
	[[Category:C-TMS User Guide\|C-150]]		[[Category:C-TMS User Guide\|C-150]]
	[[Category:Interfaces]]		[[Category:Interfaces]]

Anw: Categorisation

2024-05-08T12:36:28Z

Categorisation

← Older revision		Revision as of 14:36, 8 May 2024
Line 1:		Line 1:
			{{Incomplete}}

	An FTP process has been created to transfer Order information from a source system into [[C-TMS]]. The orders arrive in CSV files and are processed into [[C-TMS]] with errors being reported to a new [[C-TMS]] screen for manual administration by the users.		An FTP process has been created to transfer Order information from a source system into [[C-TMS]]. The orders arrive in CSV files and are processed into [[C-TMS]] with errors being reported to a new [[C-TMS]] screen for manual administration by the users.

Anw: Categorisation

2024-02-16T09:38:19Z

Categorisation

← Older revision		Revision as of 11:38, 16 February 2024
Line 14:		Line 14:
	[[Category:C-TMS Admin\|150]]		[[Category:C-TMS Admin\|150]]
	[[Category:C-TMS User Guide\|C-150]]		[[Category:C-TMS User Guide\|C-150]]
			[[Category:Interfaces]]

Anw at 13:08, 11 May 2011

2011-05-11T13:08:55Z

← Older revision		Revision as of 15:08, 11 May 2011
Line 10:		Line 10:

	The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.


			[[Category:C-TMS Admin\|150]]
			[[Category:C-TMS User Guide\|C-150]]

Admin at 10:54, 17 November 2010

2010-11-17T10:54:05Z

← Older revision		Revision as of 12:54, 17 November 2010
Line 1:		Line 1:
	An FTP process has been created to transfer Order information from a source system into C-TMS. The orders arrive in CSV files and are processed into C-TMS with errors being reported to a new C-TMS screen for manual administration by the users.		An FTP process has been created to transfer Order information from a source system into [[C-TMS]]. The orders arrive in CSV files and are processed into [[C-TMS]] with errors being reported to a new [[C-TMS]] screen for manual administration by the users.

	Interface Errors screen (a new tab will be added for each new interface).		Interface Errors screen (a new tab will be added for each new interface).
Line 5:		Line 5:
	<center>[[Image:ord_int.jpg]]</center>		<center>[[Image:ord_int.jpg]]</center>

	The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[C-TMS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate C-TMS operation (DB) to process it.		The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[C-TMS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate [[C-TMS]] operation (DB) to process it.

	The interface is designed to be generic. C-TMS reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the C-TMS Interface Errors screen. If successfully extracted, the order is validated for loading into the C-TMS orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal C-TMS orders / trip processing etc.		The interface is designed to be generic. [[C-TMS]] reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the [[C-TMS]] Interface Errors screen. If successfully extracted, the order is validated for loading into the [[C-TMS]] orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal [[C-TMS]] orders / trip processing etc.

	The FTP interface is one way (from an external source to C-TMS). Errors displayed on the error screen are administered manually via contact between C-TMS and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to [[C-TMS]]). Errors displayed on the error screen are administered manually via contact between [[C-TMS]] and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.

Admin at 14:08, 12 November 2010

2010-11-12T14:08:42Z

← Older revision		Revision as of 16:08, 12 November 2010
Line 1:		Line 1:
	An FTP process has been created to transfer Order information from a source system into ~~MTS~~. The orders arrive in CSV files and are processed into ~~MTS~~ with errors being reported to a new ~~MTS~~ screen for manual administration by the users.		An FTP process has been created to transfer Order information from a source system into C-TMS. The orders arrive in CSV files and are processed into C-TMS with errors being reported to a new C-TMS screen for manual administration by the users.

	Interface Errors screen (a new tab will be added for each new interface).		Interface Errors screen (a new tab will be added for each new interface).
Line 5:		Line 5:
	<center>[[Image:ord_int.jpg]]</center>		<center>[[Image:ord_int.jpg]]</center>

	The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[~~MTS~~]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate ~~MTS~~ operation (DB) to process it.		The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[C-TMS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate C-TMS operation (DB) to process it.

	The interface is designed to be generic. ~~MTS~~ reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the ~~MTS~~ Interface Errors screen. If successfully extracted, the order is validated for loading into the ~~MTS~~ orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal ~~MTS~~ orders / trip processing etc.		The interface is designed to be generic. C-TMS reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the C-TMS Interface Errors screen. If successfully extracted, the order is validated for loading into the C-TMS orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal C-TMS orders / trip processing etc.

	The FTP interface is one way (from an external source to ~~MTS~~). Errors displayed on the error screen are administered manually via contact between ~~MTS~~ and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to C-TMS). Errors displayed on the error screen are administered manually via contact between C-TMS and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.

Crisfordm at 14:45, 30 December 2008

2008-12-30T14:45:02Z

← Older revision		Revision as of 16:45, 30 December 2008
Line 7:		Line 7:
	The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[MTS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate MTS operation (DB) to process it.		The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[MTS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate MTS operation (DB) to process it.

	The interface is designed to be generic. MTS reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the MTS [[Interface Errors]] screen. If successfully extracted, the order is validated for loading into the MTS orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal MTS orders / trip processing etc.		The interface is designed to be generic. MTS reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the MTS Interface Errors screen. If successfully extracted, the order is validated for loading into the MTS orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal MTS orders / trip processing etc.

	The FTP interface is one way (from an external source to MTS). Errors displayed on the error screen are administered manually via contact between MTS and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.		The FTP interface is one way (from an external source to MTS). Errors displayed on the error screen are administered manually via contact between MTS and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.

Crisfordm: New page: An FTP process has been created to transfer Order information from a source system into MTS. The orders arrive in CSV files and are processed into MTS with errors being reported to a new M...

2008-12-30T14:44:18Z

New page: An FTP process has been created to transfer Order information from a source system into MTS. The orders arrive in CSV files and are processed into MTS with errors being reported to a new M...

New page

An FTP process has been created to transfer Order information from a source system into MTS. The orders arrive in CSV files and are processed into MTS with errors being reported to a new MTS screen for manual administration by the users.

Interface Errors screen (a new tab will be added for each new interface).

<center>[[Image:ord_int.jpg]]</center>

The Interfacing team should provide the interface data, extracting the necessary order data from the source system, constructing it into a [[CSV]] format consisting of a record header, order header and order detail or details lines and forward it to [[MTS]] where its arrival triggers an upload process. Each file contains exactly one order and is validated for structure on arrival to the server before invoking the appropriate MTS operation (DB) to process it.

The interface is designed to be generic. MTS reads the header to determine the interface type before channelling it for processing. The [[CSV]] format is extracted into interface order header and interface order details tables. Errors during this upload halt processing and result in the error being written to the tables for viewing in the MTS [[Interface Errors]] screen. If successfully extracted, the order is validated for loading into the MTS orders tables. Errors are written to the interface table for viewing and the order is rolled back. Successes are committed to the orders tables and are available for normal MTS orders / trip processing etc.

The FTP interface is one way (from an external source to MTS). Errors displayed on the error screen are administered manually via contact between MTS and external systems and will either result in data changes or a resend of a corrected FTP file. The FTP file name is used as the interface identifier (int_record_id) enabling order records, interface table records and files to be traced back to their origins.