Doug,
I was making the giant assumption that the software was reporting correctly.   
Guess this time the old adage did not hold true. 


Leah



________________________________
 From: Doug Anderson <[email protected]>
To: 'Leah Halpin' <[email protected]>; Brian Lehrhoff 
<[email protected]>; Stephen Martin <[email protected]>; edi-l 
<[email protected]> 
Sent: Tuesday, May 29, 2012 4:54 PM
Subject: RE: [EDI-L] Valid Sequence
 

Leah
 
Yes, in the header
your example is correct, however, in the PO1 loop it is not
always correct.  While there are multiple MSG segments
within multiple N9 loops, there is also a standalone MSG in position 289,
which follows the TD5 in position 250.  There is no N9 (loop or otherwise)
between the TD5 in position 250 and the MSG in position 289.  And the MSG
can be followed by a valid N1 segment in position 350.
 
So.. the error
message could be valid or not depending on where the TD5 - MSG -N1 sequence
appears in the data stream.
 
As it turns out
Stephen did send the entire segment listing, and the error message is indeed
valid as the sender failed to include the N9 segment.
 
Doug
 
 
-----Original Message-----
>From: Leah Halpin [mailto:[email protected]]
>Sent: Tuesday, May 29, 2012 3:41 PM
>To: Brian Lehrhoff; Stephen Martin; edi-l
>Subject: Re: [EDI-L] Valid Sequence
>
> 
>And that's what MCM meant, "buried in" means that the MSG is not valid in this 
>position without the first segment of the loop in which it is "buried", in 
>this case, the N9.  This is not a valid structure as is.
>
>This
  would be
  valid:
>
>...
>TD5
>N9
>MSG
>N1
>...
>
>Leah
>
>________________________________
>From:
  Brian Lehrhoff <[email protected]>
>To:
  Stephen Martin <[email protected]>; Brian Lehrhoff 
<[email protected]>; edi-l <[email protected]> 
>Sent: Tuesday, May 29, 2012 2:26 PM
>Subject: Re: [EDI-L] Valid
  Sequence
>
>
>  
>according to the X12 spec, that's a valid
  document.  the MSG is buried in the N9 loop, but it sits 
>
>right
  between the TD5 and N1 in the header.  i'd check your maps and see if the
  mapper deleted
>the unused segments (as they usually do) and now this is a
  used segment.  should be easy to repair the
>map and put it
  back.
>
> 
>Brian Lehrhoff, EA ([email protected])
>Messaging
  Consultant 201-913-4506
>Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com
>Circular
  230 Notice is located at http://ea.brianlehrhoff.com/230notice.html
>
>________________________________
>From:
  Stephen Martin <[email protected]>
>To:
  Brian Lehrhoff <[email protected]>; edi-l <[email protected]> 
>Sent: Tuesday, May 29, 2012 1:48 PM
>Subject: RE: [EDI-L] Valid
  Sequence
>
>-          what version?
>
>ANSI
  X12 850 4010
>
>Stephen
>
>From: [email protected] [mailto:[email protected]] On Behalf Of Brian 
>Lehrhoff
>Sent: Tuesday, May 29, 2012 1:43 PM
>To: Stephen Martin;
  edi-l
>Subject: Re: [EDI-L] Valid Sequence
>
>what version?
>
>Brian
  Lehrhoff, EA ([email protected]<mailto:blehrhof%40cybernex.net>)
>Messaging
  Consultant 201-913-4506
>Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com
>Circular
  230 Notice is located at http://ea.brianlehrhoff.com/230notice.html
>
>________________________________
>From:
  Stephen Martin <[email protected]<mailto:Stephen.Martin%40gfi.com>>
>To:
  "EDI-L@yahoogroups. com 
([email protected]<mailto:EDI-L%40yahoogroups.com>)" 
<[email protected]<mailto:EDI-L%40yahoogroups.com>>
>Sent:
  Thursday, May 24, 2012 3:58 PM
>Subject: [EDI-L] Valid
  Sequence
>
>Hello,
>
>I have an EDI PO 850 sequence in this
  order:
>
>...
>TD5
>MSG
>N1
>...
>
>But I am receiving an out
  of sequence error.
>
>On removing the MSG segment ( adjusting segment
  count etc.. ) the message goes through.
>
>Where in the segment order
  would a MSG segment usually be
  placed?
>
>Thanks
>
>Stephen
>
>DISCLAIMER The information
  contained in this electronic mail may be confidential or legally privileged.
  It is for the intended recipient(s) only. Should you receive this message in
  error, please notify the sender by replying to this mail. Please do not read,
  copy, forward or store this message unless you are an intended recipient of it
  - unauthorized use of contents is strictly prohibited. Unless expressly
  stated, opinions in this message are those of the individual sender and not of
  GFI. While all care has been taken, GFI is not responsible for the integrity
  or the contents of this electronic mail and any attachments included within.
  (GFI2012)
>
>[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>
>
>Job postings are welcome, but for job postings or
  requests for work: <JOBS> IS REQUIRED in the subject line as a
  prefix.Yahoo! Groups Links
>
>[Non-text portions of this message have been
  removed]
>
>DISCLAIMER The information contained in this electronic mail
  may be confidential or legally privileged. It is for the intended recipient(s)
  only. Should you receive this message in error, please notify the sender by
  replying to this mail. Please do not read, copy, forward or store this message
  unless you are an intended recipient of it - unauthorized use of contents is
  strictly prohibited. Unless expressly stated, opinions in this message are
  those of the individual sender and not of GFI. While all care has been taken,
  GFI is not responsible for the integrity or the contents of this electronic
  mail and any attachments included within. (GFI2012)
>
>[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>
>
>Job postings are welcome, but for job postings or
  requests for work: <JOBS> IS REQUIRED in the subject line as a
  prefix.Yahoo! Groups Links
>
>[Non-text portions of this message have been
  removed]
>
>[Non-text portions of this message have been
  removed]
>
>
> 

[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>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to