Are you setting up specifications or do you already have a set that
you're working from?  You should be able to isolate the N1 loops from
each other within a dataset so that each loop is a functional subset.
Then, based on the BT/ST code determine what kind of information you
have and apply it accordingly to you generating sales order process.

The issue you are going to struggle with is going to be the unknown code
(phone number) to your system.  You probably won't have a customer
master records to link to.  At least this is one of the issues we're
struggling against currently in our efforts to do this.  The direction
we're going is our sales orders have the extra fields for an actual
third-party name and address that is a manual entry on our screens. They
are not tied to the customer master file.

Our documents and labels that will need to use this third-party address
will have to be set so if it exists, it uses it, otherwise it will use
the normal ship-to information.  For the drop ship orders, the ship-to
will have to default to one of the partners normal ship-to's, just to be
safe and ensure the shipment never gets lost.

Oh, and there really isn't a way to do drop shipments using the SDQ
segment unless you have a matching ID of each SDQ CODE/QTY pairing
already in your customer master file.  At least not without redefining
industry standards of the EDI format.  I guess/assume you're using the
VICS standard.

This is a big monster of a change so if you want to talk concepts, we
could take this off-list.

BobW

-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen
Sent: Friday, February 10, 2012 1:07 PM
To: U2 Users
Subject: [U2] [mildly ot] - EDI and drop shipments

For those EDIers on the list.

Do any of you process drop shipments using EDI for 850's?
What method do you use?

We were thinking :

First N1 loop - N1 segment contains the BT and use the SAN (15 code)
Second N1 loop - N1 segment contains the ST but use phone# for
identification (12 code)
                                    N2 segment for Drop Ship Name
                                    N3 Segment(s) for Drop Ship Address
(2 lines per N3 segment) - maximum 2 N3's
                                    N4 Segment for Drop Ship City,
State, Zip and Country


Currently we  do not process drop shipments using EDI, and neither does
this partner with any of
   Their other suppliers...

George
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to