EDI 824 Application Advice

Functional Group AG

X12F Finance Subcommittee

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. The results of editing transaction sets can be reported at the functional group, an entire transaction set, or any portion of a transaction set, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection, acceptance with change, or partial acceptance or rejection 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).

Heading

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To indicate the beginning of a transaction set

  3. N1 Loop Optional
    Repeat >1
    1. To identify a party by type of organization, name, and code

    2. To specify additional names

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To specify identifying information

    6. To identify a person or office to whom administrative communications should be directed

Detail

Position
Segment
Name
Max use
  1. OTI Loop Mandatory
    Repeat >1
    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 or portion thereof, that is the subject of this application acknowledgment.
    2. 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 or portion thereof. The primary reference identification or number should be provided in elements OTI02-03.
    3. 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 or portion thereof.
    4. 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 or portion thereof.
    5. 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 or portion thereof.
    6. To specify quantity information

      The QTY segment should be utilized if quantity information is important to the unique identification of the original transaction set or portion thereof.
    7. 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 or portion thereof.
    8. TED Loop Optional
      Repeat >1
      1. To identify the error and, if feasible, the erroneous segment, or data element, or both

      2. Describes an event context in terms of the application or implementation contexts in force at the time the event occurred and the position in the EDI stream at which that context was activated

      3. To transmit information in a free-form format, if necessary, for comment or special instruction

      4. 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.
      5. REF Loop Optional
        Repeat 1
        1. To specify identifying information

          The REF loop allows for freeform error reporting.
        2. To identify attributes and status related to the object

        3. To transfer binary data in a single data segment, convey a critical filter for transmission and allow identification of the end of the data segment through a count; there is no identification of the internal structure of the binary data in this segment

    9. LM Loop Optional
      Repeat >1
      1. To transmit standard code list identification information

        The LM loop is used to identify industry-based or proprietary application error conditions.
      2. LQ Loop Mandatory
        Repeat 100
        1. To identify standard industry codes

        2. 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.
  2. 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 is provided for marketing purposes and is 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.