---- Original Message -----
From: Kenneway, Kirk <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 05, 2001 1:24 PM
Subject: Third party transactions
> Greetings all,
> I was hoping someone could help me out (again).
>
> I need help figuring out how to populate the Originator/Recipient fields in
> my target application header. In our world, the Originator and Recipient are
> the participants in a business transaction and are expected to be (usually)
> the owners of the business transaction (810, 850, 856, etc...).
>
> For EDI docs, we are mapping the sender/receiver values to our Originator
> and Recipient fields in the target application. Specifically, we are using
> sender and receiver values from the ISA05, ISA06, ISA07, ISA08....
> The issue is that the business entities associated with a given business
> transaction within an EDI doc may not be the same as the sender/recipient
> pair for that EDI doc.
If you want to get really technical about it, the ISA values should not be used
for anything at the 'business" or "application" level. The ISA envelope is
(well, *was*) supposed to be used strictly to route an interchange to the
correct recipient. You should be using the GS sender/receiver IDs, as those are
the IDs associated with the "business" transaction.
But... as is too often the case, the "book" usage of the ISA and GS identifiers
has been bastardized over time and all the 800-pound gorillas choose to 'roll
their own.'
As far as your case goes, it seems to me "in the abstract" the 856 should go
from the forwarder to the Manufacturer: the manufacturer authorized the shipment
of his product.
If the customer (consignee) or customer's vendor (you) wants an ASN, someone
needs to make arrangements with the forwarder, as the forwarder is the ONLY
party in this transaction who can possibly generate a Shipping Notice for
anyone. (He's the only party who really knows when the material ships). Of
course, as the customer of the manufacturer, you could make arrangements with
the manufacturer, too.
That said, I know a couple distributors who get ASNs from the shipper
(manufacturer, forwarder or public warehouse); if a drop ship, they turn around
and generate their own ASN for the consignee (customer).
Lastly... there are a number of application systems which use their own creative
definitions of "originator" or "recipient" and other "ASN fields" and I have no
idea how your application expects them to be populated.
If the above has totally confused you, then I think I explained it correctly;
because when you start throwing in all those "special cases" with "historical
usage" and "800-pound gorillas," it IS confusing.
Michael C. Mattias
Tal Systems Inc.
Racine WI
[EMAIL PROTECTED]
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
