X12 856 Ship Notice
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
A unique control number assigned by the original shipper to identify a specific shipment
3M allows for 16 character shipment number. If shipment number sent is
longer, 3M will use the first 16 characters
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.
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
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
- CTN
- Carton
- MIX
- Mixed Container Types
- PKG
- Package
- PLT
- Pallet
Number of units (pieces) of the lading commodity
3M restricts length of this field to 5 digits.
Number of packages.
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- 2B
- 20 ft. IL Container (Closed Top)
- 4B
- 40 ft. IL Container (Closed Top)
- AF
- Air Freight (Break Bulk)
- FT
- Flat Bed Trailer
- TA
- Trailer, Heated/Insulated/Ventilated
- TF
- Trailer, Dry Freight
- TN
- Tank Car
- TV
- Truck, Van
- TW
- Trailer, Refrigerated
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
If equipment number exceeds 10 characters, please send in Shipment level REF
segment with REF01 = EQ
Code qualifying the Reference Identification
Required by 3M.
Bill of Lading cannot have any special characters.
If there isn't a Bill of Lading Number, for the freight types
below use the following information as Bill of Lading:
Small Parcel –tracking number
Full Truckload –trailer and seal number
Less-than-Truckload –pro number
Ocean –container number
Air –airway bill
Use EQ: Use only if the equipment number exceeds the 10
characters allowed in the TD303.
- BM
- Bill of Lading Number
- EQ
- Equipment Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- PP
- Prepaid (by Seller)
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- FV
- Free Alongside Vessel (Free On Board [F.O.B.] Point)
- OR
- Origin (Shipping Point)
- OV
- On Vessel (Free On Board [FOB] point)
- PB
- Port of Discharge
- PD
- Place of Delivery
- ZZ
- Mutually Defined
A free-form description to clarify the related data elements and their content
Code identifying the source of the transportation terms
- 01
- Incoterms
Code identifying the trade terms which apply to the shipment transportation responsibility
Used if the incoterms code is DAP or DAT. These
incoterms codes were added in 2010 and are not
available in the ANSI 004010 standard. The incoterms
codes "DAP" or "DAT" is sent in the FOB07
- CFR
- Cost and Freight
- CIF
- Cost, Insurance, and Freight
- CIP
- Carriage and Insurance Paid To
- CPT
- Carriage Paid To
- DDP
- Delivered Duty Paid
- EXW
- Ex Works
- FAS
- Free Alongside Ship
- FCA
- Free Carrier
- FOB
- Free on Board
- ZZZ
- Mutually Defined
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- ZZ
- Mutually Defined
A free-form description to clarify the related data elements and their content
This field will only be populated if the incoterms code = "DAP" or "DAT".
These incoterms codes were added in 2010 and are not available in the ANSI
004010 standard. Send "ZZZ" in the FOB05 to indicate that the FOB07 field
contains the incoterms code.
- Required by 3M if 3M will pay freight charges.
- Highly recommended if vendor will pay freight
charges and carrier is on the 3M carrier list. - Not required if vendor is paying freight and carrier is
not on the 3M carrier list.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- CA
- Carrier
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.
3M restricts the length of this field to 10 characters.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
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.
3M restricts the length of this field to 10 characters.
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.
- O
- Order
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
Reference Identification
To specify identifying information
Required if material is crossing international borders.
Code qualifying the Reference Identification
- CT
- Contract Number
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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
Item Identification
To specify basic item identification data
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Return the item number sent in PO.
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.
If the PO line item did not contain a buyer part number (BP) or a vendor part number
(VP), please send VP in LIN02 and NA in LIN03.
- BP
- Buyer's Part Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
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.
Subline Item Detail
To specify product subline detail item data
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- B8
- Batch Number
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code defining the type of weight
- E
- Estimated Net Weight
- G
- Gross Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code qualifying the Reference Identification
Vendor's Batch or Lot Number of material being
delivered, if applicable.
Required if material is batch managed. For 3M USA
PO’s only, the PO line item text will advise if material
is batch managed.
- BT
- Batch Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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.
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
ShipNotice example from 3M
GS*SH* IDSENDERID * IDRECEIVERID *20150216*1720*650000035*X*004010
ST*856*0400
BSN*00*SHIPMENTNUMBER*20230404*0744
DTM*002*20230404
HL*1**S
TD1*PKG*1
TD3*TV**987654896
REF*BM*BILLOFLADINGNUMBER
DTM*017*20230404
FOB*CC*DE*DESCRIPTION*01*EXW*ZZ*DESCRIPTION
N1*VN*VENDOR NAME*92*VENDORNUM
N1*CA*CARRIER NAME*92*CARRIERNUM
HL*2*1*O
PRF*3MPONUMBER
HL*3*2*I
LIN*00010*BP*3MPARTNUMBER*VP*VENDORPARTNUMBER
SN1*00010*240*1I
PID*F****LINE ITEM DESCRIPTION
TD1******G*100*LB*120*LB
TD1******E*95*LB*120*LB
CTT*3
SE*21*0400
GE*1*650000035
IEA*1*650000035
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.