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 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
- ^ Repetition
- None included
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
- 00405
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2001
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)
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
- 004050
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2001
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) 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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment
To indicate the beginning of a transaction set
Code identifying purpose of transaction set
01 Batch Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
TRANSMITTER ID
Identifier of the party that sent the commodity
shipment data to the Customs and Border
Protection (CBP).
Equivalent AESTIR Proprietary Element: A –
Transmitter ID.
Equivalent X12:601 Element:ISA02
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
TRANSMITTER DATE
This is the Filer/Transmitter’s date of
transmission.
Equivalent AESTIR Proprietary Element: A –
Transmitter Date.
Equivalent X12:601 Element: ISA09.
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.
APPLICATION INTENIFER
Identifies the AES output batch type:
XT = Commodity Shipment Filing Response.
XN = Commodity Shipment Warning Reminder.
Equivalent AESTIR Propriety
- XN
- Commodity Shipment Warning Reminder
- XT
- Commodity Shipment Filing Response
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
01 Block Identification
Free-form name
USPPI NAME
Name of the US Principal Party of Interest
(USPPI) for the commodity shipment
transactions.
Equivalent AESTIR Proprietary Element: B –
USPPI Name.
Equivalent X12:601Element: N102
Code designating the system/method of code structure used for Identification Code (67)
USPPI ID TYPE
Type of US PrincipalParty of Interest ID
reported in X12:601: N104.
1 DUNS
24 EIN
34 SSN
ZZ Foreign Entity
Equivalent AESTIR Proprietary Element: B
– USPPI ID Type.
Equivalent x12:601 Element: N103
The Census Bureau has eliminated the
acceptance of SSN on any new filings
effective December 3, 2009. Corrections
(change, replace or cancel)to SEDs filed
with SSN prior to the effective date will
continue to be accepted.
- 1
- D-U-N-S Number, Dun & Bradstreet
- 24
- Employer's Identification Number
- 34
- Social Security Number
- ZZ
- Foreign Entity
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.
USPPI ID
Identifier of the US Principal Party in Interest
(USPPI) for the commodity shipments.
EquivalentAESTIR Proprietary Element: B –
USPPI DI.
Equivalent X12:601 Element:N104
Reference Information
To specify identifying information
Code qualifying the Reference Identification
01 Batch Control Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
BATCH CONTROL NUMBER
Filer/Transmitter’sinternal batch identification
sent in to the Customs and Borders Protection
(CBP).
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
02 Response Identification
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.
OT102 and OT103 identify the Customs and
Border Protection (CBP) Proprietary record
represented in the X12 response. OT102 contains
the record ID of the Proprietary record. (A1
represents A record, B1 the B record, Y1 the Y
record, Z1 represents the Z record.) See the table
in OT103
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.
OT103 identifies which instance of the Customs
and Boarder Protection (CBP)
Proprietary record is being reported on in the
TED segment.
OT102 OT103
A1 Filers
B1 USPPI ID
SC1 Shipment Reference Number
SC2 InboundsCode + Entry Number
SC3 Transportation Reference Number
N01 Party ID or Party Name
N02 Address Line 1
N03 City
CL1 Line Number + Commodity Description
CL2 Schedule B/HTS Number
ODT DDTC Registration Number
EV1 VIN/Product Number
ES1 Internal Tracking Number (ITN) for an
accepted shipment
Y1 USPPI ID
Z1 Filer ID
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.
AES SYSTEM GENERATED RECORD
INDICATOR
OT104 = “01” indicates that AES was not able to
create the Proprietary record identified in OT102
from data provided in the X12:601 inbound
transmission. Therefore a place-holder
Proprietary record was generated in order to
create syntactically correct response. A space-
holder record may be generate for the B, SC1,
CL1, Y and/or Z Proprietary records (OT102 =
“B1”, “SC1”, “CL1”, “Y1”, or “Z1”)
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
RESPONSE CODE
Code that describes the condition or final disposition. See
AESTIR Appendix A – “CommodityFiling Response
Messages.”
Equivalent AESTIR Proprietary Element: ES1 – Response
Code.
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
RESPONSE MESSAGE
Format:
SEVERITY IND + blank + FINAL DISPOSITION IND +
blank + NARRATIVE TEXT
Where: Severity Indicator -is 1 byte, alphabetic in
position 1. Final Disposition Indicator -is 1 byte,
alphabetic in position 3. Narrative Text -is up to 40 bytes,
alphanumeric starting in position 5.
There is a 1 byte space between the Severity Indicator and
the Final Disposition Indicator, and a 1 byte space
between the Final Disposition Indicator and the start of the
message text. The Final Disposition Indicator is only
present when OTI02 = "ES1".
Maximum length of the Response Message - 44
bytes.
Equivalent AESTIR Proprietary Elements: ES1 -
Severity Indicator, Final Disposition Indicator,
Narrative Text. TED03 721 Segment ID Code O 1 ID 2/3
Code defining the segment ID of the data segment in error (See Appendix A - Number 77)
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.