1Overview

This chapter contains the following:

Analyses and Reports: Administrative Overview

Analyses and reports in Oracle Applications Cloud are built using Oracle Business Intelligence (BI) tools and technologies, which you also use for administration and setup. Oracle Business Intelligence provides several tools and a variety of report types to meet different reporting requirements.

Oracle Transactional Business Intelligence is a real-time, self-service solution that lets users create ad hoc analyses and reports with real-time transactional data, using different Oracle BI technologies.

  • Analyses are visualizations, such as charts and tables, of a specific set of data. An analysis can be embedded into an application page, or included as a component of a dashboard. Analyses are generally interactive, allowing users to configure the presentation of the data in real time.

  • Dashboards are a collection of analyses grouped together to return data.

Operational reports are static reports that meet operational and statutory reporting requirements. Operational reporting includes the generation of high-volume business documents such as payroll and invoices. Oracle Business Intelligence Publisher is the tool for operational reporting, and many predefined reports may be provided with your applications.

Tools for Administering Analyses and Reports

You can use several different tools to manage and administer your analytics. Analytics can be reports or analyses, depending on how you intend to display and distribute them.

These components support modification and administration of your analyses and reports:

  • Use the Business Intelligence catalog to interact directly with your reports and analyses. Use this interface to manage permissions, properties, and the organization of your analyses and reports.

  • Use the Oracle Business Intelligence Publisher administration pages to configure settings specific to the running and scheduling of operational reports, such as setting up your delivery servers, managing scheduler work load, and setting run-time properties for reports.

Business Intelligence Catalog

There are two major work areas for analytics administration. The main interface is where your users view the analytics administrators set up in user work areas and on the infolet pages. The second area is the business intelligence catalog. Reports, analyses, dashboards, and other business intelligence (BI) objects are stored and administered in the business intelligence catalog. BI is where you build and edit analytics for your user work areas. You can toggle back and forth between the two areas.

Navigate to the Catalog

  1. Click Tools > Reports and Analytics in the Navigator.

  2. In the Reports and Analytics work area, click the Browse Catalog button.

Objects in the Catalog

The catalog stores the BI objects in a folder structure of individual files, organized by product family.

BI objects and reports are organized in the following folder hierarchy:

  • Shared Folders (parent)

  • Product family (example: Financials)

  • Product (example: Payables)

  • Report groups (example: Invoices)

  • Dashboard reports

  • Data Models

  • Report Components

  • BI Publisher reports

  • Prompts

The following table describes the common BI objects that you find in the catalog:

Catalog Object Description Location

Analysis

Analyses are used for infolets, the Sales pages, and on object pages such as Opportunities.

Analytics library

Dashboard

Dashboards organize analytical content and catalog objects, and present them in a meaningful way.

Reporting group folder

Dashboard Prompt

Dashboard prompts allow users to filter dashboard content using provided values.

Prompts folder

Filter

Filters are used in dashboards and analyses.

Prompts folder

Report

Reports are operational reports in printable format created in Business Intelligence Publisher.

Analytics library

Data Model

Data models are used by reports created in Business Intelligence Publisher.

Data Models folder

Sub-template

Sub-templates are used by reports created in Business Intelligence Publisher.

Reporting group folder

Oracle Fusion Financial Reporting Center is a powerful tool for reviewing, 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 the Financial Reporting Center

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

  • Installing Smart View, performed by your end users

  • Configuring Workspace Database Connection, performed by your administrator

Configuring Financial Reporting Center

You have access to the reports in the Financial Reporting Center and Workspace installed with Oracle Fusion Financial Applications. Your Oracle Fusion Business Intelligence (BI) administrator defines the folder structure in Workspace. The administrator considers your 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.

  • You are granted access to the folders and reports you want to view by your BI administrator.

Installing and Configuring Financial Reporting Studio

Oracle Financial Reporting Studio is client-based software. If you open Oracle Fusion Applications from Oracle Cloud, you connect to the Financial Reporting Studio through a Windows Remote Desktop Connection. Report authors download installation files for Financial Reporting Studio from Workspace by clicking Navigator > Financial Reporting Center > Tasks panel drawer > Open Workspace for Financial Reporting. Once Workspace is started, click Tools > Install > Financial Reporting Studio. After performing the prerequisites and completing the installation, start the Financial Reporting Studio. Provide your user ID, password, and the Server URL. Derive the Server URL information by following the steps:

  1. Open Navigator > Financial Reporting Center > Tasks panel drawer > 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.visioncorporation.com/workspace/index.jsp, the Server URL is https://fusionsystemtest-p-external-bi.visioncorporation.com.

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

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

Note: For end users installing the Oracle Fusion Financials Reporting Studio, the installer starts a separate console window. The installer continues to run for a brief time after the installation completes the setup tasks. The process is normal, expected, and applies to Oracle 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 the Finish button on the Financial Reporting Studio Installation dialog box. If you click the Finish button before the console window closes, the Financial Reporting Studio installation may not complete.

Note: You must save a new report before attempting to preview it with Web Preview.

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 users' computers.

Installing Smart View

Smart View is an Excel add-in that must be loaded on each client. To download Smart View, click Navigator > Financial Reporting Center > Tasks panel drawer > Open Workspace for Financial Reports. Once the workspace is started, click Tools > Install > Smart View.

Note: Since Smart View is an add-in to Microsoft Office products, you can install Smart View only on a Windows operating system.

Once Smart View is installed, you must configure the connection using the Smart View Shared Connections URL. You can derive the Shared Connections URL by following these steps:

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

  2. Edit the workspace URL by removing index.jsp and adding SmartViewProviders at the end.

    Note: The following URL is an example for a Cloud-based environment. If the workspace URL is https://efops-rel5st4-cdrm-external-bi.visioncorporation.com:10622/workspace/index.jsp, the Shared Connections URL is https://efops-rel5st4-cdrm-external-bi.visioncorporation.com:10622/workspace/SmartViewProviders.
  3. Copy the URL.

  4. Open Excel.

  5. From the Smart View menu, click Options > Advanced.

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

  7. Click OK.

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. Navigate to the Smart View menu > Open. On the Start on the ribbon, click Smart View Panel that appears in the list of values from the ribbon. The task pane opens.

  3. Click Shared Connections on the task pane.

  4. Sign in with your user name and password.

  5. Click the Select Server to proceed list of values.

    Note: If the Essbase Server is not there, then it has to be added. Use the following steps:
    1. Click the Add Essbase Server link.

    2. Specify the Essbase Server login and password.

    3. Expand the Essbase server and locate the cube in 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 db.

  10. Click the analysis link.

Note: You must perform these steps only once for a new server and database.

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

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

Note: The Smart Slice feature is not supported in Oracle Fusion General Ledger. For all other documentation, refer to the Oracle Smart View for Office User's Guide.

Configuring Workspace Database Connections

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

Note: 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. A separate cube is created for each combination of chart of accounts and accounting calendar. A database connection is needed for each cube.

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

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

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

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

For more detailed information about Smart View and Financial Reporting Studio, refer to the Using EPM with Oracle Financials Cloud link on the Books for Oracle Financials Cloud page of the Oracle Help Center at https://docs.oracle.com.

Mapping to Work Areas

You can find the Reports and Analytics panel tab in many work areas, and the analytics and reports you see in it depend on the work area. You can define what's available for a specific work area, by mapping reports from the business intelligence (BI) catalog to that work area. In this mapping context, reports refer to both analytics and reports. Your changes apply to all users who have access to the work area you're mapping.

Mapping Reports from Your Work Area

To map reports to the work area that you're in:

  1. Expand the Reports and Analytics panel tab.

  2. Click the Edit Settings icon in the panel tab.

    You see all the reports that are currently mapped to your work area.

  3. Click Select and Add.

  4. Find the report in the catalog and select it.

  5. Click OK.

  6. To remove any mapping, select the report and click Remove.

  7. Save your work.

Mapping Reports to Any Work Area

To map reports to any work area that you have access to:

  1. In the Setup and Maintenance work area use the Map Reports to Work Areas task.

  2. Select the application of the work area you want to map to.

  3. Select the work area.

  4. Click Search and see all the reports that are currently mapped to that work area.

  5. Click Select and Add.

  6. Find the report in the catalog and select it.

  7. Click OK.

  8. To remove any mapping, select the report and click Remove.

    Tip: Click Synchronize to remove all mappings to any reports that are no longer in the catalog. You synchronize all work areas, not just the one you're mapping.
  9. Save your work.

Either no reports are currently mapped to the work area you select on the Map Reports to Work Areas page, or you don't have access to the reports that are mapped.

Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator to either:

  • Assign you roles that have access to the reports you want to map to work areas.

  • Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.

In the Edit Settings window, you might not see a currently mapped report because you don't have access to it.

Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator to either:

  • Assign you roles that have access to the reports you want to map to work areas.

  • Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.

Configuring Business Intelligence Publisher

Overview of Report Delivery Servers Management

Oracle Business Intelligence Publisher, the report generation and delivery engine, requires configuration and tuning to deliver reports to users.

Report requests are received by Publisher from:

  • Oracle Enterprise Scheduler

  • The Reports and Analytics work area and panel tab

  • Application pages

Requests submitted through Oracle Enterprise Scheduler are processed by the Oracle BI Publisher scheduler. Requests submitted through the Reports and Analytics work area or panel tab can be either real-time online requests or scheduled requests. Requests submitted through an application may call Oracle Enterprise Scheduler or may return report request results directly back to the application page.

Oracle BI Publisher is configured to accept requests from Oracle Applications Cloud. However, before you can deliver report documents to their destinations, you must define the delivery servers in Oracle BI Publisher. Use the Oracle BI Publisher Administration page to define your delivery servers.

Once delivery servers are defined, you can further configure the number of report processor and delivery threads to best handle your processing and delivery requirements. In addition, you can configure report properties for the delivery servers or at the report level to tune performance of your reports. To diagnose report processing issues, BI Publisher provides a set of scheduler diagnostics.

Navigate to the BI Publisher Administration Page

You use the Oracle BI Publisher Administration Page to perform most tasks related to report delivery and performance.

Use the Oracle BI Publisher Administration page to:

  • Configure delivery servers

  • Manage report and delivery processors

  • View scheduler diagnostics

  • Set system properties and report runtime configuration properties

Request the Oracle Applications Cloud security administrator to assign the BI Platform Administrator duty role (BI stripe) to the person responsible for administering BI analyses, dashboards, and BI Publisher reports. Administration tasks include security permissions for objects, organizing objects into folders, accessing log files, and several other tasks.

Navigating to the Administration Page

To navigate to the Oracle BI Publisher Administration page:

  1. Click Tools > Reports and Analytics in the Navigator.

  2. In the Reports and Analytics work area, click Browse Catalog.

  3. In the Catalog page, click Administration, then click Manage BI Publisher.

Configure Report Delivery Servers

Set up the report delivery servers to support printing.

Configuring Servers

To configure delivery servers:

  1. From the BI Publisher Administration page, click Delivery Configuration.

  2. Enter values in the Delivery Configuration Options tab to set general properties for email deliveries and notifications.

  3. To configure a delivery server, click the appropriate tab. You can also configure role-based access to delivery servers.

Overview of Report and Delivery Processors

When Oracle Enterprise Scheduler initiates a job, it is picked up by the BI Publisher scheduler queue.

  • Job Processor: Listens for requests from the scheduler queue. When the job information is received, the job processor executes the data model (and splits the data for bursting jobs), stores the data in the shared temporary folder, and sends the report metadata to the report queue.

  • Report Processor: Listens for requests from the report queue. When the report information is received, the report processor generates the report documents, stores it in the shared temporary folder and puts the delivery information in the delivery queue.

  • Delivery Processor: Listens to the delivery queue and handles the delivery of reports for its channel. The delivery processors are:

    • Email Processor

    • File Processor

    • FTP Processor

    • Print Processor

    • WebDAV Processor

    • Fax Processor

Manage Report Processing and Delivery Server Load

Manage the processors in the BI Publisher Scheduler Configuration page.

Managing Processing and Server Load

By default, each processor is enabled and the thread count for each is set to five. For each managed server that is running in the BI cluster, a table for that instance's processors is displayed. Use the table to enable or disable processors for the instance and configure the thread counts.

To configure processor threads:

  1. From the BI Publisher Administration page, click Scheduler Configuration.

  2. In the Cluster Instances region of the Scheduler Configuration page, enter the Number Threads value in the processor configuration table.

  3. All processors are automatically set to use the number of threads defined in the Threads Per JMS Processor value of the JMS Configuration region of the page. Enter a value in the Number Threads column to change the value from this default.

After performing the scale-out procedure, configure the processor threads for each cluster instance using the same steps.

Diagnose Report Processing Issues

The Scheduler Diagnostics page provides the runtime status of the scheduler. Among others, it provides status of its JMS configuration, JMS queues, cluster instances, scheduler Database, and Oracle Enterprise Scheduler.

Diagnosing Issues

To access the Scheduler Diagnostics page:

  1. Navigate to the Oracle Business Intelligence Publisher Administration page.

  2. In the System Maintenance group, click Scheduler Diagnostics.

Configure System Properties for Reports

Use the Oracle BI Publisher Runtime Configuration page to set the system-level runtime properties for reports.

Configure Reporting Properties

To access the Runtime Configuration page:

  1. Navigate to the Oracle Business Intelligence Publisher Administration page.

  2. In the Runtime Configuration group, click Properties.

FTP and SFTP Delivery Retry Property

By default, if FTP or SFTP delivery fails, another attempt is made to deliver the file to the failed destination 10 seconds later. When you set the Enable FTP/SFTP delivery retry property to False, no retry attempt is made. This setting affects all of the FTP and SFTP delivery requests, and can't be configured for individual servers.

XPT Template Properties

Configure XPT templates by setting the properties described in the table.

Property Name Description Default

XPT Scalable Mode

When you set this property to true, scheduled reports that use the XPT template and include a large amount of data run without memory issues. The first 100,000 rows of data in the report are stored in memory and the remaining rows are stored in the file system.

For reports that contain smaller amount of data, you can set this property to false. So, scheduled reports that use the XPT template are processed in-memory.

true

Enable Asynchronous Mode for Interactive Output

When you set this property to true, interactive reports that use the XPT template make asynchronous calls to Oracle WebLogic Server.

When you set this property to false, interactive reports that use the XPT template make synchronous calls to Oracle WebLogic Server. Oracle WebLogic Server limits the number of synchronous calls. Any calls that are stuck expire in 600 seconds.

true

Upload and Apply PGP Keys for PGP Encryption for FTP Delivery

To secure report delivery through the FTP/SFTP channel, you can encrypt the report using PGP Encryption.

Upload PGP Keys

You upload, test, and delete PGP keys in the BI Publisher Administration page.

To upload PGP keys:

  1. Navigate to the BI Publisher Administration page.

  2. In the Security Center section, click the PGP Keys link to open the PGP Keys page.

  3. In the PGP Keys section, click Browse and select the PGP key file in the Open dialog box.

  4. Click OK.

  5. Click Upload. After the file is uploaded, it is imported into the keystore and its details are visible in the PGP Keys table. If a key with the same ID is imported again, the file is overwritten.

  6. Click the Download icon of the key in the Encrypted Test Output column of the PGP Keys table to download and decrypt a test output file using the secret key of the imported public key. Successful decryption confirms the encryption is working for your keys.

Delete a PGP Key

To delete an imported public key, click the Delete icon.

Apply PGP Encryption to FTP Delivery Channel

To create an FTP channel:

  1. Navigate to the BI Publisher Administration page.

  2. In the Delivery section, click the FTP link to open the FTP page.

  3. Add a new FTP Server, using the user name and the password and private key password set when you created the PGP key. The Filter Command field is read-only and is updated automatically when you select a PGP key.

  4. Click Test Connection.

  5. Select the PGP Key ID of the key you uploaded from the list.

  6. If you want PGP encrypted output in ASCII armored format on the destination FTP server, select the ASCII Armored Output check box. The Filter Command is updated with a -a option.

  7. Select the true check box for Sign Output to sign the encrypted document. If you select this check box, a -s parameter is added to the existing filter command.

  8. Test the connection again. The FTP delivery channel can now be used in a scheduled job.