The X12 TA1 technical acknowledgment reports the status of the processing of an interchange header and trailer. When the ISA and IEA of the X12-encoded message are valid, a positive TA1 ACK is sent, whatever the status of the other content is. If not, TA1 ACK with an error code is sent.
The X12 TA1 technical acknowledgment reports the status of the processing of an interchange header and trailer. EDI Tools for .NET AckMan raises TA1 automatically and only if they had been requested by the sender (ISA14 was set to a positive number). Every interchange header will be analyzed and if a problem is found a TA1 will be raised immediately. The contents of an interchange will always be processed regardless of its status. Upon reaching the interchange trailer (or improper end of file or a new interchange header) it will be analyzed and TA1 will be raised if not previously raised. Trailer faults do not trigger interchange rejection and are only informational. Duplicate detection can be incorporated by providing an external delegate.
EDI Tools for .NET AckMan analyses each ISA header as it reads the EDI document along. If the ISA can be rejected, a TA1 is generated immediately without waiting for the IEA trailer.
The following table indicates which error codes specified by the X12 specification are supported in EDI Tools for .NET AckMan and which are unsupported. The values for TA104 are as follows:
A = Accept
E = Interchange accepted with errors
R = Interchange rejected/suspended
| Definition | TA104 | TA105 | Supported? |
|---|---|---|---|
| Success | A | 0 | Yes |
| The Interchange Control Numbers in the header ISA 13 and trailer IEA02 do not match | E | 1 | Yes |
| Standard in ISA11 (Control Standards) is not supported | E | 2 | Yes |
| The version of the controls is not supported | E | 3 | Yes |
| Segment Terminator is Invalid | R | 4 | No |
| Invalid Interchange ID Qualifier for Sender | R | 5 | Yes |
| Invalid Interchange Sender ID | E | 6 | Yes |
| Invalid Interchange ID Qualifier for Receiver | R | 7 | Yes |
| Invalid Interchange Receiver ID | E | 8 | Yes |
| Unknown Interchange Receiver ID | E | 9 | No |
| Invalid Authorization Information Qualifier value | R | 10 | Yes |
| Invalid Authorization Information value | R | 11 | Yes |
| Invalid Security Information Qualifier value | R | 12 | Yes |
| Invalid Security Information value | R | 13 | Yes |
| Invalid Interchange Date value | R | 14 | Yes |
| Invalid Interchange Time value | R | 15 | Yes |
| Invalid Interchange Standards Identifier value | R | 16 | Yes |
| Invalid Interchange Version ID value | R | 17 | No (uses 003 instead) |
| Invalid Interchange Control Number value | R | 18 | Yes |
| Invalid Acknowledgment Requested value | E | 19 | Yes |
| Invalid Test Indicator value | E | 20 | Yes |
| Invalid Number of Included Groups value | E | 21 | Yes |
| Invalid Control Structure | R | 22 | Yes |
| Improper (Premature) End-of-File (Transmission) | R | 23 | Yes |
| Invalid Interchange Content (e.g., Invalid GS segment) | R | 24 | Yes |
| Duplicate Interchange Control Number | R | 25 | Yes |
| Invalid Data Element Separator | R | 26 | No |
| Invalid Component Element Separator | R | 27 | Yes |
Comments
0 comments
Please sign in to leave a comment.