How to Add a New Field to the Forms Recognition A/P Solution Project (Doc ID 1268783.1)

Last updated on JUNE 30, 2016

Applies to:

Oracle WebCenter Forms Recognition - Version 10.1.3.5.0 and later
Information in this document applies to any platform.

Goal

Under certain circumstances it may be necessary to add an additional field to the A/P Solution Project. This field will, in all probability, be unique to a specific vendor invoice and will need to be displayed in a vendor sub class.

Before adding a new field to the A/P project, please note that only the following alterations are supported by Oracle Support:

1.) Only additions to the (Invoices) Extraction Learnset are supported.
2.) Only training of new fields in the (Invoices) Extraction Learnset is supported. Do not, under any circumstances, train or alter the structure of any of the existing base fields in the Invoices class.
3.) Only use of the default verification form, Form_Invoices_1. Custom form creation is not supported.

Overview
Information about the Verification Form (Form_Invoices_1) used by Oracle Forms Recognition Verifier:

  1. This form is inherited by all sub classes of the Invoices DocClass.
  2. It is not customizable at the sub class level, only the DocClass level.
  3. Once a field is added to the form, it is considered a required field by Verifier.
  4. Creating a new form for a sub class will result in the loss of functionality. For example, the Vendor Search would need to be recreated and added to the new form.

Any new field will need to be added to the Form_Invoices_1 in order to be trained and displayed in Verifier. If this a field unique to a specific vendor, invoices from all other vendors will be placed in a 550 state for manual verification. To avoid this scenario, there are three parameters in Designer that will be used:

Always Valid – when enabled, the field is always considered valid regardless of extracted data or even if empty. This will be applied at the project level.

Use Derived Validation – when enabled, the validation settings from the parent class (Invoices) are used. This is applied at the sub class level.

Forced Validation / Permitted – when enabled, will force validation of the field regardless of parent settings. This is applied at the sub class level.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms