20 Complete Oracle Fusion Financials Post-Installation Tasks

This section describes the Oracle Fusion Financials post-installation tasks that must be reviewed and completed before starting working with an Oracle Fusion Applications Oracle Fusion Financials implementation.

This section contains the following topics:

20.1 Set Up the Financial Reporting Center

The Oracle Fusion Financial Reporting Center provides functionality for reporting on Oracle Fusion General Ledger balances. It provides secure, self-service access to reports that use real time account information.

Design traditional financial report formats such as balance sheets, profit and loss statements, and cash flow reports. Design also nontraditional formats for financial or analytic data that include text and graphics.

The following figure shows the main components in the Financial Reporting Center: Financial Reporting, Account Monitor, Account Inspector, Smart View, Financial Reporting Workspace, and Financial Reporting Studio. These components use the Oracle Fusion General Ledger preaggregated balances as the staring data.

Figure 20-1 Financial Reporting Center

20.1.1 Components

Financial Reporting Center is comprised of numerous components:

Financial Reporting: Financial users and analysts access live reports and books or published snapshot reports and books from previously scheduled batches in a variety of formats. Other functionality includes:
- Refreshing report data using runtime points of view or parameters
- Drill through capability from parents to other parents
- Drill down to detail balances, journal lines, and subledger transactions.
Oracle Hyperion Smart View: Financial analysts view, import, manipulate, distribute, and share data from the Oracle Fusion General Ledger balances in Microsoft Excel.
Account Monitor and Account Inspector: Financial analysts monitor and track key account balances in real time at every level of the dimensions and hierarchies. These tools provide multidimensional account analysis and drill down capability.
Workspace: Reporting administrators create, open, save, and delete folders and store report objects, reports, and snapshot reports.
Oracle Hyperion Financial Reporting Studio: Report authors use an object-oriented graphical report layout with report objects, such as text boxes, grids, images, and charts, to design reports.

20.1.2 Set Up the Financial Reporting Center: Critical Choices

Oracle Fusion Financial Reporting Center is a powerful tool for accessing, designing, and presenting financial reports and analytic data. The critical choices required to configure and install the components in Financial Reporting Center consist of:

Configuring Financial Reporting Center
Installing and configuring Financial Reporting Studio, performed by the end users.
Installing Smart View, performed by the end user.
Configuring Workspace Database Connection, performed by the administrator.
Configuring Oracle Fusion Transactional BI Dimensions

20.1.3 Configure Financial Reporting Center

Access the reports through the folder structure in the Financial Reporting Center and Workspace installed with Oracle Fusion Financial Applications. The Oracle Fusion Business Intelligence (BI) administrator defines the folder structure in Workspace considering the company's security requirements for folders and reports, as well as report distribution requirements for financial reporting batches. Security can be set on folders and reports from Workspace. The BI administrator grants access to view the folders and reports .

20.1.4 Install and Configure Financial Reporting Studio

Oracle Hyperion Financial Reporting Studio is client-based software. If Oracle Fusion Applications is accessed from Oracle Cloud, connect to the Financial Reporting Studio through a Windows Remote Desktop Connection.

Otherwise, report authors download the installation files for Financial Reporting Studio from Workspace by clicking Navigator, then Financial Reporting Center, and then Open Workspace for Financial Reporting. Once Workspace is launched, click Tools, then Install, and then Financial Reporting Studio. After performing the prerequisites and completing the installation, launch the Financial Reporting Studio. Provide the user ID, password, and the Server URL. Derive the Server URL information by following the steps:

Open Navigator, then Financial Reporting Center, and then Open Workspace for Financial Reporting.
Edit the Workspace URL by removing workspace/index.jsp.
Following are two examples of Server URLs:
- If the Workspace URL is https://example.com/workspace/index.jsp, the Server URL is https://example.com.
- If the Workspace URL is https://example.com:10622/workspace/index.jsp, the Server URL is https://example.com:10622.
Copy the modified URL to the Server URL field.

For end users installing the Oracle Fusion Financials Reporting Studio, the installer launches a separate console window that continues to run for a brief time after the installation completes the setup tasks. The process is normal, expected, and applies to Oracle Hyperion Reporting Studio installations in both the Oracle Fusion Applications and Enterprise Performance Manager modes.

Wait for the console window to close, which happens automatically before clicking Finish on the Financial Reporting Studio Installation dialog box. When clicking Finish before the console window closes, the Financial Reporting Studio installation may not fully complete.

MANDATORY: Save a new report before attempting to preview it with Web Preview.

Prerequisites needed for installing the Financial Reporting Studio are:

Financial Reporting Studio Client Certifications
Microsoft Office installed on the end-users computers

See Installing Multiple Versions of Financial Reporting Studio on a Client Machine in the Oracle Enterprise Performance Management System Installation and Configuration Guide, and Installing Financial Reporting Studio in the Oracle Hyperion Enterprise Performance Management System EPM System Standard Deployment Guide.

20.1.5 Install Smart View

Smart View is a Microsoft Excel add-in that must be loaded to each client. To download the installation files from Workspace click Navigator, then Financial Reporting Center, and then Open Workspace for Financial Reporting. Once the Workspace is launched, click Tools, then Install, and then Smart View.

Smart View can be installed only on a Windows operating system because it is an add-in to Microsoft Office products.

Once Smart View is installed, it must be configured to connect to Oracle Fusion Applications. This is done using the Smart View Shared Connections URL. Derive the Shared Connections URL by following the steps below:

Open Workspace for Financial Reporting from the Financial Reporting Center task panel.
Edit the Workspace URL, for example, if the Workspace URL is https://example.com/workspace/index.jsp. Remove index.jsp and add SmartViewProviders at the end of the URL.

This is another example for a Cloud based environment: If the Workspace URL is https://example.com:10622/workspace/index.jsp, the Shared Connections URL is https://example.com:10622/workspace/SmartViewProviders.
Copy the URL.
Launch Excel.
Navigate to the Smart View menu, then Options, and then Advanced.
Paste the URL in the Shared Connections URL field.
Click OK.

For more information on configuring Smart View client for users, see Installing Smart View in the Oracle Hyperion Smart View for Office User's Guide for Oracle Hyperion Smart View.

To connect Oracle Fusion General Ledger Balances cubes in Smart View:

Perform these steps only once for a new server and database.

Open Smart View from Start menu, then Programs, then Microsoft Office, and then Microsoft Excel 2007.
Go to the Smart View menu, then Open in the Start on the ribbon, then click the Smart View Panel that appears in the drop down box under the ribbon. This launches a task pane.
Click Shared Connections on the task pane.
Log in with the user name and password.
Select Essbase from the Select Server to proceed dropdown list of shared connections.

If the Essbase Server is not there, then it has to be added. Use the following steps:
- Click the Add Essbase Server link on the bottom of the spreadsheet.
- Specify the Essbase Server login and password.
- Expand the Essbase sever and locate the cube under it.
Click Expand to expand the list of cubes.
Expand the cube (name of the chart of accounts).
Click db. A list of functions appears on the bottom of the panel.
Click Ad hoc analysis.

To set how the name and alias of the Essbase database appears:

Click Options on the ribbon, then select the Member Options, and then select Member Name Display.
Set one of the following options:
- Distinct Member Name: Only shows the full Essbase distinct path.
- Member Name and Alias: Shows both the member name and the alias.
- Member Name Only: Shows only the member name.
The Smart Slice feature is not supported in Oracle Fusion General Ledger. For all other documentation, see Installing Smart View in the Oracle Hyperion Smart View for Office User's Guide for Oracle Hyperion Smart View.

20.1.6 Configure Workspace Database Connections

Administrators need to create database connections from Workspace so users can access the cubes from Workspace and Financial Reporting Studio.

Ledger setup has to be completed before the database connection can be created. Oracle Fusion General Ledger balances cubes are created as part of ledger setup. There is a separate cube for each combination of chart of accounts and accounting calendar. A database connection is needed for each cube.

To define a database connection, do the following:

From the Navigator, select Financial Reporting Center.
From the Financial Reporting Center task panel, select Open Workspace for Financial Reporting.
From within Workspace select the Navigator menu, then Applications, then BI Catalog.
From the Tools menu, select Database Connection Manager.
Click New.
Enter a user-friendly database connection.
Enter Essbase as the Type, the server, user name, and password.
Select Application (cube) and Database from the list of values. Expand the Application name to see the related Database, for example, db.
Click OK twice to save the selections.
Click Close in the Database Connection Manager window to save the connection.

For more information about configuring Essbase database connections in Workspace, see Understanding Essbase in the Oracle Essbase Database Administrator's Guide for Oracle Essbase.

The database connection is available in both Workspace and Financial Reporting Studio. Optionally, it can be set up in Financial Reporting Studio when putting grids on a report. This should only be done by an administrator.

20.1.7 Configure Oracle Fusion Transactional BI Dimensions

Within Oracle Fusion Transactional Business Intelligence (BI), Accounting Segment Dimensions such as Balancing segment or Cost Center segment are based on the Chart of Accounts configuration. These segments can be configured to be tree-enabled, which means that hierarchies are defined on the segment values for rollup purposes. In such scenarios, filter by a specific hierarchy when performing ad-hoc queries against tree-based accounting segments. Incorrect results may occur if tree filters are not applied. To apply tree filters, create a filter condition on Tree Filter attributes in Accounting Segment Dimensions.

For information on setting up General Ledger accounting segments, see the Oracle Cloud Administering Transactional Analyses.

20.2 Set Up Oracle Document Capture and Oracle Forms Recognition

Oracle Fusion Financials uses Oracle Document Capture to import payables invoice and expense receipt images from various sources including scanners, e-mail, and FTP sites. Oracle Fusion Payables also leverages Oracle Forms Recognition for intelligent data recognition for invoice entry.

This task is not applicable to Oracle Cloud implementations.

To implement Oracle Fusion Expenses and use automated receipt image processing, then set up Document Capture and configure it for expenses. If Oracle Fusion Automated Invoice Processing has been licensed, then set up Forms Recognition in addition to Document Capture, and configure both for payables.

To set up Document Capture and Forms Recognition, perform these steps in the specified order:

Configure Document Capture and Forms Recognition network shares.
Install and configure Document Capture and Forms Recognition on Windows desktop.

For details regarding users and privileges for the setup, refer to the installation guides of Oracle Document Capture and Oracle Forms Recognition.

20.2.1 Configure the Oracle Webcenter: Imaging and Process Management Input Directory Network Share

Oracle Document Capture and Oracle Forms Recognition save images to the Oracle Webcenter: Imaging (Imaging) input directory for further processing. Since Document Capture and Forms Recognition are Windows-based products, configure the input directory as a network shared directory so that Document Capture and Forms Recognition can save images to this location.

This task is not applicable to Oracle Cloud implementations.

To install network sharing for Oracle Document Capture and Oracle Forms Recognition:

Verify the Imaging input directory path.
Configure the network share for the Imaging input directory.
Verify Imaging Input Agent.
Configure the Windows mapped network drive for the input directory.

20.2.1.1 Verify the Oracle Webcenter: Imaging Input Directory Path

To verify the input directory path:

Log in to the Enterprise Manager on the Common Domain, as an Administrator.
Navigate to the Domain level.
Select System MBean Browser.
Open the oracle.imaging.config.bean.
Look for the InputDirectories value.
- This is the Imaging input directory where Imaging and Process Management checks for incoming scanned invoices.
- The path points to a directory on the server running Imaging.
Open a terminal window for the server running Imaging and check the path specified for the Input Directory.

The path should be a symbolic link pointing to a folder on a storage server. Both the Imaging server and the Windows server must have read/write access to the same folder on the storage server.

20.2.1.2 Configure the Network Share for the Oracle Webcenter: Imaging Input Directory

Enable the Imaging input directory to be accessed by Document Capture or Forms Recognition running on Windows:

The storage server share should have Common Internet File System (CIFS) enabled for Windows compatible share names.
The path to the Windows share name should be in Universal Naming Convention (UNC) format.

If licensed Oracle Fusion Automated Invoice Processing has been licensed, individual Oracle Document Capture workstations used for scanning invoices do not need access to the input directory.

The storage host must grant read/write access to the Imaging Input Agent running on the Common Domain host and at least one Windows user with login access to the server running Oracle Document Capture and Oracle Forms Recognition.

20.2.1.3 Verify Oracle Webcenter: Imaging Input Agent

To verify if the Imaging Input Agent is operating correctly:

Log in to the Oracle Enterprise Manger for the Common Domain.
Navigate to the Imaging Server.
Restart the server.

After the server restarts, check the input directory path referenced earlier. A file named InputAgent.lockshould be shown. If this file is not shown, verify that the image server is running and check the image server logs for errors. If there are errors, check whether the Input Agent has the necessary permissions in the storage directory. The Input agent needs read/write file access to this directory.

Additionally, verify that the Windows network drive is correctly mapped with permitted read/write access. Do this by creating a folder or file from the Linux box where the Imaging server is running. Oracle Forms Recognition is not compatible with NFS mounted shares on Windows. Use create CIFS shares for Windows instead. The Windows user should be able to view it on the Windows network drive and should be able to open and modify it.

20.2.1.4 Configure the Windows Mapped Network Drive for the Input Directory

Map the drive on the Windows servers running Oracle Forms Recognition and Oracle Document Capture servers. The drive is not mapped on individual user machines running Oracle Document Capture client for Invoicing.

Open Windows Explorer.
Right-click the folder icon that corresponds to the computer name.
Select Map Network Drive.
Select a drive letter, for example Y.
Specify the path for the shared directory on the storage host, using the UNC format: \\<host name>\<name>.
Click OK and verify that the network share now appears in Windows Explorer as the specified drive letter. If Windows Explorer is unable to create the mapped drive, the issue may be that the Common Internet File System (CIFS) is not enabled on the storage host.
Verify that Windows users have read/write access to the input directory and all its file contents.
Verify that the Input Agent directory includes the InputAgent.lock file (the input directory may be a sub-directory of the share). If the InputAgent.lock file is not seen, the following are possible explanations:
- The Imaging Server is not running and needs to be started.
- The Imaging Server is running but the Input Agent does not have the appropriate access to the network share directory and cannot generate the InputAgent.lock file.
- The Imaging Server configuration for Input Agent Directory does not point to the same network share as the mapped network drive, or it points to a sub-directory other than the one being verified.

To verify that the Windows network drive is correctly mapped with permitted read/write access, create a folder or file from the Linux box where the Imaging server is running and check if the Windows user is able to view the folder or file on the Windows network drive and is able to open and modify it.

20.2.2 Configure the Oracle Forms Recognition Project Network Share

The Oracle Forms Recognition project directory contains directories and files shared by Oracle Document Capture, Oracle Forms Recognition Designer, Oracle Forms Recognition Verifier, and Oracle Forms Recognition Runtime Service. In a typical installation scenario, these applications are not installed on the same computer. However, the project directory must be stored in a shared directory accessible to each application, regardless of where it is installed.

This task is not applicable to Oracle Cloud implementations.

To configure the Oracle Forms Recognition project network share, do the following:

Configure the share for the Oracle Forms Recognition AP Project Folder.
Configure the Windows mapped network drive for the AP Project Folder.

20.2.2.1 Configure the Network Share for the Oracle Forms Recognition AP Project Folder

Ensure that the Oracle Forms Recognition project directory is accessible to the Oracle Document Capture or Oracle Forms Recognition applications running on Windows.

The storage server share should be configured with Common Internet File System (CIFS) enabled for Windows compatible share names.
The Windows share name must be in universal naming convention (UNC) format.
The network share is meant for exclusive use by the Oracle Document Capture or Oracle Forms Recognition applications running on Windows.

Configure the storage host to share the Oracle Forms Recognition Project directory with the Oracle Document Capture and Oracle Forms Recognition users.

20.2.2.2 Configure the Windows Mapped Network Drive for the AP Project Folder

Log on to the Windows desktop with a user ID that has explicit access to the Oracle Forms Recognition project file share.

This mapping is done on the following:

Windows servers running Oracle Forms Recognition and Oracle Document Capture servers for Expenses
Servers running Oracle Forms Recognition Designer and Verifier
Invoice scanning workstations running Oracle Document Capture

Perform the following steps to configure the Windows mapped network drive:

In Windows Explorer, identify the folder for the PC icon that displays the same name as that of the actual PC.
Right-click the folder icon that corresponds to the computer name.
Right-click the folder and select Map Network Drive.
Select a drive letter, for example X.
Specify the path for the shared directory on the storage host, using the UNC format: \\<host name>\<share name>.
Click OK and verify that the network share now appears in Windows Explorer as the specified drive letter. If Windows Explorer is unable to create the mapped drive, the issue may be that CIFS is not enabled on the storage host.

20.2.3 Install and Configure Oracle Document Capture and Oracle Forms Recognition on Windows

To configure Oracle Document Capture and Oracle Forms Recognition to run on Windows, perform the following tasks in the given order:

These tasks are not applicable to Oracle Cloud implementations.

Install prerequisites.
Run the setup utility.
Install Oracle Document Capture.
Configure Oracle Document Capture.
Configure Oracle Document Capture Import Server for Importing Images from E-Mail.
Install Oracle Forms Recognition for Payables.
Configure Oracle Forms Recognition for Payables.
Configure shared drive access for Oracle Forms Recognition Runtime Service Manager.

Ensure that the required network shares have been configured before performing these steps. Steps 4 to 7 (Configure Oracle Document Capture to Configure Oracle Forms Recognition for Payables) are required only if Oracle Fusion Automated Invoice Processing has been licensed.

20.2.3.1 Prerequisites

Before proceeding with the installation and configuration of Oracle Document Capture and Oracle Forms Recognition, do the following:

Ensure that the empty Document Capture schema is created in the Oracle database with at least three user profiles: a read-only user profile for reporting, a read/write user profile for schema administration, and a read/write user profile for the Document Capture runtime connection. Document Capture tracks batches and stores audit information in the schema tables. The Document Capture runtime connection configuration includes read/write user profile credentials so that Document Capture can write data to the schema tables without requesting a separate login.
Install and Configure Oracle database support for Open Database Connectivity (ODBC) and OLEDB. See Oracle Database Software Downloads on Oracle Technology Network.
Ensure that Java Runtime Environment (JRE) 1.6 or higher is installed. See Java Downloads on Oracle Technology Network.
To configure expenses, create the folder C:\ODC Projects\EXM\Import. Share this folder with read-write permissions enabled for incoming expense documents.
Download the Capture-FormsRec_FA.zip file from the Oracle Fusion Applications repository. The zip file is located at <repository_root>/installers/Capture-FormsRec.

20.2.3.2 Run the Setup Utility

This program streamlines the installation and configuration of Oracle Document Capture and Oracle Forms Recognition.

Extract the contents of the Capture-FormsRec_FA.zip (downloaded earlier from the Oracle Fusion Applications repository) to a temporary folder and double-click Setup.exe to run the utility. The Oracle WebCenter Capture and Forms Recognition for Fusion Financials Setup window appears.
In the I/PM Input Agent Folder field, enter a UNC path of the folder from which IPM uploads the documents. For example, \\<server_name>\<share_name>.
In the Oracle Forms Recognition AP Project Folder field, provide the root directory for the AP project. For example, <Drive Letter>:\OFR. If the specified directory does not exist at the mentioned location, the installer creates a directory with the same name.

Install and configure Oracle Document Capture and Oracle Forms Recognition. The relevant instructions are provided in the subsequent sections.

20.2.3.3 Install Oracle Document Capture

Repeat the installation procedure on every machine that runs Oracle Document Capture.

If an error occurs while installing Oracle Document Capture, verify if the computer's print spooler service is running (Start , then Settings, then Control Panel, then Administrative Tools, and then Services). Scroll down until Print Spooler is seen. If the status shows that it has not started, right-click the Print Spooler service and select Start. Now retry installing Oracle Document Capture.

On the Oracle WebCenter Capture and Forms Recognition for Fusion Financials Setup window, in the Oracle Document Capture region, click Install. The Oracle Document Capture installer appears.
Proceed through the installation steps to complete the installation. Once the installation is complete, the Setup utility initiates an additional process to install a patch.
Proceed through the options to complete the patch installation. After it is complete, the Configure button in the Oracle Document Capture region is enabled.

20.2.3.4 Configure Oracle Document Capture

To configure Oracle Document Capture:

On the Oracle WebCenter Capture and Forms Recognition for Fusion Financials Setup window, in the Oracle Document Capture region, click Configure. The Oracle Document Capture Configuration Utility dialog box appears.
In the Batch Folder field, browse and select the folder where Oracle Document Capture batch files are stored.
In the Commit Folder field, browse and select the folder where Oracle Document Capture commits the captured files.

If Oracle Forms Recognition is used, leave this blank for now. After installing Oracle Forms Recognition, come back and set the folder path to <Drive Letter>:\OFR_Project\AP\Global\Import. If Oracle Forms Recognition is not being installed, set this to the Image Processing Management Input Directory.
Click OK. The Capture Batch Setup dialog box appears.

The Capture Batch Setup dialog box appears only when configuring Oracle Document Capture for the first time.
On the Capture Batch Setup dialog box, do the following:
1. In the Enter Path to Network Batch Folder field, specify the same folder path that is provided in the Batch Folder field on the Oracle Document Capture Configuration Utility dialog box.
2. In the Enter Path to Network Commit Folder field, specify the same folder path that is provided in the Commit Folder field on the Oracle Document Capture Configuration Utility dialog box.
3. In the Capture Database Setup area, select the Other Database Platform option and click Configure. The Configure Database Connection dialog box appears.
4. Click Configure DB Connection. The Data Link Properties dialog box appears.
  
  - On the Provider tab, select Oracle Provider for OLE DB and click Next.
  
  - On the Connection tab, do the following:
  1. In the Data Source field, enter the name of the Oracle database.
  2. Select the Use a specific user name and password option and provide the User name and Password that have read and write access to the Capture schema.
  3. Select the Allow saving password option.
  4. Click Test Connection to check for connectivity issue if any, and resolve it before proceeding with the configuration.
  - Click OK. The Data Link Properties dialog box closes.
5. On the Configure Database Connection dialog box, click OK. The Configure Database Connection dialog box closes.
6. On the Capture Batch Setup dialog box, click Initialize DB to populate the Capture schema in the Oracle database.
  - Initializing the database is required when configuring Oracle Document Capture for the first time.
  - If a standalone instance of Oracle Document Capture is being configured for testing, use the default Capture database (capture.mdb) that is installed with the product. On most systems, this database is located in the Oracle Document Capture installation directory. On Windows 2008 R2, the Capture database is installed in the system ALLUSERPROFILES\Oracle Document Capture folder. By default, ALLUSERSPROFILES is C:\ProgramData.
    
    To use the default capture.mdb, create a data source based on Microsoft Jet OLE DB 4.0. The local Capture database is only used for testing. For production environments, create the Capture schema in the Oracle database.
  A warning message appears indicating loss of existing data in the Capture schema proceeding with the initialization.
  
  - Click Yes. The Security Model dialog box appears.
  
  - Select the option that is appropriate to the system environment and click OK. The Microsoft Windows Open dialog box appears.
  
  - Navigate to the Oracle Document Capture installation directory, search for the Capture_ORACLE.sql file, select it, and click Open. Oracle Document Capture runs the script of the Capture schema and creates the required tables in the Oracle database.
7. On the Capture Batch Setup dialog box, click OK. The Capture Batch Setup dialog box closes.
On the Oracle Document Capture Configuration Utility dialog box, click OK.

If prompted for user credentials, enter the user name and password that have been used during the configuration process.

20.2.3.4.1 Configure Additional Routing Attributes for Manual Scanning

To configure additional routing attributes for manual scanning:

If the Automated Invoice Processing components are being installed for the first time, the latest cabinet files already exist. Thus, skip the unzip and import steps and proceed to Step 2. Otherwise, if Automated Invoice Processing is already used, perform the following steps to import the latest cabinet files:
1. Unzip the Capture-FormsRec_FA.zip package.
2. Import the ApInvoiceOdcCabinet.zip and ApInvoiceOfrCabinet.zip files using the Document Capture Import Export utility.
Open Oracle Document Capture and select Indexing - Manage Index Profiles.
Select the Fields tab for index profiles Fusion Payable Invoices With OFR and Fusion Payable Invoices Without OFR and verify that they contain the following index fields: Routing_Attribute_1 through Routing_Attribute_5, and URN.
Select System - Manage Macros.
Select the Scan for ISIS category.
Select the OFR-Scan-ISIS-Macro macro.
Click Setup.
(Optional) Review and modify the Prompt User upon closing Review option in the Index Documents area to meet the requirements.
Select the Do not Commit Batch option in the Commit Options area.
Click OK.
(Optional) If all five attributes are not planned to be used, or a longer length are planned to be used for each of the remaining attributes, change the maximum length of the index field attributes:
1. Select Admin - File Cabinets.
2. Select either Payables Invoice with OFR or Payables Invoices without OFR, depending on which file cabinet are used.
3. Select the routing attribute to edit.
4. Click Edit.
5. Update the Max Length field.
  - Do not modify the index field names, otherwise the predefined attribute configuration does not work as expected.
  - The sum of the maximum lengths is limited to the number of characters allowed by Oracle Forms Recognition (233), minus the number of characters in the file path where the image files are imported, minus the TIF file extension including the period (4), minus the characters reserved for internal use (40), minus one separator character per attribute.
    
    For example, if the image files are imported into the C:\OFR\Import\ directory and if all five attributes are used, do not exceed 170 characters (233-14-4-40-5).
  - The number of characters for an attribute value cannot exceed the Max Length for that attribute. If the attribute value character count exceeds the specified maximum length, an error is displayed on the Oracle Document Capture's scan and commit.
6. Click OK.

20.2.3.5 Configure Oracle Document Capture Import Server for Importing Images from E-Mail

To set up the Oracle Document Capture Import Server to import invoice images that are received through e-mail and to capture additional attributes for routing based on information in the e-mail subject, perform the following steps.

To configure additional routing attributes, do the following:

If the Automated Invoice Processing components are being installed for the first time, you already have the latest cabinet files, skip the unzip and import steps and proceed to Step 2. Otherwise, if Automated Invoice Processing is being used already, perform the following steps to import the latest cabinet files:
1. Unzip the Capture-FormsRec_FA.zip package.
2. Import the ApInvoiceOdcCabinet.zip and ApInvoiceOfrCabinet.zip files using the Document Capture Import Export utility.
(Optional) Perform Step 11 in Configure Additional Routing Attributes for Manual Scanning to change the maximum lengths of the index attribute fields.

To configure the Email Provider batch job, do the following:

Open the Oracle Document Capture Import Server.
Select Setup - Batch Jobs.
Expand the Email Provider folder.
Select the AP Email Provider batch job.
If Oracle Forms Recognition is not being used, perform the following steps, otherwise proceed to Step 6.
1. Select the General tab.
2. In the File Cabinet field, select Payables Invoice without OFR.
3. In the Server Macro field, select <NONE>.
4. Select the Processing tab.
5. Uncheck the Commit Batches option.
Select the Image Output tab. The default resolution is set to 300 x 300.

Do not modify this setting.
Select the Email Provider Settings tab.
Select the Email Accounts subtab.
1. In the Email Protocol field, select the e-mail protocol that is being used.
2. In the Email Server Name field, specify the DNS name that the e-mail server uses.
3. In the Email Addresses to Process field, enter the e-mail addresses that are designated to process scanned invoices.
Select the Email Filters subtab.
1. Configure the settings in the Process Emails containing specified text area.
  
  Specify the e-mail text that the Oracle Document Capture Import Server must find to process an e-mail. If the designated e-mail account is responsible only for receiving scanned invoices, this section can be left blank.
2. Configure the settings in the Attachment Processing area to process the invoice image attachments.
Select the Post-Processing subtab.
1. In the Upon Successful Import area, select the action to take when the import process succeeds.
  
  The default setting is to delete the message from the e-mail account.
2. In the Upon Failed Import area, select the action to take when the import process fails.
  
  The default setting is Don't Delete Message, which leaves the failed imported invoices in the e-mail account.
Click Close.

To schedule the Email Provider batch job, do the following:

Select Server - Schedule.
Click Schedule New Event.
In the Event field, select Email Provider - AP Email Provider.
In the Event Properties area, specify the intended frequency.

The recommended frequency setting is Every 1 Minute.
Select Server - Activate to run the job.

20.2.3.6 Install Oracle Forms Recognition for Payables

Install Oracle Forms Recognition for Payables on two different servers, one server each for:

The Runtime Service: The instance of Oracle Forms Recognition for the Runtime Service must be installed on a secure server accessible only to administrators. The Runtime Service normally runs without any user intervention. However, administrators need to access the Runtime Service to perform setup and configuration tasks.
The Designer and Verifier: The instance of Oracle Forms Recognition for the Designer and Verifier needs to be installed on a server that is accessible to the users of the applications.

To install Oracle Forms Recognition, perform the following steps:

On the Oracle WebCenter Capture and Forms Recognition for Fusion Financials Setup window, in the Oracle Forms Recognition region, click Install. The Oracle Forms Recognition installer appears.

While installing it on each server, ensure to select the Complete install option.
Proceed through the installation steps to complete the installation. Once the installation is complete, the Setup utility initiates an additional process to install a patch, if any.
Proceed through the options to complete the patch installation. After it is complete, the Configure button in the Oracle Forms Recognition region is enabled.

20.2.3.7 Configure Oracle Forms Recognition for Payables

To configure Oracle Forms Recognition for Payables, perform the following steps:

On the Oracle WebCenter Capture and Forms Recognition for Fusion Financials Setup window, in the Oracle Forms Recognition region, click Configure. The Oracle Forms Recognition Runtime Server Creation dialog box appears.

The Oracle Forms Recognition Runtime Server Creation dialog box appears if Oracle Forms Recognition has been installed for the first time. If Oracle Forms Recognition is already available and was earlier configured, the Oracle Forms Recognition Runtime Server Creation dialog box is skipped and the Oracle Forms Recognition Configuration Utility dialog box appears. The instructions here are provided assuming that Oracle Forms Recognition is installed for the first time.

On the Oracle Forms Recognition Runtime Server Creation dialog box, select one of the options to create the Runtime Service:

All (Import, OCR, Classification, Extraction, Export and Clean-up) to create and configure a single instance of the Runtime Service that performs all Oracle Forms Recognition workflow operations. This is the default option and is normally reserved for use by demonstration systems.
Custom to customize the creation of the Runtime Service based on several parameters as described here:

For production environments, Oracle recommends to create separate Runtime Service instances for each function using the Custom options described in the following table. To increase system capacity, add additional instances of OCR, Classification and Extraction Runtime Service.
To create separate instances for each function, create all of them at this point. This dialog box is available only during first time installation. It is not possible to access it later to add Runtime Service instances. To add instances later, create each of them manually.

Sub-option	Functional Description
Import	Selecting this checkbox creates an import enabled instance of the Runtime Service.
OCR, Classification and Extraction	Selecting this checkbox creates an OCR, Classification and Extraction enabled instance of the Runtime Service.
Number of Instances	Specify the number of OCR, Classification and Extraction enabled instances to be created. The default value is 1. An OCR, Classification and Extraction enabled instance is CPU intensive and therefore, to balance higher invoice loads, create additional instances. However, it is recommended that the number of such instances must not exceed the number of cores on the server. Add additional instances using the SET file created by the Setup utility. The SET file name is FusionAP - OCE.set, which is located in the Bin folder of the Forms Recognition install folder, for example `C:\Program Files\Oracle\Forms Recognition\Bin`.
Export and Clean-up	Selecting this checkbox creates an Export and Clean-up enabled instance of the Runtime Service.

Click OK. The Oracle Forms Recognition Runtime Server Creation dialog box closes and the Oracle Forms Recognition Configuration Utility dialog box appears.
In the AP Solution INI File field, ensure that the path is set to the automatically installed INI file.
In Database Connections, ensure that at least one connection is selected. In absence of a Database Connection, click Create to create a database connection. Ensure that the selected database connection has read-only access to the Fusion schema.
From the ODBC System DSN (32-bit) list, select one of the predefined ODBC System DSN value. If the list is blank, create an ODBC System DSN using the ellipsis button next to the field. Ensure that the ODBC connection has read-only access to the Fusion schema.
Enter the User ID and Password associated with the selected ODBC System DSN.
Click Test Connections to ensure that the selected database connection is active and working.
In the PO Format field, enter the format of the purchase order.

Use # as a wildcard character to represent a single number and @ as a wildcard character to represent a single alphabet.
In the Ignore Characters field, specify the characters such as comma, hyphen, period that may appear as part of the purchase order but need to be ignored. The ignore characters are always associated with a PO format.
Click Add. The PO format is added to the Defined Formats list, while simultaneously storing the associated characters to be ignored when that PO format is in use.

For more information on PO Formats see the AP Solution Guide located at <Drive Letter>:\OFR_Projects\AP.

20.2.3.8 Configure Shared Drive Access for Oracle Forms Recognition Runtime Service Manager

The Oracle Forms Recognition runtime service manager processes invoice images and exports them to a shared network drive. By design, Windows services are not allowed to access mapped network drives. Therefore, to access a network share, a Windows service must be running as an authenticated Windows user and it must access the share by specifying a UNC style path (\\server_name\share_name).

Subsequently, assign a Windows user profile to the Oracle Forms Recognition Runtime Service Manager. The specified user profile must have read/write access to the shared network drive.

On the server that hosts the Runtime Service, navigate to Start, then Control Panel, and then Administrative Tools.
Select Services.
Right-click Oracle Forms Recognition Runtime Service Manager and select Properties.
Select the Log On tab.
Select the This account radio button, and enter the user name and password of the user granted read/write access to the shared network folder.
Click Apply and then click OK.

20.3 Oracle Fusion Advanced Collections Dunning

Oracle Fusion Advanced Collections Dunning feature utilizes Oracle Business Intelligence Publisher to distribute dunning letters to customers via E-mail, fax or print. To use this feature, configure Oracle Business Intelligence Publisher to connect to the deploying company's internal E-mail, or the print or fax servers.

20.3.1 Add the E-Mail Server

To add an E-Mail server:

From the Admin page select E-mail. This displays the list of servers that have been added. Select Add Server.
Enter the Server Name, Host, and Port for the E-mail server.
Select a Secure Connection method to use for connections with the E-mail server. The options are: None or SSL. Use Secure Socket Layer. TLS (Transport Layer Security). Use TLS when the server supports the protocol; SSL is accepted in the response. TLS Required. If the server does not support TLS, then the connection is not made.
Optionally enter the following fields if appropriate: General fields; Port Security fields User name and Password.

20.4 Enable Encryption of Sensitive Payment Information

Financial transactions contain sensitive information which must be protected by a secure, encrypted mode. To protect the credit card and external bank account information, enable encryption. Encryption encodes sensitive data so that it cannot be read or copied. To enable encryption, create a wallet file. A wallet file is a digital file that stores the primary encryption key, which the application uses to encrypt sensitive data.

To secure the credit card or bank account data, navigate to the Setup and Maintenance work area, search for the Manage System Security Options task and perform the following steps:

Open the Manage System Security Options page
Click Apply Quick Defaults
Select all the check boxes:
- Automatically create wallet file and encryption key
- Encrypt credit card data
- Encrypt bank account data
Click Apply

20.5 Configure a Communication Channel to a Payment System

To transmit payment information to or receive payment information from a payment system, configure the channel used to communicate with the payment system. The concepts related to configuring a communication channel to a payment system are:

20.5.1 Proxy Server

Payments must communicate through a proxy server to its payment system. Use the standard Java networking proxy system properties that are in the configuration files when Oracle Fusion Applications were initially set up. Alternatively, specify proxy settings for a transmission protocol on the Create Transmission Configuration page by entering a value for the Proxy Host parameter.

20.5.2 Secure Sockets Layer Protocol

When Payments communicates with a payment system, the information exchanged may be sensitive, such as credit card numbers. If the communication isn’t secure, it poses a security risk. The security risk increases when communication tot he payment system is across a public network such as the Internet.

To set up a payment system servlet with a secured sockets layer, enable HTTPS on the middle-tier server where the servlet resides. If funds-capture-process profiles are not defined for the payment system, change the Transmission Servlet Base URL parameter on the Edit Payment Systems page to start with HTTPS. If funds capture process profiles are defined, change the value for the Destination URL parameter on the Edit Transmission Configuration page to start with HTTPS.

For secure communication with the payment system, ensure that the most current certification authority (CA) certificates are in the Fusion secure sockets trust store file. If Payments rejects the payment system’s secure sockets certificate, it might be necessary to insert the certificates manually.

The following table shows security actions which are applicable to Cloud and on-premise:

Table 20-1 Security Actions Applicable to Cloud and On-Premise

Action	Cloud	On-Premise
Set up a payment system servlet with a secure sockets layer (SSL)	Not applicable	Enable SSL on the servlet’s application server
Insert certification authority certificates	File a service request with the help desk	Enter a value in the `Value` field for the `Wallet Location` parameter on the Create or Edit Transmission Configuration page

20.5.3 Unsecure Protocols

The preferred file-based transmission protocol is Secure File Transfer Protocol (SFTP). File Transfer Protocol (FTP) is unsecured and should only be used to meet legacy third-party requirements. FTP must be used over a secure link such as a virtual private network (VPN) or a leased line with data link level encryption enabled.

20.6 Configure Oracle B2B Inbound Flow to Receive Supplier Invoices in XML

Oracle B2B Server is an Oracle SOA Suite component that manages interactions between deploying companies and trading partners such as suppliers. Oracle Fusion Payables supports an inbound Oracle B2B flow using Oracle B2B Server for receiving invoices from suppliers in XML format.

This task is not applicable to Oracle Cloud implementations.This task is not applicable to Oracle Cloud implementations.

Trading partners can use this B2B feature to communicate electronically by sending documents in XML format. The B2B XML invoices use the same XML standard 171_Process_Invoice_002 (version 7.2.1) developed by the Open Applications Group (OAG). For more information on B2B XML Invoices, see B2B XML Invoices: How They Are Processed in the Oracle Fusion Applications Procurement, Payables, Payments, and Cash Guide.

Customers or deploying companies who want to receive and process invoices in XML format (complying to OAG standards) that are provided by the suppliers, need to perform the following post-installation configurations.

Host Company Configuration
Supplier Configuration

These configurations are required only if customers or deploying companies want to use the B2B XML invoice feature.

20.6.1 Configure the Host Company

Perform the following steps to complete Host Company configuration.

Set up the Oracle B2B Server.
Set up Oracle Supplier Network for the Host Company

This step is required only if customers use Oracle Supplier Network as the communication channel.
To set up the Oracle B2B Server, do the following:
1. Create a supplier trading partner.
  
  The Oracle B2B Server is preloaded with the supported OAG document schemas and sample trading partners such as MyCompany which is the host company trading partner, and ApSampleTradingPartner which is the supplier trading partner. However, it is possible to create the supplier trading partners as instructed here.
  
  - Log in to the Oracle B2B Server.
  
  - On the left, click Add on the Partner toolbar. The Partner Name dialog box appears.
  
  - Enter the name of the trading partner and click OK. A confirmation message appears. The new supplier trading partner is listed in the Partner region.
  
  - On the Documents tab, click Add to add a document definition for the supplier trading partner. The Select Document Definition dialog box appears.
  
  - Select OAG - 7.2.1 - PROCESS_INVOICE_002 - OAG_DEF and click Add. The document definition is added to the supplier and is displayed under Documents.
  
  - For the document definition, clear the checkbox under Receiver.
  
  - In the Partner region, select the new supplier trading partner, and on the Agreement toolbar, click Add to add a new agreement between the host company and the new supplier trading partner.
  
  - Enter the name of the agreement.
  
  - On the process train, click the Select Document Definition train stop. The Select Document Definition dialog box appears.
  
  - Select the PROCESS_INVOICE_002 document definition mapped to the supplier trading partner and click OK.
  
  - Under Agreement Parameters, ensure that the Functional Ack checkbox is clear, and click Save.
  
  - To validate the agreement, click Validate.
  
  - Click Deploy. An information message appears, indicating successful deployment of the agreement.
2. Set up a listening channel.
  
  Oracle B2B Server supports multiple protocols for sending/receiving messages between trading partners. Choose a protocol that is best suited for your company. Refer to the Oracle B2B Server documentation or online help to learn about each protocol and which parameters need to be set up. Listening channel can be set up at the global level (applicable to all trading partners) or at the trading partner level.
  
  Do one of the following:
  
  - Click Administration to set up a global listening channel and click the Listening Channel tab.
  
  - Click Partners to set up a trading partner listening channel and click the Channels tab.
  
  - Do not set up a listening channel if Oracle Supplier Network is used by the suppliers to send the B2B invoice payload.
  
  When Oracle Supplier Network is used, the only required setup to communicate with the supplier trading partner is to add a Generic Identifier on the B2B Server, using the Trading Partner Alias of the supplier as the value of the identifier. The Trading Partner Alias of suppliers is defined on the Trading Partners tab of the host company trading partner in the Oracle Supplier Network. The Generic Identifier entry is added to the Identifiers table on the Profile tab of the trading partner page.
  
  Save the changes to complete the set up.
Set up Oracle Supplier Network for the Host Company if the supplier uses Oracle Supplier Network to send the B2B invoice payload. To complete the setup, perform the following:
1. Log in to the Oracle Supplier Network using the registered account.
2. Access Messaging - Communication Parameters and select HTTPS URL Connection as the Delivery Method.
3. Click Modify to update the delivery method parameter values.
4. Enter the URL of the B2B HTTP receiver. Consult the system administrator if the value is unknown.
5. Enter the User ID and password for Oracle Supplier Network.
  
  Different values for the Test and Production environments can be specified.
6. Access Messaging - Transaction Management.
7. Add the OAG PROCESS_INVOICE_002 document from the list of available documents if it is not already added.
8. From the Action drop down list, select Receive.
9. From each Delivery Method drop down list (OSN Test Delivery Method and OSN Production Delivery Method), select HTTPS URL Connection and click Submit.
10. On the Trading Partners tab, in the Add Trading Partners region, click Add to add supplier trading partners. It is possible to add all the supplier trading partners who send invoice payloads to the host company.
Set up the B2B Site Code.

For each supplier site that is enabled for B2B communication, the host company assigns a B2B Site Code to the site and communicates it to the supplier. Supplier has to provide this B2B Site Code in the invoice payload in the <PARTNER><PARTNRIDX> element, with <PARTNER><PARTNRTYPE> = Supplier within the <INVHEADER> element. To assign a B2B Site Code to a supplier site, navigate to the Manage Suppliers UI in the Fusion application. Search for the supplier and then open the supplier site. Enter a value into the B2B Supplier Site Code. Click Save. This code needs to be communicated to the suppliers manually so that they can include it in their invoice payloads.

To assign a B2B Site Code to a supplier site, do the following:
1. In Oracle Fusion Applications, access Suppliers - Manage Suppliers.
2. Search for the specific supplier and open the relevant supplier site.
3. On the Edit Site tab, in the B2B Trading Partner Information region, enter the site code (the site code set by the host company in Oracle B2B Server) in the B2B Supplier Site Code field.
4. Click Save.
Communicate the same site code to the suppliers.

20.6.2 Configure the Supplier

The following configuration steps must be performed by suppliers if they are using Oracle Supplier Network to send the invoice payload.

Log in to the Oracle Supplier Network using the registered account.
Navigate to Messaging - Communication Parameters and select HTTPS URL Connection as the Delivery Method.
Click Modify to update the delivery method parameter values.
Enter the URL of the B2B HTTP receiver.
Enter the User ID and password for Oracle Supplier Network.

Different values for the Test and Production environments can be specified.
Navigate to Messaging - Transaction Management.
Add the OAG PROCESS_INVOICE_002 document from the list of available documents if it is not already added.
From the Action drop down list, select Send.
From each Delivery Method drop down list (OSN Test Delivery Method and OSN Production Delivery Method), select HTTPS URL Connection and click Submit.
On the Trading Partners tab, in the Add Trading Partners region, click Add to add host company trading partner.

20.7 Set Up Oracle B2B to Send Receivables Transactions in XML

Oracle B2B Server is an Oracle SOA Suite component that manages interactions between deploying companies and trading partners. Oracle Fusion Receivables supports an outbound Oracle B2B flow using Oracle B2B Server to send transactions to customer trading partners in XML format.

The setup of the Oracle B2B flow for Receivables makes use of these existing elements:

XML Schema document guideline
OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition
Host trading partner MyCompany

To set up Oracle B2B to send Receivables transactions in XML:

Configure the host and remote trading partners
Configure agreements between the host and remote trading partners

20.7.1 Configure Trading Partners

Configure the enterprise as the host trading partner, and all of the customers that receive XML documents as remote trading partners.

To configure trading partners:

Log in to the Oracle B2B Server.
Navigate to the Administration page.
Click the Document tab.
Load the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition file.
Click the Types tab.
Add a new Internal Identifier with the name B2B Trading Partner Code.

This name matches the field name on the customer account profile.
Navigate to the Partners page.
In the Partner regional area, select the default host partner MyCompany.
If necessary, update the default host partner name to reflect the enterprise.
Click the Documents tab.
Verify that the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition is assigned to the host trading partner.
Ensure that the Sender option is enabled.
In the Partner regional area, click the Add icon.
Enter the name of a remote trading partner.
Select the Internal Identifier Type B2B Trading Partner Code previously created and enter the Value for the identifier.

This is the value that entered in the B2B Trading Partner Code field on the customer account profile of this remote trading partner.
Click the Documents tab.
Click the Add icon to associate the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition with the remote trading partner.
Enable the Receiver option.
Click the Channel tab.
Define a channel for the remote trading partner.

The channel determines how the XML transaction is delivered to the remote trading partner from B2B: directly; via the Oracle Supplier Network (OSN), or via a third party.

If Oracle Supplier Network (OSN) is used to communicate, select the Generic Identifier and enter the IP Address of the OSN machine.
Repeat steps 13 to 20 for each remote trading partner.

20.7.2 Configure Agreements

A trading partner agreement defines the terms that enable two trading partners, the sender and the receiver, to exchange business documents. The agreement identifies the trading partners, trading partner identifiers, document definitions and channels.

An agreement consists of two trading partners, the host trading partner and one remote trading partner, and represents one type of business transaction between these partners. For example, if the host trading partner MyCompany and the remote trading partner ABC Solutions regularly exchange both purchase orders and invoices, then two separate agreements are needed for each document definition.

To configure agreements between the host and remote trading partners:

Log in to the Oracle B2B Server.
Navigate to the Partners page.
In the Agreement regional area, click the Add icon to open a new agreement for the host trading partner MyCompany.
Enter the agreement ID and Name.
Enter the agreement parameters.
Select the Document Definition OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF for this agreement.
Select the remote trading partner to include in this agreement.
Select the channel for the remote trading partner.
Add identifiers for the remote trading partner.
Click Save to save the agreement.
Click Validate to validate the agreement.
Click Deploy to deploy the agreement.

Deployment is the process of activating an agreement from the design-time repository to the run-time repository.
Repeat steps 3 to 12 for each agreement between the host trading partner and this remote trading partner.

20.8 Next Steps

If the Fusion Accounting Hub product offering has been installed, go to Complete Oracle Fusion Applications Accounting Hub Post-Installation Tasks . Otherwise, go to the section that corresponds to the product offering that is installed.