Inspyrus Enhanced Invoice Extraction

inspryrus tekstream

Inspyrus Enhanced Invoice Extraction

By: Karla Broadrick | Technical Architect, WebCenter Imaging Team

Oracle WebCenter Forms Recognition is not a tool that is unique to the Inspyrus Solution.  WebCenter Forms Recognition (WFR) is a tool that has been around for many years.  WFR is a key component of how Oracle enables accounts payable automation because it provides intelligent classification and extraction of invoice metadata.  Key fields such as Invoice Date, Invoice Number, Supplier, PO Number as well as line items are intelligently recognized for a large number of suppliers based on a pre-trained set of invoices.

The Inspyrus solution utilizes WFR in a “black box mode.”  This means that invoices pass through WFR where the invoice metadata is extracted but instead of being routed to the Verifier application for correction, invoices do not stop in WFR but instead go directly to the Inspyrus UI.  It is there that invoices are able to be corrected, if needed, before being routed to the applicable ERP system.

What makes the Inspyrus solution’s use of WFR different than traditional solutions is that the out of the box WFR product has been enhanced to alleviate common problems and shortcomings experienced by a large number of WFR customers.  With these enhanced invoice extraction capabilities, the Inspyrus solution brings invoice automation to the next level, one of the many reasons the solution is considered the next generation in accounts payable automation.

One of the most basic examples that long time users of the WFR product can relate to is the extraction of the PO Number field.  The way that PO Number extraction typically works is that any number of PO masks can be configured in the INI file.  The masks can be as specific (TEK#####) or generic (6 digit number) as needed.  As a best practice, I advise customers to use PO masks that are as specific as possible.

If masks can be kept very specific and the number of them kept low, WFR typically does a pretty good job of finding the PO Number on the invoice, regardless of its location.  After the PO Number is extracted, it is then validated against the ERP database to ensure that it is a valid PO.  If it is not found in the database it is flagged as invalid and will require user correction.

Where problems arise is when business needs dictate that PO masks must be generic (######) or a large number of masks are required (as often happens in larger companies with multiple systems generating PO’s).  In these cases, WFR often does not do as good a job of correctly choosing the actual PO number.  Despite clear keywords such as “Purchase Order Number” that could contextually help locate the actual PO number, WFR will often incorrectly choose another value on the invoice that matches a mask but is nowhere near any labels that would indicate a PO Number.

The Inspyrus WFR solution addresses this issue by offering a routine that enhances the out of the box invoice automation by using contextual evidence to help identify the correct PO number from the possible candidates.

TekStream recently worked with a customer that faced both of these challenges.  The screen shots below illustrate the difference between the out of the box WFR extraction and the extraction results with the Inspyrus solution.  This is just one of the many examples of ways the Inspyrus solution takes accounts payables invoice automation to the next level.

Out of the box extraction: PO Number is chosen from the text under a barcode on the page that matches one of the many masks.  The number chosen has no context to suggest it is a PO number.

inspyrus-pic-1

inspyrus-pic-2

Inspyrus extraction: PO Number is correctly chosen as the candidate following the label “P.O. #”

inspyrus-pic-3

inspyrus-pic-4

 

Contact Karla Broadrick about the Inspyrus WFR Solution Today.

We're here to help!

 

Oracle Document Capture and WebCenter Enterprise Capture

Documents Capture

Oracle Document Capture and WebCenter Enterprise Capture

By: Kevin Cocilo | WebCenter Imaging Integration Engineer

Introduction

Since WebCenter 11.1.1.8.0 was introduced, there are 2 major versions of Oracle Document Capture that are available for integration: Oracle Document Capture (ODC 10g) and WebCenter Enterprise Capture (WEC 11g). WebCenter Enterprise Capture is a browser based implementation and is part of the WebCenter stack. Oracle Document Capture is an older, stand-alone Windows server and thick client technology.

Although it should be apparent which to implement, there are some considerations to take into account, mainly supportability and your current starting point.

Supportability

Oracle Document Capture, and its web counterpart ODDC (Oracle Distributed Document Capture), are no longer covered by Oracle Premium (Nov 2013) or Extended Support (Dec 2015), but only Sustaining Support. What this means is that Oracle will only help with the product as it currently exists. Sustaining Support does not include the following:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For complete information see support sheet: http://www.oracle.com/us/support/library/lifetime-support-middleware-069163.pdf.

If you’re a new WebCenter customer, the most current offering as of this writing is version 11.1.1.9.x. And since Oracle WebCenter Enterprise Capture has been offered since 11.1.1.8.0, it’s hard to imagine a scenario where you would want to use ODC/ODDC (although it is still available for download).

A more likely scenario is that you’re facing an upgrade decision.

Upgrade & Migration Considerations

If you’re currently using an ODC integration with an earlier version of WebCenter and are upgrading to WebCenter 11.1.1.9x, here are several points to consider:

Benefits

  1. Supportability, as noted above. All of Oracle’s support models are available for Oracle WebCenter Enterprise Capture 11g.
  2. WEC definitely has the advantage of strictly having a web interface and WebLogic managed server. No more need for ODC and ODDC.
  3. Security model, control and logging are now governed by your WebLogic implementation, just like your other WebCenter Managed Servers.
  4. Patching should be easier in 11g. Patches to WEC (and OIT!) are handled through the normal OPatch method. No more registry hacks, etc. (although currently Oracle WebCenter Enterprise Capture supports only Outside In technology, no Native document conversion until 12c)
  5. Migrating configurations to higher environments is easier such as “dev” to “test” and then to “production.”

Considerations

  1. Although most of the functionality for 10g is now available in 11g, upgrading will require you to reconstruct all of your ODC services (Servers, File Cabinets, Scan and Index Profiles). In other words, there is no way to migrate ODC 10g to WEC 11g. The configuration in 11g is arranged differently than it was in 10g.
  2. Scripting for Macros. It is not possible to reuse ODC 10g macros since they are written using Visual Basic scripting and WEC uses Java scripting.
  3. Recognition Processor is still a Windows OS only proposition although it’s still a Managed Server, and not a Windows client. Support for a Linux Recognition processor is not yet published.
  4. Pay attention to requirements for Java compatibility, since the WEC Client uses a JRE plugin. In addition to Java, be aware that not all Browsers versions are supported. The following link will lead to certification and supportability links:

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=1ap4gfkd0h_4&_afrLoop=408291063482624

 

Contact Kevin Cocilo about Oracle WebCenter today.

We're here to help!