Dear Georgia:
Your example shows the sequential counter "cross reference" within the
APR (Additional Price Information) inside the first element, D.E. 4043
(Class of trade, coded). Was this intended? - I realize the syntax of
the example may not be perfect, but there doesn't seem to be ANY element
within the APR which is at all "appropriate" to use as a cross
reference. In any case, APR01 is clearly unusable for such a purpose,
since it has a fixed set of code values. And as Chris Johnson was
saying, is it really even necessary to "manufacture" a cross reference
for the PRI, since the first PRI group (within a particular line item)
is implicitly no. 1, the second 2, and so on.
But assuming that you have fewer than 10 PRI (Price Details) segment
groups which have to be referred to by the ALC (Allowance or Charge),
perhaps you could use ALC04 (Calculation sequence indicator, coded).
Then Code Value 1 - First step of calculation - could refer to the first
PRI, Code Value 2 - Second step of calculation - to the second PRI, and
so on. This is probably a misuse of the sequence indicator, but at
least it would eliminate the APR. While we're on a roll for ugly
constructs, another possibility is to use D.E. 1230 (Allowance or charge
number) at ALC02-01 for the relative number of the matching PRI.
Maybe it would help to show us everything you plan to use in the PRI
group. Perhaps there's some cleaner way to "hook" an ALC with the
appropriate PRI based on criteria in subordinate groups under the ALC.
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"
----- Original Message -----
From: "Georgia Blomberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 05, 2001 1:05 AM
Subject: relating allowances to one price loop (PRICAT)
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+125
ALC+++123
ALC+++123
ALC+++123
ALC+++124
ALC+++124
ALC+++125
Suggested 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/
