AT&T
/
Application Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from AT&T. Contact AT&T for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
AT&T logo

X12 824 Application Advice

X12 Release 4010

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

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    detail
    OTI Loop
    OTI
    010
    Original Transaction Identification
    Max use 1
    Required
    REF
    020
    Reference Identification
    Max use 12
    Optional
    DTM
    030
    Date/Time Reference
    Max use 2
    Optional
    TED Loop
    SE
    090
    Transaction Set Trailer
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    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)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    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)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    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

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    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

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    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

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    AG
    Application Advice (824)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    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)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    Transaction Set Header

    RequiredMax use 1

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

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) 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
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BGN
    020

    Beginning Segment

    RequiredMax use 1

    To indicate the beginning of a transaction set

    Usage notes

    Sample EDI:
    BGN34AP*20070616~

    Example
    BGN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    34
    Payment Declined
    BGN-02
    127
    Reference Identification
    Required

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    • BGN02 is the transaction set reference number.
    Usage notes

    The hardcoded value of 'AP' will always be sent in the BGN02. This represents Accounts Payable at AT&T Mobility.

    AP
    Accounts Payable
    BGN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BGN03 is the transaction set date.

    Detail

    OTI Loop
    RequiredMax >1
    OTI
    010

    Original Transaction Identification

    RequiredMax use 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.
    Usage notes

    Sample EDI:
    OTITRTN24782-6101303******810~

    Example
    OTI-01
    110
    Application Acknowledgment Code
    Required

    Code indicating the application system edit results of the business data

    TR
    Transaction Set Reject
    OTI-02
    128
    Reference Identification Qualifier
    Required

    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.
    TN
    Transaction Reference Number
    OTI-03
    127
    Reference Identification
    Required
    Min 1Max 30

    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.
    Usage notes

    Rejected Invoice Number

    OTI-10
    143
    Transaction Set Identifier Code
    Optional

    Code uniquely identifying a Transaction Set

    810
    Invoice
    REF
    020

    Reference Identification

    OptionalMax use 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.
    Usage notes

    Sample EDI:
    REFPO1146790~
    REFLI9995~

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LI
    Line Item Identifier (Seller's)
    PO
    Purchase Order Number
    PP
    Purchase Order Revision Number
    ST
    Store Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    DTM
    030

    Date/Time Reference

    OptionalMax use 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.
    Usage notes

    Sample EDI:
    DTM00320070606~

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    003
    Invoice
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    TED Loop
    OptionalMax >1
    TED
    070

    Technical Error Description

    RequiredMax use 1

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

    Usage notes

    Sample EDI:
    TED024Invalid PO line number~

    Example
    TED-01
    647
    Application Error Condition Code
    Required

    Code indicating application error condition

    024
    Other Unlisted Reason

    The reason for the application error condition cannot be described using any other code on the standard code list

    Q
    Missing or Invalid Item Identification
    TED-02
    3
    Free Form Message
    Optional
    Min 1Max 60

    Free-form text

    • If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
    TED-07
    724
    Copy of Bad Data Element
    Optional
    Min 1Max 99

    This is a copy of the data element in error

    NTE
    080

    Note/Special Instruction

    OptionalMax use 100

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

    Usage notes

    Sample EDI:
    NTEZZZAdditional Detail Freeform Notes~

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies

    ZZZ
    Mutually Defined
    NTE-02
    352
    Description
    Required
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    SE
    090

    Transaction Set Trailer

    RequiredMax use 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)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*824*0001~
    BGN*34*AP*20070616~
    OTI*TR*TN*24782-6101303*******810~
    REF*PO*1146790~
    REF*LI*9995~
    DTM*003*20070606~
    TED*024*Invalid PO line number~
    NTE*ZZZ*Additional Detail Freeform Notes~
    SE*55*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.