X12 856 Ship Notice/Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 05
- Replace
A unique control number assigned by the original shipper to identify a specific 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
To specify pertinent dates and times
At least one of these dates is REQUIRED. Shipped Date is preferred.
Code specifying type of date or time, or both date and time
- 011
- Shipped
- 017
- Estimated Delivery
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
At least one of these dates is REQUIRED. Shipped Date is preferred.
- AS
- Alaska Standard Time
- CS
- Central Standard Time
- ES
- Eastern Standard Time
- HS
- Hawaii-Aleutian Standard Time
- MS
- Mountain Standard Time
- PS
- Pacific Standard Time
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN
- Carton
- PLT
- Pallet
- 25
- Corrugated or Solid
- 90
- Standard
- 94
- Wood
Number of units (pieces) of the lading commodity
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Trading Partner should send either SCAC or 'FSTL' for Will Call in TD503. TD05 for Carrier Name or Description is highly recommended.
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 identifying a party or other code
Use valid SCAC code. If Will Call, use 'FSTL'
Code specifying the method or type of transportation for the shipment
- 6
- Military Official Mail
- 7
- A
- Air
- AE
- Air Express
- AF
- Air Freight
- B
- Barge
- D
- Parcel Post
- H
- Customer Pickup
- M
- Motor (Common Carrier)
- P
- Private Carrier
- R
- Rail
- SR
- Supplier Truck
- VE
- Vessel, Ocean
- ZZ
- Mutually defined
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Description or Name
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
This segment is REQUIRED if any material contained in the shipment has been classified as hazardous and/or requires special handling.
Code specifying special transportation handling instructions
Code which qualifies the Hazardous Material Class Code (209)
Code specifying the kind of hazard for a material
A free-form description to clarify the related data elements and their content
Code indicating a Yes or No condition or response
- TD405 identifies if a Material Safety Data Sheet (MSDS) exists for this product. A "Y" indicates an MSDS exists for this product; an "N" indicates an MSDS does not exist for this product.
Reference Identification
To specify identifying information
User Note 1:
Qual BM and CN - BOL and Carrier Pro Number REQUIRED for LT or Truck Load Shipments.
User Note 2:
Qual CN - For small package Carrier Shipments (UPS or FedEx) send one of the Carrier's tracking numbers using qualifier CN.
User Note 3:
Qual VR - REQUIRED Return Fastenal-assigned Vendor ID sent to you on the 850/PO document in N104 where
N101 = VN (Vendor Identification Code)
Example: 0000139999
You may receive an error message similar to VENDOR ID SENT IN REF02 WHERE REF01 = VR IS NOT CORRECT if the value fails Fastenal validation. If this occurs, please correct your processes to send correct information on future transmissions.
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
Use for Carrier's Tracking Number
- VR
- Vendor ID Number
Use for Fastenal-assigned Vendor ID sent to you on the 850/PO in N104 where
N101 = VN
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
For REF01 = VR, use Fastenal assigned Vendor ID REQUIRED
For REF01 = BM, use Bill of Lading
For REF01 = CN, use Carrier Reference Number
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- PB
- Customer Pick-up/Backhaul
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
User Note 1: 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.
All Item Level information on document must have Shipped From the address specified in the N1 Loop. If multiple
Ship From locations are required for a shipment, there should be multiple 856 documents sent so each can refer
to one Ship From location.
You may receive an error notice stating VENDOR LOCATION IS NOT CORRECT if this value fails Fastenal
validation, and we ask that you correct your process for future transmissions.
Name
To identify a party by type of organization, name, and code
Ship From (SF) is REQUIRED to indicate the Vender Location the shipment was actually shipped from.
On Ship From, the N104 value must be the 10-digit Fastenal-assigned Ship From Location Id.
Example: 0000000001
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Ship From (SF) REQUIRED to provide the Postal Code (N303) the material was shipped from.
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)
Code identifying the country
Use standard 3-char country codes
Examples:
USA = United States of America
MEX = Mexico
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DK
- Dock Number
- LF
- Assembly Line Feed Location
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
User Note 2:
Ship To (ST) is REQUIRED to indicate the Fastenal Destination of the Shipment, either at the Shipment Level (this level) or at the Purchase Order level. If sending ASN containing multiple Store/Branch Orders (Will Call -Fastenal Truck Pickup) send Ship To at Order Level. On Ship To, the N104 value must be the 4-char Fastenal Location Code sent on the 850/PO in N104 where N101 = ST.
Example:s
MHUB
OTWI
You may receive an error notification of BUSINESS UNIT IS NOT VALID if the value fails Fastenal validation, and
we ask that you correct your process for future transmissions
Name
To identify a party by type of organization, name, and code
Ship From (SF) is REQUIRED to indicate the Vender Location the shipment was actually shipped from.
On Ship From, the N104 value must be the 10-digit Fastenal-assigned Ship From Location Id.
Example: 0000000001
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Ship From (SF) REQUIRED to provide the Postal Code (N303) the material was shipped from.
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)
Code identifying the country
Use standard 3-char country codes
Examples:
USA = United States of America
MEX = Mexico
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DK
- Dock Number
- LF
- Assembly Line Feed Location
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack
(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton
contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element
357 = "12"; Data element 355 = "OZ".
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
User Note 1:
Suppliers are required to send a unique SSCC-18 number at the TARE level for each pallet shipped, when the
shipment meets the following situations described in the Fastenal Standard Operating Procedures revision 4:
• Full pallet of one part on one PO (pg 25)
• Full pallet of one PO with mixed parts (pg 25)
• Full pallet of mixed POs for same destination (pg 26)
Additionally, Suppliers are required to send a unique SSCC-18 number at the PACK level for each master carton
shipped, when the shipment meets the following situations described in the Fastenal Standard Operating
Procedures revision 4:
• Full pallet of one PO with mixed parts (pg 25)
• Full pallet of mixed POs for same destination (pg 26)
• Small parcel, mixed POs for different destinations (pg 27)
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Purchase Order ID returned must match 850/PO BEG03.
Examples:
210012345
OTWI12345
You may receive an error message similar to PURCHASE ORDER NUMBER IS NOT A FASTENAL PURCHASE ORDER NUMBER if the value fails Fastenal validation. We ask that you correct your processes for future
transmissions to send correct information.
Identifying number for Purchase Order assigned by the orderer/purchaser
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Date expressed as CCYYMMDD
- PRF04 is the date assigned by the purchaser to purchase order.
Ship To (ST) is REQUIRED either at the Shipment Level or the Purchase Order level. If sending ASN containing multiple Store/Branch orders (Will Call - Fastenal Truck Pick-up), send Ship To at this (ORDER) level.
Name
To identify a party by type of organization, name, and code
User Note 1:
Ship To (ST) is REQUIRED either at the Shipment Level or the Purchase Order level. If sending ASN containing multiple Store/Branch orders (Will Call - Fastenal Truck Pick-up), send Ship To at this (ORDER) level.
User Note 2:
Qual ST - Please return the 4-Char Fastenal Location code sent on the 850/PO in the N104 where N101 = ST.
Examples:
MHUB
OTWI
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
If Fastenal 4-Char Fastenal location is supplied in N104, the N4 segment is not required, but is recommended.
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)
Code identifying the country
Use standard 3-char country codes
Examples:
USA = United States of America
MEX = Mexico
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- CM
- Centimeter
- FT
- Foot
- IN
- Inch
- MR
- Meter
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Code specifying special transportation handling instructions
Code which qualifies the Hazardous Material Class Code (209)
Code specifying the kind of hazard for a material
A free-form description to clarify the related data elements and their content
Code indicating a Yes or No condition or response
- TD405 identifies if a Material Safety Data Sheet (MSDS) exists for this product. A "Y" indicates an MSDS exists for this product; an "N" indicates an MSDS does not exist for this product.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
User Note 1:
Suppliers are required to send a unique SSCC-18 number at the TARE level for each pallet shipped, when the
shipment meets the following situations described in the Fastenal Standard Operating Procedures revision 4:
• Full pallet of one part on one PO (pg 25)
• Full pallet of one PO with mixed parts (pg 25)
• Full pallet of mixed POs for same destination (pg 26)
Additionally, Suppliers are required to send a unique SSCC-18 number at the PACK level for each master carton
shipped, when the shipment meets the following situations described in the Fastenal Standard Operating
Procedures revision 4:
• Full pallet of one PO with mixed parts (pg 25)
• Full pallet of mixed POs for same destination (pg 26)
• Small parcel, mixed POs for different destinations (pg 27)
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Code specifying the application or source of Marks and Numbers (87)
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
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
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The line number must match what was sent on the 850/PO in PO101. You may receive error messages such as THE LINE NUMBER SENT DOES NOT MATCH THE LINE NUMBER FOR THE ASSOCIATED FASTENAL PURCHASE ORDER/PART NUMBER COMBINATION. The messages indicate the value failed Fastenal validation and we ask that you correct your process to send valid information on future submissions
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
User Note 1: Buyer's (Fastenal) Part Number must match what was sent on the 850/PO PO107
User Note 2: You may receive error messages such as BUYER PART NUMBER DOES NOT MATCH PURCHASE ORDER BUYER PART NUMBER or BUYER PART NUMBER INCORRECT BUT FIXED. The messages indicate the value failed Fastenal validation and we ask that you correct your process to send valid information on future transmissions.
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)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CH
- Country of Origin Code
Identifying number for a product or service
User Note 1: Use standard 3 character country code.
Examples:
USA = United States of America
MEX = Mexico
User Note 2: You may receive Error messages such as COUNTRY OF ORIGIN IS NOT A VALID COUNTRY if the value fails Fastenal validation. We ask that you correct your processes for future transmissions.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
User Note 1: You may receive an error message similar to QUANTITY IS GREATER THAN REMAINING QUANTITY TO BE SHIPPED if the value fails Fastenal validation. If this happens, please modify your processes to send correct information on future transmissions
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.
User Note 1: Must match what was sent on 850/PO PO103. Fastenal may send any valid AIAG code. You may receive an error message similar to UNIT OF MEASURE IS NOT A VALID OR ACCEPTABLE CODE if the value fails Fastenal validation. If this happens, please correct your processes to send correct information on future transmissions.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
Reference Identification
To specify identifying information
User Note 1:
Please send an iteration of the reference loop for each code that you have a value for. Use L1 if you wish to pass a comment at the item level.
It is VERY important that Lot Number (LT) is sent if applicable!
Code qualifying the Reference Identification
- 6W
- Sequence Number
- HC
- Heat Code
- L1
- Letters or Notes
- LT
- Lot Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Dates are required for perishable products.
You may receive an error message similar to EXPIRATION DATE IS INVALID OR OCCURS IN THE PAST if the value fails Fastenal validation. If this occurs, please correct your processes to send correct information in future transmissions.
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
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.