Brad,
I'm not so sure you do have your problem solved. Please pay attention to
William Kammerer's message regarding the correct nesting of segments within
the 855. The PO1 segment does NOT nest nor is it subordinate to the SAC
segment. Rather, the SAC segment appears in table 1 as the start of a loop
which includes and starts with the SAC segment and includes only the CUR
segment.
The PO1 segment starts the Table 2 loop which also has a nested loop
beginning with the SAC segment and including the CUR segment. Thus, the PO1
segment would NEVER be nested or subordinate to the PO1 segment.
Therefore, the possible example would not be as stated below, but would
rather begin with the PO1 segment followed by nested SAC segments (max use
of 25) followed by another iteration of the PO1 loop.
I would recommend you re-analyze your solution since it's probably not
compliant with nor correct as it regards the structure of the 855 PO
Acknowledgment Transaction Set.
Rachel
Hi Brad,
Glad you got it solved. Since you have solved it I am posting this message
on the mail list so no one else will continue to help you with it. That
will give closure to it on the mail list.
Glad to help,
Steve
At 05:43 PM 7/13/00 -0700, you wrote:
>Hi Steve:
>
>I really appreciate you taking the time to look at my problem and give a
>hand. Alas, I have finally gotten the desired result! I'm sorry my
>explanation was unclear, but your example is a correct assessment of what I
>was talking about. Thanks again!
>
>Brad
>
>-----Original Message-----
>From: Steve Bollinger [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, July 13, 2000 12:52 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Please Help !! XML/EDI LOOPS
>
>
>Hi Brad,
>
>I am fairly certain that I did not follow all you said. Perhaps an XML
>sample would help the communication of the problem. Is this sometimes like
>what you want?
>
><POLines>
> <SAC value="SAC1">
> <PO1>....</PO1> (PO1s for SAC1)
> <PO1>....</PO1>
> </SAC>
> <SAC value="SAC2">
> <PO1>....</PO1> (PO1s for SAC2)
> <PO1>....</PO1>
> </SAC>
> <SAC value="SAC3">
> <PO1>....</PO1> (PO1s for SAC3)
> <PO1>....</PO1>
> </SAC>
></POLines>
>
>Can you explain the problem a little more fully perhaps in relation to a
>diagram or some visual representation?
>
>I think I lost your explanation at: "when there is a new occurrence of the
>SAC, this should stop the population of the remaining PO1's in the first
>SAC." What does "stop the population" mean exactly?
>
>Steve
>
>
>At 02:43 PM 7/12/00 -0700, [EMAIL PROTECTED] wrote:
>>Hi:
>>
>>I am an EDI analyst and have been working on an EDI2XML conversion for one
>>of our customers and have run into an issue that I cannot resolve. I am
>>hoping that someone has had similar experience and will share their
>solution
>>with me. I am converting an EDI 855 to and XML doc for our customer and
>>cannot resolve the following looping structure issue. We are passing a
>value
>>in the SAC segment that is to contain all PO1 segments, that immediately
>>follow, as child nodes of the SAC in the XML output. However, when there
is
>>a new occurrence of the SAC, this should stop the population of the
>>remaining PO1's in the first SAC. Only the PO1s that directly follow the
>>last SAC should be contained in the nearest upper level SAC. Of course the
>>element nodes have different names than the EDI, but this is the structure
>>that I am looking for. I am able to write individual and repeating nodes
>for
>>the SAC (parent), but ALL PO1s included in the entire 855 are populating
>the
>>XML output at all levels of the SAC: they are not looping at the proper
>>level. If anyone has a suggestion, I would greatly appreciate it.
>>
>>Thank You,
>>
>>Brad Williams
>>Advanced Marketing Services
>>EDI Coordinator
>>ph(858)457-2500x2355
>>fax(858)812-6480
>>[EMAIL PROTECTED]
>>
Steve Bollinger 408-853-8478
Cisco Systems GPS-IT XML/EDI Inventory Initiative
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
