It confirms whether a previously submitted ANSI X12 interchange or transaction set was received and accepted, or whether it was rejected with error details.
What Is an ANSI X12 EDI 997 Message?
An ANSI X12 EDI 997 message is a technical and functional acknowledgement sent in response to an ANSI X12 EDI transaction. It confirms whether the referenced interchange or transaction set was received and accepted, or whether it was rejected with error details. SEEBURGER supports EDI 997 acknowledgements as part of B2B/EDI processes that help trading partners monitor, troubleshoot, and stabilize electronic procurement exchanges.
Key takeaways
- An EDI 997 confirms receipt, acceptance, or rejection of a previously submitted ANSI X12 interchange or transaction set.
- A technical acknowledgement can identify the original transaction and response code; a functional acknowledgement can also include segment- and element-level error details.
- EDI 997 messages are often used in response to EDI 850 Purchase Orders and EDI 810 Invoices in electronic purchasing processes.
What is an ANSI X12 EDI 997 message used for?
An ANSI X12 EDI 997 message is used to acknowledge an EDI transmission between trading partners. It tells the sender whether the recipient received and accepted the referenced message, or whether the message was rejected. When a rejection occurs, the EDI 997 can return error information that helps the sender correct and resend the triggering message.
EDI 997 acknowledgements are not always mandatory, but they are an important message type in electronic purchasing processes, especially in manufacturing industries. They are commonly used in response to an EDI 850 Purchase Order or an EDI 810 Invoice.
How does an EDI 997 technical acknowledgement work?
A technical acknowledgement confirms receipt of the previous interchange and can indicate whether it was accepted. It references the message type and ID so the sender can match the acknowledgement to the original transaction.
AK1:
Functional Group Response Header
AK2:
Transaction Set Response Header
AK3:
Transaction Set Response Trailer
How does an EDI 997 functional acknowledgement report errors?
A functional acknowledgement can include additional details about errors in the submitted transaction. The AK3 Data Segment Note and AK4 Data Element Note identify the data segment or data element that caused the error and give reasons for the failure.
Typical rejection reasons include character-length violations, incomplete or missing data in mandatory segments, and invalid data. If the recipient never received the original message, no acknowledgement is created; that scenario requires monitoring and alerting for non-events.
What happens when an EDI 997 message is processed?
When an EDI 997 arrives, the EDI system checks its details to identify the message that triggered the acknowledgement. If the triggering message has been accepted, the sender knows that the message content and syntax have been acknowledged. If the message has been rejected, the feedback helps the sender fix and resend it.
What is the structure of an ANSI X12 EDI 997 message?
An EDI 997 message is sent in response to a received ANSI X12 message. A positive confirmation can be minimal, while a rejection can include details that explain why the message or part of the message was rejected.
- Message header
- Reference details for the previously received message
- Acceptance or rejection code at interchange and message levels
- Rejection details when the message or part of the message is rejected
ISA*00* *00* *ZZ*RECEIVER *01*SENDER *240205*1022*U*00401*000000001*0*P*>~
GS*FA*APP RECEIVER*APP SENDER*20240205*102244*1*X*004010~
ST*997*0001~
AK1*PO*0001~
AK2*850*0001~
AK3*DTM*7**923~
AK5*R~
AK9*R*1*1*0~
SE*7*0001~
GE*1*1~
IEA*1*000000001~
What is the difference between EDI 997 and EDI 824?
An EDI 997 acknowledges whether an EDI transmission has been received and translated. An EDI 824, also known as Application Advice, indicates whether an invoice has been accepted or rejected by the accounts payable system and is typically used for invoice disputes and related notes.
What are EDI 997 equivalents in other EDI standards?
Body copyANSI X12 is common in the NAFTA region. In EDIFACT, the comparable acknowledgement message is CONTRL. In VDA, APERAK messages, including VDA 4937 and VDA 4938, are used to acknowledge receipt of a message and highlight issues.
What are the benefits of using ANSI X12 EDI 997 acknowledgements?
EDI 997 acknowledgements create an automatic audit trail that shows whether the triggering message was received and accepted. They help protect supply chain and financial transactions by making message status visible, supporting troubleshooting, and returning rejection reasons when part or all of a message is denied.
EDI 997 feedback can also be compared with ERP information and diagnosed against the previously sent message.
Frequently asked questions about ANSI X12 EDI 997 messages
What does an ANSI X12 EDI 997 message confirm?
Is an EDI 997 always mandatory?
No. EDI 997 messages are not always mandatory, but they are important in electronic purchasing processes.
Which EDI messages commonly trigger an EDI 997?
The EDI 997 is commonly used as a response to an EDI 850 Purchase Order or an EDI 810 Invoice.
What information can a technical EDI 997 acknowledgement include?
It can include the original transaction, transaction control number, and response code through segments such as AK1, AK2, and AK5.
What information can a functional EDI 997 acknowledgement include?
It can include AK3 and AK4 details that identify the data segment or data element that caused an error and explain the reason for failure.
What happens if the original EDI message was never received?
If the customer never received the message, no acknowledgement is created. Monitoring and alerting are needed to identify that non-event.
How is EDI 997 different from EDI 824?
EDI 997 acknowledges receipt and translation of an EDI transmission, while EDI 824 indicates whether an invoice was accepted or rejected by the accounts payable system.
Related topics
Do you work in a sector with its own specific needs?
Take a look at the SEEBURGER range of industry-specific solutions
