Translator Error Messages
The translator report error messages are listed below by the last three digits of the message number and the error message text.
| Msg ID | Message Text | Explanation | Your Action |
|---|---|---|---|
| 100 | Mandatory Element Missing | An element that the translation object designated as "Mandatory" was not created in an Outbound document or was not received in an Inbound document. | Use the Segment/Record ID, Sequence, and Element
fields on the Translator Report to determine which mandatory element
in the document is missing. Outbound If the document was entered using the Document Editor, open the document and complete the missing field. If you imported the document into your system, delete the document and then import that document after the import file has been corrected. See the IBM® Sterling Gentran:Server® for Microsoft Windows User Guide for more information. Inbound Contact your trading partner and determine what action you should take. |
| 110 | Incorrect Element Format | An element was entered or received with an incorrect format. Some examples of incorrect format are: a numeric field that contains non-numeric characters, and a field that exceeds the maximum length or is less than the minimum length (as defined in the standard) and invalid dates. | Use the Segment/Record ID, Sequence, and Element
fields on the Translator Report to determine which element in the
document is invalid. Outbound Correct the data source. Inbound Contact your trading partner and determine what action you should take. |
| 120 | Too Many Components in Composite | A composite element in a document you received has more component elements (sub-elements) than allowed by the standard. | Use the Segment/Record ID, Sequence, and Element
fields on the Translator Report to determine which element in the
document is invalid. Outbound If the document was entered using the Document Editor, open the document and correct the invalid field. If you imported the document into your system, delete the document, correct the data, and then import that document again. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. Inbound Contact your trading partner and determine what action you should take. |
| 130 | Invalid Conditional Relationship | A conditional relationship in the document is not valid. | Use the translator report to determine where in
the document the error occurred. Outbound If the document was entered using the Document Editor, open the document and correct the conditional relationship. If you imported the document into your system, delete the document and then import that document again. Inbound Contact your trading partner and determine what action you should take. |
| 140 | Implicit Rule Failure | A validation rule set up against this field failed in the translator. Typically, this occurs when the Exclusive flag is set for a standard rule, and the field value does not match the data table. | Check the data value that you received against the valid data that is allowed for the field. |
| 200 | Mandatory Component Missing | A component (sub-element) of a composite element that the translation object designated as "Mandatory" was not created in an Outbound document or not received in an Inbound document. | Use the Segment/Record ID, Sequence, Element,
and Composite fields on the Translator Report to determine which mandatory
component in the document is missing. Outbound If the document was entered using the Document Editor, open the document and complete the missing field. If you imported the document into your system, delete the document and then import that document again. Inbound Contact your trading partner and determine what action you should take. |
| 210 | Incorrect Component Format | A component (sub-element) of a composite element that the translation object designated as "Mandatory" was entered (Outbound) or received (Inbound) with an incorrect format. Some examples of incorrect format are: a numeric field that contains non-numeric characters, and a field that exceeds the maximum length or is less than the minimum length (as defined in the standard). | Use the Segment/Record ID, Sequence, Element,
and Composite fields on the Translator Report to determine which element
in the document is invalid. Outbound If the document was entered using the Document Editor, open the document and correct the invalid field. If you imported the document into your system, delete the document, correct the data, and then import that document again. Inbound Contact your trading partner and determine what action you should take. |
| 220 | Component Delimiter | A component delimiter was encountered instead of the expected element. | Contact either/or your trading partner or the translation object creator and determine what action you should take. |
| 300 | Mandatory Segment | A segment that the translation object designated
as "Mandatory" was not created in an Outbound document or was not
received in an Inbound document. This error can be generated in a variety of circumstances. The most common is that the input data sequence does not correspond to the data sequence defined in the translation object used to translate the data. If this is the case, the information provided with the message may indicate a segment in the data. |
Use the Segment/Record ID field on the Translator
Report to determine which mandatory segment in the document is missing. Outbound If the document was entered using the Document Editor, open the document and key data into the fields that are necessary to generate the segment. If you imported the document into your system, delete the document, add the data that is necessary to generate the segment, and then import that document again. Inbound Contact your trading partner and determine what action you should take. |
| 310 | Invalid Loop Start/End Structure | An invalid Loop Start/Loop End was found in an Inbound document. | Use the information in the translator report to determine which LS/LE pairing is invalid. Contact your trading partner and determine what action you should take. |
| 315 | Invalid Segment or Record Structure | A segment (in an EDI file) or a record (in a positional flat file) in an inbound file did not match what the translation object was expecting. | From viewing the information in the translator report and viewing the "Raw EDI" interchange, determine which segment or record is invalid. Contact your trading partner to determine what action you should take. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. |
| 405 | Unknown Partner | An Interchange was received but the system cannot determine which partner sent it. | From viewing the information in the translator report and viewing the "Raw EDI" interchange, determine which partner sent you the interchange. If the partner is not listed on your system, create the partner and a relationship, and attach the interchange to that partner. If the partner already exists on your system, attach the interchange to that partner and then determine why the system did not automatically identify the partner. |
| 410 | Header/Trailer Control Numbers do not match | The control numbers on the header and trailer do not match, as specified by the standard. | Check the "Raw EDI" view to determine which control numbers are in the EDI file, and then contact your trading partner to determine what action you should take. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. |
| 415 | Control Total Incorrect | The EDI control total in the Segment Identified field of the translator report does not equal the value that was calculated by the Compliance Checker. | Check the "Raw EDI" view to determine what the control total should be, and then contact your trading partner to determine what action you should take. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. |
| 420 | Unknown Relationship | A document was received but the Partner Profile for that partner does not include a corresponding Inbound Relationship. | From the viewing the information in the translator report and viewing the "Raw EDI" interchange, determine which relationship the document requires and create that inbound relationship for the partner. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. |
| 460 | Invalid Test Mode Flag | The partner relationship was found but the test mode flag in the data did not match the test mode defined in the inbound partner relationship. | Change the test mode of the inbound partner relationship to match the test mode of the data. See the IBM Sterling Gentran:Server for Microsoft Windows User Guide for more information. Then, ask your trading partner to change the test mode of the data they are sending to match that defined by the inbound relationship. |