824 Application Device

Follow these guidelines to use the Application Advice Transaction Set (824) with an EDI environment.

Note: You can also view this information in Word format:
Walmart.com Drop Ship Vendor_824_4010_EDI.docx

Functional Group AG

This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use in 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 in either coded or free-form format at the functional group and transaction set level. It is designed to accommodate the business need to report acceptance, rejection, or acceptance with changes in 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 (such as a purchase order acknowledgment sent in response to a purchase order).

Heading

Detail

Notes

• 2/010: The OTI loop is intended to uniquely identify the transaction set that is the subject of this application acknowledgment.

Sample Spec 824 File

---

ISA*00* *00* *01*12571829 *12*73987501ME*091104*2002*U*00401*000000131*0*T*>
GS*AG*12571829*6111970076*20060829*0849*000000874*X*004010
ST*824*0001
BGN*11*000010380*20060829*0849*GM
OTI*BP*1Q*80253*****000007681
TED*024*(ORN=12635837, LINENO=1) Line Update Failed: Order request n
NTE*ERN*ORN=12635837 LINENO=1
OTI*BP*1Q*80253*****000007681
TED*024*(ORN=12607936, LINENO=1) Line Update Failed: Order request n
NTE*ERN*ORN=12607936 LINENO=1
SE*9*0001
GE*1*000000874
IEA*1*000080646

ST Transaction Set Header

To indicate the start of a transaction set and to assign a control number

• Pos: 010
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 2
• Usage Option: Must use

Element Summary

BGN Beginning Segment

To indicate the beginning of a transaction set. Identifies the original EDI file and when it was processed.

• Pos: 020
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 5
• Usage Option: Must use

Element Summary

Usage Notes:

• BGN02: Interchange Sequence Number (ISA13) from the original EDI message
• BGN03: Date the original EDI file was processed
• BGN04: Time the original EDI file was processed

OTI Original Transaction Identification

To identify the edited transaction set and the level at which the edit results are reported and to indicate the accepted, rejected, or accepted-with-change edit result. Identifies the group of the original EDI message and detects an error within the group. If there are multiple errors, there will be multiple OTI loop segments.

• Pos: 010
• Max: 1
• Detail – Mandatory
• Loop: OTI
• Elements: 4
• Usage Option: Must use

Element Summary

Usage Notes:

• OTI03: Numeric reference code assigned to specific error conditions
• OTI08: Group Control Number (GS06) from the original EDI message

TED Technical Error Description

To identify the error and, if feasible, the erroneous segment, data element, or both. Includes a human-readable error message that describes the error condition. The message can be truncated to 60 characters.

• Pos: 070
• Max: 1
• Detail – Optional
• Loop: TED
• Elements: 2
• Usage Option: Must use

Element Summary

NTE Note/Special Instruction

If necessary, transmit information in a free-form format for comment or special instruction. Detailed debugging information about the error condition or the data that contained the error. If this information is more than 80 characters, it’ll be split into multiple NTE segments.

• Pos: 080
• Max: 100
• Detail – Optional
• Loop: TED
• Elements: 2
• Usage Option: Must use

Element Summary

SE 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)

• Pos: 090
• Max: 1
• Detail – Mandatory
• Loop: N/A
• Elements: 2
• Usage Option: Must use

Element Summary