|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: 997 reporting of a segment out of order
Here's a quick guess.
Version 004030 says that AK303 is to be used for the loop identifier in LS
/ LE loops, so you probably wouldn't fill it in anyway. If we work with
that assumption, then all you need to worry about is the SGF. I would lean
toward an AK304 value of "7" - segment not in proper sequence.
If you haven't already looked at it, I suggest consulting the 997 tutorial
for a more thorough answer.
Mike
At 08:02 PM 3/30/2004 -0800, Robbi McClane wrote:
>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]
>
>
>
>
>.
>Please use the following Message Identifiers as your subject prefix:
><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
>Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>Yahoo! Groups Links
>
>
>
>
---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
