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
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
- 00406
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
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
- 004060
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2002
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
A separate transaction set will be created for each item on a given PO with errors.
Example:
ST824000007707
BGN00123456789201409080858ET
N1ST94975
OTITEPO123456789123456789006097142***855
REFIX12345
REFWO99999
TEDZZZRC -LOWE'S RP NO LONGER EFFECTIVE -CALL BUYER
SE8000007707
ST824000007708
BGN00123456789201409080858ET
N1ST94975
OTITEPO123456789123456789006097142***855
REFIX67890
REFWO99999
TEDZZZRC -LOWE'S RP NO LONGER EFFECTIVE -CALL BUYER
SE8000007708\
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.
The BGN02 will include the PO Number sent in the BAK03 in the 855.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BGN03 is the transaction set date.
The 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.
The BGN04 is the transaction set time. Time expressed in 24-hour clock time as 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). An 8-digit time will be included in the BGN04.
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.
- ED
- Eastern Daylight Time
Party Identification
To identify a party by type of organization, name, and code
Example:
N1ST**94701
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
This element will contain the location number sent in the N1-04 of the 855 document.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
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
If OTI01=TE, the 855 was accepted with errors; the trading partner should not resend the Reverse PO unless the trading partner determines it is necessary.
If OTI01=TR, the 855 was rejected; the trading partner should correct the Reverse PO and resend it.
The TED segment can be sent up to 25 times within the OTI loop for an 824. If multiple TED segments are sent and one of the errors cause the
855 to reject, then the OTI01 will include a TR value.
After the Original 855 is transmitted, all subsequent 855s should be sent as a 855 Change ONLY IF the Original 855 rejected and did not post to Lowe's systems.
For both TE and TR codes, the trading partner should review the error message included in the TED segment, and make the necessary system
application changes to eliminate the error on future 855 transactions.
- TE
- Transaction Set Accept with Error
- 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.
- PO
- Purchase Order 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.
This field will include the PO Number sent in the BAK03 in the 855.
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.
This field will include the 855 sender's ID as sent in the 855 GS02.
Code identifying party receiving transmission; codes agreed to by trading partners
This field will include Lowe's ID of 006097142.
Code uniquely identifying a Transaction Set
- 855
- Purchase Order Acknowledgment
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. The primary reference identification or number should be provided in elements OTI02-03.
Lowe's uses a qualifier of IX to indicate the item number in error. A qualifier of WO is used to indicate the Lowe's Merchant Program(MP) number.
Code qualifying the Reference Identification
- IX
- Item Number
- WO
- Work Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Monetary Amount Information
To indicate the total monetary amount
- The AMT segment should be utilized if monetary amount information is important to the unique identification of the original transaction set.
Lowe's uses a qualifier of LI to indicate the line item price sent by the trading partner on the 855 Reverse PO. A qualifier of Z7 is used to indicate the price that Lowe's has for that item on the Merchant Program (MP).
Please be aware that if an item price is NOT available, the AMT segment(s) will be suppressed.
Technical Error Description
To identify the error and, if feasible, the erroneous segment, or data element, or both
If there are multiple errors for a given PO/Item number combination, the TED and NTE segments will loop up to 25 times in order to convey all applicable error messages. Please note that the NTE segment may not necessarily be present in each loop as it is simply a continuation of the TED segment if the error message is longer than 60 bytes.
Example:
ST824000007709
BGN00123456789201409080858ET
N1ST94975
OTITEPO123456789123456789006097142***855
REFIX12345
REFWO99999
TEDZZZRC -ERROR MESSAGE 1 XXXXXXXXXXXXXX
NTEXXXXXXXXX
TEDZZZRC -ERROR MESSAGE 2
TEDZZZRC -ERROR MESSAGE 3 XXXXXXXXXXXXXXXXXXXXXXXX
NTEXXXXXXXXXXXXXX
SE12000007709\
Code indicating application error condition
The same code in the TED01 can be used for both reject and warning messages, and the same code can represent more than one error message within the reject and warning categories.
- ZZZ
- Mutually Defined
Free-form text
- If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
The TED02 will include the reason the 855 was rejected or accepted with errors. The OTI01 may be used to identify the error condition.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
The NTE segment will be included in the 824 to provide additional information on the error, or when there are additional 855 segments/elements that will be helpful for the trading partner in researching the problem with the 855.
If multiple TED segments are sent and one of the errors cause the 855 to reject, then the OTI01 will include a TR value.
The NTE01 is not used by Lowe's.
Example:
NTE**Error message continued from TED segment.
A free-form description to clarify the related data elements and their content
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)
Example:
SE11000000001
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
sample
GS*AG*SENDERGS*RECEIVERGS*20231101*012301*000000001*X*004060
ST*824*000007709
BGN*00*123456789*20140908*0858*ED
N1*ST**94*975
OTI*TE*PO*123456789*123456789*006097142*****855
REF*IX*12345
REF*WO*99999
TED*ZZZ*RC -ERROR MESSAGE 1 XXXXXXXXXXXXXX
NTE**XXXXXXXXX
TED*ZZZ*RC -ERROR MESSAGE 2
TED*ZZZ*RC -ERROR MESSAGE 3 XXXXXXXXXXXXXXXXXXXXXXXX
NTE**XXXXXXXXXXXXXX
SE*12*000007709
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.