Without seeing your approach to handling your data, and more importantly how you're feeding this data into your sales order system, I'm not real sure what you're asking for. The only thing I really see in your original question is about recognizing what the data in the N1 loop is. That's what the BT and ST are for. Your approach of how you keep track of the data inside your program is going to be based on the way you think. Myself, I like more descriptive variables like BILLTO.ID and SHIPTO.NAME kind of things.
Don't know if I'm clearing the water or stomping in the mud but I hope it helps. Good luck. 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:51 PM To: U2 Users List Subject: Re: [U2] [mildly ot] - EDI and drop shipments Aside from phone#, the other thought was just a straight text "DROPSHIP", other than That, I wouldn't be relating the phone number to anything, other than a piece of data Isolating the loops isn't a problem. I have a subroutine that converts the EDI To a dynamic array, and it knows that N1 is a loop, and will create separate Them by @VM's N1<1,x> will go with N2<1,x> where x is the loop number. Were using customized programming, so it's not a problem to do unique things Based on the partners ID, or the a specific SAN. Thanks -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Woodward, Bob Sent: Friday, February 10, 2012 4:43 PM To: U2 Users List Subject: Re: [U2] [mildly ot] - EDI and drop shipments 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 _______________________________________________ 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
