EDI 824 Application Advice

Functional Group AG

X12F Finance Subcommittee

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

Heading

1. 010 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

2. 020 · BGN · Beginning Segment · Max 1 · Mandatory

   To indicate the beginning of a transaction set

3. N1 Loop Optional Repeat >1

   1. 030 · N1 · Name · Max 1 · Mandatory

      To identify a party by type of organization, name, and code

   2. 040 · N2 · Additional Name Information · Max 2 · Optional

      To specify additional names or those longer than 35 characters in length

   3. 050 · N3 · Address Information · Max 2 · Optional

      To specify the location of the named party

   4. 060 · N4 · Geographic Location · Max 1 · Optional

      To specify the geographic place of the named party

   5. 070 · REF · Reference Identification · Max 12 · Optional

      To specify identifying information

   6. 080 · PER · Administrative Communications Contact · Max 3 · Optional

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

Detail

1. OTI Loop Mandatory Repeat >1

   1. 010 · OTI · Original Transaction Identification · Max 1 · Mandatory

      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.

   2. 020 · REF · Reference Identification · Max 12 · Optional

      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.

   3. 030 · DTM · Date/Time Reference · Max 2 · Optional

      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.

   4. 040 · PER · Administrative Communications Contact · Max 3 · Optional

      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.

   5. 050 · AMT · Monetary Amount · Max >1 · Optional

      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.

   6. 060 · QTY · Quantity · Max >1 · Optional

      To specify quantity information

      The QTY segment should be utilized if quantity information is important to the unique identification of the original transaction set.

   7. 065 · NM1 · Individual or Organizational Name · Max 9 · Optional

      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.

   8. TED Loop Optional Repeat >1

      1. 070 · TED · Technical Error Description · Max 1 · Mandatory

         To identify the error and, if feasible, the erroneous segment, or data element, or both

      2. 080 · NTE · Note/Special Instruction · Max 100 · Optional

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

      3. 082 · RED · Related Data · Max 100 · Optional

         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.

   9. LM Loop Optional Repeat >1

      1. 085 · LM · Code Source Information · Max 1 · Mandatory

         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. 086 · LQ · Industry Code · Max 1 · Mandatory

            Code to transmit standard industry codes

         2. 087 · RED · Related Data · Max 100 · Optional

            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. 090 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)