X12 856 ASN - Advance Ship Notice
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.
USAGE NOTES:
- The ASN must be sent as soon as the shipment is picked up from the vendor’s warehouse.
- A separate ASN must be provided for each bill of lading. A separate BOL is required for each
shipment. - The UCC128 serial container marking numbers cannot be re-used within a 12-month period.
- Small package carrier (FedEx) is one 856 per carton.
- ~ Segment
- * Element
- > Component
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 004030VICS
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a 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
- 07
- Duplicate
Time expressed in 24-hour clock time: HHMM, or HHMMSS,
or HHMMSSD, or HHMMSSDD
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0001
- Pick and Pack Structure
Detail
To identify dependencies and the content of hierarchically related groups of segments.
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 weight and quantity.
Code identifying the type of packaging; Part 1: Packaging
Form, Part 2: Packaging Material
- CTN
- Carton
- 25
- Corrugated or Solid
Numeric value of weight
(No decimals, round up)
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 routing.
Code designating the system/method of code structure
used for Identification Code (67)
- 2
- SCAC
Code specifying the method or type of transportation for
the shipment
- A
- Air
- C
- Consolidation
- E
- Expedited Truck
- M
- Motor (Common Carrier)
- U
- Private Parcel Service
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
- Ship Complete
- PR
- Partial Shipment
Reference Identification
To specify identifying information
Bill of Lading Number must be unique for each shipment. Duplicate Bill of Lading numbers will be rejected.
Date/Time Reference
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment.
Code identifying payment terms for transportation charges
- CC
- Collect
- PP
- Prepaid by Vendor
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
- ST
- Ship to, Bealls DC or Store Number for a direct to store order
Code designating the system/method of code structure used for Identification Code (67)
- Send code value 92 (Assigned by Buyer) when N101 = ST.
- Send code value 1 (DUNS#) when N101=SF.
- 1
- D-U-N-S Number, Dun & Bradstreet
- 92
- Assigned by Buyer
Code identifying a party or other code
- Send code value 050 (Bealls DC ID) or 3-character Bealls Store Number when N101 = ST.
- Send vendor’s DUNS# when N101 = SF.
Additional Name Information
To specify additional names or those longer than 35 characters in length.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Mandatory when N101 = SF.
Code (Standard State/Province) as defined by appropriate government agency
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
To identify dependencies and the content of hierarchically related groups of segments.
A new order level must be provided for each PO/store occurrence within the Bill of Lading/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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Product/Item Description
To describe a product or process in coded or free-form format.
Bealls requires suppliers to indicate compliance with the Fair Labor Standards Act in the PID segment.
Code indicating the format of a description
- S
- Structured
Code identifying the agency assigning the code values
- VI
- VICS
A code from an industry code list which provides specific
data about a product characteristic.
- FL
- Compliant with Fair Labor Standards Act
Carrier Details (Quantity and Weight)
To specify weight and quantity.
Reference Identification
To specify identifying information
Mandatory for Bealls Department Number
Code qualifying the Reference Identification
- DP
- Bealls Department Number
- IV
- Vendor's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- Send Invoice number when REF01 = IV.
- Send Bealls Department Number when REF01 = DP.
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
- Bealls Store Number
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer
Code identifying a party or other code Bealls 3-character Store Number
To identify dependencies and the content of hierarchically related groups of segments
A new pack level must be provided for each carton within the PO/store occurrence.
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
To identify dependencies and the content of hierarchically related groups of segments.
A new item level must be provided for each UPC/SKU within the pack occurrence.
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
Item Detail
To specify the quantities associated with the item identified in the LIN at the item level.
Numeric value (No decimals) of units shipped by UPC/SKU
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken.
- EA
- Each
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set.
Total number of line items in the transaction set
The number of HL segments present in the transaction
set
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
This will be the same number as is in the ST segment
(ST02) for the 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.