Let’s say you want to route a batch in the ILINX Capture workflow depending on the value of a certain index. Maybe this is an AP solution and you want to route to a different queue based on document type. Here is the simple way to do that:
This is it. The final installment. The end. Our tunnel of light leading us to the promise land of perfect integrations with Serendipitous Cerebration as our Virgil guiding us through the Malebolge of Content Management.
Once we got what we felt was all of the needed information from the client as to their expectations and requirements. We formulated a solid battle plan, sharpened our keyboards, and forged ahead with a spirit steeled on the principle of “Rat’s Head, Ox’s Neck”.
Serendipitous Cerebration as a problem solving technique can only be applied in the rare cases when normal logical troubleshooting has failed. As much as we hate to admit it, when all logical problem solving avenues have been exhausted and our troubleshooting prowess to a flummoxed state of tentation, this is when we begin to enter the realm where serendipitous cerebration hides in dark, dank crevasses. In reviewing this project, our hopes are that you can see how the process of Serendipitous Cerebration can develop.
I recently worked on a team tasked with a software integration project that connects invoices from between some Accounting software to ILINX® Content Store. The integration software was used for pulling invoice values from both our AP and AR invoices for modifying the image indices for the stored content in ILINX Content Store.
Oracle is rolling out best-practice ERP AP invoice processing solution accelerators as part of their 11g Fusion Middleware offering. Called “adapters”, these ERP software components are available for Oracle E-Business Suite, PeopleSoft, and Siebel.
The accelerators are a mechanism to ensure scanned invoices reach a backend ERP system for final handling even when there are issues in the invoice data gathered using OCR forms recognition during scanning. This allows for minimal user exception handling or intervention prior to each invoice arriving in the ERP system. The idea is to simply load the scanner with invoices, press a button, and then handle the invoices once they arrive in the backend.
In order for this approach to work, Oracle’s solution accelerators use XML documents to contain header and line invoice data. The XML documents are combined with business rules in an Oracle BPEL Process Manager workflow that automatically massages the data into a format that will be accepted by the ERP import functionality such as the Oracle EBS open interface table import. The invoice image resides in the Oracle IPM system.
In the case where data can’t be massaged sufficiently for insert, the invoice is keyed from image from within the BPEL workflow. Invoices that directly insert into the ERP system arrive either ready for validation, matching, payment, coding, etc., or are placed on hold with a hold code and a hold reason code. Some sample hold and reason codes are:
|Purchase Order||PO must be valid and open.
PO vendor must match invoice vendor.
|IPM_INVALID_PO_HOLD||INVALID PO NUM
INCONSISTENT PO SUPPLIER
|Supplier||Supplier is required.
Supplier must exist in vendor master.
Supplier ID and supplier site ID must match.
There are many more business rules that operate on each invoice inside of workflow that meet the requirements of the ERP system.
Oracle has created a flash demo of a scan to EBS process at:
Oracle has also created a PDF document that highlights the E-Business Suite Adapter:
As an Oracle partner, ImageSource has begun to implement these solutions in the field.
Senior Systems Engineer