X12 856 Retail 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
- 12
- Phone (Telephone Companies)
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
- 004010VICS
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
The BSN02 must be unique for each ASN sent or the entire document will be rejected.
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.
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
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN
- Carton
- 25
- Corrugated or Solid
Number of units (pieces) of the lading commodity
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, TD504 should contain code U.
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)
Code specifying the method or type of transportation for the shipment
- 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
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
This segment is only mandatory for deconsolidators that send ASNs for Import and Landed shipments.
Code identifying type of equipment used for shipment
- CN
- Container
Prefix or alphabetic part of an equipment unit's identifying number
Container SCAC Code (Alpha Characters of Container ID)
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Unique Container ID (Numeric Characters of Container ID)
Bill of Lading Number
To specify identifying information
Kohl’s requires that the Bill of Lading Number and the TP Load Number are transmitted.
The Bill of Lading number must match the number on the physical Bill of Lading that is tendered to the carrier.
Example: REFBM12345678912345678
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Carrier's Reference Number (PRO/Invoice)
To specify identifying information
The Carrier’s Reference Number is optional but preferred.
Example: REFCN293010
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
System Number
To specify identifying information
Kohl’s requires that the Bill of Lading Number and the TP Load Number are transmitted.
The TP Load Number is also referred to as the ME (Mode Execution) ID in Transplace.
The ME/TP Load Number should be 9 digits. The TP load number should not contain leading zeros.
The TP load number should contain numeric values only (do not include a leading "TP").
Example: REF06706869401
Code qualifying the Reference Identification
- 06
- System Number
System Number / TP Load Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
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)
Name
To identify a party by type of organization, name, and code
Kohl’s has multiple Distribution Centers. Store to Distribution Center relationships are transmitted via the 816 - Organizational Relationship
document.
When N101 = SF,
N102 should be the vendor/consolidator name
N103 should be 91
N104 should be the Vendor Location ID if there is more than one shipping location. If there is only one shipping location, this field can contain the vendor name.
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)
- 91
- Assigned by Seller or Seller's Agent
- 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.
Kohl’s 5-digit DC Number
Kohl’s 5-digit Store Number
Vendor’s Location ID or Vendor/Consolidator Name
Address Information
To specify the location of the named party
The N3 segment needs to be sent if the previous N1 segment contains Ship From information.
Geographic Location
To specify the geographic place of the named party
The N3 segment needs to be sent if the previous N1 segment contains Ship From information.
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
The N104 field may contain a store number only if the ASN is for a direct to store shipment. Mark for store shipments need to be sent with the DC
number.
When N101 = ST,
N102 should be Kohl’s
N103 should be 92
N104 should be a Kohl’s 5-digit Distribution Center number or 5-digit Store number
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)
- 91
- Assigned by Seller or Seller's Agent
- 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.
Kohl’s 5-digit DC Number
Kohl’s 5-digit Store Number
Vendor’s Location ID or Vendor/Consolidator Name
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 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
The Purchase Order number is required and must match the number transmitted on Kohl’s 850 or vendor’s 855.
Identifying number for Purchase Order assigned by the orderer/purchaser
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
The TD102 field should contain the store’s carton count if the ASN is for a mark for store order. The TD102 field should contain the purchase
order’s carton count if the ASN is for a non mark for store order.
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
- 25
- Corrugated or Solid
Number of units (pieces) of the lading commodity
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DP
- Department Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Name
To identify a party by type of organization, name, and code
Kohl’s has multiple Distribution Centers. Store to Distribution Center associations are transmitted via the 816 - Organizational Relationship
document.
When N101 = BY,
N102 should be KOHLS
N103 should be 92
N104 should be a Kohl’s 5-digit Distribution Center number for bulk and prepack shipments or 5-digit Store number for mark for store
shipments.
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.
Kohl’s 5-Digit DC Number
Kohl’s 5-Digit 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
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
The UPC or EAN is required and must match the UPC or EAN on Kohl’s 850 or vendor’s 855.
Kohl’s recommends when shipping an assortment that the LIN03 reflect the pack UPC number. The SN103 needs to be AS for assortment. The
SLN/Item loops would contain the item UPC numbers or EANs.
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
Item Detail (Shipment)
To specify line-item detail relative to shipment
For the Standard Carton Structure, the SN102 should be the total number of eaches per UPC shipped.
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.
- AS
- Assortment
- EA
- Each
Subline Item Detail
To specify product subline detail item data
The SLN10 must contain the item UPC numbers or EAN’s within the pack.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
- S
- Substituted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten 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
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Kohl’s does not require the PO4 segment if the ASN is in the Pick and Pack Structure.
The PO4 segment is mandatory if the ASN is in the Standard Structure.
The PO414 is required if there are inner containers in each outer carton. If there are no inner containers, send only the PO401.
Examples of an inner container can be bundles, polybags or inner cartons.
Example:
The carton contains 2 inner containers, each of which has 4 items
PO42************4
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
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.
- EA
- Each
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- S
- Structured (From Industry Code List)
Code specifying the marking, packaging, loading and related characteristics being described
- 36
- Package Specifications
Code identifying the agency assigning the code values
- Use PKG03 to indicate the organization that publishes the code list being referred to.
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
First character:
L Logical Container
P Physical Container
Last 2 characters:
01 Carton
02 Carton, Hanging Garments
03 Carton, With Hangers (not hanging)
04 Carton, With Identifiable Inner Packs
05 Carton, With Unidentifiable Inner Packs
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The MAN04 and MAN05 fields only need to be sent for Outlet store shipments.
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
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.
Code specifying the application or source of Marks and Numbers (87)
- CP
- Carrier-Assigned Package ID Number
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
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.
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- S
- Structured (From Industry Code List)
Code specifying the marking, packaging, loading and related characteristics being described
- 36
- Package Specifications
Code identifying the agency assigning the code values
- Use PKG03 to indicate the organization that publishes the code list being referred to.
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
The MAN04 and MAN05 fields only need to be sent for Outlet store shipments.
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
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.
Code specifying the application or source of Marks and Numbers (87)
- CP
- Carrier-Assigned Package ID Number
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
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 UPC or EAN is required and must match the UPC or EAN on Kohl’s 850 or vendor’s 855.
Kohl’s recommends when shipping an assortment that the LIN03 reflect the pack UPC number. The SN103 needs to be AS for assortment. The
SLN/Item loops would contain the item UPC numbers or EANs.
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
Item Detail (Shipment)
To specify line-item detail relative to shipment
For the Pick and Pack Structure, when the SN103 is AS the SN102 must be the total number of packs in the carton.
For the Pick and Pack Structure, when the SN103 is EA the SN102 must be the total number of units per carton.
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.
- AS
- Assortment
- EA
- Each
Subline Item Detail
To specify product subline detail item data
The SLN10 must contain the item UPC numbers or EAN’s within the pack.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
- S
- Substituted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten 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
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This segment can be sent only for the Pick and Pack Structure.
The PO414 is required if there are inner containers in each outer carton. If there are no inner containers, send only the PO401.
Examples of an inner container can be bundles, polybags or inner cartons.
Example:
The carton contains 2 inner containers, each of which has 4 items
PO42************4
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Total number of line items in the transaction set
The 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
Pick and Pack Structure for Bulk / Casepack Order
GS*SH*SENDERGS*RECEIVERGS*20231006*005926*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*2****G*30*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*2
N1*BY**92*00810
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*888888888888
SN1**10*EA
HL*5*2*P
MAN*GM*00000111111111122222
HL*6*5*I
LIN**UP*888888888888
SN1**10*EA
CTT*8
SE*30*0001
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure for Compound Multiple Prepack Order
GS*SH*SENDERGS*RECEIVERGS*20231006*005805*000000001*X*004010
ST*856*000000007
BSN*00*920007*20181102*1249*0001
HL*1**S
TD1*CTN25*2****G*19.00*LB
TD5*O*2*ABCD*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20181102
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*2
N1*BY**92*00810
HL*3*2*P
MAN*GM*00400000020024001008
HL*4*3*I
LIN**UP*400800440012
SN1**1*AS
SLN*1**I*1*EA****UP*222222222555
SLN*2**I*3*EA****UP*222222222666
SLN*3**I*2*EA****UP*222222222777
HL*5*2*P
MAN*GM*00400000020024003004
HL*6*5*I
LIN**UP*400800440064
SN1**1*AS
SLN*1**I*3*EA****UP*222222222555
SLN*2**I*2*EA****UP*222222222666
SLN*3**I*1*EA****UP*222222222777
CTT*6
SE*36*000000007
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure for Inner Prepack Order
GS*SH*SENDERGS*RECEIVERGS*20231006*005726*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*1****G*30*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*1
N1*BY**92*00810
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*400126789123
SN1**2*AS
SLN*1**I*1*EA****UP*222222222555
SLN*2**I*3*EA****UP*222222222666
SLN*3**I*2*EA****UP*222222222777
CTT*8
SE*28*0001
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure for Multiple Prepack Order 1
GS*SH*SENDERGS*RECEIVERGS*20231006*005554*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*1****G*30*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*1
N1*BY**92*00810
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*400126789123
SN1**1*AS
SLN*1**I*1*EA****UP*222222222555
SLN*2**I*3*EA****UP*222222222666
SLN*3**I*2*EA****UP*222222222777
CTT*8
SE*28*0001
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure for Multiple Prepack Order 2
GS*SH*SENDERGS*RECEIVERGS*20231006*005645*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*1****G*30*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*1
N1*BY**92*00810
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*400126789123
SN1**1*AS
CTT*8
SE*25*0001
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure-Direct to Store
GS*SH*SENDERGS*RECEIVERGS*20231006*010137*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*1****G*30*LB
TD5*O*2*JDOE*M
REF*BM*1Z123456789123456
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00007
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*1
N1*BY**92*00007
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*888888888888
SN1**20*EA
HL*5*3*I
LIN**UP*999999999999
SN1**5*EA
CTT*8
SE*26*0001
GE*1*000000001
IEA*1*000000001
Pick and Pack Structure-Mark for store, ship to DC
GS*SH*SENDERGS*RECEIVERGS*20231006*005529*000000001*X*004010
ST*856*0001
BSN*00*000004*20180115*1249*0001
HL*1**S
TD1*CTN25*2****G*100*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*1
N1*BY**92*00007
HL*3*2*P
MAN*GM*00000111111111111111
HL*4*3*I
LIN**UP*888888888888
SN1**20*EA
HL*5*3*I
LIN**UP*999999999999
SN1**5*EA
HL*6*1*O
PRF*234567
TD1*CTN25*1
N1*BY**92*00008
HL*7*6*P
MAN*GM*00000222222222222222
HL*8*7*I
LIN**UP*555555555555
SN1**10*EA
CTT*8
SE*37*0001
GE*1*000000001
IEA*1*000000001
Standard Structure for Bulk / Casepack Order
GS*SH*SENDERGS*RECEIVERGS*20231006*010003*000000001*X*004010
ST*856*0001
BSN*00*000001*20180115*1430*0002
HL*1**S
TD1*CTN25*2****G*30*LB
TD5*O*2*JDOE*M
REF*06*706869401
REF*BM*562834
REF*CN*293010
PER*IC**EM*JDOE@KOHLSTRADINGPARTNER.COM
DTM*011*20180115*1430
N1*ST*KOHLS*92*00810
N1*SF*COMPANY NAME
N3*123 MAIN STREET
N4*ANYWHERE*WI*55555
HL*2*1*O
PRF*12345678
TD1*CTN25*2
N1*BY**92*00810
HL*3*2*I
LIN**UP*888888888888
SN1**20*EA
HL*4*3*P
PO4*2*************5
MAN*GM*00000111111111111111
HL*5*3*P
PO4*2*************5
MAN*GM*00000111111111222222
CTT*8
SE*29*0001
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.