856 Ship Notice/Manifest 
 
   
Functional Group ID=SH
 
 
Introduction: 
 
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. 
                                                       
 
Heading:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
Must Use 010 ST Transaction Set Header M 1
Must Use 020 BSN Beginning Segment for Ship Notice M 1
  040 DTM Date/Time Reference O 10
 
Detail:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  LOOP ID - HL 200000  
Must Use 010 HL Hierarchical Level M 1 c1  
  110 TD1 Carrier Details (Quantity and Weight) O 20  
  120 TD5 Carrier Details (Routing Sequence/Transit Time) O 12  
  130 TD3 Carrier Details (Equipment) O 12  
  150 REF Reference Identification O >1  
  150 REF Reference Identification O >1  
  LOOP ID - CLD 200    
  170 CLD Load Detail O 1    
  180 REF Reference Identification O 200    
 
  210 FOB F.O.B. Related Instructions O 1  
  LOOP ID - N1 200    
  220 N1 Name O 1    
  240 N3 Address Information O 2    
  250 N4 Geographic Location O 1    
  220 N1 Name O 1    
  240 N3 Address Information O 2    
  250 N4 Geographic Location O 1    
  220 N1 Name O 1    
  240 N3 Address Information O 2    
  250 N4 Geographic Location O 1    
  255 HL Hierarchical Level O 1    
  257 PRF Purchase Order Reference O 1    
  260 REF Reference Identification O 12    
  265 HL Hierarchical Level O 1    
  267 LIN Item Identification O 1    
  268 SN1 Item Detail (Shipment) O 1    
  269 TD5 Carrier Details (Routing Sequence/Transit Time) O 1    
 
  LOOP ID - LM 10    
  340 LM Code Source Information O 1    
Must Use 350 LQ Industry Code M 100    
 
 
Summary:
 
 
  Pos. Seg. Req. Loop Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  010 CTT Transaction Totals O 1 n1
Must Use 020 SE Transaction Set Trailer M 1
 
Transaction Set Notes 
 
       
1. 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 Comments 
 
       
1. The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
 

           
Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
Comments:
Notes: Segment Example: ST*856*1150^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> ST01 143 Transaction Set Identifier Code M ID 3/3
  Code uniquely identifying a Transaction Set
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> ST02 329 Transaction Set Control Number M AN 4/9
  Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

           
Segment: BSN Beginning Segment for Ship Notice
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set
Syntax Notes: 1 If BSN07 is present, then BSN06 is required.
Semantic Notes: 1 BSN03 is the date the shipment transaction set is created.
  2 BSN04 is the time the shipment transaction set is created.
  3 BSN06 is limited to shipment related codes.
Comments: 1 BSN06 and BSN07 differentiate the functionality of use for the transaction set.
Notes: Segment Example: BSN*00*0579745*920804*1033^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> BSN01 353 Transaction Set Purpose Code M ID 2/2
  Code identifying purpose of transaction set
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  00 Original
  07 Duplicate
 
>> BSN02 396 Shipment Identification M AN 2/30
  A unique control number assigned by the original shipper to identify a specific shipment
>> BSN03 373 Date M DT 8/8
  Date expressed as CCYYMMDD
>> BSN04 337 Time M TM 4/8
  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)

           
Segment: DTM Date/Time Reference
Position: 040
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.
  2 If DTM04 is present, then DTM03 is required.
  3 If either DTM05 or DTM06 is present, then the other is required.
Semantic Notes:
Comments:
Notes: Segment Example: DTM*011*920804*1033**19^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> DTM01 374 Date/Time Qualifier M ID 3/3
  Code specifying type of date or time, or both date and time
  Suggested code for aftermarket usage. Any ASC X12 approved codes may be used.
   
  011 Shipped
 
  DTM02 373 Date X DT 8/8
  Date expressed as CCYYMMDD
  DTM03 337 Time X TM 4/8
  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)
  DTM05 1250 Date Time Period Format Qualifier X ID 2/3
  Code indicating the date format, time format, or date and time format
  Refer to 004010 Data Element Dictionary for acceptable code values.
  DTM06 1251 Date Time Period X AN 1/35
  Expression of a date, a time, or range of dates, times or dates and times

           
Segment: HL Hierarchical Level
Position: 010
Loop: HL Mandatory
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
Syntax Notes:
Semantic Notes:
Comments: 1 The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.
  The HL segment defines a top-down/left-right ordered structure.
  2 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.
  3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
  4 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.
  5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
Notes: Segment Example: HL*1**S^ 
This Segment marks the beginning of the information 
covering a single shipment by the supplier.
  This segment is used to detail the shipment.
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> HL01 628 Hierarchical ID Number M AN 1/12
  A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
>> HL03 735 Hierarchical Level Code M ID 1/2
  Code defining the characteristic of a level in a hierarchical structure
   
  S Shipment
 

           
Segment: TD1 Carrier Details (Quantity and Weight)
Position: 110
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: 20
Purpose: To specify the transportation details relative to commodity, weight, and quantity
Syntax Notes: 1 If TD101 is present, then TD102 is required.
  2 If TD103 is present, then TD104 is required.
  3 If TD106 is present, then TD107 is required.
  4 If either TD107 or TD108 is present, then the other is required.
  5 If either TD109 or TD110 is present, then the other is required.
Semantic Notes:
Comments:
Notes: Segment Example: TD1*CTN90*1****G*24*LB^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  TD101 103 Packaging Code O AN 3/5
  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
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  CTN Carton
  90 Standard
 
  TD102 80 Lading Quantity X N0 1/7
  Number of units (pieces) of the lading commodity
  TD106 187 Weight Qualifier O ID 1/2
  Code defining the type of weight
  Suggested codes for aftermaket usage. Any ASC X12 approved code may be used.
   
  G Gross Weight
  N Actual Net Weight
 
  TD107 81 Weight X R 1/10
  Numeric value of weight
  TD108 355 Unit or Basis for Measurement Code X ID 2/2
  Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  LB Pound
 
  TD109 183 Volume X R 1/8
  Value of volumetric measure
  TD110 355 Unit or Basis for Measurement Code X ID 2/2
  Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: TD5 Carrier Details (Routing Sequence/Transit Time)
Position: 120
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify the carrier and sequence of routing and provide transit time information
Syntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required.
  2 If TD502 is present, then TD503 is required.
  3 If TD507 is present, then TD508 is required.
  4 If TD510 is present, then TD511 is required.
  5 If TD513 is present, then TD512 is required.
  6 If TD514 is present, then TD513 is required.
  7 If TD515 is present, then TD512 is required.
Semantic Notes: 1 TD515 is the country where the service is to be performed.
Comments: 1 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.
Notes: Segment Example: TD5*B*2*YFSY*LT^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  TD501 133 Routing Sequence Code O ID 1/2
  Code describing the relationship of a carrier to a specific shipment movement
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  B Origin/Delivery Carrier (Any Mode)
 
  TD502 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  2 Standard Carrier Alpha Code (SCAC)
 
  TD503 67 Identification Code X AN 2/80
  Code identifying a party or other code
  TD504 91 Transportation Method/Type Code X ID 1/2
  Code specifying the method or type of transportation for the shipment
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  A Air
  AE Air Express
  LT Less Than Trailer Load (LTL)
  R Rail
  U Private Parcel Service
 
  TD507 309 Location Qualifier O ID 1/2
  Code identifying type of location
  If the code value of element TD504 is "A" or "AE," elements TD507 and TD508 would be used.
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  OR Origin (Shipping Point)
 
  TD508 310 Location Identifier X AN 1/30
  Code which identifies a specific location
  TD513 284 Service Level Code X ID 2/2
  Code indicating the level of transportation service or the billing service offered by the transportation carrier
  Refer to 004010 Data Element Dictionary for acceptable code values.
  TD514 284 Service Level Code O ID 2/2
  Code indicating the level of transportation service or the billing service offered by the transportation carrier
  Refer to 004010 Data Element Dictionary for acceptable code values.
  TD515 26 Country Code O ID 2/3
  Code identifying the country

           
Segment: TD3 Carrier Details (Equipment)
Position: 130
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: 12
Purpose: To specify transportation details relating to the equipment used by the carrier
Syntax Notes: 1 Only one of TD301 or TD310 may be present.
  2 If TD302 is present, then TD303 is required.
  3 If TD304 is present, then TD305 is required.
  4 If either TD305 or TD306 is present, then the other is required.
Semantic Notes:
Comments:
Notes: Segment Example: TD5*TL**0579745
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
  TD301 40 Equipment Description Code X ID 2/2
  Code identifying type of equipment used for shipment
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  AF Air Freight (Break Bulk)
  TL Trailer (not otherwise specified)
 
  TD303 207 Equipment Number X AN 1/10
  Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
  TD310 24 Equipment Type X ID 4/4
  Code identifying equipment type

           
Segment: REF Reference Identification
Position: 150
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: >1
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
  2 If either C04003 or C04004 is present, then the other is required.
  3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: Segment Example: REF*BM*579745^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> REF01 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  PK Packing List Number
 
  REF02 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  REF04 C040 Reference Identifier O
  To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
>> C04001 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> C04002 127 Reference Identification M AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  C04003 128 Reference Identification Qualifier X ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
  C04004 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  C04005 128 Reference Identification Qualifier X ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
  C04006 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

           
Segment: REF Reference Identification
Position: 150
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: >1
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
  2 If either C04003 or C04004 is present, then the other is required.
  3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: Segment Example: REF*PK*579745^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> REF01 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  BM Bill of Lading Number
  PK Packing List Number
 
  REF02 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  REF04 C040 Reference Identifier O
  To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
>> C04001 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
>> C04002 127 Reference Identification M AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  C04003 128 Reference Identification Qualifier X ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
  C04004 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
  C04005 128 Reference Identification Qualifier X ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
  C04006 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

           
Segment: CLD Load Detail
Position: 170
Loop: CLD Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify the number of material loads shipped
Syntax Notes: 1 If CLD05 is present, then CLD04 is required.
Semantic Notes: 1 CLD05 is used to dimension the value given in CLD04.
Comments: 1 The CLD data segment may be used to provide information to aid in the preparation of move tags and/or bar coded labels.
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> CLD01 622 Number of Loads M N0 1/5
  Number of customer-defined loads shipped by the supplier
>> CLD02 382 Number of Units Shipped M R 1/10
  Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
  CLD03 103 Packaging Code O AN 3/5
  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
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: REF Reference Identification
Position: 180
Loop: CLD Optional
Level: Detail
Usage: Optional
Max Use: 200
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
  2 If either C04003 or C04004 is present, then the other is required.
  3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
 
 
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> REF01 128 Reference Identification Qualifier M ID 2/3
  Code qualifying the Reference Identification
  Refer to 004010 Data Element Dictionary for acceptable code values.
  REF02 127 Reference Identification X AN 1/30
  Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

           
Segment: FOB F.O.B. Related Instructions
Position: 210
Loop: HL Mandatory
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify transportation instructions relating to shipment
Syntax Notes: 1 If FOB03 is present, then FOB02 is required.
  2 If FOB04 is present, then FOB05 is required.
  3 If FOB07 is present, then FOB06 is required.
  4 If FOB08 is present, then FOB09 is required.
Semantic Notes: 1 FOB01 indicates which party will pay the carrier.
  2 FOB02 is the code specifying transportation responsibility location.
  3 FOB06 is the code specifying the title passage location.
  4 FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
Comments:
Notes: Segment Example: FOB*CC^
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> FOB01 146 Shipment Method of Payment M ID 2/2
  Code identifying payment terms for transportation charges
  Suggested codes for aftermarket usage. Any ASC X12 approved code may be used.
   
  CA Advance Collect
  CC Collect
  PC Prepaid but Charged to Customer
  PP Prepaid (by Seller)
  PU Pickup
 

           
Segment: N1 Name
Position: 220
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
  2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 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.
  2 N105 and N106 further define the type of entity in N101.
Notes: Segment Example: N1*SF**91*H9811A1^ 
SF--The ship-from information is used to specify the supplier's shipment location, and is important when the supplier ships to the distributor from several points. 
ST--Ship To 
BT--Bill To
 
Data Element Summary 
                               
  Ref. Data
  Des. Element Name Attributes
>> N101 98 Entity Identifier Code M ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  SF Ship From
 
  N103 66 Identification Code Qualifier X ID 1/2
  Code designating the system/method of code structure used for Identification Code (67)
  Suggested code for aftermarket usage. Any ASC X12 approved code may be used.
   
  91 Assigned by Seller or Seller's Agent
 
  N104 67 Identification Code X AN 2/80
  Code identifying a party or other code
  N105 706 Entity Relationship Code O ID 2/2
  Code describing entity relationship
  Refer to 004010 Data Element Dictionary for acceptable code values.
  N106 98 Entity Identifier Code O ID 2/3
  Code identifying an organizational entity, a physical location, property or an individual
  Refer to 004010 Data Element Dictionary for acceptable code values.

           
Segment: N3 Address Information
Position: 240
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
 
 
 
Data Element Summary