ASC/X12 Reference
718 - Transaction Set Syntax Error Code

On this topic:

 

Technical Notes

  1. The 718 data element in a functional acknowledgment records any error found in the transaction set level. When the functional acknowledgment is enabled, the Transaction Set Response Trailer (AK5) data segment is created.  If error(s) are found, a 718 data element is created and each error is recorded in the data element.  The number of 718 data elements created depends on how much the AK5 is defined to hold.  If no errors are found, this data element is not present in the AK5 segment.
  2. When a syntax error is discovered by Framework EDI (FREDI), the error has a standard error code (SEC) relevant to the operation of FREDI only.  This SEC is mapped to one of the syntax error code below that is then eventually stored in the data element.

Standard Information

NOTE: This information is referenced from ASC/X12 and may not be current.  For the latest information please visit the ASC/X12 web site.

Code indicating error found based on the syntax editing of a transaction set.

CODE

 DESCRIPTION NOTE
1 Transaction Set Not Supported
2 Transaction Set Trailer Missing
3 Transaction Set Control Number in Header and Trailer Do Not Match
4 Number of Included Segments Does Not Match Actual Count
5 One or More Segments in Error
6 Missing or Invalid Transaction Set Identifier
7 Missing or Invalid Transaction Set Control Number
8 Authentication Key Name Unknown
9 Encryption Key Name Unknown
10 Requested Service (Authentication or Encrypted) Not Available
11 Unknown Security Recipient
12 Incorrect Message Length (Encryption Only)
13 Message Authentication Code Failed
15 Unknown Security Originator
16 Syntax Error in Decrypted Text
17 Security Not Supported
18 Transaction Set not in Functional Group
19 Invalid Transaction Set Implementation Convention Reference
23 Transaction Set Control Number Not Unique within the Functional Group
24 S3E Security End Segment Missing for S3S Security Start Segment
25 S3S Security Start Segment Missing for S3E Security End Segment
26 S4E Security End Segment Missing for S4S Security Start Segment
27 S4S Security Start Segment Missing for S4E Security End Segment