Orders Interface

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).

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.