4 Financials

Setting Up Financial Reporting Center

Financial Reporting Center : How It Works

Setting Up Your Financial Reporting Center : Critical Choices

• Configuring Financial Reporting Center

• Installing and configuring Financial Reporting Studio, performed by your end users.

• Installing Smart View, performed by your end user.

• Configuring Workspace Database Connection, performed by your administrator.

• Configuring Oracle Fusion Transactional BI Dimensions

Configuring Financial Reporting Center

Installing and Configuring Financial Reporting Studio

1. Open Navigator > Financial Reporting Center > Open Workspace for Financial Reporting.

2. Edit the Workspace URL and remove workspace/index.jsp.

3. Following are two examples of Server URLs:

   • If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com/workspace/index.jsp, the Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com.

   • If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622/workspace/index.jsp, the Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622.

4. Copy the modified URL to the Server URL field.

Prerequisites needed for installing the Financial Reporting Studio are:

1. Financial Reporting Studio Client Certifications that are found at: http://www.oracle.com/technetwork/middleware/bi-foundation/hyperion-supported-platforms-085957.html

2. Microsoft Office installed on your end-users computers.

Installing Smart View

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. You can derive the Shared Connections URL by following the steps below:

1. Open Workspace for Financial Reporting from the Financial Reporting Center task panel.

2. Edit the Workspace URL, for example, if the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com/workspace/index.jsp. Remove index.jsp and add SmartViewProviders at the end of the URL.

   Note

   This is another example for a Cloud based environment: If the Workspace URL is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/index.jsp, the Shared Connections URL is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/SmartViewProviders.

3. Copy the URL.

4. Launch Excel.

5. Navigate to the Smart View menu > Options > Advanced.

6. Paste the URL in the Shared Connections URL field.

7. Click on the OK button.

For more information on configuring Smart View client for users, see 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:

1. Open Smart View from your Start menu > Programs > Microsoft Office > Microsoft Excel 2007.

2. Go to the Smart View menu > Open, in the Start on the ribbon > click on Smart View Panel that appears in the drop down box under the ribbon. This launches a task pane.

3. Click on the Shared Connections button on the task pane.

4. Sign in with your user name and password.

5. Click on the Select Server to proceed drop down.

   Note

   If the Essbase Server is not there, then it has to be added. Use the following steps:

   1. Click on the Add Essbase Server link on the bottom of the spreadsheet.

   2. Specify the Essbase Server login and password.

   3. Expand the Essbase sever and locate the cube under it.

6. Select Oracle Essbase from the list of shared connections.

7. Click the Expand to expand the list of cubes.

8. Expand your cube (name of your chart of accounts).

9. Click on db. A list of functions appears on the bottom of the panel.

10. Click the Ad hoc analysis.

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

1. Click on the Options on the ribbon > select the Member Options > select Member Name Display.

2. Set one of these three 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.

Configuring Workspace Database Connections

Steps to define a database connection are:

1. Start at the Navigator by selecting Financial Reporting Center.

2. From the Financial Reporting Center task panel select Open Workspace for Financial Reporting.

3. From within Workspace select the Navigator menu > BI Catalog.

4. Select Tools menu > Database Connection Manager.

5. Select New button.

6. Enter a user friendly name for the Database Connection Name.

7. Enter Essbase as the Type, your server, user name, and password.

8. Select Application (cube) and Database from the list of values. Expand the Application name to see the related Database, for example, db.

9. Click the OK button twice to save your selections.

10. Click Close button in the Database Connection Manager window to save your connection.

For more information on configuring Essbase database connections in Workspace see: Oracle Essbase Database Administrator's Guide for Oracle Essbase.

Configuring Oracle Fusion Transactional BI Dimensions

Setting Up Oracle Document Capture and Oracle Forms Recognition

Installing Oracle Document Capture and Oracle Forms Recognition : Overview

If you plan to implement Oracle Fusion Expenses and use automated receipt image processing, then you must set up Document Capture and configure it for expenses. If you have licensed Oracle Fusion Automated Invoice Processing, then you must 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:

1. Configure Document Capture and Forms Recognition network shares

2. Install and configure Document Capture and Forms Recognition on Windows desktop

Configuring the Oracle Imaging and Process Management Input Directory Network Share : Procedures

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

1. Verify the Oracle Imaging and Process Management input directory path

2. Configure the network share for the Imaging and Process Management input directory

3. Verify Oracle Imaging and Process Management Input Agent

4. Configure the Windows mapped network drive for the input directory

1. Verify the Oracle Imaging and Process Management Input Directory Path

To verify the input directory path:

1. Sign in to the Enterprise Manager on the Common Domain, as an Administrator.

2. Navigate to the Domain level.

3. Select System MBean Browser.

4. Open the oracle.imaging.config.bean.

5. Look for the InputDirectories value.

   • This is the Imaging and Process Management input directory where Imaging and Process Management will check for incoming scanned invoices.

   • The path will point to a directory on the server running Imaging and Process Management.

6. Open a terminal window for the server running Imaging and Process Management 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 and Process Management server and the Windows server must have read/write access to the same folder on the storage server.

2. Configure the Network Share for the Imaging and Process Management Input Directory

Enable the Imaging and Process Management 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.

3. Verify Oracle Imaging and Process Management Input Agent

To verify if the Oracle Imaging and Process Management Input Agent is operating correctly:

1. Log on to the Oracle Enterprise Manger for the Common Domain.

2. Navigate to the Imaging Server.

3. Restart the server.

   After the server restarts, check the input directory path referenced earlier. You should see a file named InputAgent.lock. If you do not see this file, verify that the image server is running and check the image server logs for errors. If you notice 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. You can do this by creating a folder or file from the Linux box where the IPM server is running. Oracle Forms Recognition is not compatible with NFS mounted shares on Windows. You must 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.

4. Configure the Windows Mapped Network Drive for the Input Directory

You must log on to the Windows desktop with a user ID that has explicit access to the input directory file share.

You need to map the drive on the Windows servers running Oracle Forms Recognition and Oracle Document Capture servers. The drive will not be mapped on individual user machines running Oracle Document Capture client for Invoicing.

1. Open Windows Explorer.

2. Right-click on the folder for the PC icon depicting a computer with same name as the PC.

3. Select Map Network Drive.

4. Select drive letter, for example Y.

5. Specify the path for the shared directory on the storage host, using the UNC format: \\<host name>\<name>.

6. Click OK and verify that the network share now appears in Windows Explorer as the drive letter you specified. If Windows Explorer is unable to create the mapped drive, the issue may be that CIFS is not enabled on the storage host.

7. Verify that Windows users have read/write access to the input directory and all its file contents.

8. Verify that the Input Agent directory includes the InputAgent.lock file (the input directory may be a sub-directory of the share). If you do not see the InputAgent.lock file, the following are possible explanations:

   • The Imaging and Process Management (IPM) Server is not running and needs to be started.

   • The IPM 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.

   • IPM Server's 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 you are verifying.

     Note

     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 IPM 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.

Configuring the Oracle Forms Recognition Project Network Share : Procedures

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

1. Configure the share for the Oracle Forms Recognition AP Project directory

2. Configure the Windows mapped network drive for the AP Project directory

1. Configure the Network Share for the Oracle Forms Recognition AP Project Directory

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.

2. Configure the Windows Mapped Network Drive for the AP Project Directory

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

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

1. In Windows Explorer, identify the folder for the PC icon that displays the same name as that of the actual PC.

2. Right-click the folder for the PC icon depicting a computer with same name as the PC.

3. Right-click the folder and select Map Network Drive.

4. Select a drive letter, for example X.

5. Specify the path for the shared directory on the storage host, using the UNC format: \\<host name>\<share name>.

6. Click OK and verify that the network share now appears in Windows Explorer as the drive letter you specified. If Windows Explorer is unable to create the mapped drive, the issue may be that CIFS is not enabled on the storage host.

Installing and Configuring Oracle Document Capture and Oracle Forms Recognition on Windows - Part 1 : Procedures

1. Install prerequisites

2. Run the setup utility

3. Install Oracle Document Capture

4. Configure Oracle Document Capture

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

6. Install Oracle Forms Recognition for Payables

7. Configure Oracle Forms Recognition for Payables

8. Configure shared drive access for Oracle Forms Recognition Runtime Service Manager

For more information on performing post-installation tasks, see the Oracle Document Capture Installation Guide and the Oracle Forms Recognition Installation Guide.

1. Install Prerequisites

1. 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.

   For more information on configuring the Document Capture database, see the Oracle Document Capture Installation Guide.

2. Install and Configure Oracle database support for Open Database Connectivity (ODBC) and OLEDB. For more information, see Oracle Database Software Downloads on Oracle Technology Network at http://www.oracle.com/technetwork.

3. Ensure that Java Runtime Environment (JRE) 1.6 or higher is installed. For more information, see Java Downloads on Oracle Technology Network at http://www.oracle.com/technetwork.

4. To configure expenses, create the folder C:\ODC Projects\EXM\Import. You need to share this folder with read-write permissions enabled for incoming expense documents.

5. Download the Capture-FormsRec_FA.zip file from the Fusion Applications repository. The zip file is located at <repository_root>/installers/Capture-FormsRec.

2. Run the Setup Utility

1. Extract the contents of the Capture-FormsRec_FA.zip (downloaded earlier from the 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.

2. 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>.

3. 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.

You are now ready to install and configure Oracle Document Capture and Oracle Forms Recognition. The relevant instructions are provided in the subsequent sections.

3. Install Oracle Document Capture

1. 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.

2. 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.

3. Proceed through the options to complete the patch installation. After it is complete, the Configure button in the Oracle Document Capture region is enabled.

4. Configure Oracle Document Capture

1. 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.

2. In the Batch Folder field, browse and select the folder where Oracle Document Capture batch files are stored.

3. In the Commit Folder field, browse and select the folder where Oracle Document Capture commits the captured files.

   Note

   If you are using Oracle Forms Recognition, leave this blank for now. After you install Oracle Forms Recognition, you will come back and set the folder path to <Drive Letter>:\OFR_Project\AP\Global\Import. If you are not installing Oracle Forms Recognition, set this to the Image Processing Management Input Directory.

4. Click OK. The Capture Batch Setup dialog box appears.

   Note

   The Capture Batch Setup dialog box appears only when configuring Oracle Document Capture for the first time.

5. On the Capture Batch Setup dialog box, enter the following details:

   1. In the Enter Path to Network Batch Folder field, specify the same folder path that you have 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 you have 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.

      1. On the Provider tab, select Oracle Provider for OLE DB and click Next.

      2. On the Connection tab, provide the following information:

         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 you proceed with the configuration.

      3. 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.

      Note

      • Initializing the database is required when you configure Oracle Document Capture for the first time.

      • If you are configuring a standalone instance of Oracle Document Capture for testing, you can 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, you need to create a data source based on Microsoft Jet OLE DB 4.0. The local Capture database is only used for testing. For production environments, you must create the Capture schema in the Oracle database.

      A warning message appears indicating loss of existing data in the Capture schema if you proceed with the initialization.

      1. Click Yes. The Security Model dialog box appears.

      2. Select the option that is appropriate to the system environment and click OK. The Microsoft Windows Open dialog box appears.

      3. 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.

6. On the Oracle Document Capture Configuration Utility dialog box, click OK.

   Note

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

4.1 Configure Additional Routing Attributes for Manual Scanning

1. If you are installing the Automated Invoice Processing components for the first time you already have the latest cabinet files, so you can skip the unzip and import steps and proceed to Step 2. Otherwise, if you were already using Automated Invoice Processing, 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.

2. Open Oracle Document Capture and select Indexing - Manage Index Profiles.

3. 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.

4. Select System - Manage Macros.

5. Select the Scan for ISIS category.

6. Select the OFR-Scan-ISIS-Macro macro.

7. Click Setup.

8. (Optional) Review and modify the Prompt User upon closing Review option in the Index Documents area to meet your requirements.

9. Select the Do not Commit Batch option in the Commit Options area.

10. Click OK.

11. (Optional) If you are not planning to use all five attributes, or you decide to use a longer length for each of the remaining attributes, you can 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 you are using.

    3. Select the routing attribute that you want to edit.

    4. Click Edit.

    5. Update the Max Length field.

       Note

       • Do not modify the index field names, otherwise the predefined attribute configuration will 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 you are using all five attributes, you should 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, Oracle Document Capture's scan and commit will error.

    6. Click OK.

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

Configure additional routing attributes.

1. If you are installing the Automated Invoice Processing components for the first time, you already have the latest cabinet files, so you can skip the unzip and import steps and proceed to Step 2. Otherwise, if you were already using Automated Invoice Processing, 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.

2. (Optional) Perform Step 11 in section "Configure Additional Routing Attributes for Manual Scanning" to change the maximum lengths of the index attribute fields.

Configure the Email Provider batch job.

1. Open the Oracle Document Capture Import Server.

2. Select Setup - Batch Jobs.

3. Expand the Email Provider folder.

4. Select the AP Email Provider batch job.

5. If you are not using Oracle Forms Recognition, 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.

6. Select the Image Output tab. The default resolution is set to 300 x 300.

   Important

   Do not modify this setting.

7. Select the Email Provider Settings tab.

8. 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.

9. 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.

10. 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.

11. Click Close.

Schedule the Email Provider batch job.

1. Select Server - Schedule.

2. Click Schedule New Event.

3. In the Event field, select Email Provider - AP Email Provider.

4. In the Event Properties area, specify the intended frequency.

   Note

   The recommended frequency setting is Every 1 Minute.

5. Select Server - Activate to run the job.

Installing and Configuring Oracle Document Capture and Oracle Forms Recognition on Windows - Part 2 : Procedures

6. Install Oracle Forms Recognition for Payables

You need to 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:

1. 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.

   Note

   While installing it on each server, ensure that you select the Complete install option.

2. 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.

3. Proceed through the options to complete the patch installation. After it is complete, the Configure button in the Oracle Forms Recognition region is enabled.

For more information about installing Oracle Forms Recognition, see the Oracle Forms Recognition Installation Guide.

7. Configure Oracle Forms Recognition for Payables

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

1. 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.

   Note

   The Oracle Forms Recognition Runtime Server Creation dialog box appears if you have installed Oracle Forms Recognition 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.

2. 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:

     Note

     • For production environments, Oracle recommends that you create separate Runtime Service instances for each function using the Custom options as described below. If you need to increase system capacity, you need to add additional instances of OCR, Classification and Extraction Runtime Service.

     • If you plan to create separate instances for each function, create all of them at this point. This dialog box is available only during first time installation. You cannot access it later to add Runtime Service instances. If you want to add instances later, you need to create each of them manually.

     
     

     Sub-option	Functional Description
     Import	Selecting this check box creates an import enabled instance of the Runtime Service.
     OCR, Classification and Extraction	Selecting this check box creates an OCR, Classification and Extraction enabled instance of the Runtime Service.
     Number of Instances	You can specify the number of OCR, Classification and Extraction enabled instances that you want to create. The default value is 1. An OCR, Classification and Extraction enabled instance is CPU intensive and therefore, if you need to balance higher invoice loads, you need to create additional instances. However, it is recommended that the number of such instances must not exceed the number of cores on the server. You can 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 check box creates an Export and Clean-up enabled instance of the Runtime Service.

3. Click OK. The Oracle Forms Recognition Runtime Server Creation dialog box closes and the Oracle Forms Recognition Configuration Utility dialog box appears.

4. In the AP Solution INI File field, ensure that the path is set to the automatically installed INI file.

5. 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.

6. 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.

7. Enter the User ID and Password associated with the selected ODBC System DSN.

8. Click Test Connections to ensure that the selected database connection is active and working.

9. In the PO Format field, enter the format of the purchase order.

   Note

   You can use # as a wildcard character to represent a single number and @ as a wildcard character to represent a single alphabet.

10. 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.

11. 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 about installing Oracle Forms Recognition, see the Oracle Forms Recognition Installation Guide. For more information on PO Formats see the AP Solution Guide located at <Drive Letter>:\OFR_Projects\AP.

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).

You must therefore 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.

1. On the server that hosts the Runtime Service, select Start - Control Panel - Administrative Tools.

2. Select Services.

3. Right-click Oracle Forms Recognition Runtime Service Manager and select Properties.

4. Select the Log On tab.

5. 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.

6. Click Apply and then click OK.

Setting Up Tesseract

Setting Up Tesseract Optical Character Recognition Engine : Procedures

If you plan to implement the Oracle Fusion Expenses iPhone application and use automatic expense creation from receipt images, you must set up Tesseract.

One or more instances of Expenses can access a single Tesseract installation. For example, a production instance and a test instance of Expenses can access a single Tesseract installation.

To set up Tessearct, perform the following steps:

1. Verify that the user who is installing Tesseract has root access. Use the following command and ensure that the response is root.

   $whoami
   

2. Create the directory that will host the Tesseract executable. The Oracle Fusion Payables Java EE application must have access to this directory. Expenses services must have executable permission on this directory.

   $mkdir exmocr
   

3. Create a shell script in the directory you created in step 2.

   1. Open a new shell script file using the file editor.

      $vi installtesseract.sh
      

   2. Copy the following script into the file:

      #!/bin/bash
      downloadPackage()
      {
        site=$1
        file=$2
        if [ -f ${file} ] ; then
           echo "Skipping $file download since it already exists."
        else
          echo "Dowloading $file from the internet"
          wget http://${site}.googlecode.com/files/$file
          if [ "$?" -ne "0" ] ; then
             echo "Downloading ${file} failed. Confirm whether you have network connectivity.";
             exit 1;
          fi
        fi
      }
      
      prepareQuestion() {
        if [ -e tesseract-ocr ] || [ -e leptonica-1.68 ]  || [ -e tesseract-3.01 ] ; then
          echo "Previous versions of tesseract-ocr or leptonica-1.68 exists."
          echo "This installer will uninstall the current version and install the new version."
          echo -n "Do you wish to proceed? [Y/N]: "
          read wish
          if  [ $wish = "Y" ] || [ $wish = "y" ] ; then
            rm -rf tesseract-3.01 leptonica-1.68 tesseract-ocr
          else
            echo "Exiting the install process per your request."
            exit 1;
          fi
        fi
      }
      
      untarAll () {
         tar xvf tesseract-3.01.tar.gz
         mv tesseract-3.01 tesseract-ocr
         tar xvf tesseract-ocr-3.01.eng.tar.gz
         tar xvf leptonica-1.68.tar.gz
      }
      downloadAll() {
        downloadPackage tesseract-ocr tesseract-3.01.tar.gz
        downloadPackage tesseract-ocr tesseract-ocr-3.01.eng.tar.gz
        downloadPackage leptonica leptonica-1.68.tar.gz
      }
      
      buildAll() {
         cd $EXM_OCR_PATH/leptonica-1.68
         ./configure
         make
         sudo make install
      
         cd $EXM_OCR_PATH/tesseract-ocr
         ./autogen.sh
         if ! [ -d m4 ] ; then
            mkdir m4;
         fi
         ./configure
         cat -v  ccutil/strngs.h | sed -e 's/^M-oM-;M-?//g' > strngs.h.new
         mv strngs.h.new ccutil/strngs.h
         make
         #sudo make install
      }
      
      generateTesseractFiles() {
      
      cat > $EXM_OCR_PATH/tesseract-ocr/tessdata/configs/validchars << EOF
      tessedit_char_whitelist 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz.:,!@#$%&*()+=;'<>/-
      EOF
      
      cat > $EXM_OCR_PATH/tesseract << EOF
      #!/bin/sh
      basedir=\$(dirname \$0)
      export TESSDATA_PREFIX=\${basedir}/tesseract-ocr/
      \${basedir}/tesseract-ocr/api/tesseract  \$*  \${basedir}/tesseract-ocr/tessdata/configs/validchars
      EOF
      
      chmod +x $EXM_OCR_PATH/tesseract
      
      } 
      export EXM_OCR_PATH=`pwd`
      echo $EXM_OCR_PATH
      prepareQuestion
      downloadAll
      untarAll
      buildAll
      generateTesseractFiles
      
      

   3. Save the file.

      :wq
      

4. Verify that the following directories exist and the shell script can access these directories:

   /usr/local
   

   /usr/local/include
   

   /usr/local/lib
   

   Tesseract temporarily copies several files into these directories during installation.

5. Verify that wget is present on the machine. The shell script uses wget to download the files from the internet.

   $which wget
   

6. Execute the shell script with root access.

   • The shell script downloads, untars, and installs the following files:

     ./tesseract-ocr-3.01.eng.tar.gz 
     ./tesseract-3.01.tar.gz 
     ./leptonica-1.68.tar.gz 
     
     

   • On installation, Tesseract creates the following directories:

     ./tesseract-ocr
     ./leptonica-1.68
     
     

   • The shell script also creates the following shell script that is invoked by the Expenses application:

     ./tesseract
     
     

     Note

     Do not modify this shell script.

7. Create the directory for storing the image files sent to Tesseract for processing the converted text files. The Tesseract executable must have read and write access to this directory.

   The image files and the corresponding text files are not deleted from this directory. Based on your storage policies, you can remove these files periodically.

8. Create the following environment variables and set them to their respective values:

   • FIN_EXM_OCR_PATH: This directory hosts Tesseract. Enter the full path along with the executable name as the value.

   • FIN_EXM_OCR_OUTPUT_DIR: This directory stores the images and the converted files. Enter the full path as the value.

   • Modify the file and add the following entries at the end:

     • Change directory to <domain name>/bin.

     • Open the setDomainEnv.sh file in the file editor.

       $vi setDomainEnv.sh
       

     • Add the following environment variables and set them to the correct directories:

       FIN_EXM_OCR_EXEC_PATH=<Enter the full path of the directory where Tesseract is installed.>/tesseract
       

       export FIN_EXM_OCR_EXEC_PATH
       

       FIN_EXM_OCR_OUTPUT_DIR= <Enter the full path of the directory for storing image files.>
       

       export FIN_EXM_OCR_OUTPUT_DIR
       

     • Save the setDomainEnv.sh file.

9. Stop and restart the Financials domain in Oracle Fusion Applications.

If you already have Tesseract installed for your use, you can set up additional instances of Expenses to access the same Tesseract installation. To configure Expenses with an existing Tesseract installation, perform the following steps:

1. Mount the directory of the Tesseract installation on the new instance of Expenses, so that the Payables Java EE application in the new instance can access the Tesseract executable.

2. Create the directory for storing the image files sent to Tesseract for processing and the converted text files. The Tesseract executable must have read and write access to this directory.

3. Create the following environment variables and set them to their respective values.

   Modify the file and add the following entries at the end:

   1. Change directory to <domain name>/bin.

   2. Open the setDomainEnv.sh file in the file editor.

      $vi setDomainEnv.sh
      

   3. Add the following environment variables and set them to the correct directories:

      FIN_EXM_OCR_EXEC_PATH=<Enter the full path of the directory where Tesseract is installed.>/tesseract 
      

      export FIN_EXM_OCR_EXEC_PATH
      

      FIN_EXM_OCR_OUTPUT_DIR=<Enter the full path of the directory for storing image files.>
      

      export FIN_EXM_OCR_OUTPUT_DIR
      

   4. Stop and restart the Financials domain in Oracle Fusion Applications.

Setting Up Financial Transactions

Oracle Fusion Advanced Collections Dunning : Highlights

Configuring Oracle Business Intelligence Publisher

• Configure Oracle Business Intelligence Publisher by adding an e-mail server. Refer to the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher (Oracle Fusion Applications Edition).
  See: Adding an E-Mail Server

Enabling Encryption of Sensitive Payment Information : Procedures

After installing Oracle Fusion Applications, you can secure sensitive information by using any one of the following methods:

• Automatically create a wallet file, automatically generate a master encryption key, and manually enable encryption.

• Manually create a wallet file, automatically generate a master encryption key, and manually enable encryption.

• Manually create a wallet file, manually generate a master encryption key, and manually enable encryption.

• Automatically create a wallet file, automatically generate a master encryption key, and manually enable encryption.

Automatically Create a Wallet File, Automatically Generate a Master Encryption Key, and Manually Enable Encryption

To automatically create a wallet file, automatically generate an encryption key, and manually enable encryption, perform the following steps:

1. Navigate to the Manage System Security Options page as follows: Navigator link > Tools menu: Setup and Maintenance link > Overview page > All Tasks tab > Search field: Task Lists and Tasks > Name field: Payments > Search button > Expand Define Payments Security folder > Manage System Security Options task: Go to Task icon > Manage System Security Options page.

2. In the Manage System Security Options page, click the Edit Master Encryption Key button. The Edit Master Encryption Key dialog box appears.

3. In the Edit Master Encryption Key dialog box, select the Application-generated radio button.

4. Click the Save and Close button.

5. In the Manage System Security Options page, click the Encrypt button in either the Credit Card Data region or the Bank Account Data region or in both regions to enable encryption for sensitive financial data.

Manually Create a Wallet File, Automatically Generate a Master Encryption Key, and Manually Enable Encryption

To manually create a wallet file, automatically generate an encryption key, and manually enable encryption, perform the following steps:

1. Create an empty Oracle Wallet, ewallet.p12, using the Oracle Wallet Manager utility.

2. Navigate to the Manage System Security Options page as follows: Navigator link > Tools menu: Setup and Maintenance link > Overview page > All Tasks tab > Search field: Task Lists and Tasks > Name field: Payments > Search button > Expand Define Payments Security folder > Manage System Security Options task: Go to Task icon > Manage System Security Options page.

3. In the Manage System Security Options page, click the Edit Master Encryption Key button. The Edit Master Encryption Key dialog box appears.

4. In the Edit Master Encryption Key dialog box, select the Application-generated radio button.

5. Click the Save and Close button.

6. In the Manage System Security Options page, click the Encrypt button in either the Credit Card Data region or the Bank Account Data region or in both regions to enable encryption for sensitive financial data.

Manually Create a Wallet File, Manually Generate a Master Encryption Key, and Manually Enable Encryption

To manually create a wallet file, manually generate an encryption key, and manually enable encryption, perform the following steps:

1. Create an empty Oracle Wallet, ewallet.p12, using the Oracle Wallet Manager utility.

2. Navigate to the Manage System Security Options page as follows: Navigator link > Tools menu: Setup and Maintenance link > Overview page > All Tasks tab > Search field: Task Lists and Tasks > Name field: Payments > Search button > Expand Define Payments Security folder > Manage System Security Options task: Go to Task icon > Manage System Security Options page.

3. In the Manage System Security Options page, click the Edit Master Encryption Key button. The Edit Master Encryption Key dialog box appears.

4. Take one of the following actions:

   • In the Edit Master Encryption Key dialog box, select the User-defined radio button.

     In the Key File Location field, enter the path to the master encryption key, click the Save and Close button, and then click the Done button.

   • Generate a secure, custom key by copying a file containing the bits of the key to the same directory as the empty Oracle wallet, ewallet.p12

     Note

     After the wallet is created, ensure that you securely delete the file containing the key bits by using a utility that supports secure deletion.

5. In the Manage System Security Options page, click the Encrypt button in either the Credit Card Data region or the Bank Account Data region or in both regions to enable encryption for sensitive financial data.

Automatically Create a Wallet File, Automatically Generate a Master Encryption Key, and Manually Enable Encryption

To automatically create a wallet file, automatically generate an encryption key, and automatically enable encryption, perform the following steps:

1. Navigate to the Manage System Security Options page as follows: Navigator link > Tools menu: Setup and Maintenance link > Overview page > All Tasks tab > Search field: Task Lists and Tasks > Name field: Payments > Search button > Expand Define Payments Security folder > Manage System Security Options task: Go to Task icon > Manage System Security Options page.

2. In the Manage System Security Options page, click the Apply Quick Defaults button. The Apply Quick Defaults dialog box appears.

3. In the Apply Quick Defaults dialog box, select all the check boxes: Automatically create wallet file and encryption key, Encrypt credit card data, and Encrypt bank account data.

4. Click the Apply button.

For more information on Payments security, see the chapter entitled Define Funds Capture and Payments Security in the Oracle Fusion Applications Financials Implementation Guide.

Configuring Communication Channel to a Payment System : Explained

1. Configure and deploy a tunnel.

2. Set up SSL security to communicate with the payment system servlet.

1. Configure and Deploy a Tunnel

To communicate with a payment system through a firewall, you can use the Tunneling feature of Oracle Fusion Payments. The Tunneling feature is used to deliver data, such as a payment file or settlement batch, using two protocols, one of which encapsulates the other. Tunneling is also referred to as delegated transmission, since the initial transmission from Payments is a request to an external module (the transmission servlet) to deliver data using an independent transmission protocol. The name of the transmission protocol, its parameters, and the actual data to be delivered are encapsulated within the body of the tunneling transmission protocol.

The purpose of tunneling is to allow connectivity between Payments and external payment systems without compromising network security. Processor payment systems, for example, often require protocols, such as FTP or IP socket connectivity to receive payment files. Instead of creating breaches in your firewall to accommodate these connectivity requirements, you can instead deploy the Payments transmission servlet on a host outside your firewall and then tunnel or delegate requests to it from the Payments engine. The Payments transmission servlet does not use the applications database and can be completely isolated from the intranet of your deployment environment.

Tunneling Protocol

Payments uses a customized tunneling protocol called the Oracle Fusion Payments Tunneling Protocol. This protocol uses HTTP POST as its underlying transmission mechanism. HTTPS is also supported. When the tunneling protocol sends a request, it places an XML message header within the body of the request, which is meant to identify the tunneled or encapsulated protocol, as well as the parameters to use when invoking it, such as host name, user name, and password for FTP. The data to be delivered is sent after the XML message header is sent.

As a supported transmission protocol, the tunneling protocol implements the oracle.apps.financials.payments.sharedSetup.transmissions.publicModel.util.TunnelingFunction interface. The following table presents the parameters and descriptions of the Payments tunneling protocol.

Transmission Servlet

Payments transmission servlet is the module which executes tunneled or delegated transmission requests sent from the Payments engine. The servlet receives the Payments HTTP XML delivery envelope requests and parses them into XML message header and transmission data components. The format of the XML message header is defined by an XML DTD file named DeliveryEnvelope.dtd. The message header specifies the transmission protocol, as well as the parameters to pass to the tunneled or encapsulated transmission protocol, using its Java class name and entry function name. The transmission servlet then dynamically loads the Java class implementing the tunneled protocol and initiates it by passing to it the transmission parameters parsed from the XML message header and the transmission data.

This behavior is identical to that of the Payments engine. Any protocol can be tunneled, as long as it implements the oracle.apps.financials.payments.sharedSetup.transmissions.publicModel.util.TransmitFunction interface. Therefore, any custom-defined protocol can be tunneled or encapsulated to the servlet, provided the Java class which implements it is in the CLASSPATH of the servlet's application container. To deploy the servlet to a different host, such as the one in a DMZ network zone, you must copy FinPmtTransmitServlet.war to the transmission servlet's new servlet container. If you want the servlet to support any new transmission protocol that you develop, its Java code must be deployed to the transmission servlet's web application domain.

Configuring Tunneling

Tunneling is configured on the Create Transmission Configuration page. A tunneling transmission configuration is specified as any other transmission configuration, but the protocol is always Payments HTTP XML Delivery Envelope protocol. Once the tunneling protocol is configured, it can use or encapsulate any regular, non-tunneling transmission configuration by specifying a value from the Tunneling Configuration choice list on the Create Transmission Configuration page. Once that is done, ensure that you set up your payment system to support the tunneling protocol and that your corresponding funds capture process profiles and payment process profiles specify the tunneling configuration.

2. Set Up SSL Security to Communicate with the Payment System Servlet

When Payments communicates with the payment system servlets, the information exchanged may be sensitive information such as credit card numbers. If the communication is not secure, it poses a security risk.

The security risk is higher under the following circumstances:

• When Payments and the payment system servlets are installed on separate machines

• When Payments is deployed and operates outside your firewall

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 BASE URL parameter of the payment system to use the https: protocol. Otherwise, change the URLs on any transmission configurations set up to be used with that payment system to contain HTTPS.

Configuring Oracle B2B Inbound Flow to Receive Supplier Invoices in XML : Procedures

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 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.

1. Host Company Configuration

2. Supplier Configuration

1. Host Company Configuration

Perform the following steps to complete Host Company configuration.

1. Set up the Oracle B2B Server.

2. Set up Oracle Supplier Network for the Host Company

   Note

   This step is required only if customers use Oracle Supplier Network as the communication channel.

3. Set up B2B Site Code

1. To set up the Oracle B2B Server, do the following:

   1. Create a supplier trading partner.

      Note

      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, you can create your own supplier trading partners as instructed here.

      1. Sign in to the Oracle B2B Server.

      2. On the left, click Add on the Partner toolbar. The Partner Name dialog box appears.

      3. 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.

      4. On the Documents tab, click Add to add a document definition for the supplier trading partner. The Select Document Definition dialog box appears.

      5. 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.

      6. For the document definition, clear the check box under Receiver.

      7. 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.

      8. Enter the name of the agreement.

      9. On the process train, click the Select Document Definition train stop. The Select Document Definition dialog box appears.

      10. Select the PROCESS_INVOICE_002 document definition mapped to the supplier trading partner and click OK.

      11. Under Agreement Parameters, ensure that the Functional Ack check box is clear, and click Save.

      12. To validate the agreement, click Validate.

      13. Click Deploy. An information message appears, indicating successful deployment of the agreement.

   2. Set up a listening channel.

      Note

      Oracle B2B Server supports multiple protocols for sending/receiving messages between trading partners. You can 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:

      • To set up a global listening channel, click Administration and click the Listening Channel tab.

      • To set up a trading partner listening channel, click Partners and click the Channels tab.

      • No need to set up a listening channel if Oracle Supplier Network is used by the suppliers to send the B2B invoice payload.

        Note

        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.

2. 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. Sign into 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 your system administrator if you do not know the value.

   5. Enter the User ID and password for Oracle Supplier Network.

      Note

      You can specify different values for the Test and Production environments.

   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. You can add all the supplier trading partners who send invoice payloads to the host company.

3. 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.

2. Supplier Configuration

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

1. Sign 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.

5. Enter the User ID and password for Oracle Supplier Network.

   Note

   You can specify different values for the Test and Production environments.

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 Send.

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 host company trading partner.

Setting Up Oracle B2B to Send Receivables Transactions in XML : Procedures

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

Configuring Trading Partners

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

To configure trading partners:

1. Log in to the Oracle B2B Server.

2. Navigate to the Administration page.

3. Click the Document tab.

4. Load the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition file.

5. Click the Types tab.

6. Add a new Internal Identifier with the name B2B Trading Partner Code.

   This name matches the field name on the customer account profile.

7. Navigate to the Partners page.

8. In the Partner regional area, select the default host partner MyCompany.

9. If necessary, update the default host partner name to reflect your enterprise.

10. Click the Documents tab.

11. Verify that the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition is assigned to the host trading partner.

12. Ensure that the Sender option is enabled.

13. In the Partner regional area, click the Add icon.

14. Enter the name of a remote trading partner.

15. Select the Internal Identifier Type B2B Trading Partner Code that you previously created and enter the Value for the identifier.

    This is the value that you will enter in the B2B Trading Partner Code field on the customer account profile of this remote trading partner.

16. Click the Documents tab.

17. Click the Add icon to associate the OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF document definition with the remote trading partner.

18. Enable the Receiver option.

19. Click the Channel tab.

20. 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 you are communicating using Oracle Supplier Network (OSN), select the Generic Identifier and enter the IP Address of the OSN machine.

    For more information about configuring a channel, refer to the Oracle Fusion Middleware User Guide.

21. Repeat steps 13 to 20 for each remote trading partner.

Configuring Agreements

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:

1. Log in to the Oracle B2B Server.

2. Navigate to the Partners page.

3. In the Agreement regional area, click the Add icon to open a new agreement for the host trading partner MyCompany.

4. Enter the agreement ID and Name.

5. Enter the agreement parameters.

6. Select the Document Definition OAG-7.2.1-PROCESS_INVOICE_002-OAG_DEF for this agreement.

7. Select the remote trading partner to include in this agreement.

8. Select the channel for the remote trading partner.

9. Add identifiers for the remote trading partner.

10. Click Save to save the agreement.

11. Click Validate to validate the agreement.

12. Click Deploy to deploy the agreement.

    Deployment is the process of activating an agreement from the design-time repository to the run-time repository.

13. Repeat steps 3 to 12 for each agreement between the host trading partner and this remote trading partner.

Previous

Next

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

Home

Contents

Book List

Contact Us