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).
This Burlington Stores EDI Specification Document was developed exclusively for technical development purposes as would be undertaken by a typical trading partner as part of their on-boarding and technical development process; this document was designed to be as informative as possible however is not intended to provide complete compliance guidance or as part of a typical compliance management process undertaken by a typical trading partner.
The Burlington Stores Vendor Compliance guidelines can be found here:
http://www.burlingtoncoatfactory.com/Vendors/Compliance.aspx
Burlington Stores EDI Specification Documents can be found on the Burlington Stores website under :
http://www.burlingtoncoatfactory.com/Vendors/EDI.aspx
If you find this or any Burlington Stores EDI Specification contains material omissions or commentary which would be of value to your on-boarding and/or technical development process, please contact EDI Support at (609)387-7800 Ext 3340 (EDI-0) or EDI.Support@BurlingtonStores.com , where an incident will be opened and escalated to the guideline management team.
The Burlington EDI Team is committed to 'Making it Easy!'
If there are any questions about this or any Burlington Stores EDI specification contact EDI Support at (609) 387-7800 Ext 3340 (EDI-0) or EDI.Support@BurlingtonStores.com , where an incident will be opened and answered by the next available EDI coordinator.
Burlington Stores uses the Application Advice (824) business message to report the acceptance, rejection or acceptance with change of a trading partner’s transaction as it applies to its data content. The message contains information identifying the originating business message such as reference numbers, dates, quantities and monetary amounts. It also provides trading partner information, technical error descriptions with free-form text-format capability.
The Application Advice (824) is not used in place of a business message designed as a specific response to another business message such as the Functional Acknowledgment (997) to indicate the results of a syntactical analysis of functional groups and their business messages by EDI translation software.
The Application Advice (824) business message eliminates the need to communicate application errors by phone, fax, or mailed paper reports. It allows the originator of the transaction set to correct inconsistencies in a timely manner, minimizing the impact on time sensitive applications.
• Where Functional Acknowledgments (997) are automatically generated by EDI translation software for transmission back to the sending party, the Application Advice (824) business message is often generated by downstream data processing systems
• While Functional Acknowledgments (997) confirm the delivery of information and document any formatting errors or loss of data, the Application Advice (824) business message advises rejection or acceptance with change of a trading partner’s transaction as it applies to its data content.
• Where the Functional Acknowledgment (997) does not confirm that the receiver’s application system was able to process the message received , the Application Advice (824) business message advises rejection or acceptance with change in a downstream data processing systems
As with the Functional Acknowledgments (997), All Application Advice (824) business message which are noted as being ‘rejected’ must be corrected and re-transmitted by the sending party.
‘Burlington Stores’ includes trademarks, service marks and trade names used in connection with the operation of the business; documents EDI documents and or specifications may include such names as “Modecraft Fashions”, "Burlington Coat Factory,” “Cohoes,” “Luxury Linens,” “MJM Designer Shoes” and “Baby Depot.
- ~ 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
- 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.
Burlington Stores uses the 'BGN02' segment as a data carrier to carry the unique BCF Reference Number which can be used in order to assist the recipient in debugging issues.
Please use this reference number when speaking to EDI.Support@BurlingtonStores.com
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
- TC
- Transaction Set Accept with Data Content Change
- TE
- Transaction Set Accept with Error
- TP
- Transaction Set Partial Accept/Reject
- TR
- Transaction Set Reject
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.
- TN
- Transaction Reference 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.
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.
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
Code indicating application error condition
- 006
- Duplicate
- 007
- Missing Data
- 009
- Invalid Date
- 010
- Total Out of Balance
- 012
- Invalid Combination
- 024
- Other Unlisted Reason
- 802
- Invalid Debit or Credit Flag Code
- 807
- Missing or Invalid Originating Account Number
- 808
- Missing or Invalid Receiving Account Number
- 810
- Effective Payment Date is Past
- 812
- Missing Transaction Reference or Trace Number
- 813
- Missing or Invalid Payee Name and Address
- 815
- Duplicate Batch
- 817
- Duplicate Trace Number
- 834
- Missing or Invalid Effective Payment Date
- 847
- Closed/Non-Existent Account Number
- 848
- Incorrect Data
- 849
- Corrected Data
- DUP
- Duplicate Transaction
- HUG
- Quantity of Handling Units Shipped Greater Than the Quantity Specified
- IID
- Invalid Identification Code
- IQT
- Invalid Quantity
- IWT
- Invalid Weight
- MA
- Missing or Invalid Store Number
- MB
- Missing or Invalid Purchase Order Number
- MC
- Missing or Invalid Bill of Lading Number
- MD
- Missing or Invalid Invoice Date
- MDN
- Missing Department Number
- MF
- Missing or Invalid Internal Vendor Number
- MG
- Missing or Invalid U.P.C. Code
- MH
- Missing or Invalid DUNS Number
- MJ
- Missing or Invalid Terms
- T
- Unauthorized Transaction Set Purpose 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.).
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Burlington Stores uses the NTE segment only when an error description contains more than 60 characters of of information. For example, if 95 characters are required to accurately and completely describe the error condition to the recipient; the first 60 characters appear in TED02; the remaining 35 characters are sent in the NTE02.
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
ASN contains more than one shipment
GS|AG|SENDERGS|RECEIVERGS|20231106|135539|000000001|X|004010
ST|824|0001
BGN|00|24971559|20140522
OTI|TR|TN|205718|089087787|6126750000|20140522|2011|856000388|12959|856
TED|012|ASN contains more than one shipment (ship to's) and may be a
NTE||mixture of East Coast and West Coast DC's;
SE|6|0001
GE|1|000000001
IEA|1|000000001
Duplicate ASN is flagged as original (BSN01=00)
GS|AG|SENDERGS|RECEIVERGS|20231106|135546|000000001|X|004010
ST|824|0001
BGN|00|24968273|20140522
OTI|TE|TN|1761453201405221112|2122441136|6126750000|20140522|1112|176|1760001|856
TED|DUP|The shipment contained in the ASN is flagged as
NTE||original(BSN01=00),when an ASN has already been received and accepted for this
NTE||shipment;The original documents should use the '00' in the BSN01;documents
NTE||being resent should use '05' in the BSN01;
SE|8|0001
GE|1|000000001
IEA|1|000000001
Duplicate invoice number
GS|AG|SENDERGS|RECEIVERGS|20231106|135557|000000001|X|004010
ST|824|0001
BGN|00|24968010|20140522
OTI|TR|TN|8811419|2124658122|6126750000|20140522|1120|100029526|1001|810
TED|006|Duplicate invoice number|||||8811419
SE|5|0001
GE|1|000000001
IEA|1|000000001
Incorrect Unit of Measure
GS|AG|SENDERGS|RECEIVERGS|20231106|135606|000000001|X|004010
ST|824|0001
BGN|00|24962395|20140521
OTI|TE|TN|052117129|72629|6126750000|20140521|1700|4469|167267|856
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
TED|848|The ASN Unit of Measure is not AS for item with subitem;To
NTE||avoid additional errors, documents being resent should use '05' in the
NTE||BSN01;IN:PO2335698LN2;
SE|22|0001
GE|1|000000001
IEA|1|000000001
Invalid Buyer's Item Number
GS|AG|SENDERGS|RECEIVERGS|20231106|135615|000000001|X|004010
ST|824|0001
BGN|00|24927439|20140513
OTI|TR|TN|75255|118841501|6126750000|20140513|1900|86898|868980001|856
TED|848|ASN contains invalid Buyer's Item Number(IN),makes invalid
NTE||ref to style in the LIN02/SNL09;ASN must contain valid ref to the Buyer's Item
NTE||Number(IN)/UPC Code(UP),valid ref to the Buyer's Style(IT)/Vendor's Style(VA)
NTE||in the LIN02 and/or the SLN09;IN:65712935;
TED|848|ASN contains invalid SKU#; The ASN must contain valid
NTE||reference to either the Buyer's Item Number (IN) or UPC Code (UP) plus a valid
NTE||reference to the Buyer's Style Number (IT) or the Vendor's Style Number (VA) in
NTE||the LIN02 and/or the SLN09;IN:65712935;
SE|12|0001
GE|1|000000001
IEA|1|000000001
Invalid identification code qualifier
GS|AG|SENDERGS|RECEIVERGS|20231106|135624|000000001|X|004010
ST|824|0001
BGN|00|24975675|20140523
OTI|TE|TN|2863349|006415087|6126750000|20140523|1845|12777|127770001|856
TED|848|Invalid identification code qualifier at the order level in
NTE||N103.;Value:OB
SE|6|0001
GE|1|000000001
IEA|1|000000001
Invalid packaging code
GS|AG|SENDERGS|RECEIVERGS|20231106|135633|000000001|X|004010
ST|824|0001
BGN|00|24962921|20140521
OTI|TE|TN|123|364430512|6126750000|20140521|1705|804|1000|856
TED|848|Invalid packaging code at the order level in TD101.;Value is
NTE||empty
TED|848|Invalid packaging code at the order level in TD101.;Value is
NTE||empty
TED|848|Invalid packaging code at the order level in TD101.;Value is
NTE||empty
SE|10|0001
GE|1|000000001
IEA|1|000000001
More than one 'ship from'
GS|AG|SENDERGS|RECEIVERGS|20231106|135643|000000001|X|004010
ST|824|0001
BGN|00|24936699|20140515
OTI|TE|TN|750343|092000595|6126750000|20140515|1344|1266|6425|856
TED|848|ASN contains more than one 'ship from' address; ASNs are
NTE||shipment based. A single shipment cannot come from more than one distribution
NTE||or shipping point;
TED|010|The carton count at the shipment level didn't match the
NTE||total number of cartons in the subsequent detail; review and resend the ASN;
SE|9|0001
GE|1|000000001
IEA|1|000000001
Multiple Errors
GS|AG|SENDERGS|RECEIVERGS|20231106|135651|000000001|X|004010
ST|824|0001
BGN|00|24962897|20140521
OTI|TE|TN|5005071176|3365191115|6126750000|20140521|1717|714|0001|856
TED|848|ASN shows a shipment to a destination that does not match
NTE||the PO; Vendor should contact the Buyer to confirm the shipment
NTE||destination;Site: 53
OTI|TE|TN|5005071312|3365191115|6126750000|20140521|1717|714|0002|856
TED|HUG|The ASN indicates an over-ship condition on an item within
NTE||ASN by more than 10% for a non closeout PO; Vendor should contact the Buyer to
NTE||modify the PO and confirm shipping quantities to avoid future errors;PO Number
NTE||: 422052403
SE|12|0001
GE|1|000000001
IEA|1|000000001
Multiple Errors (Invoice)
GS|AG|SENDERGS|RECEIVERGS|20231106|135701|000000001|X|004010
ST|824|0001
BGN|00|24952777|20140520
OTI|TR|TN|963147|8648340346|6126750000|20140520|1106|100050001|100110001|810
TED|007|Missing IT103, unit of measure code|||||IT1
TED|848|Incorrect quantity qualifier for prepack
TED|010|Net amount of $ 280.00 does not match the line item total|||||280.00
NTE||cost of $ 124.00
OTI|TR|TN|963143|8648340346|6126750000|20140520|1106|100050001|100130001|810
TED|007|Missing IT103, unit of measure code|||||IT1
TED|848|Incorrect quantity qualifier for prepack
TED|010|Net amount of $ 316.00 does not match the line item total|||||316.00
NTE||cost of $ 450.00
OTI|TR|TN|963148|8648340346|6126750000|20140520|1106|100050001|100140001|810
TED|010|Net amount of $ 420.00 does not match the line item total|||||420.00
NTE||cost of $ 840.00
OTI|TR|TN|963138|8648340346|6126750000|20140520|1106|100050001|100170001|810
TED|007|Missing IT103, unit of measure code|||||IT1
TED|848|Incorrect quantity qualifier for prepack
SE|19|0001
GE|1|000000001
IEA|1|000000001
Non‐alphanumeric Characters
GS|AG|SENDERGS|RECEIVERGS|20231106|135712|000000001|X|004010
ST|824|0001
BGN|00|24975907|20140524
OTI|TE|TN|346673|7149630414N|6126750000|20140524|0013|405|4050001|856
TED|848|ASN contains non-alphanumeric characters in the PRO field
NTE||such as colons, commas, slashes, dashes, or pound signs; Non-alphanumeric
NTE||characters should be removed and the ASN should be resent, flagged as a
NTE||replacement (BSN01=05);
SE|8|0001
GE|1|000000001
IEA|1|000000001
Over‐ship condition
GS|AG|SENDERGS|RECEIVERGS|20231106|135721|000000001|X|004010
ST|824|0001
BGN|00|24967258|20140522
OTI|TE|TN|17374469174052|001379288|6126750000|20140522|0926|2582|582000001|856
TED|HUG|The ASN indicates an over-ship condition on an item within
NTE||ASN by more than 200% for a closeout PO; Vendor should contact the Buyer to
NTE||modify the PO and confirm shipping quantities to avoid future errors;PO Number
NTE||: 705866404
SE|8|0001
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.