ECTF EDIPro Standard
EDI 856 Ship Notice/Manifest (ASC X12 Version 4 Release 1)
This document contains an outline of common business issues for consideration when implementing the EDI 856 Ship Notice/Manifest for ASC X12 Version 4010. It is the intent of this document to act as an addendum to the ASC X12 EDI Standards documentation.
856 Ship Notice/Manifest
Included in this document:
Page
Section 1: Business Issues......................................................... 2...........................................................................................................
Section 2: Segment Notes...................................................... 5
Section 3: Example Notes..................................................... 33
Section 1
856 Ship Notice/Manifest
Business Issues
This section contains business discussions about the use of the 856 Ship Notice/Manifest. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
Page
Hierarchical Level....................................................................... 3
Use of Shipping Container Code (SCC-14) and Quantity Unit of Measure.................................................................................................................................................. 3
Use of Text Fields......................................................................... 3
Special Carrier/Shipments....................................................... 3
Identification of Business Location........................................ 4
Business Issues
The following business issues should be considered when implementing the 856 Ship Notice/Manifest:
Hierarchical structures define the placement of levels within a transaction set. Each structure sets parameters on the parent/child relationship of the hierarchical levels. The Ship Notice/Manifest supports many different hierarchical levels of detail including shipment, tare, pack, order, and item data. The required level of detail should be discussed and agreed to by both trading partners. The subsequent paragraphs outline the general information provided at each hierarchical level of the Ship Notice/Manifest.
Shipment
The information contained in this level of the Ship Notice/Manifest pertains to the entire shipment. This level will always occur as the first hierarchical level.
Tare (SSCC-18)
This hierarchical level is used to identify a transport package, which may be a pallet, master container, or other physical unit of load. The SSCC-18 (commonly referred to as the license plate) is the method of identification for a transport package.
The master container is used for overpack situations when several smaller items are combined into one master container and will be labeled with an SSCC-18. It is possible for one or more master containers to be packaged within one transport package (multiple boxes on one pallet).
Pack (SCC-14)
This hierarchical level is used to identify the pack level for an item. As defined by ASC X12, pack levels imply that items in the carton are the same U.P.C. number. The SCC-14 is used to identify these cartons.
Order
This hierarchical level identifies data related to the original purchase order.
Item (U.P.C.-12 or SCC-14)
The U.P.C.-12 or SCC-14 identifying the product and quantity shipped is included at this hierarchical level.
Detailed diagrams and examples showing the different hierarchical looping structures are provided in Section 3: Example Transactions of this document.
This SCC-14 format includes the designation of a specific package level which is associated with a discrete quantity. The quantity unit of measure (SN103 data element) should not be used to calculate the net quantity shipped of an item when the item is identified by a SCC-14. It is recommended that a value of “EA” be used as the quantity unit of measure for items identified with a SCC-14.
The PID segment promotes the inclusion of text data. When using this segment it is recommended that they be restricted to free form text and that any other use for specific data which could be mapped, be discouraged.
It should be noted that the use of text data in EDI transactions should be limited to those specific agreements between trading partners. Anytime text data is passed within a transaction, the receiving partner may have to queue the transaction into an exception process for review. In this case the transaction cannot be automatically processed.
To permit the seller to communicate special shipping conditions such as Same Day, Air Freight, etc., or to allow the specification of a specific carrier, the use of the TD5 segment is recommended.
When specifying a specific carrier it is further recommended that the Standard Carrier Alpha Code (SCAC) be used if one has been assigned to the carrier. See the TD5 segment for further discussion
It should be noted that the TD5 segment may be included at the header portion of the transaction, thereby applying to the entire order, or at the line item level of the order, applying only to the specified line.
DUNS + 4 should be used as the primary and preferred method of identifying business locations. Organizations not using the “+ 4” suffix of the DUNS number should insert four zeros in its place.
Section 2
856 Ship Notice/Manifest
Segment Details
This section contains business discussions about the segments used in the 856 Ship Notice/Manifest. These discussions will assist in determining application changes and business process changes that may be necessary within a company.
856.................................................................................................. 6
ST..................................................................................................... 7
BSN................................................................................................. 8
HL.................................................................................................... 9
LIN................................................................................................ 10
SN1............................................................................................... 12
SLN................................................................................................ 13
PRF................................................................................................ 16
PO4.............................................................................................. 17
PID................................................................................................ 18
TD1............................................................................................... 19
TD5............................................................................................... 20
TD3............................................................................................... 22
REF................................................................................................ 23
MAN............................................................................................ 24
DTM.............................................................................................. 25
FOB............................................................................................... 26
PAL............................................................................................... 27
N1................................................................................................. 28
N3................................................................................................. 29
N4................................................................................................. 30
CTT............................................................................................... 31
SE.................................................................................................. 32
|
|
||
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
010 |
ST |
Transaction Set Header |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
020 |
BSN |
Beginning Segment for Ship Notice |
M |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LOOP ID - HL |
|
|
200000 |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
010 |
HL |
Hierarchical Level |
M |
1 |
|
C2/010 |
|
|
|
|
|
|
|
|
|
|
|
|
|
020 |
LIN |
Item Identification |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
030 |
SN1 |
Item Detail (Shipment) |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
040 |
SLN |
Subline Item Detail |
O |
1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
050 |
PRF |
Purchase Order Reference |
O |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|