X12 824 Application Advice
This X12 Transaction Set 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
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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) is 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
VICS Note: The number is sequentially assigned by the sender starting with 0001 within each functional group. For each functional group, the first
transaction set control number will be 0001 and incremented by one for each additional transaction set within the group.
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.
VICS Note: The sender's internal number used to identify this transaction set within the sender's application system.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
VICS Note: The date the transaction was generated in the sender's application system. It is analogous to the date placed on the paper document; the date it was written.
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- FR
- Message From
Code designating the system/method of code structure used for Identification Code (67)
- UL
- Global Location Number (GLN)
A globally unique 13 digit code for the identification of a legal, functional or physical location within the Uniform Code Council (UCC) and International Article Number Association (EAN) numbering system.
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.
Party Identification
To identify a party by type of organization, name, and code
Reference Information
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
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
- 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.
- TN
- Transaction Reference Number
The actual business application identification number for the transaction will be in OTI03, e.g., purchase order number, invoice number, ship notice number, etc.
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.
VICS Note: Identification of the transaction within the business application, or the financial institution's trace number.
Code identifying party sending transmission; codes agreed to by trading partners
- If used, OTI04 through OTI08 will contain values from the original electronic functional group generated by the sender.
VICS Note: Contains GS02 data contents from the original functional group generated by the sender.
Code identifying party receiving transmission; codes agreed to by trading partners
VICS Note: Contains GS03 data contents from the original functional group generated by the sender.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- OTI06 is the group date.
VICS Note: Contains GS04 data contents from the original functional group generated by the sender.
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.
VICS Note: Contains GS05 data contents from the original functional group generated by the sender.
Assigned number originated and maintained by the sender
VICS Note: Contains GS06 data contents from the original functional group generated by the sender.
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
- If used, OTI09 through OTI10 will contain values from the original electronic transaction set generated by the sender.
VICS Note: Contains ST02 data contents from the original functional group transaction set header generated by the sender.
Code uniquely identifying a Transaction Set
- 204
- Motor Carrier Load Tender
- 212
- Motor Carrier Delivery Trailer Manifest
- 214
- Transportation Carrier Shipment Status Message
- 753
- Request for Routing Instructions
- 830
- Planning Schedule with Release Capability
- 832
- Price/Sales Catalog
- 855
- Purchase Order Acknowledgment
- 856
- Ship Notice/Manifest
- 879
- Price Information
- 888
- Item Maintenance
- 889
- Promotion Announcement
- 990
- Response to a Load Tender
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
- 006
- Duplicate
- 007
- Missing Data
- 008
- Out of Range
- 012
- Invalid Combination
- 024
- Other Unlisted Reason
The reason for the application error condition cannot be described using any other code on the standard code list.
- 107
- Missing or Invalid Location
- 134
- Missing or Invalid Invoice Number
- 140
- Missing or Invalid Ship-To Location
- 803
- Missing or Invalid Payment Method Code
- DTE
- Incorrect Date
The reported date is incorrect (e.g. premature date for transaction or non-existent date such as February 30).
- IID
- Invalid Identification Code
- INF
- Invalid Status Code
The Vehicle Status Code (DE1094) reported is invalid.
- IQT
- Invalid Quantity
- IWT
- Invalid Weight
- J
- Missing or Invalid Purpose Code
- MB
- Missing or Invalid Purchase Order Number
- MID
- Missing Identification Code
- MK
- Missing or Invalid Ship Date Location
- OTH
- Other
- POI
- Purchase Order Number Invalid
- SCA
- Invalid SCAC
The Standard Carrier Alpha Code (DE140) reported is invalid.
- T
- Unauthorized Transaction Set Purpose Code
- 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.).
Walmart Note: For Transportation/Fleet vendors this is used as the short description for the error code used in the TED01 (DE 647), and in conjunction with the long description listed in the NTE02 (DE 352).
Code defining the segment ID of the data segment in error (See Appendix A - Number 77)
The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1
This is used to indicate the relative position of a simple data element, or the relative position of a composite data structure with the relative position of the component within the composite data structure, in error; in the data segment the count starts with 1 for the simple data element or composite data structure immediately following the segment ID
To identify the component data element position within the composite that is in error
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
A free-form description to clarify the related data elements and their content
Walmart Note: For Transportation/Fleet vendors this is used as the long description for the error code used in the TED01 (DE 647), and in conjunction with the short description listed in the TED03 (DE 3).
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
Sample 1
GS*AG*SENDERGS*RECEIVERGS*20241009*022743*1*X*005010~
ST*824*0001~
BGN*00*2066400*20050202~
N1*FR*WAL-MART STORES INC.*UL*0078742000008~
N1*TO*SUPPLIER NAME~
REF*IA*123456060~
OTI*TR*TN*2066400*967174AM*925485US00*20050201*1530*4419*44190001*856~
TED*024*Not a valid WM store*****9999~
NTE**Error is not valid or approved Walmart store # for the vendor. Record Rejected.~
SE*9*0001~
GE*1*1~
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.