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
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
A duplicate of a successful ASN received, with purpose code 00 (original), will result in a failure.
If a correction is needed to a successfully received ASN, the replacement ASN must include the "05" purpose code.
An ASN with purpose code "05" (replacement) applies to the entire ASN. This is a complete replacement, not an adjustment.
An ASN replacement will not be accepted after the scheduled delivery date.
An ASN replacement will not be accepted after physical delivery.
- 00
- Original
- 05
- Replace
A unique control number assigned by the original shipper to identify a specific shipment
ASN number must be associated to the entire shipment and must be unique for at least 180 days after shipment.
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.
Date/Time Reference Current Schedule Delivery
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 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)
Detail
There must be only one Shipment HL per 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.
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 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
- CTN
- Carton
- MXD
- Mixed
- PLT
- Pallet
- UNT
- Unit
Number of units (pieces) of the lading commodity
This value represents the number of handling units included in the shipment. A handling unit is the largest container that will be moved as a unit - pallet, carton, or loose line item.
For example: if a shipment has all line items containerized on pallets, only the pallets would be counted as handling units. Please see the AAP Supplier EDI Barcode Shipping Label guide for further clarification.
When pallets are shipped, each pallet must contain two copies of the same License Plate (LP) with a scannable barcode. (See AAP Supplier EDI Barcode Shipping Label guide for proper placement).
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
- B
- Origin/Delivery Carrier (Any Mode)
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
Reference Identification Bill of Lading Number
To specify identifying information
One variant is required.
The BOL/Reference/Tracking number must be unique for at least 180 days.
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference Identification Carrier's Reference Number (PRO/Invoice)
To specify identifying information
One variant is required.
The BOL/Reference/Tracking number must be unique for at least 180 days.
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference Identification Tracking Number
To specify identifying information
One variant is required.
The BOL/Reference/Tracking number must be unique for at least 180 days.
Code qualifying the Reference Identification
- 2I
- Tracking Number
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
If N101= "SF" or N101= "Z7" identifiers are received on the purchase order or the purchase order change if one exists, they are required on the ASN.
- ST
- Ship To
One iteration where N101 = "ST" and N104 = a DC #, store # or web store # is required.
- VN
- Vendor
One iteration where N101 = "VN" and N104 = the Vendor ID provided in the PO is required.
- Z7
- Mark-for Party
If N101= "SF" or N101= "Z7" identifiers are received on the purchase order or the purchase order change if one exists, they are required on the ASN.
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 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.
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)
Order is a required HL and there must be one for each PO with product included in 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
This field must contain the Buyer's PO number which can be found:
For EDI 850 Purchase Orders, in the BEG03 element.
For manual orders (phone or email) the PO number must be obtained from the buyer and provided in the PRF01.
If more than one PO is on the shipment, all the POs must have the same ship-to location.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
When an EDI 860 PO Change Request has been issued, the release number can be found in the BCH04.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- PK
- Packing List Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The Pack Slip number should be a different value than the header REF tracking/BOL number and the BSN02 Shipment ID (ASN Number).
(SOI) This format is valid only for loose item shipments (An item shipped loose or in a non-standard container, such as a drum) When used it must contain a MAN segment at item level, denoting the UCC128 license plate number assigned.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
If all product in the shipment is resting on a pallet, the Pack HL is not required and should not be sent. If no pallet exists for some or all of the product under a PO, the pack is the highest handling unit for that product so the HLP is required and the HLP label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
This segment is used for carton (pack) shipment only. Do not use for pallet shipments.
Uses the HLP:MAN when the highest handling unit is a carton (no pallet).
The HLP:MAN barcode can repeat in the same 856 message when more than one order is loaded in the same carton.
When the HLT:MAN is absent and the HLP:MAN is used, the HLI:MAN will be ignored and should not be sent. If the HLT and HLP loops are not used, a HLI:MAN is required.
Each Purchase Order and Pack ID combination must be listed only once per ASN.
Example:
HL83P
MANAI*00106862260024599671
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.
The License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Carton will be used for receiving shipments.
This LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
Tare is the highest handling unit if product in the shipment is resting on a pallet. There must be one tare HL for each pallet nested under the appropriate Order HL and the HLT label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
Use the HLT:MAN when the highest handling unit is a pallet.
The HLT:MAN barcode number can repeat in the same 856 message when more than one order is loaded on the same pallet.
When the HLT:MAN is used, any child level HLP:MAN and HLI:MAN segments will be ignored. If the HLT loop is not used a HLP:MAN or HLI:MAN is required.
Each Purchase Order and pallet ID combination must be listed only once per ASN.
Example:
HL83T
MANAI*00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Pallet will be used for receiving shipments.
The LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
(SOTPI) Only the highest handling unit level (Tare, in this scenario) will be used by AAP. For that reason, this format is not recommended and will be removed in future spec versions.
If all product in the shipment is resting on a pallet, the Pack HL is not required and should not be sent. If no pallet exists for some or all of the product under a PO, the pack is the highest handling unit for that product so the HLP is required and the HLP label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
This segment is used for carton (pack) shipment only. Do not use for pallet shipments.
Uses the HLP:MAN when the highest handling unit is a carton (no pallet).
The HLP:MAN barcode can repeat in the same 856 message when more than one order is loaded in the same carton.
When the HLT:MAN is absent and the HLP:MAN is used, the HLI:MAN will be ignored and should not be sent. If the HLT and HLP loops are not used, a HLI:MAN is required.
Each Purchase Order and Pack ID combination must be listed only once per ASN.
Example:
HL83P
MANAI*00106862260024599671
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
Recommended
- 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.
The License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Carton will be used for receiving shipments.
This LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
Equipment HL is used only to identify container IDs for ocean shipments.
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.
- E
- Transportation Equipment
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 (Equipment)
To specify transportation details relating to the equipment used by the carrier
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
- SN
- Seal Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The first seal number should be provided in the TD3 segment. Use the REF segment for additional seal numbers if needed.
Order is a required HL and there must be one for each PO with product included in 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
This field must contain the Buyer's PO number which can be found:
For EDI 850 Purchase Orders, in the BEG03 element.
For manual orders (phone or email) the PO number must be obtained from the buyer and provided in the PRF01.
If more than one PO is on the shipment, all the POs must have the same ship-to location.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
When an EDI 860 PO Change Request has been issued, the release number can be found in the BCH04.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- PK
- Packing List Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The Pack Slip number should be a different value than the header REF tracking/BOL number and the BSN02 Shipment ID (ASN Number).
(SEOI) This format is valid only for loose item shipments (An item shipped loose or in a non-standard container, such as a drum) When used it must contain a MAN segment at item level denoting the UCC128 license plate number assigned.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
If all product in the shipment is resting on a pallet, the Pack HL is not required and should not be sent. If no pallet exists for some or all of the product under a PO, the pack is the highest handling unit for that product so the HLP is required and the HLP label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
This segment is used for carton (pack) shipment only. Do not use for pallet shipments.
Uses the HLP:MAN when the highest handling unit is a carton (no pallet).
The HLP:MAN barcode can repeat in the same 856 message when more than one order is loaded in the same carton.
When the HLT:MAN is absent and the HLP:MAN is used, the HLI:MAN will be ignored and should not be sent. If the HLT and HLP loops are not used, a HLI:MAN is required.
Each Purchase Order and Pack ID combination must be listed only once per ASN.
Example:
HL83P
MANAI*00106862260024599671
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
Recommended
- 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.
The License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Carton will be used for receiving shipments.
This LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
Tare is the highest handling unit if product in the shipment is resting on a pallet. There must be one tare HL for each pallet nested under the appropriate Order HL and the HLT label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
Use the HLT:MAN when the highest handling unit is a pallet.
The HLT:MAN barcode number can repeat in the same 856 message when more than one order is loaded on the same pallet.
When the HLT:MAN is used, any child level HLP:MAN and HLI:MAN segments will be ignored. If the HLT loop is not used a HLP:MAN or HLI:MAN is required.
Each Purchase Order and pallet ID combination must be listed only once per ASN.
Example:
HL83T
MANAI*00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Pallet will be used for receiving shipments.
The LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
(SEOTPI) Only the highest handling unit level (Tare, in this scenario) will be used by AAP. For that reason, this format is not recommended and will be removed in future spec versions.
If all product in the shipment is resting on a pallet, the Pack HL is not required and should not be sent. If no pallet exists for some or all of the product under a PO, the pack is the highest handling unit for that product so the HLP is required and the HLP label ID will be used for receiving.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination. For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
This segment is used for carton (pack) shipment only. Do not use for pallet shipments.
Uses the HLP:MAN when the highest handling unit is a carton (no pallet).
The HLP:MAN barcode can repeat in the same 856 message when more than one order is loaded in the same carton.
When the HLT:MAN is absent and the HLP:MAN is used, the HLI:MAN will be ignored and should not be sent. If the HLT and HLP loops are not used, a HLI:MAN is required.
Each Purchase Order and Pack ID combination must be listed only once per ASN.
Example:
HL83P
MANAI*00106862260024599671
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
Recommended
- 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.
The License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading zeros.
The scannable barcode LP number on the Carton will be used for receiving shipments.
This LP number must be unique for at least 180 days after shipment.
Each unique SKU/Item within the Tare or Pack HL (whichever is the highest handling unit) must be listed only once per handling unit and order number combination.
For example, an item that is in multiple cartons and those cartons are on a pallet, must be listed only once. In this scenario, the ASN should include only the tare and not the pack level for this item.
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
A buyer part number (LIN03) must not repeat within a purchase order loop using the same pallet/pack level barcode label id.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
ASN 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Item Detail (Shipment)
To specify line-item detail relative to shipment
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
ASN Line Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
AAP requires an integer value in this quantity element, unless a decimal value was present on the purchase order line item quantity.
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.
While any valid X12 code may be sent on a Purchase Order or Purchase Order Change if one exists, AAP typically purchases in "EA" Each UOM.
The UOM on the ASN must match the Purchase Order or Purchase Order Change if one exists.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
This segment is used for loose line items only. Do not use for pallet or pack shipments.
If the HLT: and HLP loops are not used, use the HLI:MAN when the handling unit is a loose line item (not in a container).
This could be an oversized part such as a drum. In which case the label is applied directly. The scannable barcode LP number on the loose item will be used for receiving shipments.
ASN item level structure example:
HL83I
LIN1BP9090009VPCP7527UP021467075271
SN1128EA28
MANAI00106862260024599671
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
Recommended
- 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.
This License Plate (LP) number should be a unique 20-digit identifier for the handling unit, in human-readable text, with a field length of 18 digits plus 2 leading 0's.
The scannable barcode LP number on the item will be used for receiving.
The LP number must be unique for at least 180 days after shipment.
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
When CTT is present, this must be the count of LIN segments contained in the ASN.
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 total of all quantities on the shipment.
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
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
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.