EDI

API DocsTerminal
NEW!
Programmatically translate EDI to JSON with the EDI Core REST API
Get started in minutes →
Transaction Set
in
X12 Release 004020

824 Application Advice

Functional Group AG

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).

Featured 824 mapping guides
US Foods
CVS
Costco

Heading

Sequence
Segment
Name
Max use
0100
Transaction Set HeaderMandatory
Max 1
To indicate the start of a transaction set and to assign a control number
0200
Beginning SegmentMandatory
Max 1
To indicate the beginning of a transaction set
N1 Loop
Repeat >1
0300
Name
Max 1
To identify a party by type of organization, name, and code
0400
Additional Name Information
Max 2
To specify additional names
0500
Address Information
Max 2
To specify the location of the named party
0600
Geographic Location
Max 1
To specify the geographic place of the named party
0700
Reference Identification
Max 12
To specify identifying information
0800
Administrative Communications Contact
Max 3
To identify a person or office to whom administrative communications should be directed

Detail

Sequence
Segment
Name
Max use
OTI Loop
Repeat >1
0100
Original Transaction IdentificationMandatory
Max 1
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.
0200
Reference Identification
Max 12
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.
0300
Date/Time Reference
Max 2
To specify pertinent dates and times
The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original transaction set.
0400
Administrative Communications Contact
Max 3
To identify a person or office to whom administrative communications should be directed
The PER segment should be utilized if administrative communications contact information is important to the unique identification of the original transaction set.
0500
Monetary Amount
Max >1
To indicate the total monetary amount
The AMT segment should be utilized if monetary amount information is important to the unique identification of the original transaction set.
0600
Quantity
Max >1
To specify quantity information
The QTY segment should be utilized if quantity information is important to the unique identification of the original transaction set.
0650
Individual or Organizational Name
Max 9
To supply the full name of an individual or organizational entity
The NM1 segment allows for the provision of entity identification information required to uniquely identify the original transaction set.
TED Loop
Repeat >1
0700
Technical Error Description
Max 1
To identify the error and, if feasible, the erroneous segment, or data element, or both
0800
Note/Special Instruction
Max 100
To transmit information in a free-form format, if necessary, for comment or special instruction
0820
Related Data
Max 100
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.
LM Loop
Repeat >1
0850
Code Source Information
Max 1
To transmit standard code list identification information
The LM loop is used to identify industry-based or proprietary application error conditions.
LQ Loop
Repeat 100
0860
Industry CodeMandatory
Max 1
Code to transmit standard industry codes
0870
Related Data
Max 100
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 LQ02 element.
0900
Transaction Set TrailerMandatory
Max 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.