X12 856 Domestic 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
Pick Pack format is typically used when different SKUs are packed Standard Pack format used when identical SKUs are packed. See Business Examples on POL (www.partnersonline.com) for formatting difference between pick/pack and standard pack
Code identifying purpose of transaction set
- 00
- Original
- 07
- Duplicate
A unique control number assigned by the original shipper to identify a specific shipment
Note that EDI Standards state that this should be a unique number. Target applications have been written based on that. This number will be used to differentiate multiple 856s received from a supplier. This number should be different than the Purchase Order or Bill of Lading Number.
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
Pick & Pack Format-typically used when different
SKUs are packed. - 0002
- Shipment, Order, Item, Packaging
Standard Pack Format-used when identical SKUs are packed.
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Correct information is necessary for matching to the corresponding EDI214 Carrier Shipment Status Message.
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
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
Target requires a 4-character alpha code managed by the National Motor Freight Traffic Association. See notes above. When in a consolidation zone, the consolidator's SCAC is required; Southeast Consolidators= (SOCS), National Retail Center= (NART),United Warehouse= (UW DC),USF Distribution Chicago = (USDS),USF Distribution Los Angeles= (USDF).
NOTE: The SCAC code must be sent in uppercase.
Code specifying the method or type of transportation for the shipment
The mode of transportation determines both the transportation method type code(TD504)and the REF segment qualifier (REF01).
TRANSPORTATION
Mode of Transportation: TD504 : REF01 : REF02
Air: A : CN: CarrierRef.# (Carrier Tracking Number)
Consolidation : C : MB : Master Bill of Lading#
(Optional) :BM : Underlying (When used with MB)
TL or LTL : M : BM Bill of Lading #
(Optional) : CN : CarrierPro #
Private Parcel : U : CN CarrierRef.# (Carrier Tracking Number)
- A
- Air
- C
- Consolidation
Consolidation used for overseas and domestic shipment information
- M
- Motor (Common Carrier)
Used for larger quantity shipments Truckload or LTL
- U
- Private Parcel Service
Parcel Package used for small package or small quantities. The ONLY SCAC codes that may be used with this is UPSN or FEDX. All other UPS or FedEx SCAC codes must use "M"
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Reference Identification
To specify identifying information
This segment is critical for matching theCarrier'sEDI214 Carrier Status Message with your EDI 856 Ship Notice Message.
Target requires:
A UNIQUE Bill of Lading (BOL)number for each shipment. Use the VICS (Voluntary Inter-Industry Commerce Standard)standard Bill of Lading document. Target strongly recommends the use of the VICS standard 17 digit Bill of Lading number format.
1)When routing via Truckload (TL)or Less than Truckload (LTL)carrier, one unique BOL # is required per Target ship to location. If constraints require BOL per Purchase Order, then a Master BOL must be used to summarize the underlying bills of lading.
When a Master BOL # is used, be sure to transmit this number on the856. The Master BOL # must be passed to the carrier as the Shipment BOL # for the corresponding Carrier EDI transmission.2)When routing to a Target consolidator, a MasterBOL # must be used and sent on all 856'screated per Purchase Order ship to location. The MasterBOL # must reflect the actual BOL # given to the carrier on the VICS BOL. Do not transmit the individual (underlying)Bill of Lading numbers on the856.
3)For Motor-LTL/TL, two REF segment scan be sent with the required B/L number and in the second optional REF segment with a CN qualifier, the Carrier's Pro #.
Code qualifying the Reference Identification
The mode of transportation determines both the transportation method type code (TD 504 ) and the REF segment qualifier (REF01 ).
TRANSPORTATION
Mode of Transportation: TD504 : REF01 : REF02
Air: A : CN Carrier Ref.# (Carrier Tracking Number)
Consolidation : C: MB : Master Bill of Lading#
(Optional): BM: Underlying (When used with MB)
TL or LTL : M : BM : Bill of Lading #
(Optional) : : CN : Carrier Pro #
Private Parcel : U : CN Carrier Ref.# (Carrier Tracking Number)
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- MB
- Master Bill of Lading
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A unique Bill of Lading (BOL ) number for each shipment is required . When the mode of transportation is for Consolidation, a unique Master BOL # is required for all ship to locations on that shipment.
Name
To identify a party by type of organization, name, and code
*Warning : Segment includes critical data elements. Please ensure accuracy to avoid document suspension and /or loss of data .
At least one N1 segment, containing an N101 of ST , is required .
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)
Per Target Standards:
N103 code '92 ' is only valid with an N101 equal to ST
- 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.
When N101 = ST , this will be a four digit location number.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
Identifying number sent on 850 Purchase Order in the BEG 03 segment.
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
- ZZ
- FLSA Non-Compliance or Not applicable.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
TD101 must be 5 characters. If only CTN is sent, it should be followed by 2 spaces.
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN
- Carton
25 - Carton Corrugated
31 - Carton Fiber
76 - Carton Paper
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This will be a four dig it location number.
If UCC128 (2 -digit Application Identifier+ 18 -digit SSCC ) is used on the MAN segment at the Pack level, then UCC128 (2 -digit Application Identifier+ 18 -digit SSCC ) at the Tare Level is optional.
If the shipping container identification at the Pack level is an SCC -14 (i.e. . interleaved 2 of 5 , case U .P .C .) or a selling unit U .P .C . (used only when the case pack is 1 and the selling unit is the shipping unit), then the Tare level must be used with a UCC -128 (2 - digit Application Identifier+ 18 -digit SSCC ) in the MAN segment.
Tare level is used when providing pallet barcode in formation . Please note the sample HL (Tare level) segment below .
Refer to business examples in Section 4 for proper Tare/Pack level MAN element usage.
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
To find label in formation go to : www.partnersonline .com . Click on Guideline & Info ,Click on EDI Guidelines. Find Shipping Label - Target under supporting documents to the right of the 856 guideline .
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.
- AA
- SSCC-18
This code is not commonly used.
- 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.
When GM is present in the MAN01 , the value in this field must be 20 digits.
Marks and numbers used to identify a shipment or parts of a shipment
- MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.
- When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the two ID numbers must be maintained.
Code specifying the application or source of Marks and Numbers (87)
- AA
- SSCC-18
This code is not commonly used.
- GM
- SSCC-18 and Application Identifier
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.
When GM is present in theMAN01 , the value in this field must be 20 digits.
Marks and numbers used to identify a shipment or parts of a shipment
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
Target prefers receiving the PO4 at the pack level for the pick/pack structure . If it is not possible to send at the pack level, the PO4 must be sent at the item level.
If using standard structure , the PO4 is required at the item level.
If the PO 414 element is received on the PO , then it is required to send back on the 856 . Refer to PO4 explanations in the Business Examples.
Use whole numbers only for all elements.
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this is the # of selling units with in one of the inner cartons only.
If the PO414 element is received on the PO , then it is required to be sent back on the 856 .
Reference Identification
To specify identifying information
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format
Prefer lot number at pack level, will accept at item level
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, which are based on Target item set-up designation as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
MAN01 or MAN04 must be 'GM' at Pack Level when a Tare Segment is not present.
When used together, MAN01 and MAN04 CANNOT be the same(i.e. if MAN01 is 'GM ', MAN04 cannot be GM ).
Ranging MAN Segments:
MAN * GM * 00000123456789987651* 00000123456789988651 (In Pick Pack format only)
MAN02 = First carton barcode of an item .
MAN03 = Last carton barcode of same item .
NOTE: To find label in formation go to : www.partnerson line.com . Click on Guideline & Info ,Click on EDI Guidelines. Find Shipping Label - Target under supporting documents to the right of the 856 guideline .
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.
MAN01 or MAN04 must be 'GM' at Pack Level when a Tare Segment is not present.
- AA
- SSCC-18
Not Commonly used
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Used when case pack is one and selling unit is shipping unit
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.
When GM is present in the MAN01 , the value in this field must be 20 digits.
Marks and numbers used to identify a shipment or parts of a shipment
- MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.
- When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the two ID numbers must be maintained.
Code specifying the application or source of Marks and Numbers (87)
MAN01 or MAN04 must be 'GM ' at Pack Level when a Tare Segment is not present
- AA
- SSCC-18
Not Commonly used
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
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.
Marks and numbers used to identify a shipment or parts of a shipment
Date/Time Reference
To specify pertinent dates and times
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format
Prefer expiration date at pack level, will accept at item level
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, which are based on Target item set- up designation as expiration date controlled product.
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
Target Stores:
Always send either Target DPCI number with a CB qualifier or the assigned UPC number with a UP qualifier.
Target.com :
Always send the Target.com Item number with an IN qualifier and the assigned UPC number with a UP qualifier.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- IN
- Buyer's Item Number
For use by Target.Com vendors only. The Target.com Item number must be sent with the IN qualifier. The value could be between 5 and 8 digits.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- IN
- Buyer's Item Number
For use by Target.Com vendors only. The Target.com Item number must be sent with the IN qualifier. The value could be between 5 and 8 digits.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- IN
- Buyer's Item Number
For use by Target.Com vendors only. The Target.com Item number must be sent with the IN qualifier. The value could be between 5 and 8 digits.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Not used by Retail Industry
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
The value stated in SN102 is dependent upon the 856 structure: Standard or Pick Pack, and the type of carton bar code numbers being sent at the pack level.
Pick Pack Structure:
When a UCC -128 (2 -digit Application Identifier+ 18 -digit SSCC ) is sent for every carton , the value is equal to the total number of eaches within tht case- pack. If the measurement is in cases (CA ), then the value would be one.
When a UCC -128 is being sent for the first and last carton (MAN segment ranges) at the pack level, then the value is equal to the total number of eaches shipped for that line item .
When a U .P .C . Shipping Container Code (SCC 14 d ig it) is sent, then the value is equal to the total number of eaches or cases shipped for that line item .
Standard Structure:
The value is equal to the total number of eaches or cases shipped for a line item where the respective barcode will report to the parent item level.
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.
If the productwas ordered in pounds, Targetw ill only accept the LB qualifier. If the productwas ordered in eaches or cases, Targetw ill accept either EA or CA qualifier.
- CA
- Case
- EA
- Each
- LB
- Pound
Pound is only allowed on Food Distribution Center shipments. The LB qualifier is interchangeable with the EA qualifier within Target's application systems for non random weight food items.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This segment is required for Standard Pack Structure. If sending Pick and Pack Structure, Target prefers to receive the PO4 at the Pack Level. If it is not possible to send thePO4 at the Pack Level, the PO4 must be sent at the item level.
Refer to PO4 explanations in the Business Examples.
Reference Identification
To specify identifying information
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, which are based on Target item set-up designation as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, which are based on Target item set- up designation as expiration date controlled product.
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.