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

X12 824 Application Advice

X12 Release 4030

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
  • ^ Repetition
EDI samples
    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
    0100
    Original Transaction Identification
    Max use 1
    Required
    REF
    0200
    Bill of Lading Number
    Max use 12
    Optional
    REF
    0200
    Reference Identification
    Max use 12
    Optional
    TED Loop
    SE
    0900
    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 identifying 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 identifying 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

    Code indicating 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

    Code indicating 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
    I65
    Repetition Separator
    Required
    Min 1Max 1

    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
    ISA-12
    I11
    Interchange Control Version Number
    Required

    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
    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 indicating sender's request for an interchange acknowledgment

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

    Code indicating 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 where CC represents the first two digits of the calendar year

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

    004030
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

    Heading

    ST
    0100

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

    Beginning Segment

    RequiredMax use 1

    To indicate the beginning of a transaction set

    Usage notes

    Example Data:
    BGN44987654321202011171050*CS~

    Example
    If Time Code (BGN-05) is present, then Time (BGN-04) is required
    BGN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    44
    Rejection
    BGN-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    • BGN02 is the transaction set reference number.
    BGN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • BGN03 is the transaction set date.
    Usage notes

    Date that the 824 was created.

    Format to be used CCYYMMDD.

    BGN-04
    337
    Time
    Optional
    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)

    • BGN04 is the transaction set time.
    Usage notes

    Time that the 824 was created.

    Format to be used: HHMM.

    BGN-05
    623
    Time Code
    Optional

    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

    OTI Loop
    RequiredMax >1
    OTI
    0100

    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

    This segment contains specific details of the original, rejected document.

    Example Data:
    OTITRSI1234567889_1234567898SENDERISA060060300000320201117104138000001856~

    Example
    If Transaction Set Control Number (OTI-09) is present, then Group Control Number (OTI-08) is required
    OTI-01
    110
    Application Acknowledgment Code
    Required

    Code indicating the application system edit results of the business data

    Usage notes

    Code indicates file has been rejected by Best Buy.

    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.
    SI
    Shipper's Identifying Number for Shipment (SID)

    ASN ID from the original EDI 856 ASN document that was rejected.

    OTI-03
    127
    Reference Identification
    Required
    Min 1Max 50

    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

    Unique document ID from original transmission.

    OTI-04
    142
    Application Sender's Code
    Optional
    Min 2Max 15

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

    Sender ISA from original document that was rejected.

    OTI-05
    124
    Application Receiver's Code
    Optional
    Min 2Max 15

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

    Usage notes

    ISA receiver ID from original document that was rejected.

    OTI-06
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • OTI06 is the group date.
    Usage notes

    ISA date from the original document that was rejected.

    Format to be used: CCYYMMDD.

    OTI-07
    337
    Time
    Optional
    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)

    • OTI07 is the group time.
    Usage notes

    ISA time from the original document that was rejected.

    Format to be used: HHMM.

    OTI-08
    28
    Group Control Number
    Optional
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Usage notes

    GS08 from original document that was rejected.

    OTI-09
    329
    Transaction Set Control Number
    Optional
    Min 4Max 9

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

    ST02 from original document that was rejected.

    OTI-10
    143
    Transaction Set Identifier Code
    Optional

    Code uniquely identifying a Transaction Set

    Usage notes

    This is the EDI Document type of the rejected message.

    856
    Ship Notice/Manifest
    REF
    0200

    Bill of Lading Number

    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

    Example Data:

    REFBM1116044180~

    Example
    Variants (all may be used)
    REFReference Identification
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    Usage notes

    This is the reference number from original document that was rejected.

    REF
    0200

    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

    Example Data:

    REFCN1116044180~

    Example
    Variants (all may be used)
    REFBill of Lading Number
    REF-01
    128
    Carrier's Reference Number (PRO/Invoice)
    Required

    Code qualifying the Reference Identification

    CN
    Carrier's Reference Number (PRO/Invoice)
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 50

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

    Usage notes

    This is the reference number from original document that was rejected.

    TED Loop
    OptionalMax >1
    TED
    0700

    Technical Error Description

    RequiredMax use 1

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

    Usage notes

    Data Example: TEDMGRMS_INVALID_UPC*****123456789101~

    Example
    TED-01
    647
    Application Error Condition Code
    Required

    Code indicating application error condition

    Usage notes

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

    Best Buy system generated error.

    TED-07
    724
    Copy of Bad Data Element
    Optional
    Min 1Max 99

    This is a copy of the data element in error

    Usage notes

    This is the data Best Buy is rejecting.

    NTE
    0800

    Note/Special Instruction

    OptionalMax use 100

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

    Usage notes

    Data Example: NTEZZZInvalid UPC. Fix. Resend ASN as replacement~

    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

    Usage notes

    Human readable error message. See Appendix A for reason codes and correction instructions.

    RED
    0820

    Related Data

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

    Data Example: REDABCDEFPO~

    Example
    RED-01
    352
    Description
    Required
    Min 1Max 80

    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.
    RED-02
    1609
    Related Data Identification Code
    Optional

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

    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.

    SE
    0900

    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

    More Than One Error Example

    ST*824*0001~
    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

    ST*824*0001~
    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.