CONTRL Functional Acknowledgment
An EDI CONTRL 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 CONTRL Functional Acknowledgment back to indicate that the Purchase Order was received.
EDI stands for Electronic Data Interchange. Companies use EDI to reduce the errors and costs associated with the manual keying of data, and to speed up the process of sending and receiving business documents.
EDI documents are sent and received electronically using a VAN. VAN stands for Value Added Network. 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 CONTRL 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.