EDI 997 Functional Acknowledgment

edi 997An EDI 997 Functional Acknowledgment is an electronic version of a receipt. The Functional acknowledgment tells a sending trading partner that a receiving trading partner has in fact successfully received EDI transactions. For example, when a buyer sends a supplier an 850 Purchase Order, the buyer will want the supplier to send a 997 Functional Acknowledgment back to indicate that the Purchase Order was received.

How the Functional Acknowledgment Works

Part of the EDI Functional Acknowledgment document will contain envelope information. The envelope information specifies which company is sending the document and which company is receiving the document. The sending and receiving companies are called trading partners because they exchange or “trade” the EDI Functional Acknowledgment and Functional Acknowledgments.

EDI is a mature electronic document format that has been carefully defined both by the companies that require their trading partners to use EDI and by standards bodies. The two recognized standards for EDI are ANSI X.12 and UN/EDIFACT. ANSI X.12 is by far the most widely used standard in the United States. UN/EDIFACT is more popular outside the United States, although it is used by US automotive manufactures.

Each EDI 997 Functional Acknowledgment document will have data organized into segments and data elements. Each segment contains at least one data element. Each data element is a data field. Examples of data elements on the Functional Acknowledgment include vendor number, item, quantity, price per item, street address, city, state and zip code, just like on a paper Functional Acknowledgment. The standards bodies have allowed for every conceivable possibility for data on the EDI Functional Acknowledgment document. Any one company will use a small subset of the available choices within the ANS X.12 or UN/EDIFACT standards.

Each company that requires its suppliers to use EDI will have an EDI Guide or mapping document. The EDI Guide will specify each segment and data element, the allowable values for each, and the applicable business rules that must be followed. EDI guides are detailed and extensive. It is not unusual for an EDI Guide to be more than 100 pages long.

Other Common X12 EDI Transactions

Need to send barcode labels?

Ready-to-print GS1-128 (UCC 128) barcode shipping labels are generated from both the MyB2B and B2BWorks EDI services, or from most file formats including CSV, Excel, X-12 and EDIFACT EDI, XML,text and custom format files.

Get a fast FREE QUOTE to find out how CovalentWorks can help you meet your EDI needs.

Complete EDI Solutions

Responsive Support Staff

Fast and Simple Setup

I'm Interested In a Personal Demo

EDI Solution Comparison

Comparison Item




Turnkey solution ✓* ×
Web-based software included ×
Web-based portal × ×
Interfaces to other systems Optional ×
IT support included × ×
Transaction mapping ✓** ✓** ×
GS1-128 bar code labels ×
Trading partner testing ×
EDI VAN, AS/2, FTP ✓***
Training ×
Internet access from anywhere
Unlimited number of users
Month to month agreement
Free U.S. based support

*IT support required during testing for B2BWorks.

**MyB2B and B2BWorks include mapping for all transaction types for any partner in the world.

***EDI VAN service is included at no charge with both MyB2B and B2BWorks.

Can't Find What You're Looking For?

Ask A Question
  • Using a web based EDI program has saved our company time, money and a lot of headaches. Software updates and configurations are no longer a thorn in my side, thank you Covalent Works!

    Cher Gray-AlderferController, Christine Taylor Collection

  • Our switch to Covalent Works was a fantastic move for both us and our customers. Covalent has provided excellent cost effective service, and meets all our EDI needs. Thank you, and we look forward to the same great service for years to come.

    Brian DickeyPresident, Bio Clinical Labs