{"id":31830,"date":"2015-03-10T11:32:19","date_gmt":"2015-03-10T19:32:19","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/moduleplugin-configuration\/extraction-module\/fuzzy-db-extraction\/"},"modified":"2020-11-24T09:44:56","modified_gmt":"2020-11-24T16:44:56","slug":"fuzzy-db-extraction","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/moduleplugin-configuration\/extraction-module\/fuzzy-db-extraction\/","title":{"rendered":"Fuzzy DB Extraction"},"content":{"rendered":"
Available<\/b>: on-premises, cloud<\/p>\n
This page provides an overview of the FuzzyDB plugin and its configuration in Ephesoft Transact.<\/p>\n
FuzzyDB must be added to the Extraction module and set to ON<\/strong>.<\/p>\n The FuzzyDB plugin uses a fuzzy database lookup to link your internal database to Ephesoft Transact. This allows you to pair data extracted from Ephesoft Transact with data from your internal database.<\/p>\n For example, refer to the following excerpt from a sample invoice.<\/p>\n From this invoice, Ephesoft Transact can extract the vendor name: \u201cOffice Depot\u201d. However from this document the system cannot determine your internal vendor number that you have assigned to this vendor. To match this internal information (vendor number) with the extracted information (invoice), the system can learn a database table for the list of vendors to perform automated lookups. It will then use fuzzy matching logic on the extracted information.<\/p>\n Note<\/strong>: FuzzyDB can be used for extraction or validation.<\/p>\n FuzzyDB must be set up in two places:<\/p>\n Before configuring the FuzzyDB plugin, you must first connect your database to Ephesoft Transact.<\/p>\n Note<\/strong>: The following connection (database) types are available:<\/p>\n Once you have set up your connection in the Connection Manager, you can select that connection when adding FuzzyDB extraction to a document type.<\/p>\n Note<\/strong>: This is a Document Level Field (DLF), which means it is configured at the document type level in a batch class.<\/p>\n The following options are available for mapping database data to a document:<\/p>\n In Document Fuzzy, only one database can be configured per document type.<\/p>\n<\/a>Overview<\/h2>\n
\nFigure 1. Sample Invoice<\/em><\/p>\n<\/a>Configuration<\/h2>\n
\n
<\/a>Connection Manager<\/h3>\n
\n
\nFigure 2. Add Connection<\/em><\/p>\n\n
\nFigure 3. Connection Details<\/em><\/p>\n\n
\n
<\/a>Fuzzy DB Extraction Configuration<\/h3>\n
\n
\n
<\/a>Document Fuzzy<\/h4>\n
\nFigure 4. Document Fuzzy<\/em><\/p>\n\n
\n
\nFigure 5. Map Document Fuzzy Connection<\/em><\/p>\n\n
\n
\nFigure 6. Additional Parameters Mapping<\/em><\/p>\n