824 - Application Advice

824 Application Advice

Functional Group ID=AG

Introduction:

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

Heading:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BGN Beginning Segment M 1

LOOP ID - N1 >1

030 N1 Name O 1

Not Used 040 N2 Additional Name Information O 2

Not Used 050 N3 Address Information O 2

Not Used 060 N4 Geographic Location O 1

Not Used 070 REF Reference Numbers O 12

080 PER Administrative Communications Contact O 3

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - OTI >1

Must Use 010 OTI Original Transaction Identification M 1

Not Used 020 REF Reference Numbers O 12 c1

030 DTM Date/Time Reference O 2

Not Used 040 PER Administrative Communications Contact O 3

Not Used 050 AMT Monetary Amount O 10

Not Used 060 QTY Quantity O 10

Not Used 065 N1 Name O 1

LOOP ID - TED >1

070 TED Technical Error Description O 1

Not Used 080 NTE Note/Special Instruction O 100

LOOP ID - LM >1

085 LM Code Source Information O 1 n1

003050F824_0 06 March 1996
824 - Application Advice

Must Use 086 LQ Industry Code M 100

Must Use 090 SE Transaction Set Trailer M 1

Transaction Set Notes

1. Use of the LM loop is limited to the identification of industry unique application error conditions.

Transaction Set Comments

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

003050F824_0 2 06 March 1996
824 - Application Advice

Segment: ST Transaction Set Header

Position: 010

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1

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

Syntax Notes:

Semantic Notes: 1 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).

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use ST01 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

824 X12.44 Application Advice

Must Use ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

003050F824_0 3 06 March 1996
824 - Application Advice

Segment: BGN Beginning Segment

Position: 020

Loop:

Level: Heading

Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of a transaction set

Syntax Notes: 1 If BGN05 is present, then BGN04 is required.

Semantic Notes: 1 BGN02 is the transaction set reference number.

2 BGN03 is the transaction set date.

3 BGN04 is the transaction set time.

4 BGN05 is the transaction set time qualifier.

5 BGN06 is the transaction set reference number of a previously sent transaction 

affected by the current transaction.

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use BGN01 353 Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set

00 Original

Must Use BGN02 127 Reference Number M AN 1/30

Reference number or identification number as defined for a particular 

Transaction Set, or as specified by the Reference Number Qualifier.

Must Use BGN03 373 Date M DT 6/6

Date (YYMMDD)

Must Use BGN04 337 Time X TM 4/8

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)

BGN05 623 Time Code O ID 2/2

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

CT Central Time

ET Eastern Time

GM Greenwich Mean Time

MT Mountain Time

PT Pacific Time

003050F824_0 4 06 March 1996
824 - Application Advice

Not Used BGN06 127 Reference Number O AN 1/30

Reference number or identification number as defined for a particular 

Transaction Set, or as specified by the Reference Number Qualifier.

BGN07 640 Transaction Type Code O ID 2/2

Code specifying the type of transaction

Refer to 003050 Data Element Dictionary for acceptable code values.

BGN08 306 Action Code O ID 1/2

Code indicating type of action

Refer to 003050 Data Element Dictionary for acceptable code values.

003050F824_0 5 06 March 1996
824 - Application Advice

Segment: N1 Name

Position: 030

Loop: N1

Level: Heading

Usage: Optional

Max Use: 1

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

Syntax Notes: 1 At least one of N102 or N103 is required.

2 If either N103 or N104 is present, then the other is required.

Semantic Notes:

Comments: 1 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.

2 N105 and N106 further define the type of entity in N101.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use N101 98 Entity Identifier Code M ID 2/2

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

individual

FR Message From

TO Message To

Not Used N102 93 Name X AN 1/35

Free-form name

N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for 

Identification Code (67)

1 D-U-N-S Number, Dun & Bradstreet

9 D-U-N-S+4, D-U-N-S Number with Four Character 

Suffix

10 Department of Defense Activity Address Code 

(DODAAC)

33 Commercial and Government Entity (CAGE)

93 Code assigned by the organization originating the 

transaction set

FA Facility Identification

FI Federal Taxpayer's Identification Number

N104 67 Identification Code X AN 2/20

Code identifying a party or other code

Not Used N105 706 Entity Relationship Code O ID 2/2

Code describing entity relationship

Not Used N106 98 Entity Identifier Code O ID 2/2

003050F824_0 6 06 March 1996
824 - Application Advice

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

individual

003050F824_0 7 06 March 1996
824 - Application Advice

Segment: PER Administrative Communications Contact

Position: 080

Loop: N1

Level: Heading

Usage: Optional

Max Use: 3

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

directed

Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

3 If either PER07 or PER08 is present, then the other is required.

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use PER01 366 Contact Function Code M ID 2/2

Code identifying the major duty or responsibility of the person or group 

named

AL Alternate Contact

Person to be contacted when the main contact is not 

available

EA EDI Coordinator

PER02 93 Name O AN 1/35

Free-form name

PER03 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

FX Facsimile

TE Telephone

PER04 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

applicable

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

EX Telephone Extension

FX Facsimile

TE Telephone

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

003050F824_0 8 06 March 1996
824 - Application Advice

applicable

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

EX Telephone Extension

FX Facsimile

TE Telephone

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

applicable

Not Used PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

003050F824_0 9 06 March 1996
824 - Application Advice

Segment: OTI Original Transaction Identification

Position: 010

Loop: OTI

Level: Detail

Usage: Mandatory

Max Use: 1

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

Syntax Notes: 1 If OTI09 is present, then OTI08 is required.

Semantic Notes: 1 OTI06 is the group date.

2 OTI07 is the group time.

3 If OTI11 is present, it will contain the version/release under which the original 

electronic transaction was translated by the receiver.

Comments: 1 OTI02 contains the qualifier identifying the business transaction from the 

original business application, and OTI03 will contain the original business 

application identification.

2 If used, OTI04 through OTI08 will contain values from the original electronic 

functional group generated by the sender.

3 If used, OTI09 through OTI10 will contain values from the original electronic 

transaction set generated by the sender.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use OTI01 110 Application Acknowledgment Code M ID 1/2

Code indicating the application system edit results of the business data

TA Transaction Set Accept

TC Transaction Set Accept with Data Content Change

TE Transaction Set Accept with Error

TR Transaction Set Reject

Must Use OTI02 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

TN Transaction Reference Number

Must Use OTI03 127 Reference Number M AN 1/30

Reference number or identification number as defined for a particular 

Transaction Set, or as specified by the Reference Number Qualifier.

Not Used OTI04 142 Application Sender's Code O AN 2/15

Code identifying party sending transmission; codes agreed to by trading 

partners

Not Used OTI05 124 Application Receiver's Code O AN 2/15

Code identifying party receiving transmission. Codes agreed to by trading 

partners

Not Used OTI06 373 Date O DT 6/6

003050F824_0 10 06 March 1996
824 - Application Advice

Date (YYMMDD)

Not Used OTI07 337 Time O TM 4/8

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)

OTI08 28 Group Control Number X N0 1/9

Assigned number originated and maintained by the sender

OTI09 329 Transaction Set Control Number O AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

OTI10 143 Transaction Set Identifier Code O ID 3/3

Code uniquely identifying a Transaction Set

Refer to 003050 Data Element Dictionary for acceptable code values.

OTI11 480 Version / Release / Industry Identifier Code O AN 1/12

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

Refer to 003050 Data Element Dictionary for acceptable code values.

003050F824_0 11 06 March 1996
824 - Application Advice

Segment: DTM Date/Time Reference

Position: 030

Loop: OTI

Level: Detail

Usage: Optional

Max Use: 2

Purpose: To specify pertinent dates and times

Syntax Notes: 1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use DTM01 374 Date/Time Qualifier M ID 3/3

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

097 Transaction Creation

Must Use DTM02 373 Date X DT 6/6

Date (YYMMDD)

DTM03 337 Time X TM 4/8

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)

Not Used DTM04 623 Time Code O ID 2/2

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

DTM05 624 Century O N0 2/2

The first two characters in the designation of the year (CCYY)

Not Used DTM06 1250 Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Not Used DTM07 1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003050F824_0 12 06 March 1996
824 - Application Advice

Segment: TED Technical Error Description

Position: 070

Loop: TED

Level: Detail

Usage: Optional

Max Use: 1

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

Syntax Notes:

Semantic Notes:

Comments: 1 If used, TED02 will contain a generic description of the data in error (e.g., part 

number, date, reference number, etc.).

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use TED01 647 Application Error Condition Code M ID 1/3

Code indicating application error condition

Refer to 003050 Data Element Dictionary for acceptable code values.

TED02 3 Free Form Message O AN 1/60

Free-form text

TED03 721 Segment ID Code O ID 2/3

Code defining the segment ID of the data segment in error (See Appendix 

A - Number 77)

TED04 719 Segment Position in Transaction Set O N0 1/6

The numerical count position of this data segment from the start of the 

transaction set: the transaction set header is count position 1

TED05 722 Element Position in Segment O N0 1/2

This is used to indicate the relative position of a simple data element, or 

the relative position of a composite data structure with the relative position 

of the component within the composite data structure, in error; in the data 

segment the count starts with 1 for the simple data element or composite 

data structure immediately following the segment ID

TED06 725 Data Element Reference Number O N0 1/4

Reference number used to locate the data element in the Data Element 

Dictionary

TED07 724 Copy of Bad Data Element O AN 1/99

This is a copy of the data element in error

TED08 961 Data Element New Content O AN 1/99

New data which has replaced erroneous data

003050F824_0 13 06 March 1996
824 - Application Advice

Segment: LM Code Source Information

Position: 085

Loop: LM

Level: Detail

Usage: Optional

Max Use: 1

Purpose: To transmit standard code list identification information

Syntax Notes:

Semantic Notes:

Comments: 1 LM02 identifies the applicable industry code list source information.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use LM01 559 Agency Qualifier Code M ID 2/2

Code identifying the agency assigning the code values

Refer to 003050 Data Element Dictionary for acceptable code values.

LM02 822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source 

Qualifier

003050F824_0 14 06 March 1996
824 - Application Advice

Segment: LQ Industry Code

Position: 086

Loop: LM

Level: Detail

Usage: Mandatory

Max Use: 100

Purpose: Code to transmit standard industry codes

Syntax Notes: 1 If LQ01 is present, then LQ02 is required.

Semantic Notes:

Comments:

Data Element Summary

Ref. Data

Des. Element Name Attributes

LQ01 1270 Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list

Refer to 003050 Data Element Dictionary for acceptable code values.

LQ02 1271 Industry Code X AN 1/20

Code indicating a code from a specific industry code list

003050F824_0 15 06 March 1996
824 - Application Advice

Segment: SE Transaction Set Trailer

Position: 090

Loop:

Level: Detail

Usage: Mandatory

Max Use: 1

Purpose: To indicate the end of the transaction set and provide the count of the transmitted 

segments (including the beginning (ST) and ending (SE) segments).

Syntax Notes:

Semantic Notes:

Comments: 1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use SE01 96 Number of Included Segments M N0 1/10

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

SE segments

Must Use SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

003050F824_0 16 06 March 1996