X12 856 Ship Notice/Manifest (4010DQSA)
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
DTM Segment differs from the BSN segment when the Vendor’s ship date is 24 hours after the ASN is created.
Code identifying purpose of transaction set
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
Sender's internal number must be unique.
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
- BSN04 is the time the shipment transaction set is created.
Format: HHMMSS
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
- 0002
- Shipment, Order, Item, Packaging
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
Number of units (pieces) of the lading commodity
Number of packages in this shipment.
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
Code specifying the method or type of transportation for the shipment
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
- TL
- Trailer (not otherwise specified)
Prefix or alphabetic part of an equipment unit's identifying number
Send if available.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Trailer Number
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
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
Code specifying type of date or time, or both date and time
- 011
- Shipped
Date expressed as CCYYMMDD
May be the same as the ASN Date, expressed as CCYYMMDD
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)
Format: HHMMSSDD
Name
To identify a party by type of organization, name, and code
Map Buyer Name and Address Loop at the Shipment Segment Level.
Use this segment to give the final destination (e.g. Store, DC) of an order that was first sent to our DC.
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)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
"006959555XXXX" where XXXX denotes the Meijer Final Destination.
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)
Name
To identify a party by type of organization, name, and code
Map Buyer Name and Address Loop at the Shipment Segment Level.
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)
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)
Name
To identify a party by type of organization, name, and code
Map Ship From Name and Address Loop at the Shipment Segment Level.
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)
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.
It is important that we receive “State” because it is used in conjunction with the DTM02 to calculate an arrival date for shipment.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Name
To identify a party by type of organization, name, and code
Map Ship To Name and Address Loop at the Shipment Segment Level.
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)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 11
- Drug Enforcement Administration (DEA)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
With qualifier 9 use "006959555XXXX" where XXXX denotes the Meijer Distribution Center, Store or Central Fill Unit 463.
With qualifier 92 use "0XXX" where XXX denotes the Meijer Distribution Center, Store or Central Fill Unit 463
With qualifier 11 use "PT0185276" where PT0185276 denotes Meijer DEA ID for DC90 (used for CSOS orders) or use the DEA ID for Meijer Store or Unit 463 Central Fill.
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.
It is important that we receive “State” because it is used in conjunction with the DTM02 to calculate an arrival date for shipment.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Direct Purchase Statement
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
Reference to manufacturer direct purchase statement at the shipment segment level.
Required for Exclusive Distributor and Indirect Distributor. Not required for Original 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
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- DPS
- Direct Purchase Statement
Transaction Statement
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
Seller transaction statement at the shipment segment level.
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
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- TS
- Transaction Statement
If multiple purchase orders are being filled on this shipment, send an HL (order level) loop for each purchase order on the shipment.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- 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
Meijer PO Number (9 Digits)
This HL loop is used to describe a vendor master shipping carton.
Required if using 128 labels.
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Map Mandatory NDC Number and Optional Lot Number at the Item Details Level.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- N4
- National Drug Code in 5-4-2 Format
- ND
- National Drug Code (NDC)
Identifying number for a product or service
(NDC) (5-4-2 Format, No Hyphens)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.
UCC12 (12 digits UPC number, No Hyphens)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VC
- Vendor's (Seller's) Catalog Number
- VN
- Vendor's (Seller's) Item Number
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)
- LT
- Lot Number
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Map Container Type and Number of Containers at the Item Detail Level.
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.
Other values defaulted to CA.
If the SN103 unit of measure is not ‘EA’ we assume the SN103 ship quantity needs to be multiplied by the pack size quantity which is sent in the PO4 segment, so the ASN will be rejected if there is no PO4 segment.
- CA
- Case
- DZ
- Dozen
- EA
- Each
Code specifying the action taken by the seller on a line item requested by the buyer
- AC
- Item Accepted and Shipped
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Required for all products listed in the LIN Segment.
Required if unit of measure in not EA.
To define the case pack being shipped.
The number of inner containers, or number of eaches if there are no inner containers, per outer container
No. of inner packs, or No. of EA., if there are no inner packs.
The number of eaches per inner container
No. of EA. within an inner pack.
Product/Item Description
To describe a product or process in coded or free-form format
Map Prescription name, Strength and Dosage at the Item Detail Level.
Example: PIDF***GABAPENT CAP 100MG 100 NSTAR~
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
Description must include product Name, dosage form, strength, and container size.
Example: Ibuprofen Tablets 300 MG 70
Required for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer
Name
To identify a party by type of organization, name, and code
Map the Transactional History at the Item Detail Level.
Address Information
To specify the location of the named party
Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer
Geographic Location
To specify the geographic place of the named party
Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer
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)
Yes/No Question
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
Reference to manufacturer direct purchase statement at the shipment segment level.
Required as noted below for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer.
Code indicating a condition
- 3E
- Letter of Certification
- CX
- Certification Status
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
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- DIR
- Product Purchased Directly
- RDPS
- Received Direct Purchase Statement
Required if using 128 labels.
This HL loop is used to describe a vendor master shipping carton.
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of inner containers, or number of eaches if there are no inner containers, per outer container
No. of inner packs, or No. of EA., if there are no inner packs .
Numeric value of gross weight per pack
Weight of master shipping carton in #'s.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
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.
- IN
- Inch
The number of eaches per inner container
No. of EA. within an inner pack.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
MAN01 & MAN02 must comply to the standards established by the Uniform Code Council (UCC). We must receive this segment in order to receive merchandise by scanning.
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.
If MAN01 is "GM" then MAN02 must be 20 digits and unique, but need not be sequential. If MAN01 is "UC" then MAN02 must be 12 or 14 digits.
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Shipping Container Identifier
This HL loop is used to describe a vendor master shipping carton.
Required if using 128 labels.
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 Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of inner containers, or number of eaches if there are no inner containers, per outer container
No. of inner packs, or No. of EA., if there are no inner packs.
Numeric value of gross weight per pack
Weight of master shipping carton in #'s.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
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.
- IN
- Inch
The number of eaches per inner container
No. of EA. within an inner pack.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
MAN01 & MAN02 must comply to the standards established by the Uniform Code Council (UCC). We must receive this segment in order to receive merchandise by scanning.
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.
If MAN01 is "GM" then MAN02 must be 20 digits and unique, but need not be sequential. If MAN01 is "UC" then MAN02 must be 12 or 14 digits.
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Shipping Container Identifier
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
Map Mandatory NDC Number and Optional Lot Number at the Item Details Level.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- N4
- National Drug Code in 5-4-2 Format
- ND
- National Drug Code (NDC)
Identifying number for a product or service
(NDC) (5-4-2 Format, No Hyphens)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
The product/service ID (UPC Number) or the NDC sent must match what was received in the purchase order data.
UCC12 (12 digits UPC number, No Hyphens)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VC
- Vendor's (Seller's) Catalog Number
- VN
- Vendor's (Seller's) Item Number
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)
- LT
- Lot Number
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Map Container Type and Number of Containers at the Item Detail Level.
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.
Other values defaulted to CA.
If the SN103 unit of measure is not ‘EA’ we assume the SN103 ship quantity needs to be multiplied by the pack size quantity which is sent in the PO4 segment, so the ASN will be rejected if there is no PO4 segment.
- CA
- Case
- DZ
- Dozen
- EA
- Each
Code specifying the action taken by the seller on a line item requested by the buyer
- AC
- Item Accepted and Shipped
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
To define the case pack being shipped.
Required for all products listed in the LIN Segment.
Required if unit of measure is not EA.
The number of inner containers, or number of eaches if there are no inner containers, per outer container
No. of inner pks., or No. of EA., if there are no inner pks.
The number of eaches per inner container
No. of EA. within an inner pack.
Product/Item Description
To describe a product or process in coded or free-form format
Map Prescription name, Strength and Dosage at the Item Detail Level.
Example: PIDF***GABAPENT CAP 100MG 100 NSTAR~
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
Description must include product Name, dosage form, strength, and container size.
Example: Ibuprofen Tablets 300 MG 70
Required for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer
Name
To identify a party by type of organization, name, and code
Map the Transactional History at the Item Detail Level.
Address Information
To specify the location of the named party
Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer
Geographic Location
To specify the geographic place of the named party
Optional for Exclusive Distributor, Indirect Distributor and Original Manufacturer
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)
Yes/No Question
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
Reference to manufacturer direct purchase statement at the shipment segment level.
Required as noted below for Exclusive Distributor and Indirect Distributor. Not required for Original Manufacturer.
Code indicating a condition
- 3E
- Letter of Certification
- CX
- Certification Status
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
Code identifying a specific industry code list
- 99
- Purpose Code
Code indicating a code from a specific industry code list
- DIR
- Product Purchased Directly
- RDPS
- 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
Count of all HL Segments (No.)
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.