JC Penney (CommerceHub)
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import guide into your account
JC Penney (CommerceHub) logo

X12 856 Ship Notice/Manifest

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/jc-penney-commerce-hub/ship-noticemanifest/01GQN6WQYNXSSKHAHKCDCS1TXB
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
HL Loop
HL
010
Hierarchical Level
Max use 1
Required
TD1
110
Carrier Details (Quantity and Weight)
Max use 20
Optional
TD5
120
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Optional
DTM
200
Date/Time Reference
Max use 10
Optional
HL Loop
HL
010
Hierarchical Level
Max use 1
Required
PRF
050
Purchase Order Reference
Max use 1
Optional
PID
070
Product/Item Description
Max use 200
Optional
REF
150
Reference Identification
Max use 1
Optional
SAC Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

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
ISA-12
I11
Interchange Control Version Number
Required

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required

Code identifying a group of application related transaction sets

SH
Ship Notice/Manifest (856)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BSN
020
Heading > BSN

Beginning Segment for Ship Notice

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Example
BSN-01
353
Transaction Set Purpose Code
Required

Code identifying purpose of transaction set

00
Original
BSN-02
396
Shipment Identification
Required
String (AN)
Min 2Max 30

A unique control number assigned by the original shipper to identify a specific shipment

BSN-03
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSN03 is the date the shipment transaction set is created.
BSN-04
337
Time
Required
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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.
BSN-05
1005
Hierarchical Structure Code
Optional

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

0002
Shipment, Order, Item, Packaging
Heading end

Detail

HL Loop
RequiredMax >1
HL
010
Detail > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required

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
HL-04
736
Hierarchical Child Code
Optional

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.
TD1
110
Detail > HL Loop > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Example: TD1*****A310.5*01
This segment is required to be provided when any part of an order is being shipped. If you are only reporting cancellations or backorders this segment is not required to be provided.

Example
If Packaging Code (TD1-01) is present, then Lading Quantity (TD1-02) is required
If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
TD1-01
103
Packaging Code
Optional

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

Part 2/1
01
Aluminum
04
As Specified by the DOT
07
Burlap
10
Chemically Hardened Fibre
16
Cloth Top
19
Cloth or Fabric
22
Compressed
25
Corrugated or Solid
28
Double-wall Paper
31
Fibre
34
Fibre (Paperboard)
37
Fiberboard
40
Fiberboard Metal
43
Glass
46
In Inner Containers
48
Wire/Cord
49
Insulated
50
Steel - Vinyl Coated
51
Wire Mesh
52
Iron or Steel
53
Jumbo
54
Special Jumbo
55
Lead
58
Metal
59
Metal Cans
61
Moisture Resistant
64
Molded Plastic
67
Multiple-wall Paper (2 or more walls)
70
Multiple-wall Paper (3 or more walls)
71
Not Otherwise Specified
72
Paper - VCI
73
Other than Glass
74
Other than Metal or Plastic Tubes, or Glass
75
Plastic - Vacuum Formed
76
Paper
77
Plastic - Structural Foam
78
Plastic - Injection Molded
79
Plastic
80
Polyethylene Lined
81
Plastic - Virgin
82
Pulpboard
83
Plastic - Regrind
84
Polystyrene
85
Rubber
86
Foam
88
Rubber and Fabric
89
Special
90
Standard
91
Stainless Steel
92
Tubes, Metal or Plastic
94
Wood
95
Single Wall Corrugated Board
96
Double Wall Corrugated Board
97
Triple Wall Corrugated Board
TD1-02
80
Lading Quantity
Optional
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

TD1-06
187
Weight Qualifier
Optional

Code defining the type of weight

A3
Shippers Weight
TD1-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

TD1-08
355
Unit or Basis for Measurement Code
Optional

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

01
Actual Pounds
TD5
120
Detail > HL Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Usage notes

EXAMPLE: TD5B***UG
This segment is required to be provided when any part of an order is being shipped. If you are reporting cancellations or backorders only this segment is not required to be provided.

Example
TD5-01
133
Routing Sequence Code
Optional

Code describing the relationship of a carrier to a specific shipment movement

B
Origin/Delivery Carrier (Any Mode)
TD5-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

This element contains a JCPenney specific code that indicates both the shipper and the level of service. Contact CommerceHub for a complete list of codes. Failure to include one of the approved codes (even during the testing phase of your implementation) will result in a failure to process the message.
There will be cases where an 'unspecified' code will be issued to you on the purchase order. JCPenney will not accept this same 'unspecified' code back in the shipment confirmation. It is expected that you will provide a code that actually represents the shipper and service level.

DTM
200
Detail > HL Loop > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Usage notes

EXAMPLE: DTM01120031015
This segment is required to be provided when any part of an order is being shipped. If you are reporting cancellations only this segment is not required to be provided.

Example
DTM-01
374
Date/Time Qualifier
Required

Code specifying type of date or time, or both date and time

011
Shipped
DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

HL Loop
RequiredMax >1
HL
010
Detail > HL Loop > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required

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
HL-04
736
Hierarchical Child Code
Optional

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.
PRF
050
Detail > HL Loop > HL Loop > PRF

Purchase Order Reference

OptionalMax use 1

To provide reference to a specific purchase order

Example
PRF-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

PID
070
Detail > HL Loop > HL Loop > PID

Product/Item Description

OptionalMax use 200

To describe a product or process in coded or free-form format

Example
If Product Description Code (PID-04) is present, then Agency Qualifier Code (PID-03) is required
PID-01
349
Item Description Type
Required

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)
PID-03
559
Agency Qualifier Code
Optional

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
PID-04
751
Product Description Code
Optional
String (AN)
Min 1Max 12

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.
Usage notes
  • Populate with "FL" to indicate FLSA compliance
    This element is required to be populated with "FL" to indicate FLSA compliance
REF
150
Detail > HL Loop > HL Loop > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Usage notes

EXAMPLES: REFIV1234567
This segment is required to be provided when any part of an order is being shipped. If you are reporting cancellations only this segment is not required to be provided.

Example
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

IV
Seller's Invoice Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

SAC Loop
OptionalMax >1
SAC
320
Detail > HL Loop > HL Loop > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Usage notes

EXAMPLES: SACCG830**525
The SAC
C*G830 segment is an optional segment and should only be sent if shipping charges are being billed back to JCPenney.

Example
SAC-01
248
Allowance or Charge Indicator
Required

Code which indicates an allowance or charge for the service specified

  • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
C
Charge
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Optional

Code identifying the service, promotion, allowance, or charge

G830
Shipping and Handling
SAC-05
610
Amount
Optional
Numeric (N2)
Min 1Max 15

Monetary amount

  • SAC05 is the total amount for the service, promotion, allowance, or charge.
  • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
SAC Loop end
HL Loop
RequiredMax >1
HL
010
Detail > HL Loop > HL Loop > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required

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
HL-04
736
Hierarchical Child Code
Optional

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
LIN
020
Detail > HL Loop > HL Loop > HL Loop > LIN

Item Identification

OptionalMax use 1

To specify basic item identification data

Example
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes
  • Merchant's purchase order line number
LIN-02
235
Product/Service ID Qualifier
Required

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.
VN
Vendor's (Seller's) Item Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes
  • Vendor's Item Number
SN1
030
Detail > HL Loop > HL Loop > HL Loop > SN1

Item Detail (Shipment)

OptionalMax use 1

To specify line-item detail relative to shipment

Usage notes

Example:
SHIPMENT: SN13EAAC CANCEL: SN10EA**3EA**ID
A 'ship' action is assumed if the SN1-08 code is omitted or not 'AC','ID'.

Example
If either Quantity Ordered (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN1-03
355
Unit or Basis for Measurement Code
Required

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.
EA
Each
SN1-05
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

SN1-06
355
Unit or Basis for Measurement Code
Optional

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
SN1-08
668
Line Item Status Code
Optional

Code specifying the action taken by the seller on a line item requested by the buyer

AC
Item Accepted and Shipped
ID
Item Deleted
PID
070
Detail > HL Loop > HL Loop > HL Loop > PID

Product/Item Description Free Form

OptionalMax use 200

To describe a product or process in coded or free-form format

Example
Variants (all may be used)
PIDProduct/Item Description Semi Structured
PID-01
349
Item Description Type
Required

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

Use when reporting Kimberly diamond compliance

PID-02
750
Product/Process Characteristic Code
Optional

Code identifying the general class of a product or process characteristic

CM
Compliance Method

Use when reporting Kimberly diamond compliance and PID01 = F

PID-05
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID
070
Detail > HL Loop > HL Loop > HL Loop > PID

Product/Item Description Semi Structured

OptionalMax use 200

To describe a product or process in coded or free-form format

Example
Variants (all may be used)
PIDProduct/Item Description Free Form
PID-01
349
Item Description Type
Required

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.
X
Semi-structured (Code and Text)

Used for CARB Formaldehyde Compliance Code

PID-05
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

When PID01 = X
This element contains the CARB Formaldehyde Compliance Code. One of the following codes must be populated here:
0-Non-Compliant
1-Phase 1 Compliant
2-Phase 2 Compliant
3-No Added Formaldehyde
4-Ultra Low Emission Formaldehyde Use (ULEF)
When PID01 = F
This is the text that JCPenney requires if this compliance pertains to your product.
"PRODUCT MEETS JCP JEWELRY,KP DIAMOND,BURMA RUBYJADEITE,
IR GEM REQUIREMENTS"

REF
150
Detail > HL Loop > HL Loop > HL Loop > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Usage notes

Example: REFGK199999999902
This segment only needs to be included when a CARB Identifier Code needs to be passed.
EXAMPLE: REFTDbad_sku*this sku does not exist
This segment needs to be included when reporting cancellations

Example
REF-01
128
Reference Identification Qualifier
Required

Code qualifying the Reference Identification

GK
Third Party Reference Number

Used for CARB Certifier ID

TD
Reason for Change
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

When REF01 is GK
This element contains the CARB Identifier Code. Each vendor using this element should have a unique code that should be used here. When REF01 is TD
Contact your CommerceHub Onboarding Specialist for the complete list of cancel codes.

DTM
200
Detail > HL Loop > HL Loop > HL Loop > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required

Code specifying type of date or time, or both date and time

079
Promised for Shipment
DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

N1 Loop
OptionalMax >1
N1
220
Detail > HL Loop > HL Loop > HL Loop > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

WH
Warehouse
N1-03
66
Identification Code Qualifier
Optional

Code designating the system/method of code structure used for Identification Code (67)

54
Warehouse
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

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.
Usage notes

Warehouse ID

N1 Loop end
HL Loop
OptionalMax >1

EXAMPLE: HL32*P

  • Pack level HL is required for reporting tracking number(s) when item level SN1_08 = "AC"
HL
010
Detail > HL Loop > HL Loop > HL Loop > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required

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
HL-04
736
Hierarchical Child Code
Optional

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.
MAN
190
Detail > HL Loop > HL Loop > HL Loop > HL Loop > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Example
If either Marks and Numbers Qualifier (MAN-04) or Marks and Numbers (MAN-05) is present, then the other is required
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)
Min 1Max 2

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.
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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.
Usage notes

Tracking number
IMPORTANT NOTE: CommerceHub enforces validation rules for UPS and FEDEX tracking numbers including check digit routines when applicable. Please insure that all tracking numbers you submit are correctly formatted. Any shipment confirmation message containing invalid tracking numbers will be rejected.

MAN-04
88
Marks and Numbers Qualifier
Optional

Code specifying the application or source of Marks and Numbers (87)

Usage notes

This qualifier indicates that the MAN05 contains the SSCC ID# for the package.
Note: The presence of an SSCC ID for ship to home orders will cause the message to be rejected.

GM
SSCC-18 and Application Identifier
MAN-05
87
Marks and Numbers
Optional
String (AN)
Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
Usage notes

This element contains the SSCC ID# for the package. If you are shipping in multiple boxes OR producing your own packing slips, the SSCC-ID is required and will cause the message to be rejected if not present.

HL Loop end
HL Loop end
HL Loop end
HL Loop end
Detail end

Summary

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.