Constraints and Exceptions - EDI Order Processing

The following points should be noted concerning deconstruction of Tradacoms messages. If these limit your use of the system, then we may be able to extend the application to resolve them for you. These restrictions

¨We do not believe there are any restrictions on the size of EDI file that the system can process. Some service providers limit the size of messages that they can pass on to you.

¨There are a few fields where we have restricted the size of data that we can handle, due to certain present internal constraints. Only if a trading partner may send data that exceeds the limits should you need to ask for our help.

It is not thought that these constraints will create any difficulties in current user environments.The data items concerned are as follows:

Segment Element Name TRADACOM Datafile Maximum Maximum

SDT VATN :Alphanumeric VAT Reg No 17 10

CDT CIDN :Customer ID allocated by supplier 17 –

VATR :Alphanumeric VAT Reg No 17 10

DNA SEQA First level sequence number 10 4

RTEX :Application text (all four) 40 12

OLD SEQA First level sequence number 10 4

SPRO :Supplier code for traded unit 30 12

CPRO :Customer’s item code 30 12

UNOR Consumer units in traded units 15 10

:Ordering measure 10.3 5.3

(can extend to 7.3 by using J-type field)

OQTY Number of traded units ordered 15 10

:Total measure ordered 10.3 5.3

(can extend to 7.3 by using J-type field)

OUCT Unit cost price 10.4 4.4

(can extend to 6.4 by using J-type field)

TDES Traded unit description 1 40 39

:Traded unit description 2 40 10

SCRF Specification number 17 10

:Contract number 17 –

DNB SEQA First level sequence number 10 4

SEQB Second level sequence number 10 4

RTEX :Application text (all four) 40 12

It is not thought that these constraints will create any difficulties in the present environment, but please check with your customers, particularly with respect to the DNA and DNB segment data if used.

¨Although the DNA segment data from the ORDHDR message is extracted and can be printed on the validation report and on the copy orders (if the systems constants flag is set to "1”) it is not available to be passed to the Datafile Software order processing system.

¨The DNA and DNB segment data from the ORDERS messages is available to be passed to Datafile.If you want to use this data from your customers, then don’t forget to switch on printing this data on copy orders (see System Constants Maintenance option under System Maintenance menu).

¨Some customers send the RSGRSG reconciliation message at the end of each EDI message files.Its purpose is to act as an end-of-file marker for the message file, duplicating the customer message reference and supplier EAN as a check that the file was received intact. Datafile Software creates an entry in the orders file for this message, but does not use it for any validation checks.