Honda
/
Application Advice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Honda. Contact Honda for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Honda logo

X12 824 Application Advice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the ability to report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order).

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/honda/application-advice/01HM7EEWW9KGFQPK3WPAT3ZGX4
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BGN
020
Beginning Segment
Max use 1
Required
N1 Loop Plant
N1 Loop Ship To
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

AG
Application Advice (824)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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).
824
Application Advice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BGN
020
Heading > BGN

Beginning Segment

RequiredMax use 1

To indicate the beginning of a transaction set

Example
BGN-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BGN-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • BGN02 is the transaction set reference number.
Usage notes

Application Advice Numbers are unique by transaction type code, OTI10. The Application Advice Number will not repeat within a year.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BGN03 is the transaction set date.
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

  • BGN04 is the transaction set time.
Usage notes

HHMM Format

N1 Loop Plant
RequiredMax >1
Variants (all may be used)
N1 Loop Ship ToN1 Loop Supplier/Manufacturer
N1
030
Heading > N1 Loop Plant > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

16
Plant
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

6
Plant Code
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

This is the Honda code 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]

N1 Loop Plant end
N1 Loop Ship To
OptionalMax 1
N1
030
Heading > N1 Loop Ship To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

This is the code assigned by Honda for the ship to location from the
corresponding 856.

N1 Loop Ship To end
N1 Loop Supplier/Manufacturer
RequiredMax 1
Variants (all may be used)
N1 Loop PlantN1 Loop Ship To
N1
030
Heading > N1 Loop Supplier/Manufacturer > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SU
Supplier/Manufacturer
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

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).

N3
050
Heading > N1 Loop Supplier/Manufacturer > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
060
Heading > N1 Loop Supplier/Manufacturer > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

PER
080
Heading > N1 Loop Supplier/Manufacturer > PER

Administrative Communications Contact

RequiredMax use 3

To identify a person or office to whom administrative communications should be directed

Example
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

SU
Supplier Contact
Required
String (AN)
Min 1Max 60

Free-form name

N1 Loop Supplier/Manufacturer end
Heading end

Detail

OTI Loop
RequiredMax >1
OTI
010
Detail > OTI Loop > OTI

Original Transaction Identification

RequiredMax use 1

To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result

  • The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application acknowledgment.
Example
OTI-01
110
Application Acknowledgment Code
Required
Identifier (ID)

Code indicating the application system edit results of the business data

Usage notes

Only resend the transaction set when this element (OTI01) indicates a reject (TR).

TA
Transaction Set Accept
TE
Transaction Set Accept with Error
TR
Transaction Set Reject
OTI-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

  • OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification.
SI
Shipper's Identifying Number for Shipment (SID)

Indicates this 824 is in response to an ASN (856)

OTI-03
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • OTI03 is the primary reference identification or number used to uniquely identify the original transaction set.
Usage notes

For an ASN, this will be the ASN Number (BSN02) from the original document.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • OTI06 is the group date.
Usage notes

This date applies to the document that is in error.
If a Honda supplier sends an original and replacement ASN (both with the same ASN number), the date (OTI06) and time (OTI07) will allow the supplier to link the appropriate 824 and ASN.

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

  • OTI07 is the group time.
Usage notes

HHMM Format

OTI-10
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

856
Ship Notice/Manifest
TED Loop
RequiredMax >1
TED
070
Detail > OTI Loop > TED Loop > TED

Technical Error Description

RequiredMax use 1

To identify the error and, if feasible, the erroneous segment, or data element, or both

Usage notes

This segment will be sent even if an error did not occur. General information will be transmitted if an error did not occur.

Example
TED-01
647
Application Error Condition Code
Required
Identifier (ID)

Code indicating application error condition

ZZZ
Mutually Defined
TED-02
3
Free Form Message
Required
String (AN)
Min 1Max 60

Free-form text

  • If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
Usage notes

If there was an error, there will be an error message. For example, "unit of
measure invalid".
If there was no error, a message stating the ASN is valid will appear.

TED-07
724
Copy of Bad Data Element
Optional
String (AN)
Min 1Max 99

This is a copy of the data element in error

Usage notes

If there was an error, this field will contain the actual data that was in error if available. For example: Error Data = BZ
If there was no error, the ASN number will appear.

NTE
080
Detail > OTI Loop > TED Loop > NTE

Note/Special Instruction

OptionalMax use 100

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

This segment will be provided only if data is available.

Example
NTE-01
363
Note Reference Code
Required
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

ADD
Additional Information
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Examples:
Error Description (TED02) = unit of measure invalid
Error Data (TED03) = BZ
Reference Data (NTE02) = 123456SM1A000 (Honda part number associated with 'invalid unit of measure')

TED Loop end
OTI Loop end
SE
090
Detail > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Detail end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.