1. business and industrial
2. logistics
3. air freight

856 Advance Ship Notice
Supplier Implementation Guide
856 Advance Ship Notice Implementation Guide.docx
1
Contents
Introduction to EDI 856 Advance Ship Notice ............................................................................................... 3
Introduction ............................................................................................................................................ 3
What is EDI? .......................................................................................................................................... 3
The Importance of the 856 ..................................................................................................................... 3
EDI Requirements.................................................................................................................................. 4
EDI Workflow ......................................................................................................................................... 5
EDI Benefits ........................................................................................................................................... 6
Required Fields ...................................................................................................................................... 7
General Reference Materials ........................................................................................................................ 9
Contact Information.............................................................................................................................. 10
EDI Standards and ISA/GS Information .............................................................................................. 10
The 856 EDI Technical Guidelines ............................................................................................................. 11
856 Advance Ship Notice
2
Introduction to EDI 856 Advance Ship Notice
Introduction
This document provides instructions for implementing the EDI 856 Advance Ship
Notice transaction. This document is divided into the following sections:
Introduction to EDI – A basic introduction of EDI and the 856.
Non-Technical Reference Materials – Includes contact and protocol
information.
Technical Guidelines – Your IT or technical staff will need this information
to successfully implement the 856.
While this guide is largely intended for technical personnel, the introductory
information allows you to gain a full understanding of why EDI is used and what the
benefits are to you. If you are not a technical resource, we recommend you read this
introduction prior to turning this guide over to any IT/technical resources who may
implement the 856 for your organization.
If you have questions about conducting business with Cardinal Health or EDI
concerns beyond the 856, please consult the guide Supplier Reference Manual:
Pharmaceutical Supply Chain.
What is EDI?
EDI (Electronic Data Interchange) is an electronic sharing of information in a global
standardized format. Traditionally, communications between business partners (like
purchase orders or invoices) were conducted on paper and sent via mail or fax.
With the advent of electronic file sharing, communicating such information
electronically greatly reduces the time and resources required to manage these
interactions. ANSI (American National Standards Institute) is the governing
organization that establishes EDI standards. Within ANSI, HDMA (the Healthcare
Distribution Management Association) establishes standards unique to the health
care industry. However, HDMA standards always fall within ANSI standards; they do
not conflict with nor negate one another.
Ideally, when trading partners use standardized communications in accordance with
ANSI and HDMA, communications are automated and efficient.
.
The
Importance of
the 856
The 856 is critical to timely and seamless receipt of shipments we receive from you.
It contains information about items being shipped, including purchase order number,
ship date, estimated delivery date, lot number, and supplier DEA number.
By receiving a valid and timely 856, Cardinal Health can correctly anticipate
shipments you send us. When Cardinal Health doesn‟t receive a valid 856 file:
Visibility doesn‟t exist for incoming shipments.
Shipments cannot be reconciled with purchase orders.
Manual follow-ups, such as phone calls and emails, must take place to
resolve the discrepancy.
856 Advance Ship Notice
3
EDI
Requirements
By the time you are ready to implement the 856, you have already been through new
supplier setup and testing. As a reminder about your EDI requirements to do
business with Cardinal Health, please keep the following requirements in mind.
Cardinal Health expects the supplier to be fully engaged and compliant with
all applicable EDI requirements. Compliance is required within 90 days of
becoming a supplier or upon notification of non-compliance.
Suppliers are required to send a 997 within 24 hours of receiving any EDI
transmission from Cardinal Health.
Suppliers are required to monitor 997s received from Cardinal Health. If a
997 has not been received or contains faulty data, you must take prompt
action to resolve the issue.
Suppliers are required to maintain compatible electronic document version
numbers in accordance with Cardinal Health‟s current software.
Cardinal Health will be using compliance to our EDI standards as part of our Supplier
Performance Management processes and as a criterion in the annual Supplier
Quality Award. All documents must be sent with Cardinal‟s required fields as the
minimum standard in order to be in compliance with our guidelines.
856 Advance Ship Notice
4
EDI Workflow
To illustrate the flow between Cardinal Health and our suppliers via EDI, the
following flowchart is provided:
Cardinal sends an
850 Purchase
Order to place an
order
Supplier sends a 997 Functional
Acknowledgement, confirming
receipt of 850 within 24 hours
Supplier sends an 855 Order
Acknowledgement to alert Cardinal
Health of the product availability of all
items on the original purchase order
Cardinal Health
sends a 997,
confirming receipt
of the 855
Supplier ships the
purchase order
Supplier sends 856
Advanced Ship Notice
to alert Cardinal Health
of the contents of an
upcoming shipment
Cardinal Health
sends a 997,
confirming receipt
of the 856
856 Advance Ship Notice
Supplier sends an
810 Invoice to
request payment
from Cardinal Health
for items shipped
Cardinal Health
sends a 997,
confirming receipt
of the 810
5
EDI Benefits
This document is just one part of an overall EDI implementation with Cardinal Health.
Benefits of a successful EDI program save money and time for all involved.
EDI saves time and money. When suppliers provide EDI information to
Cardinal Health via EDI it reduces the need to make follow-up phone calls for
troubleshooting. On average, that reduces the amount of supplier inquires by 57
percent when providing EDI data compared with suppliers who don‟t. This
efficiency alone offsets any cost of the implementation and maintenance, and
similar savings should be enjoyed by you with successful EDI implementation.
We can proactively reduce the number of unnecessary deductions. Our
distribution centers are able to use EDI data to enhance the accuracy of
discrepancy reporting and to proactively reduce the number of unnecessary
deductions.
Successful EDI implementation will improve your NLC Supplier Scorecard.
Cardinal Health provides each NLC supplier with a “scorecard”, measuring many
aspects of your service level.
EDI data will become vital to Pedigree requirements in the future. More and
more states within the U.S. are requiring pedigree data for certain shipments.
EDI transactions can provide the data necessary to assist with serialized
receiving and reduce turnaround time of the product.
Our standards are industry standards. Most companies conduct business via
EDI, and the terms of EDI are written to universal standards as defined by ANSI.
Additionally, HDMA provides valuable guidelines that are specific to our supply
chain while staying within the boundaries of larger EDI standards. This means no
proprietary formatting is necessary for you to become compliant. Any steps you
take to successfully implement EDI with Cardinal Health also may benefit you
with your other business partner transactions.
Improve customer experience. Timely, trusted and consistent communication
of product availability and incoming inventory will help Cardinal Health plan
accordingly. Effective EDI collaboration provides customers with a better
ordering experience with proactive, accurate and actionable product availability
information.
856 Advance Ship Notice
6
Required
Fields
The next section, the EDI 856 Technical Guidelines, provides the EDI standard and
technical documentation for the universal standards. To simplify the process for you,
below is a list of the 11 fields that Cardinal Health requires in the 856 transaction.
You may want to refer to both this section and the next for complete technical
guidelines, but this summary will allow you to focus on exactly what‟s needed for a
successful 856.
Suppliers are required to transmit an 856 as soon as the truck is loaded,
even if the truck is loaded after business hours. The supplier must send the
856 even if Cardinal Health is picking up the shipment.
All fields below are required by the Cardinal Health Standard and used
to calculate compliance.
Data Element
Business Definition
Maps to Technical
Guideline…
Hierarchical
Level Within
the ASN
Confirmed Ship
Date
The date on which the manufacturer has
confirmed the item(s) has been shipped to
the customer.
Shipment Level
Estimated
Delivery Date
The date on which the distributor is
expected to receive the item(s) from the
manufacturer.
Carrier Name
The name of the transportation company
who will deliver the product from
origination to destination or the originating
carrier's identity.
The address and ID# of the location from
where the product is being shipped
(shipping point).
DTM02 (Date/Time)
Segment, Data Element
374 with a qualifier of
„011‟ for Shipped Date
and the date in Data
Element 373.
DTM02 (Date/Time)
Segment, Data Element
374 with a qualifier of
„017„ for Expected
Arrival and the date in
Data Element 373.
TD505 (Carrier Details)
Segment, Data Element
387.
N101 (Name – Ship
From) Segment, Data
Element 098 with a
qualifier of „SF‟ for Ship
From.
REF02 Segment, Data
Element 128 contain
the qualifier of „CN‟ for
Carrier‟s Reference
Number (PRO/Invoice)
and Data Element 127
should contain the
carrier tracking number.
Shipment Level
Shipping Location
(Ship From)
Carrier Tracking
Number
The number automatically assigned to
every shipment to identify and trace it as it
travels to its destination.
856 Advance Ship Notice
Shipment Level
Shipment Level
Shipment Level
7
DEA Number /
Health Industry
Number /
D&B® D-U-N-S®
Number
The DEA number indicates a health care
provider‟s authority to write prescriptions
for controlled substances. The Health
Industry Number (HIN) is a unique ID for
identifying all trading partners. Go to
http://www.hibcc.org/hinsystem.htm to
obtain your HIN. A D&B® D-U-N-S®
Number is a unique nine-digit sequence
recognized as the universal standard for
identifying businesses worldwide.
Purchase Order
Number
The Cardinal Health Purchase Order
Number; Written authorization for a
supplier to ship products at a specified
price, which becomes a legally binding
contract once the supplier accepts it.
The NDC Number or the Universal
Product Code (UPC) associated with
each individual item that is used to place
orders.
The number of individual pieces shipped
to its destination.
NDC Number or
UPC Number
Ship Quantity
Lot Number
The number assigned to a particular
batch of product.
Expiration Date
The date after which the product is not
recommended for use.
856 Advance Ship Notice
N104 (Name – Ship
From) Segment, Data
Element 098 with a
qualifier of „SF‟ should
have Data Element 066
with a qualifier of
„1‟.‟9‟.‟11‟ or „21‟ and
Data element 067
should contain the
supplier unique
identifier.
PRF01 (Purchase
Order Reference)
Segment, Data Element
324.
Shipment Level
LIN03 (Line
Identification) Segment,
Data Element 234.
Item Level
SN102 (Item Detail
(Shipment)) Segment,
Data Element 382.
Item Level
LIN07 (Line
Identification) Segment,
Data Element 235 with
a qualifier of „LT‟ for Lot
Number and in Data
Element 234 the Lot
number.
DTM02 (Date/Time)
Segment, Data Element
374 with a qualifier of
„036‟ for Expiration
date.
Item Level
Order Level
Item Level
8
General Reference Materials
Contact
Information
If you have questions or concerns at any time about any aspect of your EDI
communications with Cardinal Health, please contact us using the following contact
information.
ECOMMERCE PHONE: (614) 757-5334
ECOMMERCE FAX: (614) 652-4028
EMAIL: [email protected]
Mailing Address
Cardinal Health Enterprise IT Technical Services
th
ECommerce Group / 5 Floor
6000 Parkwood Place
Dublin, OH 43017
856 Advance Ship Notice Implementation Guide.docx
9
EDI Standards
and ISA/GS
Information
Standards/Version: X12 004010
VAN: GXS or AS2
ISA Header Information
PRODUCTION ID‟S
TESTING ID‟S
Authorization Qualifier:
00
00
Authorization ID:
(Blank)
(Blank)
Cardinal‟s Receiver Qualifier:
ZZ
ZZ
Cardinal‟s Receiver ID:
CARDINAL
CARDINALTEST
Sub-element Sep: > (Hex 6E)
Element Sep: * (Hex 5C)
Segment Term: µ (Hex 15)
NOTE: We acknowledge all transactions at Group Level within 12 hours of receipt.
Please acknowledge any transactions you receive from us in the same manner.
GS Identification Information
Cardinal Health‟s
Application Receiver Code:
856 Advance Ship Notice
Production
Testing
CARDINAL
CARDINALTEST
10
The 856 EDI Technical Guidelines
Functional Group ID=SH Introduction:
The information presented in this section is provided to establish the requirements of the Pharmaceutical
Distribution business of Cardinal Health in passing documents electronically using EDI technology with
our trading partners. Standards were developed using the "Industry Conventions and Implementation
Guidelines for Electronic Data Interchange" documentation of the Healthcare Distribution Management
Association (HDMA). Please contact our eCommerce Group at (614) 757-5334 with any questions.
Note: The use of common special characters as the sub element separator in the ISA is not acceptable
by the Pharmaceutical Supply Chain business of Cardinal Health.
Must Use indicates Must Use elements for Cardinal, regardless of ANSI Attributes.
Heading:
Pos.
No.
Seg.
Name
Req. Des.
Max Use
Loop
Repeat
ID
Must
Use
010
ST
Transaction Set Header
M
1
Must
Use
020
BSN
Beginning Segment for Ship Notice
M
1
Detail:
Pos.
No.
Seg.
Name
Req.
Des.
Max Use
Loop Repeat
ID
LOOP ID – HL
Must
Use
200000
010
HL
Hierarchical Level - Shipment Level
M
1
110
TD1
Carrier Detail s (Quantity and Weight)
O
20
120
TD5
Carrier Details (Routing Sequence/Transit
Time)
O
12
150
REF
Reference Identification
O
>1
200
DTM
Date/Time Reference
O
10
LOOP ID - N1
200
220
N1
Name - Ship To
O
1
240
N3
Address Information
O
2
250
N4
Geographic Location
O
1
LOOP ID - N1
200
220
N1
Name - Ship From
O
1
240
N3
Address Information
O
2
250
N4
Geographic Location
O
1
LOOP ID – HL
Must
Use
200000
010
HL
Hierarchical Level - Order Level
M
1
050
PRF
Purchase Order Reference
O
1
150
REF
Reference Identification
O
>1
LOOP ID – HL
Must
Use
200000
010
HL
Hierarchical Level – Tare Level
M
1
190
MAN
Marks and Numbers
O
>1
LOOP ID – HL
Must
Use
200000
010
HL
Hierarchical Level – Container (Pack) Level
M
1
020
LIN
Item Identification
O
1
030
SN1
Item Detail (Shipment)
O
1
190
MAN
Marks and Numbers
O
>1
200
DTM
Date/Time Reference
O
10
LOOP ID – HL
Must
Use
200000
010
HL
Hierarchical Level - Item Level
M
1
020
LIN
Item Identification
O
1
030
SN1
Item Detail (Shipment)
O
1
040
SLN
Subline Item Detail
O
1000
856 Advance Ship Notice
Page 12 of 58
070
PID
Product / Item Description
O
200
190
MAN
Marks and Numbers
O
>1
200
DTM
Date/Time Reference
O
10
Summary:
Pos.No.
Seg.
Name
Req.
Des.
Max Use
Loop
Repeat
ID
Must Use
010
CTT
Transaction Totals
O
1
020
SE
Transaction Set Trailer
M
1
Transaction Set Notes
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.
Transaction Set Comments
The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has
no meaning.
856 Advance Ship Notice
Page 13 of 58
Segment:
ST Transaction Set Header
Position:
010
Loop:
Level:
Usage:
Heading
Mandatory
Max Use:
1
Purpose:
To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes:
1
The transaction set identifier (ST01) is used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g.,
810 selects the Invoice Transaction Set).
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
ST01
143
Attributes
Transaction Set Identifier Code
M
ID 3/3
M
AN 4/9
Code uniquely identifying a Transaction Set
856
Must Use
ST02
329
Ship Notice/Manifest
Transaction Set Control Number
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
856 Advance Ship Notice
Page 14 of 58
Segment:
BSN Beginning Segment for Ship Notice
Position:
020
Loop:
Level:
Usage:
Heading
Mandatory
Max Use:
1
Purpose:
To transmit identifying numbers, dates, and other basic data relating to the
transaction set
Syntax Notes:
1
If BSN07 is present, then BSN06 is required.
Semantic Notes:
1
BSN03 is the date the shipment transaction set is created.
2
BSN04 is the time the shipment transaction set is created.
3
BSN06 is limited to shipment related codes.
1
BSN06 and BSN07 differentiate the functionality of use for the transaction
set.
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
BSN01
353
Attributes
Transaction Set Purpose Code
M
ID 2/2
M
AN 2/30
Code identifying purpose of transaction set
00
Must Use
BSN02
396
Original
Shipment Identification
A unique control number assigned by the original shipper to identify a
specific shipment
Vendor Bill of Lading Number or other Shipment Identifier
Must Use
BSN03
373
Date
M
DT 8/8
M
TM 4/8
Date expressed as CCYYMMDD
Document Create Date.
Must Use
BSN04
337
Time
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 =
856 Advance Ship Notice
Page 15 of 58
hundredths (00-99)
Document Create Time.
BSN05
1005
Hierarchical Structure Code
O
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
BSN06
640
0001
Shipment, Order, Packaging, Item
0004
Shipment, Order, Item
Transaction Type Code
C
ID 2/2
Code specifying the type of transaction
AS
Shipment Advice
Notification by an inventory management
organization providing current shipping advice
relating to the outstanding requisition or order
856 Advance Ship Notice
Page 16 of 58
Segment:
HL Hierarchical Level - Shipment Level
Position:
010
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify dependencies among and the content of hierarchically related groups
of data segments
Syntax Notes:
Semantic Notes:
Comments:
1
The HL segment is used to identify levels of detail information using a
hierarchical structure, such as relating line-item data to shipment data, and
packaging data to line-item data.
The HL segment defines a top-down/left-right ordered structure.
2
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.
3
HL02 identifies the hierarchical ID number of the HL segment to which the
current HL segment is subordinate.
4
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.
5
HL04 indicates whether or not there are subordinate (or child) HL segments
related to the current HL segment.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
HL01
628
Hierarchical ID Number
Attributes
M
AN 1/12
A unique number assigned by the sender to identify a particular data
segment in a hierarchical structure
'1'
HL02
734
Hierarchical Parent ID Number
O
AN 1/12
Identification number of the next higher hierarchical data segment that
856 Advance Ship Notice
Page 17 of 58
the data segment being described is subordinate to
'0'
Must Use
HL03
735
Hierarchical Level Code
M
ID 1/2
Code defining the characteristic of a level in a hierarchical structure
S
Must Use
HL04
736
Shipment
Hierarchical Child Code
O
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.
856 Advance Ship Notice
Page 18 of 58
Segment:
TD1 Carrier Details (Quantity and Weight)
Position:
110
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
20
Purpose:
To specify the transportation details relative to commodity, weight, and quantity
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.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Data
Element Name
TD101
103
Attributes
Packaging Code
O
AN 3/5
Code identifying the type of packaging; Part1: Packaging Form, Part2:
Packaging Material; if the Data Element is used, then at 1 is always
required
TD102
80
CAS
Case
CTN
Carton
PLT
Pallet
Lading Quantity
C
N0 1/7
O
ID 1/2
C
R 1/10
Number of units (pieces) of the lading commodity
TD106
187
Weight Qualifier
Code defining the type of weight
G
TD107
81
Gross Weight
Weight
Numeric value of weight
856 Advance Ship Notice
Page 19 of 58
TD108
355
Unit or Basis for Measurement Code
C
ID 2/2
Code specifying the units in which a value is being expressed, or
manner in which a measurement has been taken
LB
856 Advance Ship Notice
Pound
Page 20 of 58
Segment:
TD5 Carrier Details (Routing Sequence/Transit Time)
Position:
120
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
12
Purpose:
To specify the carrier and sequence of routing and provide transit time
information
Syntax Notes:
1
At least one of TD502 TD504 TD505 TD506 or TD512 is required.
2
If TD502 is present, then TD503 is required.
1
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.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Data
Element Name
TD501
133
Attributes
Routing Sequence Code
O
ID 1/2
Code describing the relationship of a carrier to a specific shipment
movement
O
Must Use
TD502
66
Origin Carrier (Air, Motor, or Ocean)
Identification Code Qualifier
C
ID 1/2
Code designating the system/method of code structure used for
Identification Code (67)
2
Must Use
TD503
67
Standard Carrier Alpha Code (SCAC)
Identification Code
C
AN 2/80
C
ID 1/2
Code identifying a party or other code
TD504
91
Transportation Method/Type Code
Code specifying the method or type of transportation for the shipment
Must Use
TD505
856 Advance Ship Notice
387
Routing
C
AN 1/35
Page 21 of 58
Free-form description of the routing or requested routing for shipment,
or the originating carrier's identity
Carrier Name
TD506
368
Shipment / Order Status Code
O
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 of transaction.
856 Advance Ship Notice
CC
Shipment Complete on Date
PR
Partial Shipment
Page 22 of 58
Segment:
REF Reference Identification
Position:
150
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
>1
Purpose:
To specify identifying information
Syntax Notes:
1
At least one of REF02 or REF03 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
REF01
128
Attributes
Reference Identification Qualifier
M
ID 2/3
Code qualifying the Reference Identification
BM
Bill of Lading Number
and/or
CN
Must Use
REF02
127
Carrier's Reference Number (PRO/Invoice)
Reference Identification
C
AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
856 Advance Ship Notice
Page 23 of 58
Segment:
DTM Date/Time Reference
Position:
200
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
10
Purpose:
To specify pertinent dates and times
Syntax Notes:
1
At least one of DTM02 DTM03 or DTM05 is required.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
DTM01
374
Attributes
Date/Time Qualifier
M
ID 3/3
Code specifying type of date or time, or both date and time
Must Use
DTM02
373
011
Shipped
017
Expected Arrival
Date
C
DT 8/8
Date expressed as CCYYMMDD
856 Advance Ship Notice
Page 24 of 58
Segment:
N1 Name - Ship To
Position:
220
Loop:
N1
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify a party by type of organization, name, and code
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.
1
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.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
N101
98
Attributes
Entity Identifier Code
M
ID 2/3
Code identifying an organizational entity, a physical location, property or
an individual
ST
N102
93
Ship To
Name
C
AN 1/60
C
ID 1/2
Free-form name
Cardinal Health facility name
Must Use
N103
66
Identification Code Qualifier
Code designating the system/method of code structure used for
Identification Code (67)
11
Must Use
N104
67
Drug Enforcement Administration (DEA)
Identification Code
C
AN 2/80
Code identifying a party or other code
Cardinal Health facility DEA number
856 Advance Ship Notice
Page 25 of 58
Segment:
N3 Address Information
Position:
240
Loop:
N1
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
2
Purpose:
To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Data
Element Name
N301
166
Address Information
Attributes
M
AN 1/55
O
AN 1/55
Address information
N302
166
Address Information
Address information
856 Advance Ship Notice
Page 26 of 58
Segment:
N4 Geographic Location
Position:
250
Loop:
N1
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
1
Purpose:
To specify the geographic place of the named party
Syntax Notes:
1
If N406 is present, then N405 is required.
1
A combination of either N401 through N404, or N405 and N406 may be
adequate to specify a location.
2
N402 is required only if city name (N401) is in the U.S. or Canada.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Data
Element Name
N401
19
City Name
Attributes
O
AN 2/30
O
ID 2/2
Free-form text for city name
N402
156
State or Province Code
Code (Standard State/Province) as defined by appropriate government
agency
N403
116
Postal Code
O
ID 3/15
Code defining international postal zone code excluding punctuation and
blanks (zip code for United States)
856 Advance Ship Notice
Page 27 of 58
Segment:
N1 Name - Ship From
Position:
220
Loop:
N1
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify a party by type of organization, name, and code
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.
1
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.
2
N105 and N106 further define the type of entity in N101.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
N101
98
Attributes
Entity Identifier Code
M
ID 2/3
Code identifying an organizational entity, a physical location, property or
an individual
SF
N102
93
Ship From
Name
C
AN 1/60
X
ID 1/2
Free-form name
Vendor Ship-From Name
Must Use
N103
66
Identification Code Qualifier
Code designating the system/method of code structure used for
Identification Code (67). One of:
856 Advance Ship Notice
1
D-U-N-S Number, Dun & Bradstreet
9
D-U-N-S+4, D-U-N-S Number with Four Character
Suffix
11
Drug Enforcement Administration (DEA)
Page 28 of 58
21
Must Use
N104
67
Health Industry Number (HIN)
Identification Code
C
AN 2/80
Code identifying a party or other code
Vendor Ship-From Identifier Number
856 Advance Ship Notice
Page 29 of 58
Segment:
N3 Address Information
Position:
240
Loop:
N1
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
2
Purpose:
To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
N301
166
Address Information
Attributes
M
AN 1/55
O
AN 1/55
Address information
N302
166
Address Information
Address information
856 Advance Ship Notice
Page 30 of 58
Segment:
N4 Geographic Location
Position:
250
Loop:
N1
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
1
Purpose:
To specify the geographic place of the named party
Syntax Notes:
1
If N406 is present, then N405 is required.
1
A combination of either N401 through N404, or N405 and N406 may be
adequate to specify a location.
2
N402 is required only if city name (N401) is in the U.S. or Canada.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Data
Element Name
N401
19
City Name
Attributes
O
AN 2/30
C
ID 2/2
Free-form text for city name
N402
156
State or Province Code
Code (Standard State/Province) as defined by appropriate government
agency
N403
116
Postal Code
O
ID 3/15
Code defining international postal zone code excluding punctuation and
blanks (zip code for United States)
856 Advance Ship Notice
Page 31 of 58
Segment:
HL Hierarchical Level - Order Level
Position:
010
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify dependencies among and the content of hierarchically related groups
of data segments
Syntax Notes:
Semantic Notes:
Comments:
1
The HL segment is used to identify levels of detail information using a
hierarchical structure, such as relating line-item data to shipment data, and
packaging data to line-item data.
The HL segment defines a top-down/left-right ordered structure.
2
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.
3
HL02 identifies the hierarchical ID number of the HL segment to which the
current HL segment is subordinate.
4
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.
5
HL04 indicates whether or not there are subordinate (or child) HL segments
related to the current HL segment.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
HL01
628
Hierarchical ID Number
Attributes
M
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
AN 1/12
Identification number of the next higher hierarchical data segment that
856 Advance Ship Notice
Page 32 of 58
the data segment being described is subordinate to
Must Use
HL03
735
Hierarchical Level Code
M
ID 1/2
Code defining the characteristic of a level in a hierarchical structure
O
Must Use
HL04
736
Order
Hierarchical Child Code
O
ID 1/1
Code indicating if there are hierarchical child data segments
subordinate to the level being described
0
1
No Subordinate HL Data Segment in this
Hierarchical Structure
Additional Subordinate HL Data Segment in This
Hierarchical Structure.
856 Advance Ship Notice
Page 33 of 58
Segment:
PRF Purchase Order Reference
Position:
050
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To provide reference to a specific purchase order
Syntax Notes:
Semantic Notes:
1
PRF04 is the date assigned by the purchaser to purchase order.
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
PRF01
324
Purchase Order Number
Attributes
M
AN 1/22
O
DT 8/8
Identifying number for Purchase Order assigned by the
orderer/purchaser
PRF04
373
Date
Date expressed as CCYYMMDD
Original Purchase Order Date
856 Advance Ship Notice
Page 34 of 58
Segment:
REF Reference Identification
Position:
150
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
>1
Purpose:
To specify identifying information
Syntax Notes:
Semantic 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.
1
REF04 contains data relating to the value cited in REF02.
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
REF01
128
Attributes
Reference Identification Qualifier
M
ID 2/3
Code qualifying the Reference Identification
BM
Bill of Lading Number - Not needed
and/or
CN
Must Use
REF02
127
Carrier's Reference Number (PRO/Invoice)
Reference Identification
C
AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
856 Advance Ship Notice
Page 35 of 58
Segment:
HL Hierarchical Level - Tare Level
Position:
010
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify dependencies among and the content of hierarchically related groups
of data segments
Syntax Notes:
Semantic Notes:
Comments:
1
The HL segment is used to identify levels of detail information using a
hierarchical structure, such as relating line-item data to shipment data, and
packaging data to line-item data.
The HL segment defines a top-down/left-right ordered structure.
2
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.
3
HL02 identifies the hierarchical ID number of the HL segment to which the
current HL segment is subordinate.
4
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.
5
HL04 indicates whether or not there are subordinate (or child) HL segments
related to the current HL segment.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
HL01
628
Hierarchical ID Number
Attributes
M
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
AN 1/12
Identification number of the next higher hierarchical data segment that
856 Advance Ship Notice
Page 36 of 58
the data segment being described is subordinate to
Must Use
HL03
735
Hierarchical Level Code
M
ID 1/2
Code defining the characteristic of a level in a hierarchical structure
T
Must Use
HL04
736
Tare
Hierarchical Child Code
O
ID 1/1
Code indicating if there are hierarchical child data segments
subordinate to the level being described
0
1
No Subordinate HL Data Segment in this
Hierarchical Structure
Additional Subordinate HL Data Segment in This
Hierarchical Structure.
856 Advance Ship Notice
Page 37 of 58
Segment:
MAN Marks and Numbers
Position:
190
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
>1
Purpose:
To indicate identifying marks and numbers for shipping containers
Syntax Notes:
Semantic Notes:
1
MAN01/MAN02 and MAN04/MAN05 may be used to identify two different
marks and numbers assigned to the same physical container.
Comments:
1
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.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
MAN01
88
Attributes
Marks and Numbers Qualifier
M
ID 1/2
Code specifying the application or source of Marks and Numbers (87)
GM
Must Use
MAN02
87
Tare Level SSCC-18 Pallet Tracking ID
Marks and Numbers
M
AN 1/48
Tare Level SSCC-18 Pallet Tracking ID
856 Advance Ship Notice
Page 38 of 58
Segment:
HL Hierarchical Level - Pack Level
Position:
010
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify dependencies among and the content of hierarchically related groups
of data segments
Syntax Notes:
Semantic Notes:
Comments:
1
The HL segment is used to identify levels of detail information using a
hierarchical structure, such as relating line-item data to shipment data, and
packaging data to line-item data.
The HL segment defines a top-down/left-right ordered structure.
2
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.
3
HL02 identifies the hierarchical ID number of the HL segment to which the
current HL segment is subordinate.
4
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.
5
HL04 indicates whether or not there are subordinate (or child) HL segments
related to the current HL segment.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
HL01
628
Hierarchical ID Number
Attributes
M
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
AN 1/12
Identification number of the next higher hierarchical data segment that
the data segment being described is subordinate to
856 Advance Ship Notice
Page 39 of 58
Must Use
HL03
735
Hierarchical Level Code
M
ID 1/2
Code defining the characteristic of a level in a hierarchical structure
P
Must Use
HL04
736
Pack
Hierarchical Child Code
O
ID 1/1
Code indicating if there are hierarchical child data segments
subordinate to the level being described
0
1
No Subordinate HL Data Segment in this
Hierarchical Structure
Additional Subordinate HL Data Segment in This
Hierarchical Structure.
856 Advance Ship Notice
Page 40 of 58
Segment:
LIN Item Identification
Position:
020
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
1
Purpose:
To specify basic item identification data
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.
Comments:
ONLY APPLICABLE FOR SINGLE SKU FULL CASE CARTONS
Data Element Summary
Ref.
Des.
Data
Element Name
LIN01
350
Attributes
Assigned Identification
O
AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
ASN Line Number or Original PO Line Number
Must Use
LIN02
235
Product/Service ID Qualifier
M
ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234). One of:
N4
National Drug Code in 5-4-2 Format
5-digit manufacturer ID, 4-digit product ID, 2-digit
trade package size
ND
Must Use
LIN03
234
National Drug Code (NDC)
Product/Service ID
M
AN 1/48
C
ID 2/2
Identifying number for a product or service
NDC Number
LIN04
235
Product/Service ID Qualifier
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
LIN05
856 Advance Ship Notice
234
Product/Service ID
C
AN 1/48
Page 41 of 58
Identifying number for a product or service
Must Use
LIN06
235
Product/Service ID Qualifier
C
ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
LT
Must Use
LIN07
234
Lot Number
Product/Service ID
C
AN 1/48
Identifying number for a product or service
Lot Number
856 Advance Ship Notice
Page 42 of 58
Segment:
SN1 Item Detail (Shipment)
Position:
030
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional (Must Use)
Max Use:
1
Purpose:
To specify line-item detail relative to shipment
Syntax Notes:
Semantic Notes:
If either SN105 or SN106 is present, then the other is required.
SN101 is the ship notice line-item identification.
SN103 defines the unit of measurement for both SN102 and SN104.
Comments:
ONLY APPLICABLE FOR SINGLE SKU FULL CASE CARTONS
Data Element Summary
Ref.
Des.
Data
Element Name
SN101
350
Assigned Identification
Attributes
O
AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
ASN Line Number or Original PO Line Number, as referenced in LIN01
Must Use
SN102
382
Number of Units Shipped
M
R 1/10
Numeric value of units shipped in manufacturer's shipping units for a
line item or transaction set
Must Use
SN103
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
Original Purchase Order Unit of Measure
SN108
668
Line Item Status Code
O
ID 2/2
Code specifying the action taken by the seller on a line item requested
by the buyer
Refer to 004010 Data Element Directory for acceptable code values.
856 Advance Ship Notice
Page 43 of 58
Segment:
MAN Marks and Numbers
Position:
190
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
>1
Purpose:
To indicate identifying marks and numbers for shipping containers
Syntax Notes:
Semantic Notes:
1
MAN01/MAN02 and MAN04/MAN05 may be used to identify two different
marks and numbers assigned to the same physical container.
Comments:
1
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.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
MAN01
88
Attributes
Marks and Numbers Qualifier
M
ID 1/2
Code specifying the application or source of Marks and Numbers (87)
GM
Must Use
MAN02
87
SSCC-18 and Application Identifier
Marks and Numbers
M
AN 1/48
Marks and numbers used to identify a shipment or parts of a shipment
SSCC-18 and Application Identifier
856 Advance Ship Notice
Page 44 of 58
Segment:
DTM Date/Time Reference
Position:
200
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
10
Purpose:
To specify pertinent dates and times
Syntax Notes:
Semantic Notes:
Comments:
ONLY APPLICABLE FOR SINGLE SKU FULL CASE CARTONS
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
DTM01
374
Attributes
Date/Time Qualifier
M
ID 3/3
Code specifying type of date or time, or both date and time
Must Use
DTM02
373
208
Lot Number Expiration Date
036
Expiration
Date
C
DT 8/8
Date expressed as CCYYMMDD
856 Advance Ship Notice
Page 45 of 58
Segment:
HL Hierarchical Level - Item Level
Position:
010
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To identify dependencies among and the content of hierarchically related groups
of data segments
Syntax Notes:
Semantic Notes:
Comments:
1
The HL segment is used to identify levels of detail information using a
hierarchical structure, such as relating line-item data to shipment data, and
packaging data to line-item data.
The HL segment defines a top-down/left-right ordered structure.
2
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.
3
HL02 identifies the hierarchical ID number of the HL segment to which the
current HL segment is subordinate.
4
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.
5
HL04 indicates whether or not there are subordinate (or child) HL segments
related to the current HL segment.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
HL01
628
Hierarchical ID Number
Attributes
M
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
AN 1/12
Identification number of the next higher hierarchical data segment that
856 Advance Ship Notice
Page 46 of 58
the data segment being described is subordinate to
Must Use
HL03
735
Hierarchical Level Code
M
ID 1/2
Code defining the characteristic of a level in a hierarchical structure
I
HL04
736
Item
Hierarchical Child Code
O
ID 1/1
Code indicating if there are hierarchical child data segments
subordinate to the level being described
0
856 Advance Ship Notice
No Subordinate HL Segment in This Hierarchical
Structure.
Page 47 of 58
Segment:
LIN Item Identification
Position:
020
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
1
Purpose:
To specify basic item identification data
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.
Semantic Notes:
1
LIN01 is the line item identification
Comments:
1
See the Data Dictionary for a complete list of IDs.
2
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.
Data Element Summary
Ref.
Des.
Data
Element Name
LIN01
350
Attributes
Assigned Identification
O
AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
ASN Line Number or Original PO Line Number
Must Use
LIN02
235
Product/Service ID Qualifier
M
ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234). One of:
N4
National Drug Code in 5-4-2 Format
5-digit manufacturer ID, 4-digit product ID, 2-digit
trade package size
ND
Must Use
LIN03
234
National Drug Code (NDC)
Product/Service ID
M
AN 1/48
Identifying number for a product or service
NDC Number
856 Advance Ship Notice
Page 48 of 58
LIN04
235
Product/Service ID Qualifier
C
ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
LIN05
234
Product/Service ID
C
AN 1/48
C
ID 2/2
Identifying number for a product or service
Must Use
LIN06
235
Product/Service ID Qualifier
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
LT
Must Use
LIN07
234
Lot Number
Product/Service ID
C
AN 1/48
Identifying number for a product or service
Lot Number
856 Advance Ship Notice
Page 49 of 58
Segment:
SN1 Item Detail (Shipment)
Position:
030
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional (Must Use)
Max Use:
1
Purpose:
To specify line-item detail relative to shipment
Syntax Notes:
1
If either SN105 or SN106 is present, then the other is required.
Semantic Notes:
1
SN101 is the ship notice line-item identification.
Comments:
1
SN103 defines the unit of measurement for both SN102 and SN104.
Data Element Summary
Ref.
Des.
Data
Element Name
SN101
350
Assigned Identification
Attributes
O
AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
ASN Line Number or Original PO Line Number, as referenced in LIN01
Must Use
SN102
382
Number of Units Shipped
M
R 1/10
Numeric value of units shipped in manufacturer's shipping units for a
line item or transaction set
Must Use
SN103
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
Original Purchase Order Unit of Measure
SN104
646
Quantity Shipped to Date
O
R 1/15
C
R 1/15
C
ID 2/2
Number of Units Shipped to Date
SN105
330
Quantity Ordered
Quantity Ordered
SN106
355
Unit or Basis for Measurement Code
Code specifying the units in which a value is being expressed, or
manner in which a measurement has been taken
856 Advance Ship Notice
Page 50 of 58
SN108
668
Line Item Status Code
O
ID 2/2
Code specifying the action taken by the seller on a line item requested
by the buyer
Refer to 004010 Data Element Directory for acceptable code values.
856 Advance Ship Notice
Page 51 of 58
Segment:
SLN Subline Item Detail
Position:
040
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
1000
Purpose:
To specify product subline detail item data
Syntax Notes:
1
If either SLN04 or SLN05 is present, then the other is required.
Semantic Notes:
1
SLN01 is the identifying number for the subline item.
2
SLN02 is the identifying number for the subline level. The subline level is
analogous to the level code used in a bill of materials.
3
SLN03 is the configuration code indicating the relationship of the subline item
to the baseline item.
1
See the Data Element Dictionary for a complete list of IDs.
2
SLN01 is related to (but not necessarily equivalent to) the baseline item
number. Example: 1.1 or 1A might be used as a subline number to relate to
baseline number
SLN09 and SLN10 should only be used if the lot number and qualifier can
not be sent in LIN06 and LIN07
Comments:
3
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
SLN01
350
Attributes
Assigned Identification
M
AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
ASN Line Number or Original PO Line Number, as referenced in LIN01
Must Use
SLN03
662
Relationship Code
M
ID 1/1
C
R 1/15
Code indicating the relationship between entities
I
SLN04
380
Included
Quantity
Numeric value of quantity
SLN05
C001
Composite Unit of Measure
C
To identify a composite unit of measure (See Figures Appendix for
856 Advance Ship Notice
Page 52 of 58
examples of use)
SLN09
235
Product/Service ID Qualifier
C
R 1/15
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
SN
SLN10
234
Pedigree Serial Number
Product/Service ID
C
AN 1/48
M
ID 2/2
Identifying number for a product or service
Must Use
SLN11
235
Product/Service ID Qualifier
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Must Use
SLN12
234
Product/Service ID
M
AN 1/48
Identifying number for a product or service
856 Advance Ship Notice
Page 53 of 58
Segment:
PID Product/Item Description
Position:
070
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
200
Purpose:
To describe a product or process in coded or free-from format
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
PID01
349
Attributes
Item Description Type
M
ID 1/1
M
AN 1/80
Code indicating the format of a description
F
Must Use
PID05
352
Description
Free-form
A free-form description to clarify the related data elements and their
content. The description should contain prescription (Rx) drug
information such as dosage form, strength and size.
856 Advance Ship Notice
Page 54 of 58
Segment:
MAN Marks and Numbers
Position:
190
Loop:
HL
Level:
Detail
Usage:
Mandatory
Optional
Max Use:
>1
Purpose:
To indicate identifying marks and numbers for shipping containers
Syntax Notes:
1
If either MAN04 or MAN05 is present, then the other is required.
Semantic Notes:
1
MAN01/MAN02 and MAN04/MAN05 may be used to identify two different
marks and numbers assigned to the same physical container.
Comments:
1
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.
Data Element Summary
Ref.
Des.
Data
Element Name
MAN01
88
Marks and Numbers Qualifier
GM
MAN02
87
Attributes
M
ID 1/2
M
AN 1/48
SSCC-18 and Application Identifier
Marks and Numbers
Marks and numbers used to identify a shipment or parts of a shipment
856 Advance Ship Notice
Page 55 of 58
Segment:
DTM Date/Time Reference
Position:
200
Loop:
HL
Level:
Detail
Usage:
Mandatory
Mandatory
Max Use:
10
Purpose:
To specify pertinent dates and times
Syntax Notes:
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
DTM01
374
Attributes
Date/Time Qualifier
M
ID 3/3
Code specifying type of date or time, or both date and time
Must Use
DTM02
373
208
Lot Number Expiration Date
036
Expiration
Date
C
DT 8/8
Date expressed as CCYYMMDD
856 Advance Ship Notice
Page 56 of 58
Segment:
CTT Transaction Totals
Position:
010
Loop:
Level:
Summary
Usage:
Optional
Max Use:
1
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.
1
This segment is intended to provide hash totals to validate transaction
completeness and correctness.
Semantic Notes:
Comments:
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
CTT01
354
Number of HL Segments
Attributes
M
N0 1/6
Total number of line items in the transaction set
On the 856 document, this value represents the number of HL
Segments in the transaction set, not the number of actual line items, as
stated in the Transaction Set Notes
856 Advance Ship Notice
Page 57 of 58
Segment:
SE Transaction Set Trailer
Position:
020
Loop:
Level:
Summary
Usage:
Mandatory
Max Use:
1
Purpose:
To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments:
1
SE is the last segment of each transaction set.
Data Element Summary
Ref.
Des.
Must Use
Data
Element Name
SE01
96
Number of Included Segments
Attributes
M
N0 1/10
Total number of segments included in a transaction set including ST
and SE segments
Must Use
SE02
329
Transaction Set Control Number
M
AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
functional group assigned by the originator for a transaction set
856 Advance Ship Notice
Page 58 of 58