X12 856 Ship Notice/Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- | Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
- 05
- Replace
A unique control number assigned by the original shipper to identify a specific shipment
Vendor Bill of Lading Number or other Shipment Identifier
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
Document Create Date
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- BSN04 is the time the shipment transaction set is created.
Document Create Time. Strongly suggest HHMM only.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0001
- Shipment, Order, Packaging, Item
- 0004
- Shipment, Order, Item
Code specifying the type of transaction
- BSN06 is limited to shipment related codes.
- BSN06 and BSN07 differentiate the functionality of use for the transaction set.
- AS
- Shipment Advice
Notification by an inventory management organization providing current shipping advice
relating to the outstanding requisition or order - DO
- Drop Shipment Invoice
Used to indicate a drop ship notice, not a drop ship invoice
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
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
- CAS
- Case
- CTN
- Carton
- PLT
- Pallet
Number of units (pieces) of the lading commodity
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
- O
- Origin Carrier (Air, Motor, or Ocean)
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- H
- Customer Pickup
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- SR
- Supplier Truck
- X
- Intermodal (Piggyback)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Name
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
- CC
- Shipment Complete on (Date)
- PR
- Partial Shipment
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- CN
- Container
- RR
- Rail Car
- TL
- Trailer (not otherwise specified)
- VE
- Vessel, Ocean
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- 2I
- Tracking Number
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- MB
- Master Bill of Lading
- SN
- Seal Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Estimated and Current Schedule Delivery
To specify pertinent dates and times
ABC requires the DTM|017 or DTM|067 sent on all ASNs.
Code specifying type of date or time, or both date and time
- 017
- Estimated Delivery
- 067
- Current Schedule Delivery
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)
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
- CD
- Central Daylight Time
- CS
- Central Standard Time
- CT
- Central Time
- ED
- Eastern Daylight Time
- ES
- Eastern Standard Time
- ET
- Eastern Time
- GM
- Greenwich Mean Time
- LT
- Local Time
- MD
- Mountain Daylight Time
- MS
- Mountain Standard Time
- MT
- Mountain Time
- PD
- Pacific Daylight Time
- PS
- Pacific Standard Time
- PT
- Pacific Time
Shipped
To specify pertinent dates and times
ABC requires the DTM|011 sent on all ASNs.
Code specifying type of date or time, or both date and time
- 011
- Shipped
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)
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
- CD
- Central Daylight Time
- CS
- Central Standard Time
- CT
- Central Time
- ED
- Eastern Daylight Time
- ES
- Eastern Standard Time
- ET
- Eastern Time
- GM
- Greenwich Mean Time
- LT
- Local Time
- MD
- Mountain Daylight Time
- MS
- Mountain Standard Time
- MT
- Mountain Time
- PD
- Pacific Daylight Time
- PS
- Pacific Standard Time
- PT
- Pacific Time
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 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)
- 21
- Health Industry Number (HIN)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- UL
- UCC/EAN Location Code
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
This segment is Mandatory for Nonexempt RX Products
Geographic Location
To specify the geographic place of the named party
This segment is Mandatory for Nonexempt RX Products
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
ABC's preference is to populate this segment for Ship To, if data is available.
Code qualifying the Reference Identification
- D3
- National Association of Boards of Pharmacy Number
- FW
- State License Identification Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The license number of the ship to entity.
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
The business name and address from whom ownership is transferred, per
21 USC Sec. 581 (26) (I
Code identifying an organizational entity, a physical location, property or an individual
- SE
- Selling Party
Code designating the system/method of code structure used for Identification Code (67)
- 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)
- 21
- Health Industry Number (HIN)
- UL
- UCC/EAN Location Code
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
This segment is Mandatory for Nonexempt RX Products
Geographic Location
To specify the geographic place of the named party
This segment is Mandatory for Nonexempt RX Products
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
This segment is Mandatory for Nonexempt RX Products
Code qualifying the Reference Identification
- D3
- National Association of Boards of Pharmacy Number
Supplier’s NABP provided VAWD (Verified
Accredited Wholesale Distributors™) Number. - FW
- State License Identification Number
A unique number assigned to each provider of
service; this number is assigned by state
governments and is the provider's legal
identification number in the state that is assigned.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The license number of the ship to entity.
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 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)
- 21
- Health Industry Number (HIN)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- UL
- UCC/EAN Location Code
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
This segment is Mandatory for Nonexempt RX Products
Geographic Location
To specify the geographic place of the named party
This segment is Mandatory for Nonexempt RX Products
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
This segment is Mandatory for Nonexempt RX Products
Code qualifying the Reference Identification
- D3
- National Association of Boards of Pharmacy Number
Supplier’s NABP provided VAWD
(VerifiedAccredited Wholesale Distributors™) Number. - FW
- State License Identification Number
A unique number assigned to each provider of
service; this number is assigned by state governments and is the provider's legal identification number in the state that is assigned.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The license number of the ship to entity.
A free-form description to clarify the related data elements and their content
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CE
- Certifier
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
A valid telephone number must be provided
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
A valid email address must be provided
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 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)
- 21
- Health Industry Number (HIN)
- UL
- UCC/EAN Location Code
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
AmerisourceBergen prefers the DEA Number be used. If not possible please use HIN, GLN or DUN. Please request us for the identifier’s list for all the distribution centers if you don’t have one.
Address Information
To specify the location of the named party
This segment is Mandatory for Nonexempt RX Products
Geographic Location
To specify the geographic place of the named party
This segment is Mandatory for Nonexempt Rx Products
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
ABC's preference is to populate this segment for Ship To, if data is available.
Code qualifying the Reference Identification
- D3
- National Association of Boards of Pharmacy Number
- FW
- State License Identification Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Yes/No Question DPS
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
The YNQ02 should have a value of Y which indicates that Direct
Purchase Statement details are available at the item level. As indicated, product was purchased directly from the manufacturer, manufacturer’s exclusive distributor or repackager who purchased directly from a manufacturer
Code indicating a Yes or No condition or response
- YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
- Y
- Yes
Free-form message text
As indicated below, product was purchased directly from the manufacturer, manufacturer’s exclusive distributor or repackager who purchased directly from a manufacturer
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- DPS
Direct Purchase Statement
Yes/No Question TS
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
The YNQ02 should have a value of 'Y' which indicates that DSCSA applies.
This segment is Mandatory for Nonexempt RX Products
Code indicating a Yes or No condition or response
- YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
- Y
- Yes
"Y" indicates that the transaction is DSCSA compliant
Free-form message text
Seller has complied with each applicable subsection of FDCA Sec.
581(27)(A)-(G).
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- TS
Transaction Statement
Free-form message text
- YNQ10 contains a free-form question when codified questions are not available.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
ABC Purchase Order Number – Please send the PO number only. No
extra characters are required other than the actual PO number.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
Date expressed as CCYYMMDD
- PRF04 is the date assigned by the purchaser to purchase order.
Original Purchase Order Date
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
If using S-O-T-P-I, the T (Tare) level is strongly desired.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- T
- Shipping Tare
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
- W
- Pallet Number
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Tare Level SSCC-18 Pallet Tracking ID
MAN02 element value needs to be all numeric with 20 characters length if MAN01 is “GM”. It should start with "00" and remaining 18 characters should specify the valid SSCC. Same SSCC cannot be used multiple times in an ASN
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Only Applicable for Single (homogeneous) SKU Full Case Cartons
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN Line Number or Original PO Line Number (ABC's preference is the Original PO Line Number)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
The Product Qualifier code used here must match the code used in the EDI 850 transaction sent by AmerisourceBergen
- LT
- Lot Number
- MF
- Manufacturer
- N1
- National Drug Code in 4-4-2 Format
- N2
- National Drug Code in 5-3-2 Format
- N3
- National Drug Code in 5-4-1 Format
- N4
- National Drug Code in 5-4-2 Format
- N5
- National Health Related Item Code in 5-5 Format
- N6
- National Health Related Item Code in 4-6 Format
- ND
- National Drug Code (NDC)
- NH
- National Health Related Item Code
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- UX
- Universal Product Number
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
NDC Number – Please send the valid NDC number without additional prefix or suffix number.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Only Applicable for Single SKU Full Case Cartons
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- AM
- Ampoule
- BO
- Bottle
- BX
- Box
- CA
- Case
- CH
- Container
- CT
- Carton
- DZ
- Dozen
- EA
- Each
- GS
- Gross
- KT
- Kit
- OZ
- Ounce - Av
- P1
- Percent
- PC
- Piece
- PF
- Pallet (Lift)
- PK
- Package
- SP
- Shelf Package
- SZ
- Syringe
- UN
- Unit
Use UN for pill counts or for partials
- VI
- Vial
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
Numeric value of gross weight per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Numeric value of gross volume per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CC
- Cubic Centimeter
- CF
- Cubic Feet
- CI
- Cubic Inches
- CR
- Cubic Meter
- CY
- Cubic Yard
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- CM
- Centimeter
- IN
- Inch
- MM
- Millimeter
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- GM
- SSCC-18 and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
For MAN01- GM : SSCC-18 and Application Identifier
MAN02 element value needs to be all numeric with 20 characters length if MAN01 is “GM”. It should start with "00" and remaining 18 characters should specify the valid SSCC. Same SSCC cannot be used multiple times in an ASN
Date/Time Reference
To specify pertinent dates and times
Only Applicable for Single (homogeneous) SKU Full Case Cartons
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
This segment is used to communicate NDC and Lot Number Transaction Information for DSCSA.
Note:- For nonexempted RX products, NDC (Either N1 or N2 or N3 or N4 or ND are required along with LT)
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN Line Number or Original PO Line Number (ABC's preference is the
Original PO line Number)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
The Product Qualifier code used here must match the code used in the EDI 850 transaction sent by AmerisourceBergen.
- LT
- Lot Number
- MF
- Manufacturer
- N1
- National Drug Code in 4-4-2 Format
- N2
- National Drug Code in 5-3-2 Format
- N3
- National Drug Code in 5-4-1 Format
- N4
- National Drug Code in 5-4-2 Format
- N5
- National Health Related Item Code in 5-5 Format
- N6
- National Health Related Item Code in 4-6 Format
- ND
- National Drug Code (NDC)
- NH
- National Health Related Item Code
- UA
- U.P.C./EAN Case Code (2-5-5)
- UI
- U.P.C. Consumer Package Code (1-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- UX
- Universal Product Number
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
NDC Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Lot Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment can be used to communicate number of containers for Transaction Information for DSCSA.
ALL SHIPMENT MUST REFLECT THE SMALLEST DISTRIBUTION QUANTITY AND SHOULD BE REFLECTED IN THE SN1 SEGMENT.
Please send non-zero value in SN102. Please send SN104 - Qty shipped to date and SN105 - Qty ordered according to current shipment qty. This is critical for our item reconciliation
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ABC prefers to receive the Original PO Line Number as referenced in
LIN01. If it is not available the ASN Line Number may be used.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- AM
- Ampoule
- BO
- Bottle
- BX
- Box
- CA
- Case
- CH
- Container
- CT
- Carton
- DZ
- Dozen
- EA
- Each
- GS
- Gross
- KT
- Kit
- OZ
- Ounce - Av
- P1
- Percent
- PC
- Piece
- PF
- Pallet (Lift)
- PK
- Package
- SP
- Shelf Package
- SZ
- Syringe
- UN
- Unit
- VI
- Vial
Number of units shipped to date
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AM
- Ampoule
- BO
- Bottle
- BX
- Box
- CA
- Case
- CH
- Container
- CT
- Carton
- DZ
- Dozen
- EA
- Each
- GS
- Gross
- KT
- Kit
- OZ
- Ounce - Av
- P1
- Percent
- PC
- Piece
- PF
- Pallet (Lift)
- PK
- Package
- SP
- Shelf Package
- SZ
- Syringe
- UN
- Unit
- VI
- Vial
Product/Item Description
To describe a product or process in coded or free-form format
PID05 is mandatory for all nonexempted RX products
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
The description must include the prescription (Rx) drug product information such as proprietary or established name of the product, strength, dosage and container size
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Seller's Invoice Number
Date/Time Reference
To specify pertinent dates and times
For all nonexempted RX products, DTM01 & DTM02 are mandatory
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- DS
- Distributor
- MF
- Manufacturer of Goods
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67)
- 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)
- 21
- Health Industry Number (HIN)
- UL
- UCC/EAN Location Code
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- KK
- Delivery Reference
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Delivery Reference Date
A free-form description to clarify the related data elements and their content
Advance Ship Notice Reference Number
Yes/No Question
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
The purpose of the YNQ segment at the Item Level is to indicate that the Direct Purchase Statement established at the Shipment Level applies or that a Direct Purchase Statement was received.
Code indicating a Yes or No condition or response
- YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
“Y” indicates that the direct purchase statement applies or that a direct
purchase statement has been received
- Y
- Yes
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- DIR
- Product Purchased Directly
Product Purchased Directly
- RDPS
- Received Direct Purchase Statement
Received Direct Purchase Statement
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Total number of line items in the transaction set
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
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.