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
- 004010VICS
- Voluntary Inter-Industry Commerce Standards; The EDI Standards maintained and utilized by the retail industry.
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
- 07
- Duplicate
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.
Date the shipment transaction 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.
Time the shipment transaction 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
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN
- Carton
Number of units (pieces) of the lading commodity
The number of packages in the shipment as described in TD101
Numeric value of weight
Shipment’s Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
When using a small package service provider as the carrier, TD502 will contain code 2, TD503 will contain the carrier’s SCAC, and TD504 will contain code U to inform Dick’s of a small package service shipment.
If shipping collect, TD503 should match the carrier code that is provided in the approved routing request screen in Dick’s TMS system. If shipping prepaid, TD503 must contain the National motor freight traffic association (NMFTA) SCAC code of your chosen carrier. Any questions regarding the population of this field should be directed to tms@dcsg.com or 724-273-4500.
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
SCAC
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- BU
- Bus
- C
- Consolidation
- CE
- Customer Pickup / Customer's Expense
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- L
- Contract Carrier
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Reference Identification
To specify identifying information
- The Approved Shipment ID Number is the value assigned to a Dick’s shipment in our TMS system after routing has been requested and must be sent for all shipments.
- Small package service carriers do not use a BOL. In cases where a small package service carrier is used, the vendor should provide the current date as the BOL.
- Small package service carriers do not use a Pro Number. In all other cases, the vendor must provide the PRO Number.
Code qualifying the Reference Identification
- BB
- Authorization Number
- 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
Reference Number
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 011
- Shipped
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)
Shipped Time
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
- FOB01 indicates which party will pay the carrier.
- FOB02 is the code specifying ransportation responsibility location.
- This segment should only be sent by import vendors.
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- MX
- Mixed
- PP
- Prepaid (by Seller)
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- CA
- Country of Origin
A free-form description to clarify the related data elements and their content
Country of Origin
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Dick’s Internal Vendor Number
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Dick’s Ship To Location Number
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Purchase Order Reference
To provide reference to a specific purchase order
If a vendor is on the parent/child order program (blanket/release) with Dick’s, the PRF01 contains the parent (blanket) order, while the PRF02 contains the child (release) order. If a vendor is unable to save both the parent (blanket) and child (release) orders in their system, then the PRF01 should contain the child (release) order number.
Identifying number for Purchase Order assigned by the orderer/purchaser
Dick’s Purchase Order Number
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Dick’s release against the purchase order
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN
- Carton
Number of units (pieces) of the lading commodity
The number of packages for each order/store combination
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Invoice Number
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Dick’s Store Number
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Item Identification
To specify basic item identification data
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.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Vendor UPC or EAN Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
Vendor Style Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Quantity Shipped for Item
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.
- CA
- Case
- EA
- Each
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
Item’s Casepack
Numeric value of gross weight per pack
Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
The number of eaches per inner container
Number of components found in one inner container
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
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The SSCC-18 and Application Identifier is required for every carton
The Carrier-Assigned Package ID Number is required for every carton shipped via a small parcel package carrier
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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier.
- GM
- SSCC-18 and Application Identifier
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.
SSCC-18 Code
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
Code indicating the type of pallet
- 1
- Aluminum
- 2
- As Specified by the Department of Transportation (DOT)
- 3
- Metal
- 4
- Standard
- 5
- Steel
- 6
- Wood
- 7
- Slip sheet
The number of pieces (cartons) per layer on the pallet
The number of inner containers, or number of eaches if there are no inner containers, per outer container
- PAL04 (Pack) is the number of pieces on the pallet.
Number of pieces on the pallet
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Weight of the pallet alone, before loading
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Length of the pallet before loading
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Width of the pallet before loading
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
Height of the pallet and load
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- IN
- Inch
Numeric value of gross weight per pack
- PAL11 and PAL13 (Gross Weight and Gross Volume) are measured after loading and includes the pallet.
Gross weight measured after loading and includes the pallet
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
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
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The segment is used to specify the packaging of the item in the case or carton. There may be two levels of packaging specified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units, or it may be the number of smaller containers
within the case. The second level, specified using PO414 (Inner Pack), is the number of eaches in each inner container when PO401 is the number of smaller containers within the case.
If the BSN05 = 0001 and only one upc is packed per carton, then the PO401 and the SN102 will be the same value.
The PO401 should contain the same casepack value that is sent in the 850 Purchase Order under the PO401 and it should also reflect the casepack in the shipment. If the PO401 in the 850 Purchase Order does not match the casepack in the shipment, contact Vendor Relations
VendorRelationsComplianceTeam@dcsg.com
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Numeric value of gross weight per pack
Pack’s Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
Pack’s Length
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Pack’s Width
Vertical dimension of an object measured when the object is in the upright position
Pack’s Height
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- IN
- Inch
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The SSCC-18 and Application Identifier is required for every carton
The Carrier-Assigned Package ID Number is required for every carton shipped via a small parcel package carrier
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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier.
- CP
- Carrier-Assigned Package ID Number
- GM
- SSCC-18 and Application Identifier
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.
Tracking Number
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
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
Numeric value of gross weight per pack
Pack’s Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
Pack’s Length
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Pack’s Width
Vertical dimension of an object measured when the object is in the upright position
Pack’s Height
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- IN
- Inch
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The SSCC-18 and Application Identifier is required for every carton
The Carrier-Assigned Package ID Number is required for every carton shipped via a small parcel package carrier
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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier.
- CP
- Carrier-Assigned Package ID Number
- GM
- SSCC-18 and Application Identifier
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.
Tracking Number
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Item Identification
To specify basic item identification data
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.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Vendor UPC or EAN Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
Vendor Style Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Quantity Shipped for Item
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.
- CA
- Case
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The segment is used to specify the packaging of the item in the case or carton. There may be two levels of packaging specified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units, or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is the number of eaches in each inner container when PO401 is the number of smaller containers within the case.
If the BSN05 = 0001 and only one upc is packed per carton, then the PO401 and the SN102 will be the same value.
The PO401 should contain the same casepack value that is sent in the 850 Purchase Order under the PO401 and it should also reflect the casepack in the shipment. If the PO401 in the 850
Purchase Order does not match the casepack in the shipment, contact Vendor Relations VendorRelationsComplianceTeam@dcsg.com
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Item’s Casepack
Numeric value of gross weight per pack
Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
The number of eaches per inner container
Number of components found in one inner container
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
To indicate identifying marks and numbers for shipping containers
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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier
- GM
- SSCC-18 and Application Identifier
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.
SSCC-18 Code
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
Code indicating the type of pallet
- 1
- Aluminum
- 2
- As Specified by the Department of Transportation (DOT)
- 3
- Metal
- 4
- Standard
- 5
- Steel
- 6
- Wood
- 7
- Slip sheet
The number of pieces (cartons) per layer on the pallet
The number of inner containers, or number of eaches if there are no inner containers, per outer container
- PAL04 (Pack) is the number of pieces on the pallet.
Number of pieces on the pallet
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Weight of the pallet alone, before loading
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Length of the pallet before loading
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Width of the pallet before loading
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
Height of the pallet and load
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- IN
- Inch
Numeric value of gross weight per pack
- PAL11 and PAL13 (Gross Weight and Gross Volume) are measured after loading and includes the pallet.
Gross weight measured after loading and includes the pallet
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
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
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
Numeric value of gross weight per pack
Pack’s Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
Pack’s Length
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Pack’s Width
Vertical dimension of an object measured when the object is in the upright position
Pack’s Height
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- IN
- Inch
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The SSCC-18 and Application Identifier is required for every carton
The Carrier-Assigned Package ID Number is required for every carton shipped via a small parcel package carrier
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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier.
- CP
- Carrier-Assigned Package ID Number
- GM
- SSCC-18 and Application Identifier
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.
Tracking Number
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Item Identification
To specify basic item identification data
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.
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Vendor UPC or EAN Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
Vendor Style Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Quantity Shipped for Item
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.
- CA
- Case
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The segment is used to specify the packaging of the item in the case or carton. There may be two levels of packaging specified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units, or it may be the number of smaller containers
within the case. The second level, specified using PO414 (Inner Pack), is the number of eaches in each inner container when PO401 is the number of smaller containers within the case.
If the BSN05 = 0001 and only one upc is packed per carton, then the PO401 and the SN102 will be the same value.
The PO401 should contain the same casepack value that is sent in the 850 Purchase Order under the PO401 and it should also reflect the casepack in the shipment. If the PO401 in the 850 Purchase Order does not match the casepack in the shipment, contact Vendor Relations
VendorRelationsComplianceTeam@dcsg.com
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Item’s Casepack
Numeric value of gross weight per pack
Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
The number of eaches per inner container
Number of components found in one inner container
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
Number of HL segments present in the transaction set
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
DICKSSG_856_1
GS*SH*6122650000*DICKSSG*20050808*1430*000004113*X*004010VICS
ST*856*0001
BSN*00*004077905*20070630*00210455*0001
HL*1*0*S
TD1*CTN*3****G*9*LB
TD5**2*UPSN*U
REF*BB*CS00312085
REF*BM*BOL12345
REF*CN*1Z6910020378851370
DTM*011*20070630*00210455
N1*ST**92*0051
N1*SF**92*1234
HL*2*1*O
PRF*16000000
TD1*CTN*3
N1*BY**92*0051
HL*3*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851377
MAN*CP*1Z6910020378851370
HL*4*3*I
LIN**UP*012345678901*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
HL*5*3*I
LIN**UP*012345678902*VA*STYLEA
SN1**8*EA
PO4*1****G*1*LB*******8
HL*6*3*I
LIN**UP*012345678905*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
HL*7*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851378
MAN*CP*1Z6910020378851371
HL*8*7*I
LIN**UP*012345678901*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
HL*9*7*I
LIN**UP*012345678902*VA*STYLEA
SN1**8*EA
PO4*1****G*1*LB*******8
HL*10*7*I
LIN**UP*012345678905*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
HL*11*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851379
MAN*CP*1Z6910020378851372
HL*12*11*I
LIN**UP*012345678901*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
HL*13*11*I
LIN**UP*012345678902*VA*STYLEA
SN1**8*EA
PO4*1****G*1*LB*******8
HL*14*11*I
LIN**UP*012345678905*VA*STYLEA
SN1**4*EA
PO4*1****G*1*LB*******8
CTT*14
SE*65*0001
GE*1*000004113
IEA*1*000004113
DICKSSG_856_2
GS*SH*6122650000*DICKSSG*20050808*1430*000004113*X*004010VICS
ST*856*0001
BSN*00*004077905*20070630*00210455*0001
HL*1*0*S
TD1*CTN*3****G*9*LB
TD5**2*UPSN*U
REF*BB*CS00312085
REF*BM*BOL12345
REF*CN*1Z6910020378851370
DTM*011*20070630*00210455
N1*ST**92*0051
N1*SF**92*1234
HL*2*1*O
PRF*16000000
TD1*CTN*3
N1*BY**92*0051
HL*3*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851377
MAN*CP*1Z6910020378851370
HL*4*3*I
LIN**UP*987654321098*VA*Style Prepack A
SN1**1*CA
PO4*2****G*1*LB*******8
HL*5*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851378
MAN*CP*1Z6910020378851371
HL*6*5*I
LIN**UP*987654321098*VA*Style Prepack A
SN1**1*CA
PO4*2****G*1*LB*******8
HL*7*2*P
PO4*****G*3*LB***14*12.25*9.25*IN
MAN*GM*00000297570078851379
MAN*CP*1Z6910020378851372
HL*8*7*I
LIN**UP*987654321098*VA*Style Prepack A
SN1**1*CA
PO4*2****G*1*LB*******8
CTT*8
SE*41*0001
GE*1*000004113
IEA*1*000004113
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.