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
Example: BSN00000000001200310161211*0002
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
This element contains the transaction date as assigned by the party sending the message.
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
- 0001
- Shipment, Order, Packaging, Item
- 0002
- Shipment, Order, Item, Packaging
Detail
Example: HL*1**S
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 (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This segment is required to be provided when any part of an order is being shipped. If you are only reporting cancellations/backorders this segment is not required to be provided.
Example: TD5B***UPSN_CG
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
Always required.
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
This element contains a Home Depot specific code that indicates both the shipper and the level of service. Contact CommerceHub for a complete list of codes. Failure to include one of the approved codes (even during the testing phase of your implementation) will result in a failure to process the message.
There will be cases where an 'unspecified' code will be issued to you on the purchase order. Home Depot will not accept this same 'unspecified' code back in the shipment confirmation. It is expected that you will provide a code that actually represents the shipper and service level.
Reference Identification
To specify identifying information
Example: REFIAZ001
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
This qualifier indicates that the REF02 contains the Home Depot assigned vendor number.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
This segment is required to be included when any part of an order is shipping. If only cancellations are included, this segment may be omitted.
Example: DTM01120031015
Code specifying type of date or time, or both date and time
- 011
- Shipped
This qualifier indicates that the DTM02 contains the date that the items were shipped.
Date expressed as CCYYMMDD
This element contains the Home Depot assigned vendor number.
Name
To identify a party by type of organization, name, and code
The Home Depot requires the point-of-origin for all shipments to be reported as part of the fulfillment confirmation. The name and address of the facility from which shipment originates should be reported in this SF qualified N1 loop.
If only cancellations are being reported, this N1 loop is not required to be
reported.
Example: N1SFTHE ABC CO938119
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Name and address of fulfillment centre.
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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
Example: N321 CORPORATE DRSUITE 205
Geographic Location
To specify the geographic place of the named party
Example: N4CLIFTON PARKNY120658763USA
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)
Example: HL21*O
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Example: PRF*1999999999
Identifying number for Purchase Order assigned by the orderer/purchaser
This element contains the purchase order number as issued by The Home Depot. Failure to report a valid purchase order number will result in a failure to process the message.
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Example: LIN02VN477631SK*11254
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
This element must contain The Home Depot purchase order line number.
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.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
This element contains the Vendor SKU for the product.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
This qualifier indicates that the LIN05 contains The Home Depot SKU.
Identifying number for a product or service
This element contains The Home Depot SKU for the product.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Examples:
SN13EAAC (Shipment)
SN10EA**3EA**IR (Cancel)
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
When shipping, this element must contain the number of units shipped. When cancelling, this element must contain a zero.
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
Quantity ordered
When shipping, this element is not required to be populated. When cancelling, this element must contain the number of units being cancelled.
Code specifying the action taken by the seller on a line item requested by the buyer
When shipping, this element will always contain a value of AC. When cancelling, this element will contain one of the cancel codes listed.
- AC
- Item Accepted and Shipped
- ID
- Item Deleted
- merchant_request
- IF
- Item on Hold, Incomplete Description
- info_missing
- IR
- Item Rejected
- info_missing
- R1
- Item Rejected, Not a Contract Item
- discontinued
- R2
- Item Rejected, Invalid Item Product Number
- bad_sku
- R4
- Item Rejected, Contract Item not Available
- out_of_stock
This pack loop is not required to be provided if only cancellations or backorders are being reported.
Example: HL32*P
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.
- P
- Pack
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Example: MANCP00000983767102803932
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- CP
- Carrier-Assigned Package ID Number
This qualifier indicates that the MAN02 contains the tracking number for the package.
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
This element contains the tracking number for the package.
CommerceHub enforces validation rules for UPS and FEDEX tracking numbers including check digit routines when applicable. Please insure that all tracking numbers you submit are correctly formatted. Any shipment confirmation message containing invalid tracking numbers will be rejected.
This pack loop is not required to be provided if only cancellations or backorders are being reported.
Example: HL32*P
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.
- P
- Pack
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Example: MANCP00000983767102803932
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- CP
- Carrier-Assigned Package ID Number
This qualifier indicates that the MAN02 contains the tracking number for the package.
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
This element contains the tracking number for the package.
CommerceHub enforces validation rules for UPS and FEDEX tracking numbers including check digit routines when applicable. Please insure that all tracking numbers you submit are correctly formatted. Any shipment confirmation message containing invalid tracking numbers will be rejected.
Example: HL43*I
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
Example: LIN02VN477631SK*11254
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
This element must contain The Home Depot purchase order line number.
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.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
This element contains the Vendor SKU for the product.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
This qualifier indicates that the LIN05 contains The Home Depot SKU.
Identifying number for a product or service
This element contains The Home Depot SKU for the product.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Examples:
SN13EAAC (Shipment)
SN10EA**3EA**IR (Cancel)
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
When shipping, this element must contain the number of units shipped. When cancelling, this element must contain a zero.
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
Quantity ordered
When shipping, this element is not required to be populated. When cancelling, this element must contain the number of units being cancelled.
Code specifying the action taken by the seller on a line item requested by the buyer
When shipping, this element will always contain a value of AC. When cancelling, this element will contain one of the cancel codes listed.
- AC
- Item Accepted and Shipped
- ID
- Item Deleted
- merchant_request
- IF
- Item on Hold, Incomplete Description
- info_missing
- IR
- Item Rejected
- info_missing
- R1
- Item Rejected, Not a Contract Item
- discontinued
- R2
- Item Rejected, Invalid Item Product Number
- bad_sku
- R4
- Item Rejected, Contract Item not Available
- out_of_stock
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.
Example: CTT*1
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
Sample SOIP
BSN*00*000000001*20031016*1211*0002
HL*1**S
TD5*B****UPSN_CG
REF*IA*Z001
DTM*011*20031015
N1*SF*THE ABC CO*93*8119
N3*21 CORPORATE DR*SUITE 205
N4*CLIFTON PARK*NY*120658763*USA
HL*2*1*O
PRF*1999999999
HL*3*2*I
LIN*02*VN*477631*SK*11254
SN1**3*EA*****AC
HL*4*3*P
MAN*CP*00000983767102803932
CTT*4
SE*11*0001
Sample SOPI
BSN*00*000000001*20031016*1211*0002
HL*1**S
TD5*B****UPSN_CG
REF*IA*Z001
DTM*011*20031015
N1*SF*THE ABC CO*93*8119
N3*21 CORPORATE DR*SUITE 205
N4*CLIFTON PARK*NY*120658763*USA
HL*2*1*O
PRF*1999999999
HL*3*2*P
MAN*CP*00000983767102803932
HL*4*3*I
LIN*02*VN*477631*SK*11254
SN1**3*EA*****AC
CTT*4
SE*11*0001
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.