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
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment
To indicate the beginning of a transaction set
The beginning segment contains the reference to the ship ID number in the associated ASN or the invoice number in the associated invoice data for which the transaction is created.
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 05
- Replace
- 07
- Duplicate
- 12
- Not Processed
- 44
- Rejection
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
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.
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
- BGN05 is the transaction set time qualifier.
(Example: CS=Central, ET=Eastern, MT=Mountain)
Name
To identify a party by type of organization, name, and code
If an N1 segment with an indicator "ST", "SU" or "SF" was contained in the ASN or 810 Invoice, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information.
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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.
Name
To identify a party by type of organization, name, and code
If an N1 segment with an indicator "ST", "SU" or "SF" was contained in the ASN or 810 Invoice, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information.
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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.
Name
To identify a party by type of organization, name, and code
If an N1 segment with an indicator "ST", "SU" or "SF" was contained in the ASN or 810 Invoice, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information.
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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.
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.
To help the supplier identify the transaction which is in error, data from the original ASN is sent. A code is included which tells if all data was rejected or only specific line items. Errors related to Invoices, Deere sends the original invoice data which is in error.
Code indicating the application system edit results of the business data
- IE
- Item Accept with Error
- IR
- Item Reject
- 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.
- FR
- Freight Bill Number
- IV
- Seller's Invoice Number
- PK
- Packing List Number
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.
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.
Code uniquely identifying a Transaction Set
- 210
- Motor Carrier Freight Details and Invoice
- 810
- Invoice
- 856
- Ship Notice/Manifest
This segment is used to identify the error and, if feasible, the erroneous segment, or data element, or both. A free form error message can also be included
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
This segment is used to identify the error and, if feasible, the erroneous segment, or data element, or both. A free form error message can also be included.
Code indicating application error condition
- 006
- Duplicate
- 007
- Missing Data
- 008
- Out of Range
- 011
- Not Matching
- 012
- Invalid Combination
- 813
- Missing or Invalid Payee Name and Address
- CUR
- Invalid Currency Code
Currency Code (DE100) reported is invalid
- H
- Missing or Invalid Unit of Measure Code
- IQT
- Invalid Quantity
- IWT
- Invalid Weight
- MD
- Missing or Invalid Invoice Date
- MI
- Missing or Invalid SCAC
- MM
- Missing or Invalid Bill to Location
- S
- Missing or Unauthorized Transportation Mode/Method Code
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
Reference number used to locate the data element in the Data Element Dictionary
This is a copy of the data element in error
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
Sample from Deere
GS*AG*SENDERGS*RECEIVERGS*20231106*125430*000000001*X*004010
ST*824*00110001
BGN*00*074-267686*19980618*1342*CS
OTI*IE*FR*074-267686***19980625*1615***856
TED*012*INVALID PO NUMBER****324*639999XX
SE*5*00110001
ST*824*00110002
BGN*07*12246*19980618*1342*CS
N1*ST*JOHN DEERE*1*305678132
N1*SF*AJAX CO*1*005289806
OTI*TR*FR*12246***19980625*1615***856
TED*006*DUPLICATE SHIP ID FOR ORIGINAL ASN
SE*7*00110002
GE*2*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.