X12 856 Ship Notice/Manifest (Shipper)
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
- ZZ
- Mutually Defined
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
FLEXPORTEDI(Prod) / FLEXPORTEDIQA(Test)
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
FLEXPORTEDI(Prod) / FLEXPORTEDIQA(Test)
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
- 04
- Change
A unique control number assigned by the original shipper to identify a specific shipment
Notes: Flexport Standard = FLEX-ID formarted as FLEX-#####
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.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0004
- Shipment, Order, Item
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.
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
- BAG
- Bag
- BAL
- Bale
- BBL
- Barrel
- BDL
- Bundle
- BLK
- Bulk
- BOX
- Box
- CRT
- Crate
- CTN
- Carton
- DRM
- Drum
- PKG
- Package
- PLT
- Pallet
- ROL
- Roll
- SKD
- Skid
Number of units (pieces) of the lading commodity
Code defining the type of weight
- B
- Billed Weight
- G
- Gross Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CR
- Cubic Meter
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
Notes: Flexport Standard = main freight carrier (carrier on leg departing from port of loading)
- O
- Origin Carrier (Air, Motor, or Ocean)
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.
- 2
- Standard Carrier Alpha Code (SCAC)
Code specifying the method or type of transportation for the shipment
- A
- Air
- S
- Ocean
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
- CC
- Shipment Complete on (Date)
The point of origin and point of direction
- SB
- Seller to Buyer
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- AF
- Air Freight (Break Bulk)
- CN
- Container
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- AW
- Air Waybill Number
- BM
- Bill of Lading Number
- BN
- Booking Number
- MA
- Ship Notice/Manifest Number
- MB
- Master Bill of Lading
- RE
- Release Number
- SN
- Seal Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Vessel Identification
To provide vessel details and voyage number
Name of ship as documented in "Lloyd's Register of Ships"
Identifying designator for the particular flight or voyage on which the cargo travels
Code specifying the method or type of transportation for the shipment
- 10
- LCL VES NON-CON
- 11
- FULL CTNR LOAD
Port or Terminal
Contractual or operational port or point relevant to the movement of the cargo
R4 is required for each port to be identified.
Code defining function performed at the port or terminal with respect to a shipment
- D
- Port of Discharge (Operational)
- L
- Port of Loading (Operational)
Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 011
- Shipped
- 017
- Estimated Delivery
- 274
- Requested Departure Date
- AA1
- Estimated Point of Arrival
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
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
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
- SF
- Ship From
- ST
- Ship To
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- US
- Unique Supplier Identification Number (USIN)
- ZZ
- Mutually Defined
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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
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
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.
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
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
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
Identifying number for a product or service
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.
- EA
- Each
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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
Code identifying the general class of a product or process characteristic
- ZZ
- Mutually Defined
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- ZZ
- Mutually Defined
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
PID04 = US Tariff Number when PID03 = ZZ
A free-form description to clarify the related data elements and their content
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
By Container, Multiple POs
GS*SH*SENDERGS*RECEIVERGS*20231101*010231*000000001*X*004010~
ST*856*0002~
BSN*00*FLEX-555107*20190816*0136*0004~
HL*1**S~
TD1*PKG*18****G*35699.4*LB*18.5*CR~
TD5*O*2*EGLV*S**CC***SB~
TD3*CN**TEMU416058~
REF*BM*EGLV143982064624~
DTM*011*20190801*0400~
DTM*017*20190902*1700~
FOB*CC~
N1*SF*SUPPLIER23 LTD*US*0001~
N3*#1 QUIHA ROAD~
N4*HAINING CITY*33*314422*CN~
N1*ST*DISTRIBUTION*9*0754585215403~
N3*600 LAS SPECIAL BLVD E*SUITE 400~
N4*LOS ANGELES*TX*75039-5616*US~
HL*2*1*O~
PRF*9299445~
HL*3*2*I~
LIN*1*VP*B-4707Q*BP*Q2~
SN1**1008*EA**11760*EA~
PID*F****4707Q NEW STEEL SHOE~
HL*4*1*O~
PRF*9247816~
HL*5*4*I~
LIN*2*VP*B-4711Q*BP*B2~
SN1**1512*EA**2000*EA~
PID*F****4711Q NEW STEEL SHOE~
CTT*5~
SE*30*0002~
GE*1*000000001~
IEA*1*000000001~
By Container, One PO
GS*SH*SENDERGS*RECEIVERGS*20231101*010451*000000001*X*004010~
ST*856*0001~
BSN*00*FLEX-555181*20190817*0227*0004~
HL*1**S~
TD1*PKG*24****G*37831.3*LB*9.5*CR~
TD5*O*2*ONEY*S**CC***SB~
TD3*CN**TCNU8408606******TW167378B*42G0~
REF*BM*ONEYNK8GL4635600~
DTM*011*20190801*0400~
DTM*017*20190917*1600~
FOB*CC~
N1*SF*SUPPLIER1., LTD*US*0001~
N3*PARK DISTRICT*SUITE 300~
N4*NANJING*32**CN~
N1*ST*DISTRIBUTION*9*0354585215427~
N3*600 LAS COLINAS BLVD E*SUITE 400~
N4*LOS ANGELES*CA*75039-5616*US~
HL*2*1*O~
PRF*694832~
HL*3*2*I~
LIN*1*VP*ITEM1*BP*SAMPLE1~
SN1**250*EA**250*EA~
PID*F*ZZ***HARDWARE KIT~
HL*4*2*I~
LIN*2*VP*OTR4515QHD*BP*SAMPLE2~
SN1**6250*EA**6250*EA~
PID*F****Q HARDWARE BRAKE KIT W/HD SPRING~
HL*5*2*I~
LIN*3*VP*OTR4515X*BP*SAMPLE3~
SN1**500*EA**500*EA~
PID*F****16.5 FRUEHAUF X3 HARDWARE KIT~
HL*6*2*I~
LIN*4*VP*OTR4524QM*BP*SAMPLE4~
SN1**500*EA**500*EA~
PID*F****MACK HARDWARE KIT W/OFFSET SPRING~
HL*7*2*I~
LIN*5*VP*OTR4702*BP*SAMPLE5~
SN1**500*EA**500*EA~
PID*F****15X4 Q-PLUS FRONT HARDWARE KIT~
CTT*5~
SE*40*0001~
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.