Chuck,

A couple of comments: First of all, what you have depicted below is not a
transaction; rather it's an interchange. Thus the rules for an interchange
are that it must begin with the ISA segment and end with the IEA segment.
Enclosed within an interchange are functional groups (GS/GE) of transactions
(ST/SE). Optionally, the TAI Interchange Acknowledgment Segment can also be
returned properly enclosed within an interchange (ISA/IEA). Thus, what
you've depicted below is correct.

I recommend you reference the X12.5 Interchange Control Standard, portions
of which I've inserted.

3.5 Order of Control Segments
The interchange prepared by the interchange sender shall occur in the order
as listed in Figure 3. (See
explanations of field heading that follow figure 4.)
Seg. ID         Name                            Req. Des.               Max  Use
ISA             Interchange Control Header      M                       1
ISB             Grade of Service                O                       1
ISE             Deferred Delivery Request       O                       1
TA1             Interchange Acknowledgment      O                       >1
-               Functional Groups (see note)    O                       99,999
IEA             Interchange Control Trailer     M                       1
Figure 3: Order of the Interchange Segments for Interchange Sender

While the use of the TAI is not typical for many EDI implementers, it's juse
is normal and in compliant with the standard. If your software is abending
on this sequencing of control segments, then it doesn't know what the
standard is. The originator of this interchange has sequenced the segments
correctly. Therefore, it's extremely useful to use the actual X12 Standards
as a resource to resolve these kinds of issues with trading partners and
your software vendor. If you don't have access to them, you should get them
and become familiar with them.

Rachel

|
|The following 997 was received by a client of mine. Can anyone please
|comment as to the legality of this 997, specifically with
|regard to the TA1
|segment? I'm not referring to common usage..I realize that
|including a TA1
|is not at all 'normal'. My problem is that my software is
|abending with an
|error message of 'Segment out of sequence' and the Support
|folks are saying
|that the TA1 segment does not go between the ISA and GS, which I really
|don't believe. I guess I'm looking for verification that this
|transaction is
|technically correct, and I appreciate any responses.
|
|ISA*00*          *00*          *12*99999999       *01*009999999
|*000724*0817*U*00400*000000304*0*P*>
|TA1*000000012*000724*0847*A*000
|GS*FA*999999999*999999999*20000724*0817*3*X*004010
|ST*997*000000003
|AK1*IN*72408748
|AK2*810*0011
|AK5*A
|AK2*810*0012
|AK5*A
|AK9*A*2*2*2
|SE*8*000000003
|GE*1*3
|IEA*1*000000304
|
|Chuck Boucos
|Willow Farm Solutions
|http://www.willowfarmsolutions.com
|
|=======================================================================
|To signoff the EDI-L list,  mailto:[EMAIL PROTECTED]
|To subscribe,               mailto:[EMAIL PROTECTED]
|To contact the list owner:  mailto:[EMAIL PROTECTED]
|Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/

=======================================================================
To signoff the EDI-L list,  mailto:[EMAIL PROTECTED]
To subscribe,               mailto:[EMAIL PROTECTED]
To contact the list owner:  mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/

Reply via email to