X12 856 Ship Notice/Manifest
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
Use Packing Slip Number
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- BSN04 is the time the shipment transaction set is created.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 011
- Shipped
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
Code identifying the broad category to which a measurement applies
- PD
- Physical Dimensions
Code identifying a specific product or process characteristic to which a measurement applies
- G
- Gross Weight
- N
- Actual Net Weight
The value of the measurement
Weight of shipment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- ZZ
- Mutually Defined
Code identifying a party or other code
TD503 should contain Assigned Tracking Number or Carrier Pro Bill Number
Code identifying type of location
- RS
- Standard Carrier Alpha Code
Code which identifies a specific location
TD508 should contain SCAC Code. This is the Standard Carrier Alpha Code for the carrier assigned.
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- TL
- Trailer (not otherwise specified)
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
TD303 should be the number assigned to the Trailer for this particular shipment.
Reference Identification
To specify identifying information
Note: Use a separate ASN for each Packing Slip Number.
Code qualifying the Reference Identification
- PK
- Packing List Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Free-form name
N102 should match N102 from 850 N102 where N101 is 'ST'.
If N101 is SF: Your company name up to 9 characters
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N104 should match N104 from 850 N104 where N101 is 'ST'.
N104 should match N104 from 850 N104 where N101 is 'SF'.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- BP
- Buyer's Part Number
Identifying number for a product or service
LIN03 should match 850 PO107.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PN
- Company Part Number
Identifying number for a product or service
LIN05 should match 850 PO109.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CH
- Country of Origin Code
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Quantity of pieces shipped for this line item.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- PC
- Piece
Number of units shipped to date
SN04 is calculated per PO Line Item Order Quantity.
Quantity ordered
Original Order Quantity
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
PRF01 should match 850 BEG03.
Alphanumeric characters assigned for differentiation within a transaction set
PRF05 should match 850 PO101.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CAS
- Case
Number of units (pieces) of the lading commodity
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
- X
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
Use status code “CC” if you are shipping 100% of the quantity requested on the purchase order.
Use status code “CP” if you are shipping less than 100% of the quantity requested on the purchase order and canceling the balance.
Use status code “BP” if you are shipping less than 100% of the quantity requested on the purchase order and backordering the balance.
Use status code “BK” if you are shipping an item that was previously backordered.
- BK
- Back Ordered from Previous Order
- BP
- Shipment Partial, Back Order to Ship on (Date)
- CC
- Shipment Complete on (Date)
- CP
- Partial Shipment on (Date), Considered No Backorder
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
MULTI-LINE ASN
GS*SH*SENDERGS*RECEIVERGS*20240207*230722*000000001*X*004010
ST*856*19487
BSN*00*56453002*20060711*1539
DTM*011*20060711*1539
HL*1**S
MEA*PD*N*1218*LB
MEA*PD*G*1218*LB
TD5**ZZ*129-0260422-6****RS*HMES
TD3*TL**11
REF*PK*56453002
N1*SF*NUESTRO, LLC*92*AKNBA
N1*ST*WELLS MFG*92*72260-8
HL*2*1*I
LIN**BP*F3XY-10884-C*PN*812700359*CH*XXXX
SN1**31*PC*0*118
PRF*173854-E85157****1
TD1*CAS*47
TD5*****X*BP
HL*3*1*I
LIN**BP*E4TZ-9278-A*PN*811900130*CH*XXXX
SN1**96*PC*0*96
PRF*175436-E92178****1
TD1*CAS*47
TD5*****X*CC
CTT*3*127
SE*25*19487
GE*1*000000001
IEA*1*000000001
SINGLE LINE ITEM: Complete Shipment
GS*SH*SENDERGS*RECEIVERGS*20240207*230423*000000001*X*004010
ST*856*000000001
BSN*00*PACKING SLIP NO*20240207*1545
DTM*011*20240207*1600
HL*1**S
MEA*PD*N*125*LB
MEA*PD*G*150*LB
TD5**ZZ*432-78909P88****RS*HMES
TD3*TL**TS76898
REF*PK*PACKING SLIP NO
N1*ST*CUSTOMER SHIP TO NAME*92*CUSTOMER SHIP TO CODE
N1*SF*YOUR NAME*92*YOUR VENDOR CODE
HL*2*1*I
LIN**BP*F81Z-7D392-AB*PN*D36592B*CH*XXXX
SN1**100*PC*100*100
PRF*FCS PURCHASE ORDER NUM****FCS PURCHASE LINE RE
TD1*CAS*1
TD5*****X*CC
CTT*1*100
SE*19*000000001
GE*1*000000001
IEA*1*000000001
SINGLE LINE ITEM: Partial Shipment/Back-Order Balance
GS*SH*SENDERGS*RECEIVERGS*20240207*230532*000000001*X*004010
ST*856*000000001
BSN*00*PACKING SLIP NO*20240207*1545
DTM*011*20240207*1600
HL*1**S
MEA*PD*N*125*LB
MEA*PD*G*150*LB
TD5**ZZ*432-78909P88****RS*HMES
TD3*TL**TS76898
REF*PK*PACKING SLIP NO
N1*ST*CUSTOMER SHIP TO NAME*92*CUSTOMER SHIP TO CODE
N1*SF*YOUR NAME*92*YOUR VENDOR CODE
HL*2*1*I
LIN**BP*F81Z-7D392-AB *PN*D36592B*CH*XXXX
SN1**50*PC*50*100
PRF*FCS PURCHASE ORDER NUM****FCS PURCHASE LINE RE
TD1*CAS*1
TD5*****X*BP
CTT*1*50
SE*19*000000001
GE*1*000000001
IEA*1*000000001
SINGLE LINE ITEM: Previous Back-Order
GS*SH*SENDERGS*RECEIVERGS*20240207*230704*000000001*X*004010
ST*856*000000001
BSN*00*PACKING SLIP NO*20240207*1545
DTM*011*20240207*1600
HL*1**S
MEA*PD*N*125*LB
MEA*PD*G*150*LB
TD5**ZZ*432-78909P88****RS*HMES
TD3*TL**TS76898
REF*PK*PACKING SLIP NO
N1*ST*CUSTOMER SHIP TO NAME*92*CUSTOMER SHIP TO CODE
N1*SF*YOUR NAME*92*YOUR VENDOR CODE
HL*2*1*I
LIN**BP*F81Z-7D392-AB *PN*D36592B*CH*XXXX
SN1**25*PC*75*100
PRF*FCS PURCHASE ORDER NUM****FCS PURCHASE LINE RE
TD1*CAS*1
TD5*****X*BK
CTT*1*25
SE*19*000000001
GE*1*000000001
IEA*1*000000001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.