Oracle® Fusion Middleware

Oracle WebCenter Forms Recognition/Capture Integration Guide

11g Release 1 (11.1.1)

E49971-01

November 2013

Oracle WebCenter Forms Recognition is a learning-based solution that uses intelligent data capture capabilities to recognize, categorize, and extract information from documents. WebCenter Forms Recognition automatically extracts metadata values needed for workflow routing from document images, along with header level and line item data and validates the metadata against a database (such as a line of business application's database) to confirm accuracy.

Together with WebCenter Capture and WebCenter Content: Imaging capabilities, WebCenter Forms Recognition facilitates processing large volumes of business documents to automate data extraction and minimize the need for human intervention.

This document describes how to configure Capture components for use with WebCenter Forms Recognition. WebCenter Forms Recognition can be used with Capture 11g or 10g releases and in a variety of automated imaging solutions. This guide uses an Invoice Processing use case in its examples.

This document covers the following main sections:

- Section 1, "Configuring WebCenter Forms Recognition Integration with Capture 11g"

- Section 2, "Configuring WebCenter Forms Recognition Integration with Capture 10g"

- Section 3, "Documentation Accessibility"

1 Configuring WebCenter Forms Recognition Integration with Capture 11g

This section covers the following topics:

- Section 1.1, "Capture 11g Integration Overview"

- Section 1.2, "Task 1: Configure an Invoices Workspace and Elements"

- Section 1.3, "Task 2: Configure Client Scanning of Invoices"

- Section 1.4, "Task 3: Configure Commit Processing"

- Section 1.5, "Task 4: Test the Client Profile and Commit Profile"

- Section 1.6, "Task 5: Configure Import Processing of Emailed Invoices"

- Section 1.7, "Task 6: Configure Document Conversion Processing"

- Section 1.8, "Task 7: About Configuring Recognition Processing for Document Separation"

- Section 1.9, "Task 8: About Configuring WebCenter Forms Recognition to Process the Committed Documents"

- Section 1.10, "Related Capture 11g Integration Documents"

1.1 Capture 11g Integration Overview

Figure 1 illustrates a Capture workspace configuration for manual and automated capture, conversion, and commit of invoices for subsequent Accounts Payable processing.

Figure 1 Example Forms Recognition Integration With Capture 11g

1. Invoices enter a Capture workspace through one of several manual or automated paths:

1. Capture Client: An Accounts Payable clerk scans paper invoices using a client profile. Because scanning always creates image documents, no document conversion is needed.

2. Email: Vendors email invoices as attachments to email messages. In Capture, an email Import Processor job imports the attachments and creates batches for them, then sends the batches to the Document Conversion Processor to ensure image format for Forms Recognition processing. (Invoice documents already in image format pass through document conversion unchanged.)

2. A commit profile commits the emailed or scanned invoice documents to a folder. The Capture commit outputs each invoice document as a multiple page TIFF file with a unique name.

3. WebCenter Forms Recognition imports the image files from the Capture commit folder and processes them.
WebCenter Forms Recognition monitors the Capture commit folder, importing image files it finds, parsing their filename metadata, and processing them through OCR, classification, and extraction. It then exports processed data to an export folder. The export includes:

- A TIFF image file for each processed document, unchanged from its Capture commit.

- An XML file for each processed document, containing values extracted by WebCenter Forms Recognition. For example, XML files for invoices might contain detailed information such as line item values.

- A CSV file that identifies, on a batch level, the location of image and XML files and key metadata values.

4. Oracle Imaging's Input Agent imports the CSV, image, and XML files into Imaging.
Typically, image files become viewable in the Imaging Viewer, and each XML data file is stored in Imaging as a supporting document. In Imaging, workflow processing is initiated that processes the XML data.

1.1.1 System Requirements for Capture 11g Integration

Integrating Oracle WebCenter Capture 11g with WebCenter Forms Recognition requires the following components:

- Oracle WebCenter Capture 11g Release 1 (11.1.1.8.0 or later)

- Oracle WebCenter Forms Recognition 11g Release 1 (11.1.1.8.0 or later), including a project

- Oracle WebCenter Content: Imaging (referred to as Imaging) 11g Release 1 (11.1.1)

Prerequisites for Invoices Use Case

To work with this use case, you need the following:

- Invoice images, such as TIFF or PDF files, to import in the client and to attach to email messages.

- An email server account from which to import email messages.

- A location to which to commit files. For testing purposes, this might be a shared folder on your network, such as C:\WFR_Projects\AP\Import.

Note:

The instructions in this section assume one invoice per document, which is standard. If you plan to capture multiple invoices contained in one document, see information in Section 1.8 about configuring the Recognition Processor to separate the invoice documents. Each invoice within the multiple invoice document must contain a separator coversheet as its first page, and the coversheet must contain a separator patch code or bar code.

1.2 Task 1: Configure an Invoices Workspace and Elements

Begin by creating the structure and building blocks for the invoices use case. For more information about these tasks, see Oracle Fusion Middleware Managing Oracle WebCenter Capture.

1. Create a workspace.
Click the Add button in the Capture Workspaces pane, and enter a name (for example, Invoices). Select the new workspace.

2. On the Metadata tab, add a metadata field to pass an organization ID value.

1. Click the Add button in the Metadata Fields table.

2. Enter Org ID as the field name.

3. In the Auto Populate Type field, select Default Value.

4. In the Default Value field that becomes available, enter a value that represents the organization ID for the documents being captured (for example, 204).

5. Click Submit to complete creating the metadata field.

3. On the Classification tab, add a document profile to pass the organization ID metadata value.

1. Click the Add button in the Document Profiles table.

2. Enter Invoice Documents in the Name field.

3. Move the Org ID field you created in the previous step to the Selected Metadata Fields box.

4. Click Submit to complete creating the document profile.

1.3 Task 2: Configure Client Scanning of Invoices

Configure a client profile that client users can use to scan and import invoices.

1. On the Capture tab, create a client profile by clicking the Add button in the Client Profiles table.

2. Select settings on the General Settings train stop.

1. In the Profile Type field, select 2 - Capture and Index.

2. Enter a Profile Name (for example, Invoices).

3. In the Batch Prefix field, enter a prefix (for example, INV-).

3. Select settings on the Image Settings train stop.

1. In the Default DPI field, select 300.

2. Select Convert to Image Format in the Non-Image File Import Action field. This will allow you to import non-image files such as PDF files, and Capture will automatically convert them to image format. (Image format is required by WebCenter Forms Recognition.)

3. In the DPI field under Non-Image Conversion options, select 300.

4. Select settings on the Document Indexing Settings train stop.

1. In the Document Creation Option field, select 4 - Prompt User.

2. In the Document Profiles field, select the Invoice Documents profile you created in Section 1.2.

Figure 2 Client Profile for A/P Clerks to Manually Scan Invoices

5. On the Security train stop, add yourself to the client profile.

6. On the Post-Processing train stop, select Commit Processor in the Batch Processor field.

7. Click Submit to complete the client profile.

1.4 Task 3: Configure Commit Processing

Follow these steps to configure a text file commit that commits the images to a folder. Because an actual text commit file with metadata values is not needed, you configure the commit profile so it does not create a text file.

1. On the Commit tab, create a commit profile by clicking the Add button in the Commit Profiles table.

2. Specify settings on the General Settings train stop.

1. In the Commit Profile Name field, enter a name (for example, Commit Invoices).

2. In the Commit Driver field, select Text File.

3. In the Document Output Format field, select TIFF Multi-Page.

4. In the Default Date Format field, enter yyyyMMdd. This is the format that WebCenter Forms Recognition expects.

3. Select the Commit Driver Settings train stop to configure settings specific to text file commits.

4. On the Text File Folder tab, select the Do not create Commit Text File field.

5. On the Document Folder tab, specify a location such as a shared network folder in the Document Folder field. (This is the folder from which WebCenter Forms Recognition will import the committed invoice documents.)
Select the Create a folder per committed batch field.

6. On the Document File Naming tab, configure how invoice documents are named upon commit.

1. Select the Name document file based on metadata field values field.

2. Move the following fields to the Selected Fields box and order them as follows:
<Batch Name>

<Document ID>

Org ID

<Batch Creation Date>

3. In the Field Delimiter field, enter an _ (underscore) character.

Figure 3 Commit Profile for Writing Invoice Documents to a Folder

7. Click Submit to save the commit profile.

1.5 Task 4: Test the Client Profile and Commit Profile

Now test the profiles you configured. For more information about client use, see Oracle Fusion Middleware Using Oracle WebCenter Capture.

1. Sign in to the Capture client.

2. Select the client profile you created (for example, Invoices).

3. Capture one or more invoices.

- If scanning invoices, the Document Creation Option window displays each time you scan.

- If scanning one or two page invoices, choose the One Page or Two Pages option, respectively.

- If scanning multiple page invoices, include a blank separator page between invoices, and choose the Variable Number of Pages option.

- If importing invoices, select the Create one document per import file option when prompted for an import option. Note that you can import PDF files in addition to TIFF files, because you selected Convert to Image Format in the Non-Image File Import Action field in step 3 in Section 1.3.

4. Review, then release a batch.

Figure 4 Use the Capture Client to Test Invoices Client Profile Settings

5. Verify the commit. Click the Refresh Batch List button.

1. The batch was successfully committed if it was removed from the batch pane list. Open the document folder you specified in the commit profile in Section 1.4 and verify that the documents (but no text file) were committed to the folder.

2. If the batch remains and displays an error (red x) icon, right-click the document and select Display Batch Errors. For example, an error may have occurred in committing to the shared network folder.

1.6 Task 5: Configure Import Processing of Emailed Invoices

Now that you have configured manual invoice scanning/importing, configure the automated portion of the use case. In this task, configure how invoices attached to email messages are imported and sent for processing.

1. On the Capture tab of your workspace, click the Add button in the Import Processor Jobs table.

2. Complete settings on the General Settings train stop.

1. In the Import Job Name field, enter a name (for example, Import Invoices).

2. In the Batch Prefix field, enter a prefix (for example, INV).

3. In the Import Source field, select Email Source.

4. In the Import Frequency field, select Every 30 seconds. Then deselect the Online field above. When online, the import processor job monitors the specified inbox folder at the specified import frequency for files to import. When you are ready, you will change the job to Online.

Figure 5 Import Processor Job for Importing Invoices Attached to Email Messages

3. Select the Import Source Settings train stop and complete settings on the Email Accounts tab.

1. In the Email Server Name field, enter a DNS name or IP address (for example, address@example.com).

2. Click the Add button in the Email Accounts to Process table.

3. In the Email Address and Password fields of the Add/Edit Email Account window, enter an address and password.

4. Click Verify to verify the address/password entry. A message displays that the email account connection was successful. Click OK.

4. On the Message Filters tab, specify the folder to process in the Folders to Process field.
For example, you might specify inbox/invoices to import email messages stored in an invoices folder in the email inbox.

Caution:

Be sure to specify a limited folder from which to import. Otherwise, Capture may attempt to process an entire inbox, which could result in unintended consequences.

5. On the Processing tab, optionally restrict the type of attachments to be imported.
By default, the Include attachments matching these mask(s) field is set to *.* (all attachments are processed). To restrict import to certain file types, enter their extensions. For example, enter *.TIF;*.PDF to import all email attachments with a TIF or PDF extension.

6. On the Post-Processing tab, leave the default settings selected, which will delete email messages after they are successfully imported but retain email messages that fail import.

7. Click Submit to complete creating the import processor job.

8. When ready to begin importing, ensure there are email messages with attached documents in the specified inbox folder. Select the job in the Import Processor Jobs table and click the Toggle Online/Offline button until the job's status changes to Online.

9. Start the client. Wait about a minute for imported batches to display in the batch pane. If they do not appear, check your email inbox folder settings.

10. To stop importing, select the job in the Import Processor Jobs table and click the Toggle Online/Offline button until its status displays as Offline.

1.7 Task 6: Configure Document Conversion Processing

Invoices in non-image formats (such as PDF) that arrive in Capture attached to email messages need to be converted to image format to be processed by WebCenter Forms Recognition. In this task, configure a document conversion processor job to automatically convert documents from PDF to TIFF format.

1. On the Processing tab, click the Add button in the Document Conversion Jobs table.

2. Complete settings on the Document Selection train stop.

1. In the Name field, enter a job name (for example, Convert Non-Images).

2. In the Documents to Convert field, choose Selected non-image documents. Enter *.pdf in the File Name Filter field.

3. On the Output Format train stop, select TIFF: black and white in the Output Image Format field.

4. On the Post-Processing train stop, select Commit Processor in the Batch Processor field under the When there is no system error options. This setting will direct successfully converted batches to the commit profile.

5. Click Submit to complete creating the document conversion processor job.

6. Set the import processor job to direct imported batches to the document conversion job.
Click the Capture tab and edit the import processor job. On the Post-Processing train stop, select Document Conversion Processor in the Batch Processor field, then select the conversion processor job you created in the Batch Processor Job field. Click Submit.

7. Verify the document conversion processor job.
Ensure there are email messages with attached documents in the specified inbox folder and change the import processor job's status to Online. Note that it will take a little longer for batches to be imported, converted, and committed. Check your commit folder for processed results.

1.8 Task 7: About Configuring Recognition Processing for Document Separation

If the invoice documents imported as attachments may contain multiple invoices within a single file, you can configure a Recognition Processor job to separate the invoice documents, as described in this section. You can skip this section if your invoice processing configuration will always include one invoice per document.

Below is a summary of this task's configuration, which includes additional document conversion and recognition processing steps for separating and organizing multiple invoice documents. For more information, see Oracle Fusion Middleware Managing Oracle WebCenter Capture.

1. Ensure that each invoice within a multiple invoice document that arrives in Capture contains a separator coversheet as its first page, and the coversheet contains a separator patch code or bar code.

2. On the workspace's Processing tab, create a recognition processor job that includes the following settings.

- On the Document Organization train stop, set an organization type of Separator pages.

- On the Document Processing train stop, configure an invoice coversheet separator page that detects either a patch code or a bar code for separation.

- Set post-processing to go to the Commit Processor when there is no system error.

3. On the workspace's Processing tab, edit the document conversion job for this use case.
Because the Recognition Processor expects a single image document, you must configure the Document Conversion Processor job to merge all documents into a single document so that the Recognition Processor can organize the documents in the batch.

- On the Document Merge Options train stop, select the Merge all documents in the Batch Merge Option field.

- Set the Document Conversion Processor job's post-processing to go to the Recognition Processor job when there is no system error.

1.9 Task 8: About Configuring WebCenter Forms Recognition to Process the Committed Documents

After completing these tasks, configure WebCenter Forms Recognition to import the committed invoice documents, extract and validate their data, and store the documents in WebCenter Content Imaging. See the WebCenter Forms Recognition documentation listed in Section 1.10. For an A/P invoice solution, see the Oracle Fusion Middleware Oracle WebCenter Forms Recognition AP Project Guide.

1.10 Related Capture 11g Integration Documents

See the following documents for information related to a WebCenter Forms Recognition/Capture 11g integration.

Oracle WebCenter Capture

- Oracle Fusion Middleware Managing Oracle WebCenter Capture

- Oracle Fusion Middleware Using Oracle WebCenter Capture

Oracle WebCenter Forms Recognition

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Installation Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition AP Project Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Runtime Server User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Designer User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Verifier User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Web Verifier User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Scripting User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Product Migration Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition AP Project Migration Guide

Oracle Imaging and Process Management

- Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management

2 Configuring WebCenter Forms Recognition Integration with Capture 10g

This section includes the following sections:

- Section 2.1, "Capture 10g Integration Overview"

- Section 2.2, "Task 1: Configure Capture Index Fields For Autopopulating"

- Section 2.3, "Task 2: Configure the Capture Macro or VBScript"

- Section 2.4, "Task 3: Configure the Capture 10g Commit Profile"

- Section 2.5, "Task 4: Configure WebCenter Forms Recognition to Process the Committed Documents"

- Section 2.6, "Related Capture 10g Integration Documents"

2.1 Capture 10g Integration Overview

Below are the main steps by which documents are captured, autopopulated, and committed by Capture 10g, then imported, processed, and exported by WebCenter Forms Recognition, and finally imported into Imaging.

1. Documents enter Capture via one of several scenarios. Documents can consist of single or multiple pages, and may include a patch code or bar code on their first page.
For example, users might scan invoices using Oracle Document Capture, or vendors might email invoices to an Accounts Payable account. See Section 2.1.1 for configuration scenarios.

2. In Capture 10g, documents are separated and index fields are autopopulated.
Depending on configuration and Capture components used, document separation occurs automatically or by users, who can separate or join documents on-the-fly by pressing a specified keyboard shortcut (hot key).

Instead of indexing, key values such as a unique reference number (URN) and batch name are typically autopopulated by Capture.

3. Documents are committed from Capture via a text file commit profile.
The commit creates a folder for the batch and outputs each document as a single or multiple page TIFF file, named using its autopopulated values, including its unique reference number.

4. WebCenter Forms Recognition imports the image files from the Capture commit folder and processes them.
It monitors the Capture commit folder, importing image files it finds, parsing their filename metadata, and processing them through OCR, classification, and extraction.

5. WebCenter Forms Recognition exports processed data to an export folder. The export includes:

- A TIFF image file for each processed document, unchanged from its Capture commit.

- An XML file for each processed document, containing values extracted by WebCenter Forms Recognition. For example, XML files for invoices might contain detailed information such as line item values.

- A CSV file that identifies, on a batch level, the location of image and XML files and key metadata values.

6. Oracle Imaging's Input Agent imports the CSV, image, and XML files into Imaging.
Typically, image files become viewable in the Imaging Viewer, and each XML data is stored in Imaging as a supporting document. In Imaging, workflow processing is initiated that processes the XML data.

2.1.1 Capture 10g Integration Scenarios

Below are several configurations for capturing invoice documents using Capture 10g components.

Centralized Capture Using Oracle Document Capture

In this scenario, users use Oracle Document Capture to scan invoices centrally. A Capture 10g/WebCenter Forms Recognition scan macro allows users to scan, review, and commit images without indexing. For configuration information, see Section 2.3.1.

Distributed Capture Using Import Server (Via Email, MFD, or Fax)

In this scenario, invoices are received through any of these methods:

- via an email alias, such as AP@example.com

- scanned remotely using an MFD (Multi-Function Device) to a network folder

- transferred by fax to a network folder

In each case, Oracle Document Capture's Import Server monitors the folder or email alias inbox and imports the documents using settings stored in the Capture 10g/WebCenter Forms Recognition Import Server macro. Key values are autopopulated, and Commit Server commits the invoices to a folder for WebCenter Forms Recognition import. For configuration information, see Section 2.3.2.

Distributed Capture Using Oracle Distributed Document Capture

In this scenario, users use Oracle Distributed Document Capture to scan invoices at remote locations, which are then sent for committing via Commit Server and centralized processing. A Capture 10g/WebCenter Forms Recognition VBScript assigns each document its unique reference number. For configuration information, see Section 2.3.3.

2.1.2 Overview of Capture 10g Integration Tasks

Configuring a Capture 10g/WebCenter Forms Recognition integration involves the following key tasks:

1. Configure Capture index fields to be autopopulated. These values will be committed with images via their filenames. See Task 1: Configure Capture Index Fields For Autopopulating.

Note:

If you imported a file cabinet configuration using the Capture Import/Export utility as part of a solution, these index fields may already be configured.

2. Configure settings in the Capture scan macro and scan profile, Import Server macro and batch job, or Oracle Distributed Document Capture VBScript and scan profile.
See Task 2: Configure the Capture Macro or VBScript.

3. Configure the Oracle Document Capture commit profile.
The commit profile must be configured using the commit text file driver and set to commit documents to a network folder that WebCenter Forms Recognition monitors. See Task 3: Configure the Capture 10g Commit Profile.

4. Configure WebCenter Forms Recognition to import the document image files, as described in the WebCenter Forms Recognition documentation. See Task 4: Configure WebCenter Forms Recognition to Process the Committed Documents.

2.1.3 System Requirements for Capture 10g Integration

Integrating Oracle Document Capture 10g with WebCenter Forms Recognition 11g requires the following components:

- Oracle Document Capture 10g Release 3 (10.1.3.5.0 or later)

- Oracle Distributed Document Capture 10g Release 3 (10.1.3.5.0 or later); required for remote scanning only

- WebCenter Forms Recognition 11g Release 1 (11.1.1.8.0 or later), including a project

- Oracle WebCenter Content: Imaging (referred to as Imaging) 11g Release 1 (11.1.1)

- Capture/WebCenter Forms Recognition macros and VBScript, contained in the ..\Projects\AP\Capture Integration subfolder in the WebCenter Forms Recognition installation folder.

2.2 Task 1: Configure Capture Index Fields For Autopopulating

To commit batches, index values are autopopulated in Capture. A scanned or imported document's index values are then passed to WebCenter Forms Recognition via its filename. Autopopulating and passing the index values requires these main steps:

- Add the index fields in Capture as described in this section.

- When configuring the Capture text commit profile, select each Capture field on the Document File Naming tab to pass it to WebCenter Forms Recognition via an image file name, as described in Section 2.4.

- In the WebCenter Forms Recognition INI file (IMP section), identify these fields' position so WebCenter Forms Recognition can properly parse the file name into fields. See the WebCenter Forms Recognition documentation for more information.

Table 1 lists Capture fields available for autopopulating by the macros. Note that the URN field, which will contain the document's unique reference number generated automatically by the macro or VBScript, is required.

Table 1 Capture Fields for Autopopulating

Capture Field

Values

Required or Optional

How Used

URN

Data Type: Alphanumeric

Max Value: 32

Required

Unique identifier that must be passed through to WebCenter Forms Recognition upon commit.

Batch Name

Data Type: Alphanumeric

Max Value: 25

Optional

Pass through the batch name, for tracking purposes.

Scan Date

Date Type: Date

Optional

Pass through the scan date, for tracking purposes.

Other default fields to autopopulate, such as Organization, CompanyCode, or DepartmentCode

Data Type: Alphanumeric

Optional

Pass through standard values, such as organization, or company or department code.

Follow these steps to add key index fields to Capture.

1. In Capture Administration, select File Cabinets from the Admin menu.

2. In the tree, select the file cabinet to which to add index fields.

3. Click Add. Complete fields in the Add New Index Field dialog box.

4. Create fields as listed in Table 1.

2.3 Task 2: Configure the Capture Macro or VBScript

This section covers the following topics:

- Section 2.3.1, "Configure the Capture Scan Macro"

- Section 2.3.2, "Configuring the Import Server Macro"

- Section 2.3.3, "Configuring the Oracle Distributed Document Capture VBScript"

2.3.1 Configure the Capture Scan Macro

The scan macro enables users to scan and commit batches directly to a WebCenter Forms Recognition import folder, without requiring the use of the Oracle Document Capture Index component.

About Document Separation With the Scan/Commit Macro

When batches include multiple page documents, you must configure how Capture identifies the start of new documents.

You can configure document separation using the following methods:

- Physically include a printed patch code or bar code on a page and specify it for detection in the scan profile. Oracle Document Capture searches for a patch code or the specified bar code during batch scanning, and if found, applies the virtual patch code specified in the macro (II, III, or T). If no patch or bar codes are detected during scanning, the scan macro assumes that the batch is comprised of single page documents.

- Include blank separator sheets between documents and specify a Blank Page size threshold in the scan macro. Pages whose size is less than this setting are considered blank and treated as document separators, as if a patch code were physically printed on them.

- Allow users to assign a virtual patch code to any page during document review, by pressing a hot key that switches between starting a new document (if no patch code is applied) or joining the document with the previous document (if a patch code has been applied).

Importing the Scan/Commit Macro

Follow these steps to import the scan/commit macro into Oracle Document Capture.

1. Locate the scan macro for your configuration. See Section 2.1.3.
Two versions of the scan macro are provided:

- WFR-Scan-ISIS-Macro.bas, for use with Scan for ISIS

- WFR-Scan-Adrenaline-Macro.bas, for use with Scan for Adrenaline

2. In Oracle Document Capture, import the WebCenter Forms Recognition scan macro.

1. From the System menu, select Manage Macros.

2. In the Category field of the Manage Macros screen, select Scan for ISIS or Scan for Adrenaline.

3. Click the Import button on the toolbar.

4. In the Import Macro File dialog box, select the appropriate macro (.bas) file. Add an optional description and click OK.

The imported scan macro is listed for the selected category.

3. Close the Manage Macros screen.

Configuring Scan/Commit Macro Settings

After importing the scan macro, follow these steps to configure its settings.

1. In the Manage Macros screen of Oracle Document Capture, select the scan macro from the list of macros and click the Setup button on the toolbar.

2. In the Scan/Commit Macro Settings screen shown in Figure 6 and described in Table 2, specify commit batch settings.

1. Specify if batches are to be committed directly after scanning or if users will review, edit, and commit them.

2. Specify how multiple page documents are identified and separated within batches. Also specify if users can create or join documents when reviewing and if separator sheets should be retained in documents.

3. Specify how document files are to be autopopulated, by identifying the Capture index fields you created in Section 2.2, "Task 1: Configure Capture Index Fields For Autopopulating."

3. Click OK.

Figure 6 WFR Scan Macro Settings

Table 2 Scan/Commit Macro Settings Screen

Element

Description

Document Separation Settings

Patch Code

Select a patch code to be applied virtually to identify the start of new documents.

Choose from the following patch codes: Patch II, Patch III, and Patch T.

Set Patch Code Using

Interactive Hot Key

Optionally specify a hot key that users can press for the selected page when reviewing batches. Pressing the hot key either:

- inserts a virtual patch code if none was detected, starting a new document.

- removes detection of a previously detected patch code or removes a previously applied virtual patch, merging the selected document with its previous document.

Note: This interactive hot key option requires that the Prompt User Upon Closing Review field be selected, which allows users to edit and review batches after scanning.

Bar Code Value

To identify new documents by bar code during batch scanning, enter the bar code value to detect. In the scan profile, configure the bar code type and detection method. When a barcode of this value is detected on a page, the specified virtual patch code is applied.

Note: Detected bar code values are used for document separation only. The value cannot be passed via Capture as an index value.

Blank Page

To identify new documents by blank separator pages, enter the byte threshold at which to detect a blank page. Any page of a size less than this setting is considered blank and is used as a document separator, as if a patch code is physically printed on it.

A value of zero indicates that this setting is not in use. You may need to experiment with this setting as file size varies with resolution. The recommended starting value is 3000 bytes.

Include Separator Pages in Documents

Select this field to retain pages on which a patch code or bar code is detected. By default, this setting is deselected. Note that blank pages detected as document separator sheets are automatically removed from documents.

If patch codes or bar codes are present on otherwise blank pages, leave this field deselected so that separator sheets are removed from documents.

User Prompt Field 1

Define a prompt field linked to a defined Capture picklist. If you specify a prompt in these fields and/or under User Prompt Field 2 options, a dialog box displays when users close the batch review window or immediately after they scan, depending on the Index Documents field selection. This dialog box requires the user to select a value from the picklist, then populates the specified Capture field with the selected value for all documents in the batch.

Picklist

Select the picklist from which users will be required to select an index value. Note that this picklist must exist in the Capture file cabinet.

Field Name

Enter the name of the Capture index field to which to apply the selected picklist value.

Note that you must enter this field name as it is defined in the Capture file cabinet. Validation does not occur until commit.

Index Documents

Prompt User Upon Closing Review

After scanning, allow users to review and edit document batches before committing them. When selected, users are prompted to commit batches when they close the review window.

Automatically After Scanning

Commit each batch immediately after the user has scanned it, without allowing the user to review and edit its documents.

Batch Status

Specify a status to assign to batches upon commit (optional).

Auto-Populate Fields

Unique Reference Number

Enter the Capture index field (created in Section 2.2) to contain the document's unique reference number. This number will uniquely name document files upon their commit into the Capture commit/WebCenter Forms Recognition import folder. The scan macro generates this number automatically. This field is required.

When configuring the text commit profile (described in Section 2.4), select this field on the Document File Naming tab to pass this unique image identifier to WebCenter Forms Recognition via image file name.

Note: Enter the index field name exactly as it exists in Capture Administration, including case.

Batch Name

Enter the Capture index field (created in Section 2.2) to contain the batch's name. This field is optional and needed only to include the batch name as part of document names.

To pass this batch name to WebCenter Forms Recognition via image file name, select this field on the Document File Naming tab when configuring the text commit profile, as described in Section 2.4.

Enter the index field name exactly as it exists in Capture Administration, including case.

Default Values

Define one or more static values to pass to WebCenter Forms Recognition via image file name. Separate multiple field definitions with a ; (semi-colon).

For example, you might include the following default value to pass an organization's ID to WebCenter Forms Recognition:

CompanyCode=2222

Scan Date

To pass the scan date to WebCenter Forms Recognition via image file name, enter the Capture index field (created in Section 2.2) to contain the batch's scan date.

This field is optional and needed only to include the scan date as part of document names.

To pass this scan date WebCenter Forms Recognition via image file name, select this field on the Document File Naming tab when configuring the text commit profile, as described in Section 2.4.

Format

Select the date format to use.

User Prompt Field 2

Define a prompt field linked to a defined Capture picklist. If you specify a prompt in these fields and/or under User Prompt Field 1 options, a dialog box displays when users close the batch review window or immediately after they scan, depending on the Index Documents field selection. This dialog box requires the user to select a value from the picklist, then populates the specified Capture field with the selected value for all documents in the batch.

Picklist

Select the picklist from which users will be required to select an index value. Note that this picklist must exist in the Capture file cabinet.

Field Name

Enter the name of the Capture index field to which to apply the selected picklist value.Note that you must enter this field name as it is defined in the Capture file cabinet. Validation does not occur until commit.

Commit Options

Commit Batch

Select to commit the batch, rather than make it available for indexing.

Use Commit Server

Mark the batch for commit processing by the Commit Server. If deselected, batches are committed immediately from Oracle Document Capture.

Do not Commit Batch

If selected, the batch will not be committed. Instead, the batch will be available for indexing in Capture's Batch Indexing.

Configuring the Scan Profile

After configuring the macro's settings, follow these steps to incorporate it in a scan profile.

1. In Oracle Document Capture, choose Manage Scan Profiles from the Scanning menu, and select a scan profile.

2. Select General options.

3. In the Macro Name field, select the macro you configured (WFR-Scan-ISIS-Macro or WFR-Scan-Adrenaline-Macro).

4. To detect a patch code or bar code during scanning, configure detection in the scan profile. For more information, see the Administrator's Guide for Oracle Document Capture.

5. Save the scan profile. Close the Manage Scan Profiles screen.

Handling Multiple Scan/Commit Macro Configurations

If you need to provide users with multiple scan/commit configuration options, follow these steps to import additional instances of the scan macro and configure them separately. For example, if users are processing batches that use different document separation methods, you will need to create multiple scanning profiles that utilize different macro settings.

1. Save the scan/commit macro (.bas) file under a new name.

2. In the Manage Macros screen, import the scan/commit macro you just saved.

3. Select the macro, click Setup, and configure this new instance of the macro with alternate settings.

4. In the Manage Scan Profiles screen, create a new scan profile and select the new macro in the Macro Name field under General options.

2.3.2 Configuring the Import Server Macro

The Import Server macro enables importing and committing documents to a WebCenter Forms Recognition import folder without using the Index component.

About Document Separation With the Import Server Macro

With this macro, you identify to Import Server how imported files are comprised (one document, single page documents, or multiple page documents). If a file includes multiple page documents (for example, a single PDF file containing documents with multiple pages that are separated with a blank page), you must configure how Capture identifies the start of new documents, by specifying a patch code to be applied and a blank page byte threshold for detection.

Note:

The Import Server does not support patch code or bar code recognition. Therefore, this macro depends upon a blank page for multiple page document separation.

Importing the Import Server Macro

Follow these steps to import the Import Server macro.

1. Locate the WFR-Import-Server-Macro.bas file.
See Section 2.1.3.

2. In the Import Server, import the WebCenter Forms Recognition macro.

1. From the Setup Menu, select Macro Manager.

2. In the Category field of the Manage Macros screen, select Oracle Document Capture Import Server.

3. Click the Import button on the toolbar.

4. In the Import Macro File screen, select the WFR-Import-Server-Macro.bas file. Add an optional description and click OK.

The imported macro is listed.

3. Close the Macro Manager screen.

Configuring Import Server Macro Settings

After importing the Import Server macro, follow these steps to configure its settings.

1. In the Macro Manager screen of Import Server, select Oracle Document Capture Import Server from the Category field.

2. Select the Import Server macro and click the Setup button on the toolbar.

3. In the Import Server/WebCenter Forms Recognition Macro Settings screen shown in Figure 7 and described in Table 2, specify commit batch settings.

1. Specify how files are comprised: of one document, single page documents, or multiple page documents.

2. For multiple page documents, specify the blank page byte threshold at which to detect blank pages and the virtual patch code value to set.

3. Specify how document files are to be autopopulated, by identifying the Capture index fields created in Section 2.2.

4. Click OK.

Figure 7 Import Server/WebCenter Forms Recognition Macro Settings

Table 3 Import Server/WebCenter Forms Recognition Macro Settings

Element

Description

File Contains

Specify how imported files are comprised:

- One document only

- Single page documents

- Multiple page documents
If a file contains multiple documents, also specify document separation options, which require a blank separator page.

Document Separation Settings

Patch Code

For multiple page documents, select a patch code to be applied virtually to identify the start of new documents. This setting specifies the patch code attribute to apply to the page if a blank page is detected.

Choose from the following patch codes: Patch II, Patch III, and Patch T.

Blank Page

To identify the start of new documents by blank separator pages, enter the byte threshold at which to detect a blank page. Any page consisting of a file size less than this setting is considered blank and is used as a document separator, as if a patch code is physically printed on it. Blank pages are not included in the document.

A value of zero indicates that this setting is not in use. You may need to experiment with this setting as file size varies with resolution. The recommended starting value is 3000 bytes.

Batch Status

Specify a status to assign to batches upon commit (optional).

This is particularly useful when batches are not being exported directly to WebCenter Forms Recognition, but may require review within Oracle Document Capture. For example, batch statuses might include Requires Review or Waiting for Commit Server.

Auto Populate Fields

Unique Reference Number

Enter the Capture index field (created in Section 2.2) to contain the document's unique reference number. (Enter the index field name exactly as it exists in Capture Administration, including case.) This number will uniquely name document files upon their commit into the Capture commit/WebCenter Forms Recognition import folder. The scan macro generates this number automatically. This field is required.

When configuring the text commit profile (described in Section 2.4), you must select this field on the Document File Naming tab, in order to pass this unique image identifier to WebCenter Forms Recognition via image file name.

Batch Name

Enter the Capture index field (created in Section 2.2) to contain the batch's name. (Enter the index field name exactly as it exists in Capture Administration, including case.) This field is optional and needed only to include the batch name as part of document names.

In order to pass this batch name to WebCenter Forms Recognition via image file name, you must select this field on the Document File Naming tab when configuring the text commit profile, as described in Section 2.4.

Scan Date

To pass the scan date to WebCenter Forms Recognition via image file name, enter the Capture index field (created in Section 2.2) to contain the batch's scan date.

This field is optional and needed only to include the scan date as part of document names.

In order to pass this scan date WebCenter Forms Recognition via image file name, you must select this field on the Document File Naming tab when configuring the text commit profile, as described in Section 2.4.

Format

Select the date format to use for the scan date.

Default Values

Define one or more static values to pass to WebCenter Forms Recognition via image file name. Separate multiple field definitions with a ; (semi-colon).

For example, you might include the following to pass an organization's ID to WebCenter Forms Recognition:

CompanyCode=2222

Configuring the Import Server Batch Job

After configuring the macro's settings, follow these steps to associate it with an Import Server batch job.

1. In Import Server, create or open a batch job by selecting Batch Jobs from the Setup menu. For example, create an email or folder-type batch job.

2. In the Server Macro field on the General tab, select the Import Server macro you configured.

3. If you configured blank page separation in the macro, select the Processing tab and select Skip page in the If invalid page found or timeout occurs field.

4. Under Commit Options on the Processing tab, select the Commit Batches field. Typically, you would also select the Use Commit Server field to off load processing to Commit Server. (Note that batches may also appear in Oracle Document Capture while waiting for Commit Server to process them.)
To route batches to Oracle Document Capture, leave the Commit Batches field deselected.

5. Save the batch job and use the Scheduler to schedule the job to be run.

2.3.3 Configuring the Oracle Distributed Document Capture VBScript

The VBScript's task is to autopopulate the URN (Unique Reference Number) for documents. Follow these steps to configure the script and a scan profile for the integration.

1. Locate the WebCenter Forms Recognition script file (WFR-ODDC-AssignURN.vbs) and save it to the ...\Document Capture\WebPages\Scripts folder.
See Section 2.1.3.

2. Open the script and search for the constant conURNField. Set its value to match the index field you added in Section 2.2 to contain the unique reference number for each document (for example, URN).
Once configured, the script assigns a system generated unique reference number to this URN field before the batch is sent.

3. In Oracle Distributed Document Capture administration, create or open a scan profile for scanning or importing documents for WebCenter Forms Recognition.

4. In the Scanning Type field under General options, select a scanning type that allows indexing: either 2 - Scan and Index Documents or 3 - Scan and Index Batches. (The script does not work if the scanning type is set to 1 - Scan Only.)

5. In the Profile Script field, select the WebCenter Forms Recognition script.

6. Under Auto Populate options, configure other fields (created in Section 2.2) to be autopopulated. For example, you might autopopulate scan date, batch name, and a default value such as an organization code.

2.4 Task 3: Configure the Capture 10g Commit Profile

After configuring how documents enter Capture, follow the steps below to configure how images and metadata are committed so WebCenter Forms Recognition can import and process them. You do this by configuring a text file-type commit profile to output images as multi-page TIFF files for import into WebCenter Forms Recognition.

1. In Capture Administration, create a commit profile.

1. From the Admin menu, choose File Cabinets and select the file cabinet.

2. Choose Commit Profiles in the left pane and click the New (sun) button from the toolbar. Enter a name for the profile and click OK.

2. In the Document Output field, select TIFF - Multiple Page. (Select this output format even if scanning single page documents.)

3. In the Commit Driver field, select Commit Text File. Click its adjacent Configure button.

4. Select settings on the General tab, as shown in Figure 8.

1. In the Commit Text File Settings screen, select the Do not create Commit Text File field.

2. In the Document Folder field, click Browse and specify the folder to which to commit images for import by WebCenter Forms Recognition.

Note:

Ensure that this path matches the path to the WebCenter Forms Recognition project's Import folder.

3. Select the Create a folder per committed batch field.

Figure 8 Commit Text File Settings, General Options

5. On the Document File Naming tab (shown in Figure 9), map all Capture autopopulated fields to pass to WebCenter Forms Recognition in image filenames.

1. Select the Name document file based on index values field.

2. Select the Unique Reference Number field you created (for example, URN) from the Available Fields list and move it to the Selected Fields list.

3. Map other fields you configured (for example, Organization, ScanDate, or the system field <Batch ID>), by selecting them in the Available Fields list and moving them to the Selected Fields list.

4. Enter an underscore (_) in the Field Delimiter field.

Figure 9 Commit Text File Settings, Document File Naming Options

For example, the following image file might be named as follows:

12_FC7C58E4E9934A82A2073571A96BB77C_1733_15122010.TIF

where:

- 12 identifies the Oracle Document Capture batch ID, useful for batch auditing in Oracle Document Capture's audit table.

- FC7C58E4... identifies the document's unique reference number, populated by the macro or VBScript.

- 1733 identifies the organization code, autopopulated as a default value

- 15122010 identifies the scan date.

6. Activate the commit profile by selecting Commit Profiles in the left pane and selecting the profile.

2.5 Task 4: Configure WebCenter Forms Recognition to Process the Committed Documents

After completing these tasks, configure WebCenter Forms Recognition to import the committed invoice documents, extract and validate their data, and store the documents in WebCenter Content Imaging. See the WebCenter Forms Recognition documentation listed in Section 2.6. For an A/P invoice solution, see the Oracle WebCenter Forms Recognition AP Project Guide.

2.6 Related Capture 10g Integration Documents

See the following documents for information related to a WebCenter Forms Recognition/Capture 10g integration.

Oracle Document Capture/Oracle Distributed Document Capture

- Administrator's Guide for Oracle Document Capture

- Administrator's Guide for Oracle Distributed Document Capture

Oracle WebCenter Forms Recognition

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Installation Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition AP Project Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Runtime Server User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Designer User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Verifier User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Web Verifier User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Scripting User's Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition Product Migration Guide

- Oracle Fusion Middleware Oracle WebCenter Forms Recognition AP Project Migration Guide

Oracle Imaging and Process Management

- Oracle Fusion Middleware Administrator's Guide for Oracle Imaging and Process Management

3 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Fusion Middleware Oracle WebCenter Forms Recognition/Capture Integration Guide, 11g Release 1 (11.1.1)

E49971-01

Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.