Michael, Yes, there is a problem with this - at least for MY situation.
We use the SOPI structure for a reason.... The format works better for US.... HL 1 - Shipment info about the particular shipment (carrier, BOL, ship date, etc.) HL 2 - Order This is where the specific PO information is sent - PO #, dates, etc. HL 3 - Pack Info about the package - i.e. the UCC128 lable number. HL 4 - Item This is the item specific information - SKU, UPC, Vendor Style, etc. Also UOM (ea vs. dz) and quantity in the carton/package. >From here on, the P and I levels repeat for each carton in the shipment. If the vendor is mixing multiple POs in a single shipment (which we allow), then the format would be: S O P I P I P I P I O P I P I O P I etc... Each new PO would have a new HL for ORDER and then the Pack and Item levels for that PO. And semantics are not an - again for MY situation. We are the BUYER - and we, therefore, are the RECEIVER of the ASN. The SELLER is the SENDER of the ASN. So My use of SENDER and RECEIVER would equate to SELLER and BUYER, respectively, for the post. As we sell through retail outlets and have no online business, we don't send any kind of ASN out. Craig Dunham EDI Coordinator Big 5 Sporting Goods --- In [email protected], "Michael Mattias/LS" <[EMAIL PROTECTED]> wrote: > > > > As for Michael's post about "Although personally I would never use "O" > > level above either P or I, I'd use a PRF segment at the Item level > > whereever that ends up." - there's a problem with this.... > > There is? > > Pick and Pack... > HL*1**S > stuff > HL*2**P > pack info > HL*3 **I > PRF > ItemInfo > HL*4 > PRF > more item info > HL*5**P next pack > > Standard Pack > HL*1**S > stuff > HL*2**I > PRF > HL*3 **P > Pack info > HL*4**P next pack of this item for this PO > HL*I > PRF > HL*n**P first pack of this item for another PO.. > > > -------------------------------------------------------- > > Perhaps just a semantic thing, but.....you make numerous references in your > post to both 'sender' and 'receiver' of the ASN. > > In my experience the data requirements are based not so much who is sending > and who is receiving the ASN, but on who is BUYING and who is SELLING the > merchandise. > > Michael C. Mattias > Tal Systems Inc. > Racine WI > [EMAIL PROTECTED] > ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
