X12 856 Retail Ship Notice/Manifest (Pick & Pack)
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
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
In some implementations, it may be appropriate to omit the unit load level and packaging levels, i.e., tare and pack, from the transaction set. Depending on the retailer's receiving systems, carton identification may not be required. Code 0004 in BSN05 indicates the use of a hierarchical structure that does not include a unit load level or any packaging levels.
Example: BSN00007111200010310745*0001~
Code identifying purpose of transaction set
- 00
- Original
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.
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.
Detail
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
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 (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
This segment, at the shipment level, is used to specify total containers and gross weight of the shipment.
Example: TD1CTN2524***G147*LB~
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
First 3 characters:
- BAG Bag
- CTN Carton
- MIX Mixed Container Types
More than one type of container is included in a shipment (shipment could consist of 3 pieces that include 1 box, 1 crate, and 1 basket).
Can be used only with code 71 in Part 2. - PLT Pallet
- SLP Slip Sheet
Shipping containers utilizing slip sheets, which are cardboard platforms used to hold product for storage or transportation. - SRW Shrink Wrap
In packaging, a method of securing a unit load by placing a large "bag" of plastic film over the components and applying heat to induce shrinkage and cause the bag to tighten around the contents.
Last 2 characters:
- 01 Aluminum
- 25 Corrugated or Solid
- 31 Fiber
- 58 Metal
- 71 Not Otherwise Specified
- 76 Paper
- 79 Plastic
- 91 Stainless Steel
-94 Wood
Number of units (pieces) of the lading commodity
The number of packages in the shipment as described in TD101.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previously identified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only use TD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a preestablished routing guide, use code 91 or 92 in TD502 and identify the routing sequence, from the routing guide, in TD503. To identify a specific private parcel service, TD502 will contain code 2 and TD503 will contain the corresponding SCAC. TD510 and TD511 are used to specify transit time.
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 the receiver of a small package service shipment.
Example: TD5O2CENF**CC~
Code describing the relationship of a carrier to a specific shipment movement
- O
- Origin Carrier (Air, Motor, or Ocean)
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
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
- BK
- Back Ordered from Previous Order
- BP
- Shipment Partial, Back Order to Ship on (Date)
- CC
- Shipment Complete on (Date)
- CM
- Shipment Complete with Additional Quantity
- CP
- Partial Shipment on (Date), Considered No Backorder
- CS
- Shipment Complete with Substitution
- DE
- Deleted Order
- IC
- Item Canceled
- IS
- Item Represents Substitution from Original Order
- PR
- Partial Shipment
- SS
- Split Shipment
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
This segment is used to specify the trailer number for a truckload shipment.
Example: TD3*TL**123456~
Code identifying type of equipment used for shipment
- CV
- Closed Van
- FT
- Flat Bed Trailer
- RT
- Controlled Temperature Trailer (Reefer)
- TL
- Trailer (not otherwise specified)
Bill of Lading Number
To specify identifying information
In some cases, individual shipments with bill of lading may be grouped under a Master Bill of Lading. Under this circumstance, specifying both the bill of lading and the associated Master Bill of Lading Number will facilitate tracking.
Example: REFBM13828700000A~
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Carrier's Reference Number (PRO/Invoice)
To specify identifying information
Example: REFCN13828700000A~
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Load Planning Number
To specify identifying information
Shipping Routing Request (SRR) is generated from Boscov’s TMS System to route all our inbound shipments.
Code qualifying the Reference Identification
- LO
- Load Planning Number
Current Schedule Delivery
To specify pertinent dates and times
Example: DTM06720000202~
Shipped
To specify pertinent dates and times
Example: DTM01120000202~
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Example: FOB*PP~
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- CF
- Collect, Freight Credited Back to Customer
- DF
- Defined by Buyer and Seller
- PC
- Prepaid but Charged to Customer
- PO
- Prepaid Only
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- OR
- Origin (Shipping Point)
Code identifying the source of the transportation terms
- 01
- Incoterms
See External Code Source 35 in Section III for the source reference document of INCOTERMS codes, which will appear in FOB05.
Name
To identify a party by type of organization, name, and code
N103 and N104 are required except when N101 contains code MA or OB.
When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.;
In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within each transaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104 will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in the combination listed above and may be used only to identify the sender and/or receiver of the transaction set.
Example: N1SF**1123456789~
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 91
- Assigned by Seller or Seller'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.
This is the location code as defined by N103. The location code may be a formal number, e.g., DUNS, or it may be assigned by either the buyer or seller. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
Address Information
To specify the location of the named party
Example: N3*100 MAIN ST~
Geographic Location
To specify the geographic place of the named party
N401 and N402 are required unless N405 and N406 are used.
Example: N4SAN FRANCISCOCA*94111~
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)
Name
To identify a party by type of organization, name, and code
N103 and N104 are required except when N101 contains code MA or OB.
When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.;
In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within each transaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104 will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in the combination listed above and may be used only to identify the sender and/or receiver of the transaction set.
Example: N1STBOSCOV9200015~
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.
Boscov’s five digit store number (may have leading zeroes).
Address Information
To specify the location of the named party
Example: N3*100 MAIN ST~
Geographic Location
To specify the geographic place of the named party
N401 and N402 are required unless N405 and N406 are used.
Example: N4SAN FRANCISCOCA*94111~
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)
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
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: PRF835490**20000114~
Identifying number for Purchase Order assigned by the orderer/purchaser
Boscov's 6-digit purchase order number (may use leading zeros).
Department Number
To specify identifying information
Example: REFDP00131~
Code qualifying the Reference Identification
- DP
- Department Number
Seller's Invoice Number
To specify identifying information
Example: REFIV807764626~
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Name
To identify a party by type of organization, name, and code
There will be at least one occurrence, of this segment, to identify the buying party by using code BY in N101.
N103 and N104 are required except when N101 contains code CT, MA or OB.
Example: N1BY**9200014~
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.
Boscov’s five digit store # (must use leading zeroes).
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Example: HL43*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
When the shipping container is the same as the consumer unit, the U.P.C. may be the only UCC identification code on the container. In many applications, it is necessary to positively identify what identification code is to be scanned and matched at point of receipt. Since the U.P.C. is not a unique serial shipping container code, only one pack level for each item is required when using the pick and pack structure. The total number of shipping units for this item is the same as the quantity for the item in the SN1 segment at the item level.
Example: MANGM00007000320000113906~
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
This is a twenty-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Example: HL54*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
The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.
See Section III for complete U.P.C. and EAN code definitions.
Example: LIN*UP700032591261VA20191~
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)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
This is the code assigned by the vendor.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used to specify the quantities associated with the item identified in the LIN at the item level.
When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 will contain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Each different component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.
Example: SN1*1EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
See Section III for code list.
- CA
- Case
- DZ
- Dozen
- EA
- Each
- PK
- Package
- PR
- Pair
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Example: HL32*T~
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.
Trailer Shipment Details
To specify details of shipments on a trailer
This segment may be used to indicate the location of the pallet within the trailer/container.
Example: TSD0011
Alphanumeric characters assigned for differentiation within a transaction set
- TSD01 indicates the loading sequence and relative shipment position on the trailer.
Indicates the loading sequence.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment, at the tare level, is used to specify the identification numbers for the pallet.;
Example: MANGM00107000320000113901~
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
This is a twenty-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.
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
Example: PAL44936
The number of pieces (cartons) per layer on the pallet
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Example: HL43*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
When the shipping container is the same as the consumer unit, the U.P.C. may be the only UCC identification code on the container. In many applications, it is necessary to positively identify what identification code is to be scanned and matched at point of receipt. Since the U.P.C. is not a unique serial shipping container code, only one pack level for each item is required when using the pick and pack structure. The total number of shipping units for this item is the same as the quantity for the item in the SN1 segment at the item level.
Example: MANGM00007000320000113906~
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
This is a twenty-character UCC/EAN-128 Serial
Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Example: HL54*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
The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.
See Section III for complete U.P.C. and EAN code definitions.
Example: LIN*UP700032591261VA20191~
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)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
This is the code assigned by the vendor.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- SZ
- Vendor Alphanumeric Size Code (NRMA)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VE
- Vendor Color
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used to specify the quantities associated with the item identified in the LIN at the item level.
When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 will contain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Each different component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.
Example: SN1*1EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
See Section III for code list.
- CA
- Case
- DZ
- Dozen
- EA
- Each
- PK
- Package
- PR
- Pair
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*9~
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*SH*SENDERGS*RECEIVERGS*20231002*145758*000000001*X*004010~
ST*856*856000706~
BSN*00*007111*20001031*0745*0001~
HL*1**S~
TD1*BAG*7****G*147*LB~
TD5*O*2*CENF~
TD3*TL**123456~
REF*BM*13828700000A~
REF*LO*123456~
DTM*011*20000202~
DTM*067*20000202~
FOB*PP~
N1*ST*BOSCOV*92*00015~
HL*2*1*O~
PRF*835490***20000114~
REF*DP*00482~
REF*IV*807764626~
N1*BY**92*00014~
HL*3*2*T~
TSD*001*1~
MAN*GM*00107000320000113901~
PAL*4*4*9*36~
HL*4*3*P~
MAN*GM*00007000320000113906~
HL*5*4*I~
LIN**UP*700032591261*VA*20191~
SN1**1*EA~
HL*6*2*T~
MAN*GM*00107000320000113831~
HL*7*6*P~
MAN*GM*00007000320000113838~
HL*8*7*I~
LIN**UP*700032591285*VA*20195~
SN1**2*EA~
HL*9*7*I~
LIN**UP*700032591339*VA*20205~
SN1**1*EA~
CTT*9~
SE*38*856000706~
GE*1*000000001~
IEA*1*000000001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.