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
- ^ 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
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
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
Beginning Segment
To indicate the beginning of a transaction set
Example Data:
BGN44987654321202011171050*CS~
Code identifying purpose of transaction set
- 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 where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
Date that the 824 was created.
Format to be used CCYYMMDD.
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.
Time that the 824 was created.
Format to be used: HHMM.
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.
- CD
- Central Daylight Time
- CS
- Central Standard Time
- CT
- Central Time
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.
This segment contains specific details of the original, rejected document.
Example Data:
OTITRSI1234567889_1234567898SENDERISA060060300000320201117104138000001856~
Code indicating the application system edit results of the business data
Code indicates file has been rejected by Best Buy.
- 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)
ASN ID from the original EDI 856 ASN document that was rejected.
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.
Unique document ID from original transmission.
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.
Sender ISA from original document that was rejected.
Code identifying party receiving transmission; codes agreed to by trading partners
ISA receiver ID from original document that was rejected.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- OTI06 is the group date.
ISA date from the original document that was rejected.
Format to be used: CCYYMMDD.
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.
ISA time from the original document that was rejected.
Format to be used: HHMM.
Assigned number originated and maintained by the sender
GS08 from original document that was rejected.
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.
ST02 from original document that was rejected.
Code uniquely identifying a Transaction Set
This is the EDI Document type of the rejected message.
- 856
- Ship Notice/Manifest
Bill of Lading Number
To specify identifying information
- The REF segment allows for the provision of secondary reference identification or numbers required to uniquely identify the original transaction set. The primary reference identification or number should be provided in elements OTI02-03.
Example Data:
REFBM1116044180~
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This is the reference number from original document that was rejected.
Reference Identification
To specify identifying information
- The REF segment allows for the provision of secondary reference identification or numbers required to uniquely identify the original transaction set. The primary reference identification or number should be provided in elements OTI02-03.
Example Data:
REFCN1116044180~
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This is the reference number from original document that was rejected.
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Data Example: TEDMGRMS_INVALID_UPC*****123456789101~
Code indicating application error condition
See Appendix A for error messages indicating what issue has occurred and what action will need to be taken to resolve.
- 006
- Duplicate
- 007
- Missing Data
- 814
- Received After Cutoff Date or Time
- 817
- Duplicate Trace Number
- 848
- Incorrect Data
- IID
- Invalid Identification Code
- IQT
- Invalid Quantity
- J
- Missing or Invalid Purpose Code
- MB
- Missing or Invalid Purchase Order Number
- MG
- Missing or Invalid U.P.C. Code
- MID
- Missing Identification Code
- ML
- Missing or Invalid Sell to Location
- POI
- Purchase Order Number Invalid
- Q
- Missing or Invalid Item Identification
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
Best Buy system generated error.
This is a copy of the data element in error
This is the data Best Buy is rejecting.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Data Example: NTEZZZInvalid UPC. Fix. Resend ASN as replacement~
Code identifying the functional area or purpose for which the note applies
- ZZZ
- Mutually Defined
A free-form description to clarify the related data elements and their content
Human readable error message. See Appendix A for reason codes and correction instructions.
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.
Data Example: REDABCDEFPO~
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.
RED02 is identifying the data from the original rejected document.
- PO
- Purchase Order Number
- PS
- Product or Service Identification
- RP
- Reference Identification (Primary)
Tare level SSCC ID.
- RS
- Reference Identification (Secondary)
Pack Level SSCC ID.
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
More Than One Error Example
BGN*44*221212121*20201117*1050*CS~
OTI*TR*SI*1212121212_1234567898*SENDERISA*0600603000003*20201117*1041*3800*0001*856~
REF*BM*1122232280~
REF*CN*1111111111~
TED*Q*RMS_INVALID_SKU*****1234567~
NTE*ZZZ*Incorrect UPC. Fix. Resend ASN as replacement~
RED*DDDDDD*PO~
RED*00200887270113096555*RS~
TED*IQT*ZERO_SHIP_QUANTITY*****0~
NTE*ZZZ*Ship qty for item 0. Fix. Resend ASN as replacement~
RED*DDDDDD*PO~
RED*00200887270113091111*RS~
RED*123456789101*PS~
TED*MID*ASN_NO_PACK_NO_TARE_SSCC~
NTE*ZZZ*Missing SSCCs. Fix. Resend ASN as replacement~
RED*ABCDEW*PO~
SE*18*0001~
One Error Example
BGN*44*987654321*20201117*1050*CS~
OTI*TR*SI*1234567889_1234567898*SENDERISA*0600603000003*20201117*1041*3800*0001*856~
REF*BM*1116044180~
REF*CN*1116044180~
TED*MG*RMS_INVALID_UPC*****123456789101~
NTE*ZZZ*Invalid UPC. Fix. Resend ASN as replacement~
RED*ABCDEF*PO~
RED*00200887270113096480*RS~
SE*10*0001~
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.