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
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSN05 indicates the structure of the 856 and tells Kmart how to process the document.
Pick and pack structure (BSN05 contains code 0001) must be used for all JIT and direct-to-store shipments. If the no pack or standard carton pack structure is used, the ship notice cannot be processed; JIT product will be returned.
No pack structure may be used for DC (stock) shipments only.
Only one data structure may be used within a single transaction set.
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
- 0004
- Shipment, Order, Item
Detail
This HL segment marks the beginning of the shipment loop. The
shipment level is mandatory and may occur only once per transaction set.
The value in HL01 will always be 1 for the first occurrence of the HL
segment in the transaction set and will be incremented by 1 for each additional occurrence of the HL segment present within the
transaction set. This value may contain leading zeroes.
The shipment level specifies the details relative to the entire physical shipment and associated Bill of Lading.
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
The lading quantity reflects the total number of cartons or pallets in the shipment as consigned to the carrier. The gross weight reflects the total weight in pounds of the shipment as stated on the Bill of Lading and as consigned to the carrier.
TD101 is a two part element.
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
- PLT
- Pallet
- 25
- Corrugated or Solid
- 94
- Wood
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
- KG
- Kilogram
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This segment is required on all ship notices to specify the SCAC.
TD504 and TD505 are required when using UPS or FEDX only.
The Standard Carrier Alpha Code (SCAC) lists and codes transportation carriers operating in North America. Each carrier is assigned a unique 2 - 4 letter code for use as an abbreviation or to identify a particular carrier for transportation data processing purposes.
The documentation for the Standard Carrier Alpha Codes and Standard Tariff Agent's Codes may be purchased from the American Trucking Association, www.nmfta.org.
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 or pre-established from routing guide
Code specifying the method or type of transportation for the shipment
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
UPS or FEDX
Reference Identification
To specify identifying information
Kmart requires the Bill of Lading number for all Truckload and LTL
shipments.
The Bill of Lading is not required for small package carriers shipments (e.g. UPS, FEDX). The correct codes must be specified in the preceding TD5 segment. EXAMPLE: TD5***UUPS
The Bill of Lading number must be unique for each trailer and destination.
The Bill of Lading number must be five to seventeen characters. It must be numeric and cannot include any alpha characters, spaces, hyphens, etc.
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
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
The information in this segment is used to contact the vendor about problems with their 856. The email address information is preferred, the telephone number is also helpful.
The contact information sent in this segment is not currently stored in any database. It may be used to help in locating a contact at the vendor, but this is not always available to all levels that address errors; e.g. the application.
The telephone number must contain numeric only; do not include dashes or parentheses.
The PER segment can be used to send both the phone number and email address.
EXAMPLE: PERICEMemail addressTE*telephone number
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
- TE
- Telephone
Complete communications number including country or area code when applicable
1 - 80 Email address (PER Qualifier=EM)
10 - 15 Telephone number with area code and extension, if applicable (PER Qualifier=TE)
Current Schedule Delivery
To specify pertinent dates and times
When DTM01 contains 067, the date in DTM02 should contain the original delivery date (DTM002) from the 850 purchase order or the revised delivery date (DTM002)from the 860.
Shipped
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- PP
- Prepaid (by Seller)
Name
To identify a party by type of organization, name, and code
The N1 segment at the shipment level identifies the shipper and the
ship to location for the physical shipment - the same details as entered on the associated Bill of Lading.
When N101 contains code SF, N102 should contain the Vendor Name.
When N101 contains code SF, N104 must contain the 11 digit Pay (Remit) Vendor number. N103 must contain code ‘92’. The remit-to number is sent on the 850 purchase order where N101 contains code RE and N104 will contain the remit-to/pay Duns number.
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Free-form name
When N101 contains code SF, N102 should contain the Vendor Name
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.
Name
To identify a party by type of organization, name, and code
The N1 segment at the shipment level identifies the shipper and the
ship to location for the physical shipment - the same details as entered on the associated Bill of Lading.
When N101 contains code ST, the ship-to information sent in the N1 segment must be sent in one of two ways. Either it can be returned EXACTLY as it is sent on the 850 purchase order (9 qualifier in N103 and Duns plus four digit unit number in N104) or it can be sent with a 92 qualifier in N103 and the four digit unit number in N104. If the ship-to information is not sent in correctly, your ship notice will be rejected.
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)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 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.
The order level is always subordinate to the shipment level.
Therefore the parent HL parent number for the HL-O must always be 1 (may contain leading zeroes).
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
Product/Item Description
To describe a product or process in coded or free-form format
One occurrence of this segment is required on every order-level HL on every ship notice to Kmart to indicate compliance with the Fair Labor Standards Act
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- S
- Structured (From Industry Code List)
Code identifying the agency assigning the code values
- Use PID03 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 a product characteristic
- PID04 should be used for industry-specific product description codes.
- FL
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
The carton count and weight of each HL-Order level are required on Kmart ship notices. The data reported in this TD1 applies only to this order level.
TD101 is a two part element.
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
- PLT
- Pallet
- 25
- Corrugated or Solid
- 94
- Wood
Number of units (pieces) of the lading commodity
Total number of pallets or cartons shipped for a PO
Reference Identification
To specify identifying information
The internal vendor number is present on the purchase order and is required to be returned on the ship notice. The value of REFIA on the ship notice must be the same as the value of REFIA on the purchase order. This is the KMart assigned Vendor Order Number, which is 11 characters
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
KMart assigned Vendor Order Number, which is 11 characters
Tare and Pack levels cannot be used within the same Order level.
They may be used in the same 856 Ship Notice, but only for different Order levels.
Use the Tare level when you are palletizing your shipment and Pack level when shipping loose cartons.
This level is not required for DC stock product only.
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
Numeric value of gross weight per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
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.
- CM
- Centimeter
- IN
- Inch
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment, at the pack level, is used to specify the identification
numbers for a carton. This segment is required when the Pack level
is used.
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.
20 characters
Tare and Pack levels cannot be used within the same Order level.
They may be used in the same 856 Ship Notice, but only for different Order levels.
Use the Tare level when you are palletizing your shipment and Pack level when shipping loose cartons.
This level is not required for DC stock product only
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
1.The qualifiers used in data element 235 Product/Service ID Qualifier
fields (e.g. LIN02, LIN04) may come in any order as long as they are paired with their appropriate Product ID. For example, the LIN02 may contain UP if LIN03 contains the U.P.C. number. Or LIN02 may contain IN if LIN03 contains the KSN.
2.The shipping GTIN is required to be returned on the 856 if sent on the 850 purchase order. This MUST be present for all DC-stocked orders (non-JIT).
3.The KSN number (data element IN) MUST be returned on every 856.
- he KSN is nine characters; the format is different than displayed in IMA. The KSN that is sent and required to be returned contains the seven or eight characters displayed in IMA with leading zeroes to make a nine digit number. The dash and check digit displayed in IMA must not be used in EDI.
EXAMPLES:
IMA: 5432121-2 EDI: 005432121
IMA: 87655454-8 EDI: 087655454
5.For direct-to-store; if you receive the shipping GTIN (qualifier UK) on the 850 purchase order, it must be returned on the 856. If you receive the UPC (qualifier UP) on the purchase order, it must be returned in the 856. HOWEVER, if you do NOT receive the shipping GTIN on the 850, do NOT send a shipping GTIN on the 856.If you do NOT receive the UPC on the 850 do NOT send a UPC on the 856.
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)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (LIN Qualifier=EN)
9 - 9 Kmart KSN item number (LIN Qualifier=IN)
14 - 14 Shipping GTIN (LIN Qualifier=UK)
12 - 12 U.P.C. number (LIN Qualifier=UP)
1 - 17 Vendor's item number (LIN Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used to specify the actual quantity shipped for the
purchase order line item identified in the associated LIN segment.
The value sent in SN103 MUST be the same value sent on the PO
If a substitution has been authorized by the Kmart buyer, the LIN segment will specify the substituted purchase order line item, the SN1 segment will report a quantity shipped and the SLN segment(s) following will report the originally ordered purchase order line item and quantity.
The unit of measure sent in the 856 ASN (ship notice) in SN103 MUST match the unit of measure sent in the 850 purchase order PO103.
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.
- CA
- Case
- EA
- Each
Subline Item Detail
To specify product subline detail item data
1.The SLN segment should be used only to report authorized substitutions.
2.For Authorized Substitutions, the SLN should specify the originally
ordered product ID and quantity. The value in SLN03 must be 'S'.
The LIN and SN1 segments should report the product ID and quantity shipped of the substituted product.
3.The value of SLN01 should be a sequential number, beginning with
one and incrementing by one for each occurrence of the SLN segment within each HL-I loop.
4.SLN06 and SLN07 are required if there are changes in the pricing
specifications on pre-ticketed items.
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.
- D
- Delete
- I
- Included
- S
- Substituted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- EA
- Each
Price per unit of product, service, commodity, etc.
SL06 and SLN07 are required if there are changes in the pricing specifications on pre-ticketed items only.
Code identifying the type of unit price for an item
SL06 and SLN07 are required if there are changes in the pricing specifications on pre-ticketed items only.
- RE
- Retail Price per 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)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (SLN Qualifier=EN)
9 - 9 Kmart KSN item number (SLN Qualifier=IN)
14 - 14 Shipping GTIN (SLN Qualifier=UK)
12 - 12 U.P.C. number (SLN Qualifier=UP)
1 - 17 Vendor's item number (SLN Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
1.For approved vendors only, this segment may be used to cancel the balance of an ordered quantity. The LIN segment must specify the purchase order line item shipped, SN1 will report the quantity shipped and TD506 will be sent to cancel the balance of the ordered item. Do NOT send the TD5 segment to cancel the balance of an item if your company is not approved for this by the buying and inventory teams.
2.TD5 segment must be present if shipping complete or if shipping substitutions
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
- CC
- Shipment Complete on (Date)
- CP
- Partial Shipment on (Date), Considered No Backorder
MUST HAVE APPROVAL OF BUYING AND INVENTORY TEAM TO USE THIS
- IS
- Item Represents Substitution from Original Order
Item represents substitution from original order (‘IS’ can only be sent when sending the SLN segment and must have Kmart buyer approval)
Tare and Pack levels cannot be used within the same Order level.
They may be used in the same 856 Ship Notice, but only for different Order levels.
Use the Tare level when you are palletizing your shipment and Pack level when shipping loose cartons.
This level is not required for DC stock product only.
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
This segment, at the tare level, is used to specify the identification
numbers for a pallet. This segment is required when the Tare level is used
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.
20 characters
Tare and Pack levels cannot be used within the same Order level.
They may be used in the same 856 Ship Notice, but only for different Order levels.
Use the Tare level when you are palletizing your shipment and Pack level when shipping loose cartons.
This level is not required for DC stock product only
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
1.The qualifiers used in data element 235 Product/Service ID Qualifier
fields (e.g. LIN02, LIN04) may come in any order as long as they are paired with their appropriate Product ID. For example, the LIN02 may contain UP if LIN03 contains the U.P.C. number. Or LIN02 may contain IN if LIN03 contains the KSN.
2.The shipping GTIN is required to be returned on the 856 if sent on the 850 purchase order. This MUST be present for all DC-stocked orders (non-JIT).
3.The KSN number (data element IN) MUST be returned on every 856.
- he KSN is nine characters; the format is different than displayed in IMA. The KSN that is sent and required to be returned contains the seven or eight characters displayed in IMA with leading zeroes to make a nine digit number. The dash and check digit displayed in IMA must not be used in EDI.
EXAMPLES:
IMA: 5432121-2 EDI: 005432121
IMA: 87655454-8 EDI: 087655454
5.For direct-to-store; if you receive the shipping GTIN (qualifier UK) on the 850 purchase order, it must be returned on the 856. If you receive the UPC (qualifier UP) on the purchase order, it must be returned in the 856. HOWEVER, if you do NOT receive the shipping GTIN on the 850, do NOT send a shipping GTIN on the 856.If you do NOT receive the UPC on the 850 do NOT send a UPC on the 856.
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)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (LIN Qualifier=EN)
9 - 9 Kmart KSN item number (LIN Qualifier=IN)
14 - 14 Shipping GTIN (LIN Qualifier=UK)
12 - 12 U.P.C. number (LIN Qualifier=UP)
1 - 17 Vendor's item number (LIN Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See LIN03
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used to specify the actual quantity shipped for the
purchase order line item identified in the associated LIN segment.
The value sent in SN103 MUST be the same value sent on the PO
If a substitution has been authorized by the Kmart buyer, the LIN segment will specify the substituted purchase order line item, the SN1 segment will report a quantity shipped and the SLN segment(s) following will report the originally ordered purchase order line item and quantity.
The unit of measure sent in the 856 ASN (ship notice) in SN103 MUST match the unit of measure sent in the 850 purchase order PO103.
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.
- CA
- Case
- EA
- Each
Subline Item Detail
To specify product subline detail item data
1.The SLN segment should be used only to report authorized substitutions.
2.For Authorized Substitutions, the SLN should specify the originally
ordered product ID and quantity. The value in SLN03 must be 'S'.
The LIN and SN1 segments should report the product ID and quantity shipped of the substituted product.
3.The value of SLN01 should be a sequential number, beginning with
one and incrementing by one for each occurrence of the SLN segment within each HL-I loop.
4.SLN06 and SLN07 are required if there are changes in the pricing
specifications on pre-ticketed items.
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.
- D
- Delete
- I
- Included
- S
- Substituted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- EA
- Each
Price per unit of product, service, commodity, etc.
SL06 and SLN07 are required if there are changes in the pricing specifications on pre-ticketed items only.
Code identifying the type of unit price for an item
SL06 and SLN07 are required if there are changes in the pricing specifications on pre-ticketed items only.
- RE
- Retail Price per 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)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (SLN Qualifier=EN)
9 - 9 Kmart KSN item number (SLN Qualifier=IN)
14 - 14 Shipping GTIN (SLN Qualifier=UK)
12 - 12 U.P.C. number (SLN Qualifier=UP)
1 - 17 Vendor's item number (SLN Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See SLN10
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
1.For approved vendors only, this segment may be used to cancel the balance of an ordered quantity. The LIN segment must specify the purchase order line item shipped, SN1 will report the quantity shipped and TD506 will be sent to cancel the balance of the ordered item. Do NOT send the TD5 segment to cancel the balance of an item if your company is not approved for this by the buying and inventory teams.
2.TD5 segment must be present if shipping complete or if shipping substitutions
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
- CC
- Shipment Complete on (Date)
- CP
- Partial Shipment on (Date), Considered No Backorder
MUST HAVE APPROVAL OF BUYING AND INVENTORY TEAM TO USE THIS
- IS
- Item Represents Substitution from Original Order
Item represents substitution from original order (‘IS’ can only be sent when sending the SLN segment and must have Kmart buyer approval)
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
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.