X12 856 Dropship Ship Notice/Manifest
This X12 Transaction Set 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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00406
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 004060
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
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) 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).
- 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
- 14
- Advance Notification
A unique control number assigned by the original shipper to identify a specific shipment
The Homedepot.com and YOW Requirements: This reference number should be guaranteed not to repeat for at least a 12 month period. Supplier should insure that this number could be associated with the corresponding invoice.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- 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.
Format: HHMMSS
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0002
- Shipment, Order, Item, Packaging
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
The Homedepot.com and YOW Requirements: The interests of the shipper and the consignee are best served by the provision of the carton or piece counts. “Said to contain” pallet counts do not provide an adequate measure of shipment integrity. Home Depot requires use of the PCS25 qualifier.
- PCS
- Pieces
Number of units (pieces) of the lading commodity
The Homedepot.com and YOW Requirements: Must contain the actual number of lading pieces shipped. The count will typically be a carton count but may also reflect rolls, bags, or other lading units of measure.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
The Homedepot.com and YOW Requirements: Should be the carrier’s SCAC code as assigned by the National Motor Freight Traffic Association. If the shipment is delivered by the supplier’s truck, this element should be valued with “V1”.
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
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)
Reference Information
To specify identifying information
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
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
Party Identification
To identify a party by type of organization, name, and code
Party Location
To specify the location of the named party
Address information
The Homedepot.com and YOW Requirements: Your corporate street address.
Address information
The Homedepot.com and YOW Requirements: Your additional corporate street address.
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)
Code identifying type of location
The Homedepot.com and YOW Requirements: The N405 and N406 are used when the N101 contains the OB qualifier.
- SN
- Store Number
Code which identifies a specific location
The Homedepot.com and YOW Requirements: The N405 and N406 are used when the N101 contains the OB qualifier.
The N406 should contain the 4 digit Home Depot store number provided in the N104 of the PO.
Party Identification
To identify a party by type of organization, name, and code
Party Location
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)
Party Identification
To identify a party by type of organization, name, and code
Party Location
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)
Party Identification
To identify a party by type of organization, name, and code
Party Location
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
The Homedepot.com and YOW Requirements: Should match the PO number of the original order.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- PRF04 is the date assigned by the purchaser to purchase order.
The Homedepot.com and YOW Requirements: YYMMDD. Should match the PO date of the original order.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
The Homedepot.com and YOW Requirements: The PO Weight (TD106 TD108) is REQUIRED for ALL Transit Facility shipments.
If a supplier shipping Direct to Store shipments is utilizing 1 ASN map to support both (1) Transit Facility and (2) Direct to Store shipments, then this segment may be provided on the ASN.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Marks and Numbers Information
To indicate identifying marks and numbers for shipping containers
The Homedepot.com and YOW Requirements: The Carrier Assigned Tracking Number is OPTIONAL for Transit Facility shipments and is only REQUIRED forALL Direct to Store Small Package shipments.
If a Transit Facility supplier is utilizing 1 ASN map to support both (1) Transit Facility shipments and (2) Direct toStore small package shipments, then this segment may be provided on all ASNs.
The small package carrier assigned tracking number provided on the ASN should match the physical barcode provided on the product.
The MAN segment will be repeated for each tracking/package number associated with the PO.
Options for providing ASNs for small package shipments:
- 1 ASN per PO.
- Multiple ASNs per PO.
- 1 ASN for each tracking number.
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
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.
The Homedepot.com and YOW Requirements: The carrier assigned tracking number/package number for the carton shipped. The MAN segment will be repeated for each tracking/package number associated with the PO.
The Homedepot.com and YOW Requirements: The HL - T (Tare) and corresponding MAN segment for Pallet and Loose Unit Barcode are REQUIRED for all Transit Facility Optional for Direct to Store shipments.
If a Small Package Direct to Store supplier is utilizing 1 ASN map to support both (1) Transit Facility shipments and (2) Direct to Store small package shipments, then this segment may be provided on all ASNs.
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.
- T
- Shipping Tare
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 Information
To indicate identifying marks and numbers for shipping containers
The Homedepot.com and YOW Requirements: The Pallet and Loose Unit Barcode (MAN01-MAN02) is REQUIRED for ALL Transit Facility shipments.
If a supplier shipping to the Transit Facility is utilizing 1 ASN map to support both (1) Transit Facility and (2) Direct to Store shipments, then this segment may be provided on the ASN.
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.
- GM
- SSCC-18 and Application Identifier
The Homedepot.com and YOW Requirements: The GM qualifier represents the SSCC-18/UCC128 pallet level barcode.
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.
The Homedepot.com and YOW Requirements: The SSCC-18/UCC128 provided in the MAN02 should represent the pallet level barcode.
The HL - I Item loop(s) within the HL - T (Tare) loop should represent all of the merchandise items that are contained on a specific pallet based on the barcode identified in the MAN02.
The number of characters must be 20 characters. The reference number may not be duplicated on subsequent shipments.
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.
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
Data structure for the 12 digit EAN.UCC (EAN International.UniformCode Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.).
- 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)
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
Data structure for the 12 digit EAN.UCC (EAN International.UniformCode Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.).
- 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)
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
Data structure for the 12 digit EAN.UCC (EAN International.UniformCode Council) Global Trade Identification Number (GTIN). Also known as the Universal Product Code (U.P.C.).
- VP
- Vendor's (Seller'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
The Homedepot.com and YOW Requirements: Total item quantity shipped. This ship quantity and unit of measure must correspond to the original ordered quantity/unit of measure. Conversion of “eaches” to “pack” or “linear feet” is invalid and will render item information useless.
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.
The Homedepot.com and YOW Requirements: Must equal Home Depot purchase order UOM.
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
Value to be used as a multiplier to obtain a new value
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Value to be used as a multiplier to obtain a new value
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Value to be used as a multiplier to obtain a new value
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Value to be used as a multiplier to obtain a new value
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Value to be used as a multiplier to obtain a new value
Price per unit of product, service, commodity, etc.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the unit of measure of the "Size" identified in the PO402.
For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
The Homedepot.com and YOW Requirements: Must use UOM on the original order.
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.
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
The Homedepot.com and YOW Requirements: Number of HL Loops in transaction.
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
The Homedepot.com and YOW Requirements: The Sum on SN102 elements (units shipped).
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
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.