X12 824 Application Advice
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).
- ~ 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
- AG
- Application Advice (824)
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).
- 824
- Application Advice
Beginning Segment
To indicate the beginning of a transaction set
Code identifying purpose of transaction set
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
Application Advice Numbers are unique by transaction type code, OTI10. The Application Advice Number will not repeat within a year.
Date expressed as CCYYMMDD
- BGN03 is the transaction set 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)
- BGN04 is the transaction set time.
HHMM Format
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)
- 6
- Plant Code
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 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
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).
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Detail
Original Transaction Identification
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.
Code indicating the application system edit results of the business data
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
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)
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.
For an ASN, this will be the ASN Number (BSN02) from the original document.
Date expressed as CCYYMMDD
- OTI06 is the group date.
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.
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.
HHMM Format
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
This segment will be sent even if an error did not occur. General information will be transmitted if an error did not occur.
Code indicating application error condition
- ZZZ
- Mutually Defined
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
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.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
This segment will be provided only if data is available.
Code identifying the functional area or purpose for which the note applies
- ADD
- Additional Information
A free-form description to clarify the related data elements and their content
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')
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.