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
- None included
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
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.
The sender's internal number used to identify this transaction set within the sender's application system.
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
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 92
- Assigned by Buyer or Buyer's Agent
- UL
- Global Location Number (GLN)
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.
Code indicating the application system edit results of the business data
- IR
- Item Reject
- 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.
Identifies error transaction set's key field. For example, Transaction Set 810's key is invoice number
- 1X
- Credit or Debit Adjustment Number
- 2F
- Consolidated Invoice Number
- 08
- Carrier Assigned Package Identification Number
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- IV
- Seller's Invoice Number
- PD
- Promotion/Deal Number
- PO
- Purchase Order Number
- SI
- Shipper's Identifying Number for Shipment (SID)
- TN
- Transaction Reference Number
- VP
- Vendor Product 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.
Assigned number originated and maintained by the sender
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.
Contains ST02 data contents from the original transaction set header generated by the sender.
Code uniquely identifying a Transaction Set
Contains ST01 data contents from the original transaction set header generated by the sender. If the original document was not an EDI transaction, use the appropriate code that would have been in ST01, e.g, paper invoice would be 810.
Separate iterations of the TED loop should be generated for each error condition detected.
This segment is required except when OTI01 contains code GA or TA.
The codes listed for TED02 may not be used in conjunction with any code other than 024 in TED01
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
- 003
- Duplicate Billing
- 005
- Route Error
- 006
- Duplicate
- 007
- Missing Data
- 008
- Out of Range
- 009
- Invalid Date
Missing or invalid date
- 010
- Total Out of Balance
Line item totals do not match transaction totals.
- 011
- Not Matching
- 012
- Invalid Combination
- 024
- Other Unlisted Reason
This code is used only when the application error condition cannot be described using any other code in TED01.
- 026
- Customer Identification Number is Invalid
- 027
- Customer Identification Number Does not Exist
- 802
- Invalid Debit or Credit Flag Code
- 803
- Missing or Invalid Payment Method Code
- 807
- Missing or Invalid Originating Account Number
- 808
- Missing or Invalid Receiving Account Number
- 809
- Missing Effective Entry Date
- 812
- Missing Transaction Reference or Trace Number
- 813
- Missing or Invalid Payee Name and Address
- 814
- Received After Cutoff Date or Time
- 815
- Duplicate Batch
- 817
- Duplicate Trace Number
- 834
- Missing or Invalid Effective Payment Date
- 847
- Closed/Non-Existent Account Number
- 848
- Incorrect Data
- DBL
- Duplicate Bill of Lading Number
- DDT
- Departure Date Invalid
- DRC
- Duplicate Railcar Departure
- DTE
- Incorrect Date
- DUP
- Duplicate Transaction
- H
- Missing or Invalid Unit of Measure Code
- ICG
- Invalid Charge Allowance Qualifier
- INC
- Incomplete Transaction
- IQT
- Invalid Quantity
- IWT
- Invalid Weight
- MA
- Missing or Invalid Store Number
- MB
- Missing or Invalid Purchase Order Number
- MBL
- Multiple Bills of Lading
- MC
- Missing or Invalid Bill of Lading Number
- MDN
- Missing Department Number
- ME
- Missing or Invalid Department Number
- MF
- Missing or Invalid Internal Vendor Number
- MG
- Missing or Invalid U.P.C. Code
- MH
- Missing or Invalid DUNS Number
- MI
- Missing or Invalid SCAC
- MID
- Missing Identification Code
- MJ
- Missing or Invalid Terms
- MM
- Missing or Invalid Bill to Location
- MN
- Missing or Invalid Unit Cost
- MQT
- Missing Quantity
- MWT
- Missing Weight
- N
- Missing or Invalid Payer Identification
- NAU
- Not Authorized
- P
- Missing or Invalid Item Quantity
- POI
- Purchase Order Number Invalid
- PPD
- Previously Paid
- Q
- Missing or Invalid Item Identification
- QTY
- Quantity
- RTE
- Invalid Shipper's Route Code
- S
- Missing or Unauthorized Transportation Mode/Method Code
- SCA
- Invalid SCAC
- SPL
- Invalid SPLC Code
- T
- Unauthorized Transaction Set Purpose Code
- TYP
- Invalid Damage Type Code
- U
- Missing or Unauthorized Transaction Type Code
- UNP
- Invalid Unit Price
- V
- Missing or Unauthorized Action Code
This code is used in conjunction with the invalid or unauthorized code sent in BCT10 in Transaction Set 832.
- VIN
- Invalid Vehicle Identification Number
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
When TED01 contains code 024, TED02 must contain either application error code or free-form text description of the application error. When more than 60 characters are required to describe the error condition, the first 60 characters appear in this data element, and the remaining error description characters appear in NTE02. For example, TED01 contains code 010, TED02 contains "SUM of SKU cost extensions does not equal total invoice", and NTE02 contains "quantity."
Code Values:
101 Effective Date Too Early
102 Improper Placement of Labels
103 Invoice Number
104 Item Already Exists (Product/Service ID)
105 Item Marked for Delete (Product/Service ID)
106 Item Not Authorized For Buyer Assigned Vendor Number
107 Missing or Invalid Location
108 Location Received Not On Order
109 Negative Value
110 Missing Pack Level (Marking Identification is Missing)
111 Duplicate Purchase Order Number
112 Missing Product Description 1
113 Missing Product Description 2
114 Qualifier or Code Not Mapped To Application
115 Missing Qualifier or Code (For Application)
116 Retail Price Is Greater Than Suggested Retail Price
117 Sender Not Authorized to Submit Ship Notice For Buyer Assigned Ven #
118 Sender Not Authorized to Submit Ship Notice for Item(s)
119 Duplicate Shipment Identification Number
120 Ship To Location Not Consistent With Purchase Order Ship To
121 Duplicate SSCC
122 Invalid SSCC Range
123 Invalid SSCC Structure
124 Missing Tare Level (Marking Identification Is Missing)
125 Unscannable Labels
126 Incorrect Label Format
127 Improper Placement of Labels
128 Missing Labels on Shipping Container
129 Cost Change Not Accepted
130 UCC-12 Change not Allowed
131 Zero Value
132 Item Marked for Delete
133 Item Not Found on Purchase Order
134 Missing or Invalid Invoice Number
135 Duplicate Purchase Order Number
136 Receiving Location not on Order
137 Allowance Errors
138 Purchase Order Closed or Cancelled
139 Missing or Invalid Vendor Pack Quantity
140 Missing or Invalid Ship To Location
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
This segment is only generated when an error description contains more than 60 characters of data. For example, if 95 characters are required to describe the error condition, the first 60 characters appear in TED02, and the remaining 35 characters are sent in NTE02.
Related Data
To provide business data related to an item within a transaction to which a business application editing process has been applied, and an error condition has resulted
- The RED segment may be used to provide data related to the error condition specified in the associated TED01 element.
This segment is used to provide the receiver of the transaction additional information about the error condition specified in the associated TED segment. This segment is not used to specify the data in error, but provides a "pointer" or "clue" to the error condition.
A free-form description to clarify the related data elements and their content
- RED01 provides the related business data, whose nature is defined by the code in RED02 or RED06.
- As an example of the use of the RED01 element, an application edit is applied to the Unit Price element within an Invoice (810) transaction set. The result of that edit indicates an invalid unit price. One piece of related business data would be the associated Product or Service Identification (data element #234). In this example, RED01 would be used to convey the associated Product or Service Identification.
Code identifying the nature of data related to an application edit error condition
- RED02 is an X12-defined code identifying the specific type of related data in RED01.
- DT
- Date of Transaction
- IN
- Invoice Number
- LI
- Location Identification
- MA
- Monetary Amount
- MV
- Measurement Value
- PO
- Purchase Order Number
- PR
- Pricing Specification
- PS
- Product or Service Identification
- QY
- Quantity
- UP
- Unit Price
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.