[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

997 reporting of a segment out of order

From: "Robbi McClane" <rmcclane@...>
Date: Wed Mar 31, 2004  4:02 am
Subject: 997 reporting of a segment out of order
Looking for opinions to help settle a debate:



If transaction set definition contained the following (indentation
represents loop contents):

ST

SGA segment a

SGB segment b, so on....

LOOPA

SGC

SGD

LOOPB

SGE

SGF

SE



If the input data consisted of:



ST

SGA

SGB

LOOPA

SGC

SGF <<< invalid placement

LOOPB

SGE

SE



Would you expect the 997 to report:

AK3*SGF*6*LOOPA*7 Invalid Placement SGF found in LoopA

or

AK3*SGF*6*LOOPB*7 Invalid Placement LoopB/SGF (assumes that if
transaction set definition contained multiple SGFs that you can

identify that this SGF is the one allowed for use in LoopB)

or

AK3*SGF*6*LOOPA*2 Unexpected SGF found in Loop A





[Non-text portions of this message have been removed]




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.