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
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
- The Honda supplier creates this number. For an original ASN (BSN01=00), the ASN Number cannot be repeated within 18 months.
- This number must consist of characters from the ranges 0 thru 9, A thru Z, or a thru z.
- For shipments crossing borders (US / Canada / México) the relationship between the ASN# and the BOL# must be one to one. (See "ASN and BOL
Relationship" at the end of the chapter for further clarification.)
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.
HHMM Format
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 011
- Shipped
Date expressed as CCYYMMDD
This is the Actual Ship Date the trailer was sent to Honda.
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)
This is the Actual Ship Time format HHMM
Midnight should be represented by a time of 00:00, not 24:00
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
This segment must be used three times: Once for gross weight (use elements 06, 07, 08), a second time for net weight (use elements 06, 07, 08), a third time for container count (use elements 01, 02.) Do not add the Lading Quantity elements with either of the weight segments, it must be in its own iteration of the TD1 segment.
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
- CNT
- Container
Number of units (pieces) of the lading commodity
- This field and the corresponding packaging code will be used once per ASN.
- When used, the 02 element is a count of the total number of containers that hold parts. Examples include Honda A1, C & D containers that hold parts, as well as cardboard boxes holding parts. The following containers would not be included because they do not hold parts: Returnable pallets (AP) and wooden pallets.
- This count may be different from the Container Summary on the MPL.
Code defining the type of weight
- G
- Gross Weight
- N
- Actual Net Weight
Numeric value of weight
- Both the Net Weight and Gross Weight must be sent (different iterations of the TD1 segment) in each ASN.
- The Net Weight represents the total shipment net weight for this ASN. This value should include the product weight only.
- The Gross Weight represents the total shipment gross weight for this ASN. This value should include packaging.
- Round to the nearest positive whole unit and shall not be zero.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
This code must be from the same value system as the MEA04 (i.e. Ounces = pounds, grams = kilograms, not mixing English and Metric).
- 01
- Actual Pounds
- 50
- Actual Kilograms
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
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
- Standard Carrier Alpha Code (SCAC) of carrier.
- Honda suppliers must return the SCAC code of the trucking company picking up the freight on the 856 (Advance Ship Notice), unless otherwise specified by your Purchasing contact. This will usually match the SCAC found in the ordering document.
- If a SCAC code of “XXXX” was sent in the ordering document, suppliers
may return (1) the SCAC code of the carrier or (2) "XXXX" on the 856
(Advanced Ship Notice).
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
For OEM Mfg, return the following:
-- Less than Trailer Load (LTL) - Pro Number
-- FedEx or UPS (i.e. Partial Shipments) etc. – Tracking Number
-- Full Trailer Loads/Collection Routes - will be determined at a future date.
- For AHM Service parts this information is preferred but not required
Pro or Tracking Numbers to be entered without dashes or spaces: Continuous Data String
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- TL
- Trailer (not otherwise specified)
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
- The number on the side of the trailer. This number must consist of characters from the ranges 0 thru 9, A thru Z, or a thru z.
- This data element is mandatory; therefore it must be completed for air
shipments also. - This number must match the trailer number on the Master Packing List.
- If the trailer number used is greater than 10 characters, enter only the last 10 characters (i.e. UPS/FED EX tracking numbers).
- In the case of an expedite where 'XXXX' has been used as the SCAC, the trailer # or PRO # must be provided in the Trailer No. field. If sufficient space permits, the name of the expediting carrier should be included after the trailer/Pro#. (Data on the MPL should be the same as what is on the ASN).
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
- Optional segment to be used by all suppliers shipping hazardous material.
- All suppliers must have the capability to send this data.
Code specifying special transportation handling instructions
- To be completed for any shipments that contain hazardous materials.
- This segment must be sent if any part(s) on the ASN contain hazardous materials.
- All other ASN's should not contain this element/segment.
- Contact the appropriate Honda Parts Regulatory department if you have questions on your hazardous materials shipments.
- HM
- Endorsed as Hazardous Material
Reference Identification
To specify identifying information
For shipments crossing borders (US / Canada / México) the relationships between the ASN# and the BOL# must be one to one. (See "ASN and BOL Relationship" in the Operating Procedures section of this chapter for further clarification.)
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Honda uses the shipment date & time to help sync 862 requirements to ASN shipments for short shipment analysis.
Code specifying type of date or time, or both date and time
- 010
- Requested Ship
Date expressed as CCYYMMDD
ASN response to an 862:
- This is the earliest planned ship date for all parts on this ASN. The planned ship date(s) comes from the corresponding 862.
- Example: For an ASN with three line items with planned ship dates of 5/20, 5/21, 5/21 (from the 862), your DTM Planned Ship Date would be 5/20.
ASN response to an 850: - This is the actual ship date.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
HHMM Format
ASN response to an 862:
This planned ship time relates to the date in DTM02.
ASN response to an 850:
This is the actual ship time.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- 16
- Plant
Code designating the system/method of code structure used for Identification Code (67)
- 98
- Purchasing Office
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This is the Honda code number for each logistical company.
For example: (May not be an all-inclusive list.)
AEP = Anna Engine Plant
AHM = American Honda Motor Co., Inc.
ELP = East Liberty Auto Plant
GDL = Honda de México, Guadalajara Plant (Ending ~ TBD 2019)
HCL = Honda de México, Celaya Plant
HCM = Honda of Canada Mfg.
HDM = Honda de México, Guadalajara Plant (Starting ~ TBD 2019)
HMA = Honda Manufacturing of Alabama
HMI = Honda Manufacturing of Indiana
HMS = Honda México Sales
HPE = Honda Power Equipment
HPG = Honda Precision Parts Georgia
HSC = Honda of South Carolina
HSP = Honda Supply Parts
HTM = Honda Transmission
IPS = Int’l Operating Office (IOO), aka Int’l Parts Supply
MAP = Marysville Auto Plant
MPS = Honda de México Parts Supply
MSP = Mexico Supply Parts
MTP = Mexican Transmission Plant
PMC = Performance Manufacturing Center
T(XX) = Honda Trading [The “(XX)” will be replaced with two digits signifying the Honda Trading location]
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
This is the code assigned by Honda for this ship to location.
- For OEM orders, this will be a ship to code.
- For DSPS orders, this will be the supplier number and location code.
- Honda ship-to codes may have spaces within the code.
- The ship-to code on the ASN must be the same as the corresponding ordering document.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code, (which may be 00).
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 Identification
To specify basic item identification data
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.
- PG
- Packaging Specification Number
Identifying number for a product or service
- This will be a 1 to 10 digit code corresponding to the Honda returnable type.
- If the packaging type is not a Honda returnable, input "XX".
- Suppliers should not manually enter the packaging type. See Chapter 5, page 5-21
- Unless using an approved alternative packaging, the container type should match the ordering document (850/862).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RC
- Returnable Container Number
Identifying number for a product or service
- LIN04 & 05 should not be sent if the packaging type is a non-returnable.
- LIN04 & 05 are optional for a returnable packaging type.
- This value is the scanned returnable ID tag (also called a fixed asset tag).
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- LS
- Bar-Coded Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- Scanned serial number from the Master or Mixed load label. This number shall not match any Item level serial number except when using “Container is the Pallet” Option Two page 19-43.
- This number is created by the Honda supplier.
- Format: first eight digits should be the supplier and location code, the second eight digits should be assigned such that the number is unique within an 18 month period.
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
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
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BE
- Buyer's Engineering Change Level Number
Indicates the part being shipped is at the design level listed in LIN05.
Identifying number for a product or service
- For Honda manufacturing facilities this field (and the corresponding qualifier) must be present for a Manufacturing Base Part Number that begins with a number less than 92.
- This must be the actual D/C Level of the part being shipped, even if the D/C Level is different from what was ordered. (See Chapter 5, Understanding How the Design Change (DC) works)
- Exceptions:
- AHM: This field (and qualifier) will not be present.
- HTA: This field (and qualifier) may be present.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
- LIN06/07 must be returned if present on the corresponding ordering document.
- The data comes from the corresponding Honda outbound 862 (REF02 Pos. 120).
- See Honda Lot Number in the Operating Procedures portion of this chapter for further details.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ON
- Customer Order Number
Identifying number for a product or service
- This field and the corresponding qualifier are only used for ship schedules.
- LIN08 & LIN09 are mutually exclusive of LIN12 & LIN13.
- If used, the data comes from the corresponding Honda outbound 862: REF02 (Pos 137)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- L1
- Program Level
Identifying number for a product or service
- This is a reference number for a particular event or project.
- If a project number is included in the corresponding 850 or 862, it must be returned in this field
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Identifying number for a product or service
- This field and the corresponding qualifier are only used for purchase orders.
- LIN12 & LIN13 are mutually exclusive of LIN08 & LIN09.
- If used, the data comes from the corresponding Honda outbound 850 PO101.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
If IPP Tag 1 is used, LIN 14, 15, 16 & 17 must all be completed.
- A6
- Document Identification Code
Identifying number for a product or service
- See Initial Production Parts (IPP) in the Operating Procedures portion of this chapter for further details.
- An HTR number may be used in place of an actual IPP Tag Number for
certain reason codes. Please review current quality manual or contact your Honda Quality Representative for guidance. - Format must be 10 characters, use leading zeroes if necessary (do not use Plant Code)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
If IPP Tag 2 is used, LIN 18, 19, 20 & 21 must all be completed.
- A6
- Document Identification Code
Identifying number for a product or service
- See Initial Production Parts (IPP) in the Operating Procedures portion of this chapter for further details.
-An HTR number may be used in place of an actual IPP Tag Number for
certain reason codes. Please review current quality manual or contact your Honda Quality Representative for guidance.
-Format must be 10 characters, use leading zeroes if necessary (do not use Plant Code)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SL
- Seller's Lot Number
Identifying number for a product or service
- Honda quality departments use this field for tracking purposes. This number should be a supplier’s reference in identifying production of the parts. See Honda Quality Manual for further information.
- For JSP ASNs sent from Honda, the PC # will be entered in this field.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RC
- Returnable Container Number
Identifying number for a product or service
- LIN24 & 25 should not be sent if the packaging type is a non-returnable.
- LIN24 & 25 are optional for a returnable packaging type.
- Scanned returnable ID tag (also called a fixed asset tag).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PG
- Packaging Specification Number
Identifying number for a product or service
- The packaging type should match the corresponding Honda outbound 862 TD105 or 850 TD105.
- This will be a 1 to 10 digit code corresponding to the Honda returnable type.
- If the packaging type is not a Honda returnable, input "XX".
- Suppliers should not manually enter the packaging type. See Chapter 5, page 5-21.
- Unless using an approved alternative packaging, the container type should match the ordering document (850/862).
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
This field is mandatory in the ASN and must match the associated label.
For Honda Manufacturing Facilities:
Examples include:
CA - Canada
CN - China
JP - Japan
MX - México
PH - Philippines
TH - Thailand
US - United States
The above list is not all-inclusive. For additional codes contact the Trade Compliance Group at the Honda company which ordered the parts or reference the ISO country code list on the internet.
This code must be used in the ASN and Container Label and must match.
For AHM:
LIN29 represents multiple countries of origin. The following codes must be included:
T - Federal Trade Commission Type Code
XX - Federal Trade Commission Country of Origin
YY - NAFTA Country of Origin
ZZ - Substantial Transformation Country of Origin
The data should be sent in the following format: TXXYYZZ.
For a list of valid codes contact your company’s Trade Compliance Group, or contact AHM’s Trade Compliance Group.
When the Country Code is the same for each of the categories above,
the supplier should use the same value for each category.
The container label should contain the same values as sent in the ASN
with slashes separating the characters.
Example: ASN: TXXYYZZ
Label: T/XX/YY/ZZ
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
The quantity in the container listed in the previous LIN. No zero or negative numbers.
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.
Measurements
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
(See Figures Appendix for example of use of C001)
Code identifying the broad category to which a measurement applies
- PD
- Physical Dimensions
Code identifying a specific product or process characteristic to which a measurement applies
- WT
- Weight
The value of the measurement
- This is the weight of ONE unit / piece / part. No packaging weight should be included. No zero or negative values.
- Examples of valid data: 1, 1.0, 1.12, 1.1234, 0.1234, .1234
- Honda will round values more than 4 digits to the right of the decimal point to 4 digits.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
This code must be from the same value system as the TD108 (i.e. Ounces = pounds, grams = kilograms, not mixing English and Metric).
- GR
- Gram
- KG
- Kilogram
- LB
- Pound
- OZ
- Ounce - Av
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- LS
- Bar-Coded Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- Scanned serial number from parts identification label on each container.
- This number is created by the Honda supplier.
- Format: first eight digits should be the supplier and location code, the second eight digits should be assigned such that the number is unique within an 18 month period. This number shall not match any other LIN S/N within the ASN.
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
The accumulation of the number of HL segments.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
The sum of the value of units shipped (SN102) for each SN1 segment.
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
Responding to an 850
GS*SH*SENDERGS*RECEIVERGS*20240117*021747*000000001*X*004010
ST*856*10047
BSN*00*10000048*20110810*1330
DTM*011*20110810*1430
HL*1**S
TD1******N*35*01
TD1******G*41*01
TD1*CNT*2
TD5**2*CUOT
TD3*TL**893
REF*BM*23456
DTM*010*20110810*1430
N1*16**98*HMA
N1*ST**92*HMA1 01
N1*SU**92*12345601
HL*2*1*T
LIN**PG*AP
REF*LS*1234560100005122
HL*3*2*I
LIN**BP*35244S84A001*BE*01*******PO*12345600*********SL*52415***PG*D10001*CH*MX
SN1**60*EA
MEA*PD*WT*2.14*OZ
REF*LS*1234560100005128
HL*4*2*I
LIN**BP*47546S84A010*BE*00BB*******PO*1234560002*********SL*52446***PG*C10001*CH*US
SN1**60*EA
MEA*PD*WT*1.5*OZ
REF*LS*1234560100005127
CTT*4*120
SE*29*10047
GE*1*000000001
IEA*1*000000001
Responding to an 862
GS*SH*SENDERGS*RECEIVERGS*20240117*021656*000000001*X*004010
ST*856*10046
BSN*00*10000481*20110810*1330
DTM*011*20110810*1430
HL*1**S
TD1******N*35*01
TD1******G*41*01
TD1*CNT*3
TD5**2*CUOT
TD3*TL**893
REF*BM*23456
DTM*010*20110810*1430
N1*16**98*HMA
N1*ST**92*HMA1 01
N1*SU**92*12345601
HL*2*1*T
LIN**PG*AP
REF*LS*1234560100005096
HL*3*2*I
LIN**BP*71800S84A100BB*BE*00BB***ON*79*************SL*12345***PG*D10001*CH*MX
SN1**60*EA
MEA*PD*WT*.3*GR
REF*LS*1234560100005090
HL*4*2*I
LIN**BP*71800S84A100BB*BE*00BB***ON*79*************SL*12345***PG*D10001*CH*MX
SN1**60*EA
MEA*PD*WT*.3*GR
REF*LS*1234560100005091
HL*5*1*T
LIN**PG*EP
REF*LS*1234560100005098
HL*6*5*I
LIN**BP*35250S87JA100M1*BE*10MA01***ON*79*************SL*54321***PG*C10001*CH*US
SN1**60*EA
MEA*PD*WT*1.502*GR
REF*LS*1234560100005100
CTT*6*180
SE*37*10046
GE*1*000000001
IEA*1*000000001
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.