Leah,

You are right. Every industry is going to have particular requirements. 
Ocean containers, sub packs, item level serialization, lot # tracking,
part revision level and other details have not been mentioned.

Here is a revised version of Brian's list of  HL Levels:


1. what's on the truck? (ship level)

2. what's is on the ocean container (optional)

3. what orders/invoices are on the truck? (order level)(optional)

4. what pallets are on the truck? (optional)

5. what containers (cartons, bins, etc) are on the pallet? (pack level)
(optional)

6. what's in the box? (item level) (UPC, part number,style number)

       * part / item characteristics such as heat level, expiration date,
lot number, serial numbers, etc etc are defined here

7. what sub-packs are in the container  (optional)







Todd LaBonte

Web-site:    www.e-supplylink.com











From: [email protected][mailto:[email protected]] On Behalf Of
Leah Halpin

Sent: Thursday, August 04, 2011 1:09 PM

To: Earl Wertheimer; Joe Matuscak; [email protected]

Subject: Re: [EDI-L] 856 design theory documents/websites/books??





I'm just saying, this is not the golden rule for allindustries,
certainly not for Automotive, no UPC codes and you'd better knowwhat
pallet, and it's part number, too, by jinky, not to mention JITs. Steel,
I don't care about pallets, not even using them are you kidding? No
cartons, either, but you'd better tell me the heat number or I'm not
buyingfrom you again.  Don't even think about trying to ship to Mexico
unlessyou can get that invoice number on your ASN. I'm quite certain
other industrieshave other, rational (or not so) requirements as well.

Leah



________________________________

From: Earl Wertheimer <[email protected]>

To: Joe Matuscak <[email protected]>;[email protected]

Sent: Thursday, August 4, 2011 12:59 PM

Subject: Re: [EDI-L] 856 design theory documents/websites/books??





Joe



> I'm in the process of working through a design of an856 transaction
and

> I've been looking for something that would describegeneric design

considerations

> in the implementation of an 856. Things like howwhat makes sense for
the

> hierarchy, etc. I've Googled around and while I'vefound lots of

organizations

> implementation guides, I've not found anything thatreally addresses
sort of

> addresses the zen of how to build an 856.



Brian covered it perfectly:



Here's the "golden rule":



1. what's on the truck? (ship level)

2. what orders/invoices are on the truck? (order level)

3. what pallets are on the truck? (maybe)

4. what cartons are on the pallet? (carton level)

5. what's in the box? (item level)



-----------------



Bottom line: You need to convert your incoming POs (orexisting ERP
Orders)

into the S (truck) O (Order) T (Tare/Pallet) P (Carton) I(Item)
structure.



Each of these levels is nested under the next up.



I was able to combine the T and P levels with an optionalPallet code.



You need at least 3 tables to hold all the data.(important data fields)



1) S = Shipment table (B/L#, ShipTo, ShipDate)

2) T/P = Carton Header (20 digit UCC carton#, UPSwaybill(optional),
Store,

MarkFor, CustomerPO, Pallet# )

3) I = Carton Details (Item info, pointers back to Orderline)



I can send you file layouts, etc... or screen shots.



The ASN S level is built from the Shipment

The O level is built from the CartonHeader.CustomerPOgrouping.

The T level is built from the CartonHeader.Pallet#grouping (I have not
seen

this a lot until recently)

The P level is build from the CartonHeader

The I level is built from the CartonDetails.



Earl Wertheimer

[email protected]

http://www.spe-edi.com



[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]



------------------------------------

...
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:
    [email protected] 
    [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/

Reply via email to