This is a difficult one. I can see the business case you are trying to satisfy but I am not sure that I would agree on the use of the APR segment as you have proposed. None of the data elements in the APR segment appear to fit the use of the segment as you have defined and you would need to get the application to generate a dummy references to hold the whole thing together, something that should be avoided at all cost if possible.
The only way around this (I think) is to repeat the LIN group, perhaps as sublines for each PRI-ALC combination. This might look as follows:
LIN+1++EAN1'
PIA
IMD
MEA
PAC
etc - all the descriptive data excluding PRI and ALC information
.....
.....
LIN+2++EAN1+1:1'
PRI
ALC
ALC
ALC
LIN+3++EAN1+1:1'
PRI
ALC
LIN+4++EAN1+1:1'
PRI
ALC
ALC
While there is a slight overhead in this approach (i.e., the LIN needs to be repeated) the advantages are that you keep the data which is to be related in clearly defined groups without needing to create artificial references.
Anyway, that is my AUS $0.2 worth. Hope that it helps.
Regards,
Gerry Owens
Xilinx
Georgia Blomberg wrote:
Dear EDI-L,We are mapping to the D.96A UN/EDIFACT PRICAT message and have come across
structural problems.We need to link one or many Allowances (ALCs) back to one specific price
(PRI loop occurrence). However, the Allowances loop (ALC) is not nested
inside the Pricing loop (PRI), which means we must define an explicit link
between ALC and PRI loop (something like an SGP segment which links GIDs to
EQDs, for those familiar with shipping/container messaging).We had been using ALC.7160 to carry a "price cross reference", made up of
concatenated fields from the specific "parent" PRI segment, but there are
some cases in which this price cross reference calculates out to be the same
for different PRI loops. What we really need is a unique reference to link
particular ALCs to one particular PRI segment, and one only.We have thought of putting a sequential counter in the APR segment, which
itself occurs once only in the PRI loop, then repeating it in its associated
ALC(s) to link those ALC(s) back to the parent PRI via this "cross
reference" (see example below, please excuse syntax):PRI+......
APR+123....
PRI+...
APR+124....
PRI+...
APR+125ALC+++123
ALC+++123
ALC+++123
ALC+++124
ALC+++124
ALC+++125Suggested example above links those ALC segments (123) with the PRI loop
occurrance containing APR(123), ALC(124) with PRI occurrence 124 etc.Can anyone assist with an opinion on this suggestion above or an alternative
you may have tried??!Any comments much appreciated.
Regards
Georgia Blomberg
-------------------------------------------------------
Project Manager
EAN Australia, Locked Bag 10 Oakleigh, 3166
National Tel.No: 1300 366 033
Fax No: 03 9569 1525
Mobile No: 0407 821 766
URL: www.ean.com.au
--------------------------------------------------------------------=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
begin:vcard n:Owens;Gerry tel;fax:+ 353 1 403 2131 tel;work:+ 353 1 403 2158 x-mozilla-html:FALSE url:http://www.xilinx.com org:Xilinx version:2.1 email;internet:[EMAIL PROTECTED] title:EDI Projects Manager adr;quoted-printable:;;Xilinx Ireland=0D=0ALogic Drive=0D=0ACitywest Business Campus=0D=0ASaggart;Dublin;;;Ireland x-mozilla-cpt:;0 fn:Gerry Owens end:vcard
