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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
Ship notice number.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BSN03 is the date the shipment transaction set is created.
Ship notice date.
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.
Ship notice time.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
This data element is required by JCPenney to inform us of the structure of the transaction set.
- 0001
- Shipment, Order, Packaging, Item
- 0002
- Shipment, Order, Item, Packaging
- 0003
- Shipment, Packaging, Order, Item
Detail
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
This segment, at the shipment level, is used to specify total containers and gross weight of the shipment as specified on the bill of lading (see VICS EDI 856 Ship Notice/Manifest Guidelines for further detail).
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
- BAG
- Bag
- CTN
- Carton
- 25
- Corrugated or Solid
- 79
- Plastic
Number of units (pieces) of the lading commodity
The number of packages in the shipment as described in TD101
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
This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previously identified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only use TD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routing guide, use code 91 or 92 in TD502 and identify the routing sequence, from the routing guide, in TD503. To identify a specific private parcel service, TD502 will contain code 2 and TD503 will contain the corresponding SCAC.
When using a small package service provider as the carrier, TD502 will contain code 2, TD503 will contain the carrier's SCAC, and TD504 will contain code U to inform the receiver of a small package service shipment.
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.
Code "91" is only used for Indirect Imports and is limited to identifying ocean vessel carriers.
- 2
- Standard Carrier Alpha Code (SCAC)
- 91
- Assigned by Seller or Seller's Agent
Code identifying a party or other code
To obtain the SCAC code list for all carriers, contact:
National Motor Freight Trucking Association
2200 Mill Road
Alexandria, VA 22314
Code specifying the method or type of transportation for the shipment
If utilizing a parcel service (UPS, FedEx, etc), use code "U". For ocean vessel shipments to JCP Wholesale Distribution Centers, use code "S".
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Original carrier.
Ocean vessel.
Code identifying type of location
Used only for Indirect Imports and is limited to ocean vessel shipments referencing port of discharge.
- PE
- Port of Entry
Code which identifies a specific location
Used only for Delivered Imports and is limited to ocean vessel shipments referencing port of discharge.
Bill of Lading Number
To specify identifying information
Bill of Lading (REF01 = BM): This segment is required and contains the Bill of Lading number. For UPS and FedEx shipments, the value will be '0' and TD504 of the TD5 segment will be 'U'. For Ocean Vessel shipments this is the Ocean Bill of Lading
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
Carrier Reference Number (REF01 = CN): This segment is optional and contains the Carrier reference number
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
Pick Up Appointment Number
To specify identifying information
Authorization Number (REF01 = PUA): This segment contains the JCP load ID or authorization number from the Transportation Management System [TMS] programs (Dynamic Routing or TMS Routing Authorization).
Code qualifying the Reference Identification
- PUA
- Pick Up Appointment 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
E-mail address is required to send ASN error notifications.
Only one contact e-mail address is allowed, preferably a common mailbox to ensure coverage.
Current Schedule Delivery
To specify pertinent dates and times
Current Schedule Delivery (DTM01 = 067): This segment is required on Delivered Import shipments, specifying the estimated date of arrival of the shipment.
Code specifying type of date or time, or both date and time
- 067
- Current Schedule Delivery
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Shipped
To specify pertinent dates and times
Shipped (DTM01 = 011): This segment is required, specifying the date and time the merchandise was shipped. The information provided in this segment represents the actual date and time that the carrier picked up the shipment.
Code specifying type of date or time, or both date and time
- 011
- Shipped
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Name
To identify a party by type of organization, name, and code
Ship From (N101 = SF): This loop is only required for Delivered Imports. It will consist of a N1 segment to specify the originating location of the ocean shipment, e.g. actual port of origin. Elements N103 and N104 will be used to transmit this data. The N4 segment will be used to specify the geographic ship point. [See business rules for Delivered Imports].
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This is the location code as defined by N103. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Code identifying the country
Code required if country is not USA.
Name
To identify a party by type of organization, name, and code
Ship To (N101 = ST): This loop is required. It will contain one N1 segment identifying the five digit Ship To location number. This identifies the Bill of Lading delivery location as determined from Routing Instructions. It may be a PEPS consolidation facility or another interim location such as an SSC or Catalog Logistics Center.
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This is the location code as defined by N103. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Code identifying the country
Code required if country is not USA.
The HL segment is used to identify levels of detail information using a hierarchical structure. HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
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.
- UT
- Unit or Lot
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 (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- 2B
- 20 ft. IL Container (Closed Top)
- 4B
- 40 ft. IL Container (Closed Top)
- 20
- 20 ft. IL Container (Open Top)
- 40
- 40 ft. IL Container (Open Top)
- CN
- Container
- CZ
- Refrigerated Container
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
Retailer's original purchase order number
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- PRF04 is the date assigned by the purchaser to purchase order.
Retailer's original purchase order date
Contract number
This element can be used to include the Blanket Order number the Delivery Instruction PO (PRF01) is associated with.
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.
- 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
- Compliant with Fair Labor Standards Act
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
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
This segment, at the order level, is used to specify the status of the order
- BP
- Shipment Partial, Back Order to Ship on (Date)
- CC
- Shipment Complete on (Date)
- CP
- Partial Shipment on (Date), Considered No Backorder
- CS
- Shipment Complete with Substitution
- DE
- Deleted Order
- LS
- Last Shipment on (Date)
- SS
- Split Shipment
Department Number
To specify identifying information
Department Number (REF01 = DP): This segment is required, specifying the three-digit subdivision number.
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
Internal Vendor Number
To specify identifying information
Internal Vendor Number (REF01 = IA): This segment is required, specifying the JCPenney assigned six-digit supplier number.
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
Seller's Invoice Number
To specify identifying information
Seller's Invoice Number (REF01 = IV): This segment is optional, specifying the supplier's invoice number
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Vendor Order Number
To specify identifying information
Vendor Order Number (REF01 = VN): This segment is optional and is used to specify the supplier's order number. The order number must be unique for each transmission against a selected order. If the supplier's order number is more than 15 characters in length, the right most 15 characters will be returned on an outbound document (ex. 869 - Order Status Inquiry). For example, if your order number is 12345678901234567, JCPenney will send 456789012354567.
Code qualifying the Reference Identification
- VN
- Vendor Order 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
Bill-to Party (N101 = BT): This loop will consist of one N1 segment. This is the JCPenney unit to be invoiced for the shipment. This party is identified as the Bill-To Party on the 850 Purchase Order. For Factory Ship or DFW Furniture, N104 will have the store number where the order originated from. This loop is required for all business entities.
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
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.
This is the location code as defined by N103. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
This element will contain the JCPenney five-digit unit number.
Name
To identify a party by type of organization, name, and code
Mark-for Party (N101 = Z7): This loop will consist of one N1 segment and may contain an N3 and N4 segment. The N3 and N4 segments can be included to identify the address and geographic location of the Mark-for Party. This loop is optional for Indirect Imports to JCP Wholesale Distribution Centers and required for all other business entities.
Code identifying an organizational entity, a physical location, property or an individual
- Z7
- Mark-for Party
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.
This is the location code as defined by N103. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
This element will contain the JCPenney five-digit unit number.
Address Information
To specify the location of the named party
Trading partner has the option to use this segment to identify the address of the Mark-for Party.
Geographic Location
To specify the geographic place of the named party
Trading partner has the option to use this segment to identify the geographic location of the Mark-for Party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Code identifying the country
Code required if country is not USA.
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- T
- Shipping Tare
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- SM
- Shipper Assigned
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.
Unique number for each pallet.
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
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.
Subline Item Detail
To specify product subline detail item data
This segment, when used in a standard carton pack structure at the pack level, may only be used to specify an individual component of the item identified in the LIN segment in the previous item level. The quantity specified in SN102, at the item level, represents the number of sets, and SN103 will contain code ST, to identify it as a set. Each subsequent MAN segment, within this pack level, identifies the carton ID for each component identified in the SLN segment. Additional pack level SLN segments and MAN segments are used to represent each different component of the SKU.
The codes listed for SLN09 apply to every occurrence of the Data Element 235 in the LIN segment.
SLN09 and SLN10 will be used to specify either the JCPenney item number* (SLN09 = IN) or the UPC number (SLN09 = UP). A trading partner can only send the UPC number if it exist in JCPenney's product database.
If SLN10 is used to specify the JCPenney item number, SLN11 and SLN12 can be used to specify either the UPC (SLN11 = UP) or the EAN (SLN11 = EN) number corresponding to that JCPenney item number.
- The JCPenney item number is sent in the following format: AAAABBBBCCCCC, where AAAA = lot number, BBBB = line number, CCCCC = size description.
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.
Increment by one starting with one (1).
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- ST
- Set
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
- EAN/UCC - 13
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
For retail shipments, PKG01, PKG02, and PKG05 are used. For catalog shipments, PKG01 and PKG05 are used.
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.
- F
- Free-form
Code specifying the marking, packaging, loading and related characteristics being described
- OPI
- Optional Procedure Indicator
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
The following codes will be used in this data element:
Retail - "Y"
Catalog - "45", "50", or "55"
- 45
- 50
- 55
- Y
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- 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.
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier.
The HL segment is used to identify levels of detail information using a hierarchical structure.
HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.
HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.
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
If the 850 Purchase Order did not include the UPC number, then the JCPenney item number* is required in LIN03 (LIN02 = IN).
Min/Max length of characters of JCPenney item numbers by business entity:
9/13 - Retail
11/11 - Catalog
9/13 - Liquidation [Outlet Stores]
If the 850 Purchase Order included the UPC number for the item, the Trading Partner has the option to send only the UPC number in LIN03 (LIN02 = UP).
Trading Partner also has the option to send both the JCPenney item number (LIN02 = IN) in LIN03 and the UPC (LIN04 = UP) or EAN number (LIN04 = EN) in LIN05.
- The JCPenney item number must match the item number sent on the 850 Purchase Order.
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
- EAN/UCC - 13
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used to specify the quantities associated with the item identified in the LIN at the item level.
When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 will contain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Each different component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Total number of consumer units.
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
- BX
- Box
- CA
- Case
- EA
- Each
- FT
- Foot
- PC
- Piece
- PK
- Package
- PR
- Pair
- RL
- Roll
- ST
- Set
- YD
- Yard
Quantity ordered
The quantity ordered comes from the original quantity on the purchase order, less any cancellations the supplier makes to the original quantity.
For Procurement shipments, three decimal positions are allowed. All other business entities will continue with no decimals.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- BX
- Box
- CA
- Case
- EA
- Each
- FT
- Foot
- PC
- Piece
- PK
- Package
- PR
- Pair
- RL
- Roll
- ST
- Set
- YD
- Yard
Subline Item Detail
To specify product subline detail item data
If SLN03 contains code D or code I, then SLN04 and SLN05 are required.
The codes listed for SLN09 apply to every occurrence of Data Element 235 in the SLN segment.
If this segment may be used to denote a component. Data elements SLN09 and SLN10 will be used to specify either the JCPenney item number* (SLN09 = IN) or the UPC number (SLN09 = UP). A trading partner can only send the UPC number if it exist in JCPenney's product database.
Min/Max length of characters of JCPenney item numbers by business entity:
9/13 - Retail
11/11 - Catalog
9/13 - Liquidation [Outlet Stores]
If SLN10 is used to specify the JCPenney item number, SLN11 and SLN12 can be used to specify either the UPC (SLN11 = UP) or the EAN (SLN11 = EN) number corresponding to that JCPenney item number.
- The JCPenney item number must match the item number sent on the 850 Purchase Order.
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.
Increment by one starting with one (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
Numeric value of quantity
The quantity should reflect the number of consumer units.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- BX
- Box
- CA
- Case
- EA
- Each
- FT
- Foot
- PC
- Piece
- PK
- Package
- PR
- Pair
- RL
- Roll
- ST
- Set
- YD
- Yard
Price per unit of product, service, commodity, etc.
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95'', and $29.00 would be sent as "29''. Up to 2 decimal places can be sent.
To indicate a no charge item or free goods, SLN06 will contain a single zero (0) and SLN07 will contain code NC.
Code identifying the type of unit price for an item
This data element is used to clarify or alter the basis of unit price. The unit price expressed in SLN06 is always in the same terms as the unit of measure in SLN05, unless otherwise specified in SLN07.
- WH
- Wholesale
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
- EAN/UCC - 13
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Product/Item Description
To describe a product or process in coded or free-form format
The PID segment is used to provide product/item descriptions in text and or coded formats.
Used on Delivered Imports to indicate an item sequence number, if applicable.
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
- S
- Structured (From Industry Code List)
- X
- Semi-structured (Code and Text)
Code identifying the general class of a product or process characteristic
- 08
- Product
- 73
- Vendor color description
- 74
- Vendor size description
- 75
- Buyer's Color Description
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.
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
This segment, at the item level, is used only to specify the status of the item.
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
- BP
- Shipment Partial, Back Order to Ship on (Date)
- CC
- Shipment Complete on (Date)
- CP
- Partial Shipment on (Date), Considered No Backorder
- CS
- Shipment Complete with Substitution
- IC
- Item Canceled
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
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.