X12 856 Advanced Shipment Notification (ASN) for Direct Store Delivery (DSD)
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
Only one Walgreens Purchase Order number will be accepted on each Ship Notice.
Code identifying purpose of transaction set
When sending a code of '00' in the BSN01, the BSN02 must be unique. The code of '05' is used when sending a corrected ASN with the same BSN02 as previously transmitted.
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
This number cannot contain dashes, spaces, or any other special characters
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
This field should contain ASN creation 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.
This field should contain ASN creation time
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
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
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.
Reference Identification Invoice Number
To specify identifying information
Code qualifying the Reference Identification
- IK
- Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
If an Invoice Number is sent in the REF02, them a DTM01 with a "003" is required (Invoice Date).
A free-form description to clarify the related data elements and their content
Marketing Vendor Name.
Reference Identification Vendor ID Number
To specify identifying information
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This field must contain your Legacy 6-digit Walgreens Marketing Vendor Number or 10-digit SAP Vendor Number, as communicated to you on the Purchase Order. Note: This is NOT the same as your Walgreens Accounts Payable Number, which may be up to 9 digits in length.
This value corresponds to Zone F on the Shipping Labe
A free-form description to clarify the related data elements and their content
Marketing Vendor Name. Corresponds to Zone A on the Shipping Label .
Date/Time Reference Current Schedule Delivery Date
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 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)
Date/Time Reference Invoice Date
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 003
- Invoice
Date expressed as CCYYMMDD
If an Invoice Date is sent in the DTM02, then the REF01 element with an "IK" qualifier and the REF02 element with an Invoice Number is required.
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)
Date/Time Reference Shipped
To specify pertinent dates and times
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)
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)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This must be either the Walgreens Legacy 5-character store number or 4-character SAP Site number, as communicated to you on the Purchase Order.
Corresponding to Zone H on the Shipping Label
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Only one Walgreens Purchase Order number will be accepted on each Ship Notice.
Identifying number for Purchase Order assigned by the orderer/purchaser
This must be either the Walgreens Legacy 6-digit store-level PO Number or the 10-digit SAP Purchase Order number, as communicated to you on the Purchase Order. Use of a value not from either the Walgreens Legacy environment (SIMS) or future SAP system will result in processing issues and may affect proper and timely payment for this transaction. The future Walgreens SAP back-end environment will only support maximum PO length of 10 characters - items sent with values beyond 10 characters will fail in the future Walgreens SAP Environment.
Corresponds to Zone E on the Shipping Label
Date expressed as CCYYMMDD
- PRF04 is the date assigned by the purchaser to purchase order.
This should be the Purchase Order date sent in the BEG05 of the 850 PO document.
Required by Walgreens if marking data is sent at Pack level.
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Required by Walgreens if marking data is sent at Pack level. Walgreens allows only one marking value per segment.
When shipping products to Walgreens Stores, each carton must have a UCC-128 shipping label applied, containing a unique SSCC-18 number that matches the value supplied in the MAN02 field.
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
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.
If used, This corresponds to Zone I in the Shipping Label.
Either the Tare (Pallet) loop or the Pack (Case) loop is required.
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
Walgreens requires you to send the original Purchase Order line number in both the LIN01 and SN101 elements.
The ordering number qualifier (LIN02) and ordering number (LIN03) must match the original ordering number qualifier (PO106) and ordering number (PO107) sent in the Purchase Order.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Failure to use the assigned PO line number from either the Walgreens Legacy system (SIMS) or future SAP system will result in processing errors.
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 Primary Item ordering qualifier must be sent in this position. This value is always referenced from the ordering qualifier in your current catalog.
Note: This is the ordering number qualifier sent in the PO106 field of the Purchase Order
- EI
- Expense Identifier
- 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)
Identifying number for a product or service
The primary Item ordering identifier must be sent in this position. This value is always referenced from the ordering number in your current catalog.
Note: This is the ordering number sent in the PO107 field of the Purchase Order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
This element is not required/needed for non-Rx transactions.
- EN
- European Article Number (EAN) (2-5-5-1)
- LT
- Lot Number
- ND
- National Drug Code (NDC)
- 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)
Identifying number for a product or service
This element is not required/needed for non-Rx transactions
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- MG
- Manufacturer's Part Number
- ND
- National Drug Code (NDC)
- 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)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
This element is not required/needed for non-Rx transactions. For pharmaceutical products, you must supply the 11-digit NDC (5-4-2 format) of the product.
Note: This number cannot contain dashes, spaces, or any other special characters
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
This element is not required/needed for non-Rx transactions.
- EN
- European Article Number (EAN) (2-5-5-1)
- MG
- Manufacturer's Part Number
- ND
- National Drug Code (NDC)
- 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)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
This element is not required/needed for non-Rx transactions
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- MD
- Method of Delivery Code
- MG
- Manufacturer's Part Number
- ND
- National Drug Code (NDC)
- 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)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
If using MD indicator, follow with "drop ship" verbiage in LIN-11.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Walgreens requires you to send the original Purchase Order line number in both the LIN01 and SN101 elements.
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Failure to use the assigned PO line number from either the Walgreens Legacy system (SIMS) or future SAP system will result in processing errors
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
2 decimal positions will be accepted.
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.
- EA
- Each
This UOM measure (EA) is the Mandatory qualifier to be used for vendors on the Three-Way Match Program/Invoice Reconciliation in the Legacy Walgreens environment. Other values, such as "CA," may become available after Walgreens has finished its SAP deployment across all internal systems.
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
- EA
- Each
This UOM measure (EA) is the Mandatory qualifier to be used for vendors on the Three-Way Match Program/Invoice Reconciliation in the Legacy Walgreens environment. Other values, such as "CA," may become available after Walgreens has finished its SAP deployment across all internal systems.
Code specifying the action taken by the seller on a line item requested by the buyer
- AC
- Item Accepted and Shipped
- BP
- Item Accepted - Partial Shipment, Balance Backordered
- ID
- Item Deleted
- IS
- Item Accepted - Substitution Made
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
The item description must be supplied using up to a maximum of 50 characters. Walgreens requests that the Unit of Measure and Quantity be included in the item description
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
this value is the accumulation of the number of HL segments.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
This is the Hash total of the SN102
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.