Skip to Content

Tradacoms ORDERS Messages - EDI Order Processing

Datafile Software

Tradacoms ORDERS Messages - EDI Order Processing

*** ERROR *** Order type ­nnnnnot a valid Tradacoms order type

This indicates that the customer quoted an incorrect order type nnnn. Such an error should never occur, unless new order types are introduced for Tradacoms orders whose codes are not present on your table. Either enter the code in the table or refer back to the customer to find out what was intended. Mark the order for manual treatment. You will have to enter the order code in the general lookup file to allow this order to be archived, but should remove it afterwards.

*** ERROR *** This message is not for us! Check with customer

Supplier EAN is nnnnnnnnnnnnn

Somehow you have received a message intended for another supplier — or else you have opened a new branch but have not yet entered its EAN location code into the system. If the latter, then do so now. If the former, then remove the order using the Delete EDI Order from Pending File option from the Exception Procedures menu.

*** ERROR *** This message is from a new customer not on file

Customer EAN is nnnnnnnnnnnnn

You have received an order from a customer who is not yet recorded within the general lookup file.If you have marked the EAN code in the sales ledger record, then you have not run the global option that updates the general lookup file. If you prefer, you can enter the code directly into this file before re-validating orders.

*** ERROR *** Customer location EAN code not in ledger file

This is similar to the previous message, except that it refers to the EAN code for a customer location that is not yet in the general lookup file. Take the same corrective action as above.

*** WARNING *** Earliest delivery date dd/mm/yy already gone

This does not count as an error as such — it doesn’t prevent you passing the order through to the Datafile system — but notes that the delivery date required by the customer (earliest delivery date if earliest and latest are present) has already passed.

*** ERROR *** Neither EAN nor our product code quoted

The EAN and supplier product code data items are blank. It may be that this is a special order not quoting any product code, but at present the EDI order processing software does not cater for such a condition — please contact us about this. Since this error won’t go away, you’ll have to use the Delete EDI Order from Pending File option from the Exception Procedures menu.

Note

It is likely that the special DNA and DNB segments will be used to convey the information needed about this product. If so, you’ll need to switch on printing these segments — see System Constants Maintenanceunder System Maintenance above — and do another print of the order before deleting it.

*** ERROR *** Product EAN doesn’t appear in our stock file

The EAN product code is not recognised. If you have marked the EAN code in the stock file, then you have not run the global option that updates the general lookup file. If you prefer, you can enter the code directly into this file before re-validating orders — see System Maintenance options.

*** ERROR *** Line missing, duplicated, or out of sequence

This indicates that an OLD segment — represent an order detail line — is out of sequence. The most probable reason is that the message has not deconstructed correctly, and you may need to seek support help. It is almost certain that you should remove the order details using the Delete EDI Order from Pending Fileoption from the Exception Proceduresmenu.

*** ERROR *** Supposed to be nnnorder lines, but counted nnn

A check at the end of the order shows a difference between the number of order lines processed and the number of lines that were supposed to appear for the order. The probable cause of this error is that order lines have failed correctly to deconstruct, in which case the previous error is likely to have occurred on this order too. You’ll need support help to determine the cause of the problem, but almost certainly you must remove the EDI order details using the Delete EDI Order from Pending File option from the Exception Procedures menu.

** WARNING ** Sender’s reference in STX segment:

not same as in RSGRSG message:

** WARNING ** Recipient EAN code in STX segment:

not same as in RSGRSG message:

These two messages indicate that the RSGRSG message did not match the start of transmission STX segment, which it always should. They should never occur, and if they do, there would almost certainly be other error messages too. As such they don’t reject the message, but you should check to see what the problem was.

*** WARNING *** ERRORS FOUND. CORRECT AND REVALIDATE DATA ***

If any errors are found when deconstructing an EDI file, then none of the database records created from that file can be passed to the Datafile order processing system.Correct any errors that have occurred, and then re-validate the incoming orders.

  • Release ID: Standard