X12 824 Application Advice

X12 Release 3040

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 accomodate 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 acknowledgement sent in response to a purchase order).

Delimiters

• ~ Segment
• * Element
• > Component

ISA Interchange Control Header

Required · Max use 1

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

ISA-01 · I01 · Authorization Information Qualifier · Required · Identifier (ID)

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 · String (AN) · Min 10 Max 10

Information used for additional identification or authorization of the sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.

ISA-03 · I03 · Security Information Qualifier · Required · Identifier (ID)

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 · String (AN) · Min 10 Max 10

This is used for identifying the security information about the sender or the data in the interchange. The type of information is set by the Security Information Qualifier.

ISA-05 · I05 · Interchange ID Qualifier · Required · Identifier (ID) · Min 2 Max 2

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

Codes

• 01: Duns (Dun & Bradstreet)
• 02: SCAC (Standard Carrier Alpha Code)
• 03: FMC (Federal Maritime Commission)
• 04: IATA (International Air Transport Association)
• 08: UCC EDI Communications ID (Comm ID)
• 09: X.121 (CCITT)
• 11: DEA (Drug Enforcement Administration)
• 12: Phone (Telephone Companies)
• 13: UCS Code (The UCS Code is the Only Code Used for UCS Transmissions. It includes the Area Code and Telephone Number of a Modem. It Does Not Include Punctuation, Blanks or Access Code.)
• 14: Duns Plus Suffix
• 15: Petroleum Accountants Society of Canada Company Code
• 16: Duns Number With 4-Character Suffix
• 17: American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit)
• 18: Association of American Railroads (AAR) Standard Distribution Code
• 19: EDI Council of Australia (EDICA) Communications ID Number (COMM ID)
• 20: Health Industry Identification Number
• 21: Integrated Postsecondary Education Data System, or (IPEDS)
• 22: Federal Interagency Commission on Education, or FICE
• 23: National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES
• 24: The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ACT
• 25: American College Testing Program 4-Digit Code of Postsecondary Institutions, or ACT
• NR: National Retail Merchants Association (NRMA) - Assigned
• ZZ: Mutually Defined

ISA-06 · I06 · Interchange Sender ID · Required · String (AN) · Min 15 Max 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 number in the sender ID element.

ISA-07 · I05 · Interchange ID Qualifier · Required · Identifier (ID) · Min 2 Max 2

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

Codes

• 01: Duns (Dun & Bradstreet)
• 02: SCAC (Standard Carrier Alpha Code)
• 03: FMC (Federal Maritime Commission)
• 04: IATA (International Air Transport Association)
• 08: UCC EDI Communications ID (Comm ID)
• 09: X.121 (CCITT)
• 11: DEA (Drug Enforcement Administration)
• 12: Phone (Telephone Companies)
• 13: UCS Code (The UCS Code is the Only Code Used for UCS Transmissions. It includes the Area Code and Telephone Number of a Modem. It Does Not Include Punctuation, Blanks or Access Code.)
• 14: Duns Plus Suffix
• 15: Petroleum Accountants Society of Canada Company Code
• 16: Duns Number With 4-Character Suffix
• 17: American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit)
• 18: Association of American Railroads (AAR) Standard Distribution Code
• 19: EDI Council of Australia (EDICA) Communications ID Number (COMM ID)
• 20: Health Industry Identification Number
• 21: Integrated Postsecondary Education Data System, or (IPEDS)
• 22: Federal Interagency Commission on Education, or FICE
• 23: National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES
• 24: The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ACT
• 25: American College Testing Program 4-Digit Code of Postsecondary Institutions, or ACT
• NR: National Retail Merchants Association (NRMA) - Assigned
• ZZ: Mutually Defined

ISA-08 · I07 · Interchange Receiver ID · Required · String (AN) · Min 15 Max 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 · Date (DT) · YYMMDD format

Date of the interchange.

ISA-10 · I09 · Interchange Time · Required · Time (TM) · HHMM format

Time of the interchange.

ISA-11 · I10 · Interchange Control Standards Identifier · Required · Identifier (ID)

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 · Identifier (ID)

This version number covers the interchange control segments.

• 00304: Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993

ISA-13 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

ISA-14 · I13 · Acknowledgment Requested · Required · Identifier (ID) · Min 1 Max 1

Code sent by the sender to request an interchange acknowledgment.

• 0: No Acknowledgment Requested
• 1: Interchange Acknowledgment Requested

ISA-15 · I14 · Test Indicator · Required · Identifier (ID) · Min 1 Max 1

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

• P: Production Data
• T: Test Data

ISA-16 · I15 · Subelement Separator · Required · String (AN) · Min 1 Max 1

This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).

• >: Component Element Separator

GS Functional Group Header

Required · Max use 1

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

GS-01 · 479 · Functional Identifier Code · Required · Identifier (ID)

Code identifying a group of application related Transaction Sets.

• AG: Acceptance/Rejection Advice (999) and Application Advice (824)

GS-02 · 142 · Application Sender's Code · Required · String (AN) · Min 2 Max 15

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

GS-03 · 124 · Application Receiver's Code · Required · String (AN) · Min 2 Max 15

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

GS-04 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

GS-05 · 337 · Time · Required · Time (TM) · 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 · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 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 · String (AN)

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.

• 003040: Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993

Heading

010 Heading > ST

ST Transaction Set Header

Required · Max use 1

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

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

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: X12.44 Application Advice

ST-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

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

020 Heading > BGN

BGN Beginning Segment

Required · Max use 1

To indicate the beginning of a transaction set.

BGN-01 · 353 · Transaction Set Purpose Code · Required · Identifier (ID)

Code identifying purpose of transaction set.

• 12: Not Processed

BGN-02 · 127 · Reference Number · Required · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

• BGN02 is the transaction set reference number.

BGN-03 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• BGN03 is the transaction set date.

N1 Loop Required Max >1

030 Heading > N1 Loop > N1

N1 Name

Required · Max use 1

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

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, or an individual

• VN: Vendor

N1-03 · 66 · Identification Code Qualifier · Required · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

• 92: Assigned by Buyer or Buyer's Agent

N1-04 · 67 · Identification Code · Required · String (AN) · Min 2 Max 17

Code identifying a party or other code.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

Usage notes

TMS assigned vendor code.

Detail

OTI Loop Required Max >1

010 Detail > OTI Loop > OTI

OTI Original Transaction Identification

Required · Max use 1

To identify the edited transaction set, the level at which the results of the edit are reported, and to indicate the accepted, rejected or accepted with change edit result.

Usage notes

The purpose of this segment is to notify the vendor that an 856 has not been received for the following REF segment.

OTI-01 · 110 · Application Acknowledgment Code · Required · Identifier (ID)

Code indicating the application system edit results of the business data.

• TR: Transaction Set Reject

OTI-02 · 128 · Reference Number Qualifier · Required · Identifier (ID)

Code qualifying the Reference Number.

• OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification.

• PO: Purchase Order Number

OTI-03 · 127 · Reference Number · Required · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Reference number. Purchase order number.

OTI-10 · 143 · Transaction Set Identifier Code · Required · Identifier (ID) · Min 3 Max 3

Code uniquely identifying a Transaction Set.

Usage notes

Transaction set identifier code. TMS uses “856” to indicate ship notice.

020 Detail > OTI Loop > REF

REF Reference Numbers

Required · Max use 12

To specify identifying numbers.

• REF segments can be used as needed to further identify the original transaction set.

REF-01 · 128 · Reference Number Qualifier · Required · Identifier (ID)

Code qualifying the Reference Number.

• BP: Part Number

REF-02 · 127 · Reference Number · Required · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Reference number. Part number.

030 Detail > OTI Loop > DTM

DTM Date/Time Reference

Required · Max use 2

To specify pertinent dates and times

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

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

• 011: Shipped

DTM-02 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

060 Detail > OTI Loop > QTY

QTY Quantity

Required · Max use 10

To specify quantity information.

QTY-01 · 673 · Quantity Qualifier · Required · Identifier (ID)

Code specifying the type of quantity.

• 39: Shipped Quantity

QTY-02 · 380 · Quantity · Required · Decimal number (R) · Min 1 Max 15

Numeric value of quantity.

TED Loop Optional Max >1

070 Detail > OTI Loop > TED Loop > TED

TED Technical Error Description

Required · Max use 1

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

TED-01 · 647 · Application Error Condition Code · Required · Identifier (ID)

Code indicating application error condition.

Usage notes

The “007: Call TMS Buyer" indicates that these parts/PO are missing based on the 862 Shipping Schedule. You need to contact your TMS buyer to verify this information and send the missing parts/PO and 856 if requested. Once the 856 have been sent the 824 will stop being transmitted to you.

• 007: Call TMS Buyer

090 Detail > SE

SE Transaction Set Trailer

Required · Max 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).

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 10

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

SE-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

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

GE Functional Group Trailer

Required · Max use 1

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

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 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 · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.

IEA Interchange Control Trailer

Required · Max use 1

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

IEA-01 · I16 · Number of Included Functional Groups · Required · Numeric (N0) · Min 1 Max 5

A count of the number of functional groups included in a transmission.

IEA-02 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

EDI Samples

824 Sample

ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *240314*2041*U*00304*000000001*0*T*>~
GS*AG*SENDERGS*RECEIVERGS*240314*204138*000000001*X*003040~
ST*824*000000001~
BGN*12*PS300*960223~
N1*VN**92*0367A~
OTI*TR*PO*TS999999*******856~
REF*BP*1234567890AAAAA~
DTM*011*960304~
QTY*39*20~
TED*007~
SE*9*000000001~
GE*1*000000001~
IEA*1*000000001~