Understanding and Testing Look outs for 856 X12

This documentation is intended for EDI testers who are expected to have pretty good conceptual knowledge. Its expected that any bug found should be notified for early attendance.

Ambarnath Ghosh
Sr. Tech Team Lead (EDI)
Crossroad Technologies



HIERARCHICAL LEVELS
The concept of hierarchical levels is a key feature of the Ship Notice/Manifest. Applying a common hierarchy to levels of data allows the supplier to describe the details of a physical shipment in an electronic format. In this way, the receiver can
successfully process the transaction - correctly associating the ship notice data to the physical shipment. Each level within the Ship Notice/Manifest groups together related details about a physical shipment. Data is transmitted at the level to which
it logically applies, thereby avoiding redundancy. The six levels defined for use within retail industry implementations are:

•SHIPMENT - Data related to a shipment moving from an origin location to a receiving location, such as Bill of Lading number, ship to, ship from, etc. There is one and only one shipment level in each transaction set.
•UNIT LOAD - Data related to a physical shipping unit which is marked with a UCC/EAN-128 Serial Shipping Container Code (SSCC-18), and, consists of transport packages marked for multiple final destinations.
•ORDER - Data related to the supplier’s order and buyer’s original purchase order, such as purchase order number, buying location, department number, etc.
•TARE - Data related to pallets. This may be omitted if there are no identifiable pallets.
•PACK - Data related to the shipping cartons, racks, bags, etc., such as carton serial number. This may be omitted if there are no identifiable packs, or there is no desire to transmit pack level information.
•ITEM - Data related to the shipped products, such as SKU identification, quantity shipped, etc. The hierarchical structure defines the sequence or order in which the levels will appear within a Ship Notice/Manifest. There are two distinct hierarchical structures which are defined for use within retail industry implementations: Pick and Pack and
Standard Carton Pack. Each structure contains the same levels, and the usage of each level is the same for both. The only difference between the two is the order in which the levels may appear within the transaction set (i.e., where the Packaging
levels are positioned in relation to the Item level). A code in the beginning segment of the Ship Notice/Manifest (BSN05) indicates which structure is used.

BSN*00*ABC111222333444*19980522*1345*0001
0001 Shipment, Order, Packaging, Item (Pick and Pack)
0002 Shipment, Order, Item, Packaging (Standard Carton Pack)
0004 Shipment, Order, Item (No Packaging Level)
The actual structure of the Ship Notice/Manifest is determined by the sender (shipper) of the transaction set. Depending on the shipper’s packing environment, one of these two structures will be more applicable to use than the other. The shipper
should choose whichever structure best reflects the packing environment; however, only one data structure can be present in a single ship notice. The buyer (receiver) should be prepared to receive and process any data structure. In the event the partnership does not require a packaging level to be transmitted in the Ship Notice/Manifest, code 0004 is used in BSN05.


PICK AND PACK
The Pick and Pack structure should be used in a Pick and Pack order filling
environment. Typically when different SKUs are packed within the same physical
shipping container [e.g., 48 men’s shirts in 3 colors and 4 sizes each (12 different
U.P.C.s)], at least one packaging level must be included. However, two packaging
levels may be present if Tare is used. The transaction hierarchy is:


• Shipment,
• Order,
• Packaging (Tare and Pack), and
• Item

The Item level is subordinate to the Packaging levels (i.e., the specification of the
SKU is always within the shipping container Tare or Pack level). The shipping
container is specified, then all SKUs within the shipping container are identified.

•Different SKUs packed within a shipping container
•Item is the lowest level
•Item is subordinate to the packaging levels

STANDARD CARTON PACK
The Standard Carton Pack structure should be used in an environment where identical SKUs are packed within one or more physical shipping containers [e.g., 12 blue twin-size sheets (one U.P.C.)]. The transaction hierarchy is:



• Shipment,
• Order,
• Item, and
• Packaging (Tare and Pack).

In this structure, the Item level is subordinate to the Order and the Packaging levels are subordinate to the Item level [e.g., the specification of the shipping containers is always within the SKU (Item level)]. Once the SKU is specified, then all the
shipping containers for the SKUs are identified.

•Identical SKUs packed within a shipping container
•Pack or tare is the lowest level
•Packaging is subordinate to the item level

NO PACKAGING LEVEL
In some implementations, it may be appropriate to omit the packaging levels from the transaction. Depending on the retailer’s receiving environment, carton identification may not be required. Here, only three levels are present in the transaction.
The transaction hierarchy is:

• Shipment,
• Order, and
• Item.

•One or more U.P.C.s
•No packaging level


HIERARCHICAL STRUCTURE EXAMPLES
Following are examples of Pick and Pack and Standard Carton Pack hierarchical structures. Each box in the diagram represents a detail loop (one HL segment followed by data segments) in an Ship Notice/Manifest transaction set.

Pick and Pack Structure Example
In this example, the shipment contains 2 orders. The first order has 3 cartons. The first carton contains a quantity of 2 SKUs (Items). The second carton contains 2 SKUs (Items). The third carton contains 1 SKU (Item). The second order contains one carton with quantities of 3 different SKUs (Items). The data segments in a single Pack level will uniquely identify only one physical shipping container. The data segments in the associated Item levels specify the SKU contents of the shipping container. (For additional understanding, review the “Pick and Pack” examples in the Business Examples section of this guide.)

•Top-down/left-right reporting sequence is used
•The Item level is subordinate to the packaging level
•Only one shipping container in a single packaging level

Standard Carton Pack Structure Example
In this example, the shipment contains 2 orders. The first order has 3 SKUs (Items). Each SKU (Item) has 1 Pack level. The second order has 1 SKU (Item) with 4 Pack levels, each pack containing a quantity of the same SKU. The packaging levels are below the Item. The data segments in a single Pack level specify the total quantity shipped for the SKU. The data segments in the associated Pack levels uniquely identify the shipping containers, and report the quantity of
SKUs in a single shipping container. A single packaging level may specify one or more physical shipping containers, each
containing a quantity of the same SKU. (For additional understanding, review the “Standard Pack” examples in the Business Examples section of this guide.)

•Top-down/left-right reporting sequence is used
•The Packaging level is subordinate to the Item level
•More than one shipping container may be specified within a single packaging level

Shipping Container Identification Numbers
Container identification numbers are transmitted in MAN segments within the appropriate packaging level (Shipment, Unit Load, Tare or Pack). The recommended ID is the human-readable interpretation of the UCC/EAN-128 Serial Shipping
Container Code (SSCC-18). When MAN01 contains code AA, MAN02 will contain the eighteen-character UCC/EAN-128 Serial Shipping Container Code which does not include the two-digit application identifier. When MAN01 contains code GM, MAN02 will contain the twenty-character UCC/EAN-128 Serial Shipping Container Code, which includes the two-digit application identifier. Codes AA and GM should not be used to identify the same shipping container; use one or the other, but
not both. Container ID numbers are transmitted without any spaces or dashes. Other shipping containers that may need to be reported include U.P.C./EAN Shipping Container Code (SCC-14) or carrier assigned package IDs.

SSCC-18 (without Application Identifier)
MAN*AA*000123459876543210

SSCC-18 and Application Identifier
MAN*GM*00000123459876543210

SCC-14
MAN*UC*00098765100018

CARRIER-ASSIGNED PACKAGE ID
MAN*CP*426711103

When reporting two ID numbers which have been assigned to the same physical shipping container, one MAN segment will be sent containing both ID numbers. For example, if both the UCC/EAN-128 Serial Shipping Container Code (SSCC-18)
and the U.P.C./EAN Shipping Container Code (SCC-14) are assigned to the same physical shipping container, one MAN segment will be present to specify the two ID numbers.
MAN*GM*00000123459876543210**UC*50098765100018

When there are more than two ID numbers which have been assigned to the same physical shipping container, one HL loop will be created for each physical shipping container, and multiple MAN segments within that HL loop will be used to specify
the ID numbers assigned to the container. In this scenario, each Pack level will represent one and only one physical shipping container.

Pick and Pack
For Pick and Pack shipments, each packaging loop will report the serial number for one shipping container. The SKU contents of the shipping container are reported in one or more item loops which follow a packaging loop. Example 1 is a carton with a UCC/EAN-128 carton ID (SSCC-18). Example 2 is a pallet with a UCC/EAN-128 pallet ID (SSCC-18).
Example 1
HL*3*2*P
MAN*GM*00000123459876543210
Example 2
HL*3*2*T
MAN*GM*00100123459876543210

Standard Carton Pack
When using the Standard Carton Pack structure, the sender may choose to create a single Pack level to report all container IDs for a shipped SKU. For example, to report a shipment of 4 cases of blue twin-size blankets, each case containing a
quantity of 6, one packaging level is generated with 4 MAN segments to specify the 4 cartons. The PO4 segment is used to report the quantity of blankets contained in one shipping container. The Item loop will specify the shipped SKU and the total
quantity shipped for that SKU (24 each).

HL*3*2*I
LIN**UP*012345555558
SN1**24*EA
HL*4*3*P
PO4*6
MAN*GM*00000123451111111110
MAN*GM*00000123452222222220
MAN*GM*00000123453333333330
MAN*GM*00000123454444444440

Using Two Packaging Levels
In some implementations it may be necessary to report shipping container IDs using two packaging levels. All items in the highest identifiable container (e.g. pallet, truck, etc.) must be marked for the same final location. The Pick and Pack structure
must be used if more than one U.P.C. is contained in the highest identifiable container. In the following example, one pallet is shipped containing 15 cases of case code “44444” (Item 11111) and 9 cases of case code “55555” (Item 22222). The Pick and Pack data structure must be used (Item below Packaging).

Example 1:
HL*3*2*T
MAN*GM*00100123451111111110
HL*4*3*P
PO4*15*************6
MAN*UC*50012345444448
HL*5*4*I
LIN**UP*012345111110
SN1**90*EA
HL*6*3*P
PO4*9*************5
MAN*UC*50012345555558
HL*7*6*I
LIN**UP*012345222220
SN1**45*EA


The most commonly used segments in 856 are given below. While testing we have to keep in mind the syntax as well as Retailer’s Symantec rules.

Heading:
ST Transaction Set Header M 1
BSN Beginning Segment for Ship Notice M 1

Detail:
LOOP ID - HL 200000
HL Hierarchical Level - Shipment M 1 c1
TD1 Carrier Details (Quantity and Weight) O 20
TD5 Carrier Details (Routing Sequence/TransitTime) O 12
LOOP ID - TD3 12
TD3 Carrier Details (Equipment) O 1
REF Reference Information O >1
MAN Marks and Numbers Information O >1
DTM Date/Time Reference O 10
FOB F.O.B. Related Instructions O 1
LOOP ID - N1 200
N1 Party Identification O 1
N3 Party Location O 2
N4 Geographic Location O 1
REF Reference Information O 12
PER Administrative Communications Contact O 3

LOOP ID - HL 200000
HL Hierarchical Level - Order M 1
PRF Purchase Order Reference O 1
REF Reference Information O >1

LOOP ID - HL 200000
HL Hierarchical Level - Shipping Tare M 1
MAN Marks and Numbers Information O >1
PAL Pallet Type and Load Characteristics O 1

LOOP ID - HL 200000
HL Hierarchical Level - Pack M 1
LIN Item Identification O 1
SN1 Item Detail (Shipment) O 1
PO4 Item Physical Details O 1
MAN Marks and Numbers Information O >1
DTM Date/Time Reference O 10

LOOP ID - HL 200000
HL Hierarchical Level - Item M 1
LIN Item Identification O 1
SN1 Item Detail (Shipment) O 1
PO4 Item Physical Details O 1
SLN Subline Item Details O 1000
DTM Date/Time Reference O 10
Summary:
CTT Transaction Totals O 1
SE Transaction Set Trailer M 1


The data segment with elements of 856 x12 is given below :

ST (Transaction Set Header)
Purpose: To indicate the start of a transaction set and to assign a control number

ST*856*0001

856 is the Transaction Set Identifier Code for the Advance
Ship Notice.
0001 is the Transaction Set Control Number.

BSN (Beginning Segment for Shipment Notice)
Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

BSN*00*01140824*20051015*1345*0001

00 is the Transaction Set Purpose Code.
“00” indicates “Original”.
“01” indicates “Cancellation”.
“04” indicates “Change”.
“07” indicates “Duplicate”.

01140824 is the Shipment Identification.
20051015 is the Document Creation Date.
1345 is the Time.
0001 is the Hierarchical Structure Code.
“0001” indicates “Pick and Pack Structure”.
“0004” indicates “Standard Carton”.

Data Element Summary
Ref. Data
Des. Element Name Attributes
M BSN01 353 Transaction Set Purpose Code M 1 ID 2/2
Code identifying purpose of transaction set
00 Original
M BSN02 396 Shipment Identification M 1 AN 2/30
A unique control number assigned by the original shipper to identify a specific
shipment
M BSN03 373 Date M 1 DT 8/8
Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
M BSN04 337 Time M 1 TM 4/8
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)
BSN05 1005 Hierarchical Structure Code O 1 ID 4/4
Code indicating the hierarchical application structure of a transaction set that
utilizes the HL segment to define the structure of the transaction set

HL (Hierarchical Level – Shipment)
Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

HL*1**S*1

1 is the Hierarchical ID Number.
S is the Hierarchical Level Code. “S” indicates “Shipment”.
This HL is the first HL used, and has no parent to identify.
1 is the Hierarchical Child Code. “1” indicates “Additional
Subordinate HL Data Segment in This Hierarchical Structure”.


TD1 Carrier Details (Quantity and Weight)
Purpose: To specify the transportation details relative to commodity, weight, and quantity

TD1*CTN25*2****G*45582*LB*4*SF

CTN25 is the Packaging Code. “CTN” indicates “Carton”,and “25” indicates “Corrugated or Solid”.
2 is the Lading Quantity.
G is the Weight Qualifier. “G” indicates “Gross Weight”.
45582 is the Weight.
LB is the Unit or Basis for Measurement Code. “LB” indicates “Pound”.
4 is the Volume.
SF is the Unit or Basis for Measurement Code. “SF”

Syntax Notes:
1 If TD101 is present, then TD102 is required.
2 If TD103 is present, then TD104 is required.
3 If TD106 is present, then TD107 is required.
4 If either TD107 or TD108 is present, then the other is required.
5 If either TD109 or TD110 is present, then the other is required.


Data Element Summary
TD101 103 Packaging Code O 1 AN 3/5
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 1
CTN Carton
MIX Mixed Container Types
More than one type of container is included in a shipment
(shipment could consist of 3 pieces that include 1 box, 1
crate, and 1 basket)
Can be used only with code 71 in Part 2
PLT Pallet
SLP Slip Sheet
Shipping containers utilizing slip sheets, which are
cardboard platforms used to hold product for storage or
transportation
SRW Shrink Wrap
In packaging, a method of securing a unit load by placing
a large "bag" of plastic film over the components and
applying heat to induce shrinkage and cause the bag to
tighten around the contents
Part2
03 Hard Wood
05 Soft Wood
25 Corrugated or Solid
71 Not Otherwise Specified
76 Paper
94 Wood

TD102 80 Carton X 1 N0 1/7
Number of units (pieces) of the lading commodity
The number of packages in the shipment as described in TD101

TD103 23 Commodity Code Qualifier O 1 ID 1/1
Code identifying the commodity coding system used for Commodity Code

TD104 22 Commodity Code X 1 AN 1/30
Code describing a commodity or group of commodities



TD105 79 Lading Description O 1 AN 1/50
Description of an item as required for rating and billing purposes

TD106 187 Weight Qualifier O 1 ID 1/2
Code defining the type of weight
G Gross Weight

TD107 81 Weight X 1 R 1/10
Numeric value of weight

TD108 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
KG Kilogram
LB Pound

TD109 183 Volume X 1 R 1/8
Value of volumetric measure
Gross volume

TD110 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
CF Cubic Feet
CR Cubic Meter


TD5 Carrier Details (Routing Sequence/Transit Time)
Purpose: To specify the carrier and sequence of routing and provide transit time information

TD5*B*2*JBHT*M

B is the Routing Sequence Code. “B” indicates “Origin/Delivery Carrier (Any Mode)”.
2 is the Identification Code Qualifier. “2” indicates “Standard Carrier Alpha Code (SCAC)”.
JBHT is the Identification Code. “JBHT” indicates “J.B. Hunt”.
M is the Transportation Method/Type Code. “M” indicates “Motor (Common Carrier)”.

Syntax Notes:
1 At least one of TD502 TD504 TD505 TD506 or TD512 is required.
2 If TD502 is present, then TD503 is required.
3 If TD507 is present, then TD508 is required.
4 If TD510 is present, then TD511 is required.
5 If TD513 is present, then TD512 is required.
6 If TD514 is present, then TD513 is required.
7 If TD515 is present, then TD512 is required.

Data Element Summary
TD501 133 Routing Sequence Code O 1 ID 1/2
Code describing the relationship of a carrier to a specific shipment movement
B Origin/Delivery Carrier (Any Mode)

TD502 66 Identification Code Qualifier X 1 ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code X 1 AN 2/80
Code identifying a party or other code

TD504 91 Transportation Method/Type Code X 1 ID 1/2
Code specifying the method or type of transportation for the shipment
A Air
AE Air Express
BU Bus
C Consolidation
CE Customer Pickup / Customer's Expense
D Parcel Post
E Expedited Truck
H Customer Pickup
L Contract Carrier
M Motor (Common Carrier)
R Rail
S Ocean
T Best Way (Shippers Option)
U Private Parcel Service

TD505 387 Routing X 1 AN 1/35
Free-form description of the routing or requested routing for shipment, or the
originating carrier's identity
TD506 368 Shipment/Order Status Code X 1 ID 2/2
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
TD507 309 Location Qualifier O 1 ID 1/2
Code identifying type of location
TD508 310 Location Identifier X 1 AN 1/30
Code which identifies a specific location
TD509 731 Transit Direction Code O 1 ID 2/2
The point of origin and point of direction
TD510 732 Transit Time Direction Qualifier O 1 ID 2/2
Code specifying the value of time used to measure the transit time
TD511 733 Transit Time X 1 R 1/4
The numeric amount of transit time
TD512 284 Service Level Code X 1 ID 2/2
Code indicating the level of transportation service or the billing service offered by the transportation carrier
TD513 284 Service Level Code X 1 ID 2/2
Code indicating the level of transportation service or the billing service offered by the transportation carrier
TD514 284 Service Level Code O 1 ID 2/2
Code indicating the level of transportation service or the billing service offered by the transportation carrier
TD515 26 Country Code O 1 ID 2/3
Code identifying the country


TD3 (Carrier Details (Equipment)
Purpose: To specify transportation details relating to the equipment used by the carrier


TD3*TL*AB23*07213567******30394938483234

TL is the Equipment Description Code. “TL” indicates “Trailer”.
AB23 is the Equipment Initial.
07213567 is the Equipment Number.
30394938483234 is the Seal Number. This is a unique number on seal used to close a shipment.

Syntax Notes:
1 Only one of TD301 or TD310 may be present.
2 If TD302 is present, then TD303 is required.
3 If TD304 is present, then TD305 is required.
4 If either TD305 or TD306 is present, then the other is required.


Data Element Summary
TD301 40 Equipment Description Code X 1 ID 2/2
Code identifying type of equipment used for shipment
TL Trailer (not otherwise specified)
TD302 206 Equipment Initial O 1 AN 1/4
Prefix or alphabetic part of an equipment unit's identifying number
TD303 207 Equipment Number X 1 AN 1/15
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
TD304 187 Weight Qualifier O 1 ID 1/2
Code defining the type of weight
TD305 81 Weight X 1 R 1/10
Numeric value of weight
TD306 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
TD307 102 Ownership Code O 1 ID 1/1
Code indicating the relationship of equipment to carrier or ownership of equipment
TD308 407 Seal Status Code O 1 ID 2/2
Code indicating condition of door seal upon arrival
TD309 225 Seal Number O 1 AN 2/15
Unique number on seal used to close a shipment
TD310 24 Equipment Type X 1 ID 4/4
Code identifying equipment type

REF (Reference)
Purpose: To specify identifying information

REF*AO*567845660
REF*BM*01140824
REF*CN*082131
REF*2I*123123123
REF*D3*22558899
REF*DH*222222
REF*0B*999999*AZ
REF*FW*11111111*AR
REF*IA*211555050
REF*IV*01140824
REF*DP*00005
REF*MR*0033

AO is the Reference Identification Qualifier. “AO” indicates “Appointment Number”.
BM is the Reference Identification Qualifier. “BM” indicates “Bill of Lading Number”.
CN is the Reference Identification Qualifier. “CN” indicates “Carrier’s Reference Number (PRO/Invoice)”.
2I is the Reference Identification Qualifier. “2I” indicates” tracking Number”.
D3 is the Reference Identification Qualifier. “D3” indicates “National Association of Boards of Pharmacy Number”.
DH is the Reference Identification Qualifier. “DH” indicates “Drug Enforcement Administration Number”.
0B is the Reference Identification Qualifier. “0B” indicates “State License Number”.
FW is the Reference Identification Qualifier. “FW” indicates the “State License Identification Number”., AR is the
Description (2-character postal abbreviation for the state in which the License Number is Applicable).
“IA” indicates “Internal Vendor Number”.
“IV” indicates “Seller’s Invoice Number”
“DP” indicates “Department Number”
“MR” indicates “Merchandise Type Code”

Syntax Notes:
1 At least one of REF02 or REF03 is required.
2 If either C04003 or C04004 is present, then the other is required.
3 If either C04005 or C04006 is present, then the other is required.

Data Element Summary
REF01 128 Reference Identification Qualifier M 1 ID 2/3
Code qualifying the Reference Identification
“AO” indicates “Appointment Number”.
“BM” indicates “Bill of Lading Number”.
“CN” indicates “Carrier’s Reference Number (PRO/Invoice)”.
“2I” indicates” tracking Number”.
“D3” indicates “National Association of Boards of Pharmacy Number”.
“DH” indicates “Drug Enforcement Administration Number”.
“0B” indicates “State License Number”.
“FW” indicates the “State License Identification Number”

REF02 127 Reference Identification X 1 AN 1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
REF03 352 Description X 1 AN 1/80
A free-form description to clarify the related data elements and their content
REF04 C040 Reference Identifier O 1
To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier
C04001 128 Reference Identification Qualifier M ID 2/3
Code qualifying the Reference Identification
C04002 127 Reference Identification M AN 1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
C04003 128 Reference Identification Qualifier X ID 2/3
Code qualifying the Reference Identification
C04004 127 Reference Identification X AN 1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
C04005 128 Reference Identification Qualifier X ID 2/3
Code qualifying the Reference Identification
C04006 127 Reference Identification X AN 1/50
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier


DTM (Date/Time)
Purpose: To specify pertinent dates and times

DTM*067*20051015
DTM*011*20051015

067 is the Date/Time Qualifier. “067” indicates “Current Schedule Delivery”.
011 is the Date/Time Qualifier. “011” indicates “Date Shipped”.
20051015 is the Date.

Syntax Notes:
1 At least one of DTM02 DTM03 or DTM05 is required.
2 If DTM04 is present, then DTM03 is required.
3 If either DTM05 or DTM06 is present, then the other is required.

Data Element Summary
DTM01 374 Date/Time Qualifier M 1 ID 3/3
Code specifying type of date or time, or both date and time
067 Current Schedule Delivery
DTM02 373 Date X 1 DT 8/8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
DTM03 337 Time X 1 TM 4/8
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)
DTM04 623 Time Code O 1 ID 2/2
Code identifying the time. In accordance with International Standards
Organization standard 8601, time can be specified by a + or - and an
indication in hours in relation to Universal Time Coordinate (UTC) time; since
+ is a restricted character, + and - are substituted by P and M in the codes
that follow
DTM05 1250 Date Time Period Format Qualifier X 1 ID 2/3
Code indicating the date format, time format, or date and time format
DTM06 1251 Date Time Period X 1 AN 1/35
Expression of a date, a time, or range of dates, times or dates and times


FOB (F.O.B. Related Instructions)
Purpose: To specify transportation instructions relating to shipment

FOB*PP

PP is the Shipment Method of Payment. “PP” indicates “Prepaid (by Seller)”.
Note: Collect Suppliers use the code “CC”

Syntax Notes:
1 If FOB03 is present, then FOB02 is required.
2 If FOB04 is present, then FOB05 is required.
3 If FOB07 is present, then FOB06 is required.
4 If FOB08 is present, then FOB09 is required.

Data Element Summary
FOB01 146 Shipment Method of Payment M 1 ID 2/2
Code identifying payment terms for transportation charges
CC Collect
PP Prepaid (by Seller)
FOB02 309 Location Qualifier X 1 ID 1/2
Code identifying type of location
FOB03 352 Description O 1 AN 1/80
A free-form description to clarify the related data elements and their content
FOB04 334 Transportation Terms Qualifier Code O 1 ID 2/2
Code identifying the source of the transportation terms
FOB05 335 Transportation Terms Code X 1 ID 3/3
Code identifying the trade terms which apply to the shipment transportation
responsibility
FOB06 309 Location Qualifier X 1 ID 1/2
Code identifying type of location
FOB07 352 Description O 1 AN 1/80
A free-form description to clarify the related data elements and their content
FOB08 54 Risk of Loss Code O 1 ID 2/2
Code specifying where responsibility for risk of loss passes
FOB09 352 Description X 1 AN 1/80
A free-form description to clarify the related data elements and their content


N1 (Party Identification)
Purpose: To identify a party by type of organization, name, and code

N1*CQ*CORPORATE NAME*UL*9999999999999
N1*ST*WAL-MART PHARMACY WAREHOUSE 6013*UL*0078742028873
N1*SF*SUPPLIER NAME

CQ is the Entity Identifier Code. “CQ” indicates “Corporate Office”.
Corporate Name is the Name.
UL is the Identification Code Qualifier. “UL” indicates “Global Location Number (GLN)”.
9999999999999 is the Identification Code.

ST is the Entity Identifier Code. “ST” indicates “Ship To”.
WAL-MART PHARMACY WAREHOUSE 6013 is the party Name.
UL is the Identification Code Qualifier. “UL” indicates “Global Location Number (GLN)”.
0078742028873 is the Identification Code.

SF is the Entity Identifier Code. “SF” indicates “Ship From”.
SUPPLIER NAME is the Name.

Syntax Notes:
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.

Data Element Summary
N101 98 Entity Identifier Code M 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an individual
CQ Corporate Office
[there can be many more identifiers like ST,SF,BY,BT ect]
N102 93 Name X 1 AN 1/60
Free-form name
N103 66 Identification Code Qualifier X 1 ID 1/2
Code designating the system/method of code structure used for Identification Code (67)
UL Global Location Number (GLN)
A globally unique 13 digit code for the identification of a legal, functional or physical location within the Uniform
Code Council (UCC) and International Article Number Association (EAN) numbering system
[there can be many more identifiers like 9,91,92 etc, depending on which length of N104 is determined]
N104 67 Identification Code X 1 AN 2/80
Code identifying a party or other code
N105 706 Entity Relationship Code O 1 ID 2/2
Code describing entity relationship
N106 98 Entity Identifier Code O 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an individual

N3 (Party Location)
Purpose: To specify the location of the named party

N3*CORP ST ADDRESS

CORP ST ADDRESS is the Address Information.


N4 (Geographic Location)
Purpose: To specify the geographic place of the named party

N4*CITY*ST*99999

CITY is the City Name. ST is the State or Province Code.
99999 is the Postal Code.

Syntax Notes:
1 Only one of N402 or N407 may be present.
2 If N406 is present, then N405 is required.
3 If N407 is present, then N404 is required.

Data Element Summary
N401 19 City Name O 1 AN 2/30
Free-form text for city name
N402 156 State or Province Code X 1 ID 2/2
Code (Standard State/Province) as defined by appropriate government agency
N403 116 Postal Code O 1 ID 3/15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
N404 26 Country Code X 1 ID 2/3
Code identifying the country
N405 309 Location Qualifier X 1 ID 1/2
Code identifying type of location
N406 310 Location Identifier O 1 AN 1/30
Code which identifies a specific location
N407 1715 Country Subdivision Code X 1 ID 1/3
Code identifying the country subdivision


PER (Administrative Communications Contact)
Purpose: To identify a person or office to whom administrative communications should be directed

PER*PL*BOB SMITH*TE*9999999999*EM*BSMITH@yahoo.com
PER*CE*ALICE JONES*TE*999999999*EM*AJONES@juno.com

PL is the Contact Function Code. “PL” indicates “Manufacturing Plant Contact”. Bob Smith is the Name.
CE is the Contact Function Code. “CE” indicates “Certifier”.
TE is the Communication Number Qualifier. “TE” indicates “Telephone”. 9999999999 is the Communications Number.
EM is the Communications Number Qualifier. “EM” indicates “Electronic Mail”. BSMITH@yahoo.com is Communication #

Syntax Notes:
1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
3 If either PER07 or PER08 is present, then the other is required.


Data Element Summary

PER01 366 Contact Function Code M 1 ID 2/2
Code identifying the major duty or responsibility of the person or group named
PL Manufacturing Plant Contact
PER02 93 Name O 1 AN 1/60
Free-form name
PER03 365 Communication Number Qualifier X 1 ID 2/2
Code identifying the type of communication number
TE Telephone
PER04 364 Communication Number X 1 AN 1/256
Complete communications number including country or area code when applicable
A valid telephone number must be provided.
PER05 365 Communication Number Qualifier X 1 ID 2/2
Code identifying the type of communication number
EM Electronic Mail
PER06 364 Communication Number X 1 AN 1/256
Complete communications number including country or area code when applicable
A valid e-mail address must be provided.
PER07 365 Communication Number Qualifier X 1 ID 2/2
Code identifying the type of communication number
PER08 364 Communication Number X 1 AN 1/256
Complete communications number including country or area code when applicable
PER09 443 Contact Inquiry Reference O 1 AN 1/20
Additional reference number or description to clarify a contact number

YNQ (Yes/No Question)
Purpose: Yes/No Question
Purpose: To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

YNQ*3E*Y
YNQ*CX*N

3E is the Condition Indicator. “3E” indicates “Letter of Certification”.
Y is the Yes/No Condition or Response Code. “Y” indicates “Yes”.

CX is the Condition Indicator. “CX” indicates “Certification Status”.
Y is the Yes/No Condition or Response Code. “N” indicates “No”.

Syntax Notes:
1 Only one of YNQ01 YNQ09 or YNQ10 may be present.
2 If either YNQ03 or YNQ04 is present, then the other is required.
3 If YNQ09 is present, then YNQ08 is required.

Data Element Summary
YNQ01 1321 Condition Indicator X 1 ID 2/3
Code indicating a condition
3E Letter of Certification
M YNQ02 1073 Yes/No Condition or Response Code M 1 ID 1/1
Code indicating a Yes or No condition or response
N No
Y Yes
Code indicating the date format, time format, or date and time format
YNQ04 1251 Date Time Period X 1 AN 1/35
Expression of a date, a time, or range of dates, times or dates and times
YNQ05 933 Free-form Message Text O 1 AN 1/264
Free-form message text
YNQ06 933 Free-form Message Text O 1 AN 1/264
Free-form message text
YNQ07 933 Free-form Message Text O 1 AN 1/264
Free-form message text
YNQ08 1270 Code List Qualifier Code X 1 ID 1/3
Code identifying a specific industry code list
YNQ09 1271 Industry Code X 1 AN 1/30
Code indicating a code from a specific industry code list
YNQ10 933 Free-form Message Text X 1 AN 1/264
Free-form message text


HL (Hierarchical Level – Order)
Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
(for details please see the HL item level)

HL*2*1*O*1

2 is the Hierarchical ID Number.
1 is the Hierarchical Parent ID Number. (Shipment)
O is the Hierarchical Level Code. “O” indicates “Order”. 1
is the Hierarchical Child Code. “1” indicates “Additional Subordinate HL Data Segment in This Hierarchical Structure”.

PRF (Hierarchical Level – Order)
Purpose : Purchase Order Reference

PRF*1478523690***20051015

1478523690 is the Purchase Order Number.
20051015 is the Date.

Data Element Summary
PRF01 324 Purchase Order Number M 1 AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
Retailer's original purchase order number
PRF02 328 Release Number O 1 AN 1/30
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
PRF03 327 Change Order Sequence Number O 1 AN 1/8
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
PRF04 373 Date O 1 DT 8/8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Retailer’s original purchase order date
PRF05 350 Assigned Identification O 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
PRF06 367 Contract Number O 1 AN 1/30
Contract number
PRF07 92 Purchase Order Type Code O 1 ID 2/2
Code specifying the type of Purchase Order

HL (Hierarchical Level – Pack)
Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
(for details please see the HL item level)

HL*3*2*P*1

3 is the Hierarchical ID Number.
2 is the Hierarchical Parent ID Number. (Order)
P is the Hierarchical Level Code. “P” indicates “Pack”.
1 is the Hierarchical Child Code. “1” indicates “Additional Subordinate HL Data Segment in This Hierarchical Structure”.


MAN (Marks and Numbers Information)
Purpose: To indicate identifying marks and numbers for shipping containers

MAN*UC*00088155091083

UC is the Marks and Numbers Qualifier. “UC” indicates “the fourteen digit U.P.C. Shipping Container Code".
00088155091083 is the Marks and Numbers number.

Syntax Notes:
1 If either MAN04 or MAN05 is present, then the other is required.
2 If MAN06 is present, then MAN05 is required.

Data Element Summary
MAN01 88 Marks and Numbers Qualifier M 1 ID 1/2
Code specifying the application or source of Marks and Numbers (87) AA SSCC-18
This is an eighteen-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that does not include the two digit application identifier, the symbology code, or the modulo 103 check character.
GM EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.
M MAN02 87 Marks and Numbers M 1 AN 1/48
Marks and numbers used to identify a shipment or parts of a shipment
MAN03 87 Marks and Numbers O 1 AN 1/48
Marks and numbers used to identify a shipment or parts of a shipment
MAN04 88 Marks and Numbers Qualifier X 1 ID 1/2
Code specifying the application or source of Marks and Numbers (87)
MAN05 87 Marks and Numbers X 1 AN 1/48
Marks and numbers used to identify a shipment or parts of a shipment
MAN06 87 Marks and Numbers O 1 AN 1/48
Marks and numbers used to identify a shipment or parts of a shipment


PAL (Pallet Type and Load Characteristics)
Purpose: To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet

PAL*1

1 Aluminum

Syntax Notes:
1 If either PAL05 or PAL06 is present, then the other is required.
2 If PAL07 is present, then PAL10 is required.
3 If PAL08 is present, then PAL10 is required.
4 If PAL09 is present, then PAL10 is required.
5 If PAL10 is present, then at least one of PAL07 PAL08 or PAL09 is required.
6 If either PAL11 or PAL12 is present, then the other is required.
7 If either PAL13 or PAL14 is present, then the other is required.

Data Element Summary
PAL01 883 Pallet Type Code O 1 ID 1/2
Code indicating the type of pallet
1 Aluminum
2 As Specified by the Department of Transportation (DOT)
3 Metal
4 Standard
5 Steel
6 Wood
7 Slip sheet
Typically cardboard or plastic sheets used to hold product
for storage or transportation
PAL02 884 Pallet Tiers O 1 N0 1/3
The number of layers per pallet
PAL03 885 Pallet Blocks O 1 N0 1/3
The number of pieces (cartons) per layer on the pallet
PAL04 356 Pack O 1 N0 1/6
The number of inner containers, or number of eaches if there are no inner containers, per outer container
PAL05 395 Unit Weight X 1 R 1/8
Numeric value of weight per unit
PAL06 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PAL07 82 Length X 1 R 1/8
Largest horizontal dimension of an object measured when the object is in the upright position
PAL08 189 Width X 1 R 1/8
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
PAL09 65 Height X 1 R 1/8
Vertical dimension of an object measured when the object is in the upright position
PAL10 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PAL11 384 Gross Weight per Pack X 1 R 1/9
Numeric value of gross weight per pack
PAL12 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PAL13 385 Gross Volume per Pack X 1 R 1/9
Numeric value of gross volume per pack
PAL14 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PAL15 399 Pallet Exchange Code O 1 ID 1/1
Code specifying pallet exchange instructions
PAL16 810 Inner Pack O 1 N0 1/6
The number of eaches per inner container
PAL17 1699 Pallet Structure Code O 1 ID 1/1
Code identifying the pallet structure


HL (Hierarchical Level – Item)
Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

HL*4*3*I*1

4 is the Hierarchical ID Number.
3 is the Hierarchical Parent ID Number. (Pack)
I is the Hierarchical Level Code. “I” indicates “Item”.
1 is the Hierarchical Child Code. “1” indicates “Additional Subordinate HL Data Segment in This Hierarchical Structure”.

Data Element Summary
M HL01 628 Hierarchical ID Number M 1 AN 1/12
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
HL02 734 Hierarchical Parent ID Number O 1 AN 1/12
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
This data element will contain the value of the HL01 in the parent pack (case)- level HL segment, as appropriate to the transaction set structure.
M HL03 735 Hierarchical Level Code M 1 ID 1/2
Code defining the characteristic of a level in a hierarchical structure I Item
HL04 736 Hierarchical Child Code O 1 ID 1/1
Code indicating if there are hierarchical child data segments subordinate to the level being described
1 Additional Subordinate HL Data Segment in This Hierarchical Structure.

Special Note :
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.

LIN (Item Identification)
Purpose: To specify basic item identification data

LIN**UP*088155091838*LT*55555*ND*77777*UK*00088155091838

UP is the Product/Service ID Qualifier. “UP” indicates “UCC - 12”.
088155091838 is the Product/Service ID.
LT is the Product/Service Qualifier. “LT” indicates “Lot Number”.
55555 is the Product/Service ID.
ND is the Product/Service ID. “ND” indicates National Drug Code.
77777 is the Product/Service ID.
UK is the Product/Service ID Qualifier. "UK" indicates "GTIN 14-digit Data Structure".
00088155091838 is the Product/Service ID.

Syntax Notes:
1 If either LIN04 or LIN05 is present, then the other is required.
2 If either LIN06 or LIN07 is present, then the other is required.
3 If either LIN08 or LIN09 is present, then the other is required.
4 If either LIN10 or LIN11 is present, then the other is required.
5 If either LIN12 or LIN13 is present, then the other is required.
6 If either LIN14 or LIN15 is present, then the other is required.
7 If either LIN16 or LIN17 is present, then the other is required.
8 If either LIN18 or LIN19 is present, then the other is required.
9 If either LIN20 or LIN21 is present, then the other is required.
10 If either LIN22 or LIN23 is present, then the other is required.
11 If either LIN24 or LIN25 is present, then the other is required.
12 If either LIN26 or LIN27 is present, then the other is required.
13 If either LIN28 or LIN29 is present, then the other is required.
14 If either LIN30 or LIN31 is present, then the other is required.

Data Element Summary

LIN01 350 Assigned Identification O 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
M LIN02 235 Product/Service ID Qualifier M 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
UA U.P.C./EAN Case Code (2-5-5)
M LIN03 234 Product/Service ID M 1 AN 1/48
Identifying number for a product or service
LIN04 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
PJ Product Date Code (A code indicating the period during which a product was manufactured.)
LIN05 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN06 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LT Lot Number
LIN07 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN08 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
UK GTIN 14-digit Data Structure (Data structure for the 14 digit EAN.UCC (EAN International.Uniform Code Council) Global Trade Item Number (GTIN))
LIN09 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN10 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN11 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN12 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN13 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN14 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN15 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN16 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN17 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN18 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN19 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN20 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN21 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN22 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN23 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN24 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN25 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN26 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN27 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN28 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN29 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
LIN30 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
LIN31 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service

SN1 Item Detail (Shipment)
Purpose: To specify line-item detail relative to shipment

SN1**4*EA

4 is the Number of Units Shipped.
EA is the Unit or Basis for Measurement Code. “EA” indicates “Each”.

Syntax Notes:
1 If either SN105 or SN106 is present, then the other is required.

Data Element Summary
SN101 350 Assigned Identification O 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
M SN102 382 Number of Units Shipped M 1 R 1/10
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
M SN103 355 Unit or Basis for Measurement Code M 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken CA Case
SN104 646 Quantity Shipped to Date O 1 R 1/15
Number of units shipped to date
SN105 380 Quantity X 1 R 1/15
Numeric value of quantity
SN106 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
SN107 728 Returnable Container Load Make-Up Code O 1 ID 1/2
Code identifying the load make-up of the returnable containers in the shipment
SN108 668 Line Item Status Code O 1 ID 2/2
Code specifying the action taken by the seller on a line item requested by the buyer

SLN Subline Item Detail
Purpose: To specify product subline detail item data

SLN*1**I******MF*MF NAME*BL*BRAND NAME

1 is the Assigned Identification. I is the Relationship Code. “I” indicates “Included”.
MF is the Product/Service ID Qualifier. “MF” indicates “Manufacturer”.
MF NAME is the PRODUCT/SERVICE ID.
BL is the Product/Service ID Qualifier. “BL” indicates “Brand/Label”.
BRAND NAME is the PRODUCT/SERVICE ID.

Syntax Notes:
1 If either SLN04 or SLN05 is present, then the other is required.
2 If SLN07 is present, then SLN06 is required.
3 If SLN08 is present, then SLN06 is required.
4 If either SLN09 or SLN10 is present, then the other is required.
5 If either SLN11 or SLN12 is present, then the other is required.
6 If either SLN13 or SLN14 is present, then the other is required.
7 If either SLN15 or SLN16 is present, then the other is required.
8 If either SLN17 or SLN18 is present, then the other is required.
9 If either SLN19 or SLN20 is present, then the other is required.
10 If either SLN21 or SLN22 is present, then the other is required.
11 If either SLN23 or SLN24 is present, then the other is required.
12 If either SLN25 or SLN26 is present, then the other is required.
13 If either SLN27 or SLN28 is present, then the other is required.


Data Element Summary
M SLN01 350 Assigned Identification M 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
An identifying number must be provided for the item. Since only one item
should be referenced, please supply a value of '1'.
SLN02 350 Assigned Identification O 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
M SLN03 662 Relationship Code M 1 ID 1/1
Code indicating the relationship between entities
I Included
SLN04 380 Quantity X 1 R 1/15
Numeric value of quantity
SLN05 C001 Composite Unit of Measure X 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C00101 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
C00102 1018 Exponent O R 1/15
Power to which a unit is raised
C00103 649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
C00104 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
C00105 1018 Exponent O R 1/15
Power to which a unit is raised
C00106 649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
C00107 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
C00108 1018 Exponent O R 1/15
Power to which a unit is raised
C00109 649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
C00110 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
C00111 1018 Exponent O R 1/15
Power to which a unit is raised
C00112 649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
C00113 355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
C00114 1018 Exponent O R 1/15
Power to which a unit is raised
C00115 649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
SLN06 212 Unit Price X 1 R 1/17
Price per unit of product, service, commodity, etc.
SLN07 639 Basis of Unit Price Code O 1 ID 2/2
Code identifying the type of unit price for an item
SLN08 662 Relationship Code O 1 ID 1/1
Code indicating the relationship between entities
SLN09 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
MF Manufacturer
SLN10 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
The manufacturer's name, as it appears on the product label, must be supplied.
SLN11 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
BL Brand/Label
SLN12 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
The name of the item, as it appears on the product label, must be supplied.
SLN13 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN14 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN15 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN16 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN17 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN18 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN19 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN20 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN21 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN22 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN23 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN24 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN25 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN26 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service
SLN27 235 Product/Service ID Qualifier X 1 ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SLN28 234 Product/Service ID X 1 AN 1/48
Identifying number for a product or service


PO4 (Item Physical Details)
Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

PO4*1*4*EA**G*10*LB*1*BO*5*7*4*IN*1

1 is the Pack.
4 is the Size.
EA is the Unit or Basis for Measurement Code. “EA” indicates “Each”.
G is the Weight Qualifier. “G” indicates “Gross”.
10 is the Gross Weight Per Pack.
LB is the Unit or Basis for Measurement Code. “LB” indicates “Pound”.
1 is the Gross Volume Per Pack.
BO is the Unit or Basis for Measurement Code. “BO” indicates “Bottle”.
5 is the Length.
7 is the Width.
4 is the Height.
IN is the Unit or Basis for Measurement Code. “IN” indicates “Inches”.
1 is the Inner Pack.

Syntax Notes:
1 If either PO402 or PO403 is present, then the other is required.
2 If PO405 is present, then PO406 is required.
3 If either PO406 or PO407 is present, then the other is required.
4 If either PO408 or PO409 is present, then the other is required.
5 If PO410 is present, then PO413 is required.
6 If PO411 is present, then PO413 is required.
7 If PO412 is present, then PO413 is required.
8 If PO413 is present, then at least one of PO410 PO411 or PO412 is required.
9 If PO417 is present, then PO416 is required.
10 If PO418 is present, then PO404 is required.

Data Element Summary
PO401 356 Pack O 1 N0 1/6
The number of inner containers, or number of eaches if there are no inner containers, per outer container
PO402 357 Size X 1 R 1/8
Size of supplier units in pack
PO403 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PO404 103 Packaging Code X 1 AN 3/5
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
PO405 187 Weight Qualifier O 1 ID 1/2
Code defining the type of weight
PO406 384 Gross Weight per Pack X 1 R 1/9
Numeric value of gross weight per pack
PO407 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
GR Gram
KG Kilogram
LB Pound
OZ Ounce - Av
PO408 385 Gross Volume per Pack X 1 R 1/9
Numeric value of gross volume per pack
PO409 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
PO410 82 Length X 1 R 1/8
Largest horizontal dimension of an object measured when the object is in the upright position
PO411 189 Width X 1 R 1/8
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
PO412 65 Height X 1 R 1/8
Vertical dimension of an object measured when the object is in the upright position
PO413 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
CM Centimeter
IN Inch
MM Millimeter
PO414 810 Inner Pack O 1 N0 1/6
The number of eaches per inner container
PO415 752 Surface/Layer/Position Code O 1 ID 2/2
Code indicating the product surface, layer or position that is being described
PO416 350 Assigned Identification X 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
PO417 350 Assigned Identification O 1 AN 1/20
Alphanumeric characters assigned for differentiation within a transaction set
PO418 1470 Number O 1 N0 1/9
A generic number


CTT (Transaction Totals)
Purpose: To transmit a hash total for a specific element in the transaction set

Syntax Notes:
1 If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.

Data Element Summary
M CTT01 354 Number of Line Items M 1 N0 1/6
Total number of line items in the transaction set
The number of HL segments present in the transaction set
CTT02 347 Hash Total O 1 R 1/10
Sum of values of the specified data element. All values in the data element will
be summed without regard to decimal points (explicit or implicit) or signs.
Truncation will occur on the left most digits if the sum is greater than the
maximum size of the hash total of the data element.
Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
18E2 Fifth occurrence of value being hashed.
--------
1873 Hash Total
CTT03 81 Weight X 1 R 1/10
Numeric value of weight
CTT04 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
CTT05 183 Volume X 1 R 1/8
Value of volumetric measure
CTT06 355 Unit or Basis for Measurement Code X 1 ID 2/2
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
CTT07 352 Description O 1 AN 1/80
A free-form description to clarify the related data elements and their content