X12 824 Application Advice
This X12 Transaction Set 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. The results of editing transaction sets can be reported at the functional group, an entire transaction set, or any portion of a transaction set, in either coded or free-form format. It is designed to accomodate the business need of reporting the acceptance, rejection, acceptance with change, or partial acceptance or rejection 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
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
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
Code specifying the version number of the interchange control segments
- 00701
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2013
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
- 2
- Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
- 3
- Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 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
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
- 007010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2013
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code 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
Beginning Segment
To indicate the beginning of a transaction set
Example: BGN00404201801181454
Code identifying purpose of transaction set
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
404 = Transaction Set Code Being Acknowledged
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- 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.
Format: HHMM
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 or portion thereof, that is the subject of this application acknowledgment.
Example: OTITABMYL78919*2018011214545759001
Code indicating the application system edit results of the business data
- TA
- Transaction Set Accept
- TE
- Transaction Set Accept with Error
- TR
- Transaction Set Reject
Code identifying 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.
- BM
- Bill of Lading Number
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.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- OTI06 is the group 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)
- OTI07 is the group time.
Format: HHMM
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.
Reference Information
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 or portion thereof. The primary reference identification or number should be provided in elements OTI02-03.
Example: REFEQCNRU123456
Code identifying the Reference Identification
- BM
- Bill of Lading Number
- EQ
- Equipment Number
- P8
- Pickup Reference Number
- WO
- Work Order Number
- WY
- Waybill Number
Examples:
TED007A PROBLEM HAS BEEN DETECTED IN THE ELECTRONIC BILL OF LADING
NTETHIS ELECTRONIC BILL OF LADING WAS REJECTED BECAUSE THE
NTEREGISTERED COMPANY NAME OR THE CONTRACT NUMBER REGISTERED
NTEWITH THE 24 HOUR EMERGENCY RESPONSE PROVIDER WAS NOT
NTEIDENTIFIED. PLEASE CORRECT AND RESUBMIT THE BILL OF LADING.
NTECONTACT YOUR LOCAL SERVICE DELIVERY CENTER OR EDI SUPPORT
NTEIF FURTHER INFORMATION IS REQUIRED.
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
- 001
- Car Not in Umler
- 003
- Duplicate Billing
- 004
- Invalid Commodity Code
- 005
- Route Error
- 007
- Missing Data
- 012
- Invalid Combination
- 024
- Other Unlisted Reason
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
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
Transaction Set Accepted
GS*AG*SENDERGS*RECEIVERGS*20231102*033529*000000001*X*007010
ST*824*5766001
BGN*00*404*20180112*1454
OTI*TA*BM*YL78919***20180112*1454*5759*0001
REF*EQ*CNRU123456
REF*WY*580881
SE*6*5766001
GE*1*000000001
IEA*1*000000001
Transaction Set Accepted With Error(s)
GS*AG*SENDERGS*RECEIVERGS*20231102*033538*000000001*X*007010
ST*824*33030001
BGN*00*404*20180112*1454
OTI*TE*BM*006394***20180112*1454*40860*408600001
REF*EQ*CNIS789012
REF*WY*580191
TED*024*A PROBLEM HAS BEEN DETECHED IN THE ELECTRONIC BILL OF LADING
NTE**THIS SHIPMENT CANNOT MOVE DUE TO A RAILROAD RESTRICTION THAT IS
NTE**IN EFFECT.VIEW THE AAR WEBSITE HTTP://AAREMBARGO.RAILINC.COM
NTE**FOR FURTHER INFORMATION ON EMBARGOES AND OPSL RESTRICTIONS.
NTE**IF FURTHER ASSISTANCE IS REQUIRED EMAIL EDIMGR@CN.CA.
NTE**PLEASE CONTACT YOUR LOCAL EDI SUPPORT CENTER IF FURTHER
NTE**INFORMATION IS REQUIRED. IF YOU ARE UNCERTAIN HOW TO CONTACT
NTE**YOUR LOCAL EDI SUPPORT CENTER PHONE US AT 800-267-9779
SE*14*33030001
GE*1*000000001
IEA*1*000000001
Transaction Set Rejected
GS*AG*SENDERGS*RECEIVERGS*20231102*033549*000000001*X*007010
ST*824*4206001
BGN*00*404*20180112*1454
OTI*TE*BM*10***20180112*1454*83041*23905
REF*EQ*CN555555
REF*WY*509072
TED*007*A PROBLEM HAS BEEN DETECTED IN THE ELECTRONIC BILL OF LADING
NTE**THIS ELECTRONIC BILL OF LADING WAS REJECTED BECAUSE THE RAIL
NTE**CAR INITIAL AND NUMBER ARE NOT IN THE ASSOCIATION OF
NTE**AMERICAN RAILROADS DATABASE OR INTERMODAL SHIPMENT TYPE IS
NTE**MISSING. PLEASE CORRECT AND RESUBMIT THE ELECTRONIC BILL OF LADING
NTE**PLEASE CONTACT YOUR LOCAL EDI SUPPORT CENTER IF FURTHER
NTE**INFORMATION IS REQUIRED. IF YOU ARE UNCERTAIN HOW TO CONTACT
NTE**YOUR LOCAL EDI SUPPORT CENTER PHONE US AT 800-267-9779.
SE*14*4206001
GE*1*000000001
IEA*1*000000001
Transaction Set Rejected – All Reference Numbers From Original 404 Displayed
GS*AG*SENDERGS*RECEIVERGS*20231102*033602*000000001*X*007010
ST*824*125795001
BGN*00*404*20180112*1454
OTI*TE*BM*10***20180112*1454*22829*0001
REF*EQ*WC44222
REF*WY*126624
REF*BM*LMNO9140620
REF*P8*220124
REF*WO*0000125436
SE*9*125795001
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.