RFI Browser

Back  RFI # 339: Invalid ISA segment

Formal vs. Informal Help Informal Formal

Submitter

Robert Huffman

Description

What is the preferred / mandated response to an incoming transaction that has errors in the ISA segment making it unreadable. An error such as using one element delimiter between the first and second elements and a different element delimiter between other elements. It would be like receiving a letter at home where the send to and return addresses are in Old Latin. How can you respond? Should one throw it in the trash and wait for the sender to call asking why their transaction wasn't processed? When they call you can explain that the ISA was unreadable and you couldn't do anything with it. In some cases (maybe many) you will know the route the transaction came in from and could then craft a proprietary response.

Submitter Assigned Keywords

ISA Error

Response

This issue is explicitly addressed in all guides in appendix B. While its usage is not mandated by the guides, the ASC X12 response to an invalid Interchange Header (ISA segment) is the TA1 segment. For the specific error mentioned, a second value for the data element separator in the ISA, that second separator would not be seen as a separator, but as a part of the prior element. That element should be the cause of the error and would be invalid as being too long.

The TA1 segment can be returned with just an Interchange envelope or in combination with other business transactions as illustrated below:

ISA...
TA1...
IEA

-or-

ISA...
TA1...
GS...
ST...
...
SE...
GE...
IEA...

The TA1 segment does not have to be immediately after the ISA, but must not be between a GS and GE envelope.
Submission 10/18/2005
Status Date 10/18/2005
Status F - Final
Primary References
Document 004010X092A1
SectionB
Page3
Set ID270