X12 824 Application Advice
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).
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- AG
- Application Advice (824)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Beginning Segment
To indicate the beginning of a transaction set
Code identifying purpose of transaction set
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
Date expressed as CCYYMMDD
- BGN03 is the transaction set date.
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.
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.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
Code specifying the type of transaction
Detail
Original Transaction Identification
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.
Code indicating the application system edit results of the business data
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.
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.
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.
Code identifying party receiving transmission. Codes agreed to by trading partners
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.
Assigned number originated and maintained by the sender
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.
Code uniquely identifying a Transaction Set
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
- If OTI11 is present, it will contain the version/release under which the original electronic transaction was translated by the receiver.
Code identifying purpose of transaction set
- OTI12 is the purpose of the original transaction set, and is used to assist in its unique identification.
Code specifying the type of transaction
- OTI13 is the type of the original transaction set, and is used to assist in its unique identification.
Code identifying an application
- OTI14 is the application type of the original transaction set, and is used to assist in its unique identification.
Code indicating type of action
- OTI15 is the type of action indicated or requested by the original transaction set, and is used to assist in its unique identification.
Code designating the action to be taken by all parties
- OTI16 is the action requested by the original transaction set, and is used to assist in its unique identification.
Reference Identification
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.
Code qualifying the Reference Identification
- 11
- Account Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- DIS
- District Number
- SI
- Shipper's Identifying Number for Shipment (SID)
A unique number (to the shipper) assigned by the shipper to identify the shipment.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
Code defining the segment ID of the data segment in error (See Appendix A - Number 77)
The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1
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
Reference number used to locate the data element in the Data Element Dictionary
This is a copy of the data element in error
Related Data
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.
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.
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.
Code identifying the agency assigning the code values
- RED03 identifies the agency maintaining the code list identified in RED05.
A reference that indicates the table or text maintained by the Source Qualifier
- RED04 provides further qualification of the agency identified in RED03.
Code identifying a specific industry code list
- RED05 identifies the code list containing the code indicated in RED06.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Load is Already Completed but Received Update After Closed
GS^AG^SENDERGS^RECEIVERGS^20231117^044343^000000001^X^004010
ST^824^24980001
BGN^00^00000000001^20100414^1604^ET
OTI^TR^CN^123123123^^^20100414^1502^35337^353370001^214
REF^11^ENERSYS
REF^SI^LOADNBR
TED^848^Load LOADNBR is in Completed status. Cannot update Delivery
TED^999^Arrival.
SE^8^24980001
GE^1^000000001
IEA^1^000000001
Statuses Received Out of Sequence
GS^AG^SENDERGS^RECEIVERGS^20231117^044246^000000001^X^004010
ST^824^24810001
BGN^00^00000000001^20100414^1257^ET
OTI^TR^CN^123123123^^^20100413^1413^35330^353300001^214
REF^11^ENERSYS
REF^SI^LOADNBR
TED^848^Either delivery arrival is missing or delivery departure is
TED^999^before delivery arrival
SE^8^24810001
GE^1^000000001
IEA^1^000000001
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.