Outbound acknowledgement contains invalid ISA11 in response to a bad Inbound ISA11 *|* -FE48F462F03A7876852579170046579D-

Per X12 standards the ISA11 for all Interchange versions 00402 and higher is considered a Repetition Separator. As such it must contain a special character that is different from all other delimiters used in the data.

Older Interchange versions typically contained the value 'U' in the ISA11 (called 'Interchange Control Standards Identifier' before 00402).

The IBM Sterling Gentran:Basic and Realtime Inbound editors (EBDI001 and EDIR001) evaluate the ISA11 based on the Interchange version in the ISA12.

If the ISA12 is 00402 or higher a GT114 (Invalid Repetition Separator) error will occur if the ISA11 is not a valid special character. This is a Warning error that produces a RC = 04 by default. This error alone does not prevent the document from processing.

In certain cases other related errors such as the GT113 (Transaction Contains Segment With Repeating Elements And Repetition Separator Is Invalid) might cause data suspension. When this happens the sender must correct the ISA11 and retransmit.

If you receive an invalid ISA11 and a 997 acknowledgement is created the Inbound Editor will create an outbound ISA11 with the same invalid value it received. While the Outbound Editors (EBDI002 and EDIR002) will generate a GT114 error this is normal behavior and as mentioned above does not prevent the 997 from being sent to your partner.