3Analytics Access, Currency, and Display

This chapter contains the following:

Analytics Work Areas

As an administrator, your job is to create, edit, and maintain analytics for your organization. The work areas are the pages that you use to create and edit all things analytics. You also add analytics for your users on these pages.

Work Area Name Description

Oracle Business Intelligence (BI)

You view, edit, and create analytics in BI. You also can view, edit, and create subject areas here.

Home Page

This page is the main landing spot for you and your users and is the springboard to get to all your analytics pages.

Sales Infolet Page

This page comes prebuilt with infolets specific your user roles. You can do just about anything to change the way this page looks and which analytics show. To get to this page click the white navigation dot on the home page.

Sales Pages

You enable these pages for your users. These five blank pages are available for you to add analytics related to any area.

Object Pages

On these pages sales users work with opportunities, accounts, contacts, activities and so on. Administrators enable the tabs on these pages and add analyses to the tabs on the side or bottom of the page.

Analytics Page

This page is where sales users search for analytics they have permissions to view and make them favorites. Sales users also see analytics that administrators have configured to show specific to their role.

This is an example of an Infolet page.

sales infolet page

This is the Analytics page. It's a page where users add and view analytics.

Analytics page

This is the Opportunities work area. Users can click the analytic icon and view analytics specific to a record. Administrators add analytics to this object page.

Object page analytic

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


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

Analytics library


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


Filters are used in dashboards and analyses.

Prompts folder


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-templates are used by reports created in Business Intelligence Publisher.

Reporting group folder

Analytics Security and Permissions

Some analytics might contain information specific to job roles that you don't want everyone to see. An example might be analytics with salary information. Access to data in subject areas, which in turn are used to build analytics are controlled by permissions. Permissions are authorizations that determine who can see what. Permissions are a part of the security model, and how permissions are initially assigned is based on how users, roles, and groups were initially set up on your application.

The setup administrator has likely assigned you the role of Sales Administrator, or the Sales Administrator might have created a sub-role specifically for administering analytics, such as BI Administrator. As the person responsible for administering analytics, your permissions enable you to access and edit all of the analytics and analytic work areas. You have access to the BI catalogs, dashboards, and tools to create, edit, and add analytics to your team work areas. For more information, see Security Reference for Sales and Service.

BI Administrator Permissions

If you're a Sales Administrator you have lots of permissions already. But you likely want to perform high-level tasks in BI as well. To get these extra permissions you need the BI Administrator role. BI Administrators have access to these additional things:

  • Catalog groups

  • Privileges

  • Sessions

  • Publisher scheduling and delivery

Assign the BI Administrator Role

  1. Sign in as a Security Manager. For example, IT_SECURITY_MANAGER.

  2. Click Tools > Security Console.

  3. Select the Roles.

  4. Click Create Role.

  5. Fill in the required information.

    This is the Create Role page for entering basic information.

    Create job role basic information
  6. Click Next until you come to the Role Hierarchy page.

  7. Click the Plus icon to bring up the Add Role Membership page.

  8. Search All for BI Administrator Role.

    This is the Add Role Membership page for creating roles.

    Add role membership
  9. From the search result select BI Administrator Role and click Add Role Membership.

  10. Click Next until you get to the Users page.

  11. Add the users that you want to have the BI Administrator role. You can assign the BI administrator role to users later too.

  12. Click Next.

  13. Click Save and Close.

Assign Additional Users

After the BI Administrator role is created you can assign additional users to the same role.

  1. Sign in as a Security Manager. For example, IT_SECURITY_MANAGER.

  2. Click Tools > Security Console

  3. Select the Users tab.

  4. Search for the user to be assigned the BI Administrator role.

  5. Select the user and choose Edit.

  6. Click Add Role.

  7. Search for the BI Administrator role you created in the steps for Assigning the BI Administrator Role.

  8. Click Done.

  9. Click Save and Close.

Optimize Analytics Display

Why Use Responsive Sizing?

Responsive sizing ensures that analytics are displayed on your laptop, mobile, or tablet browser in the best possible way. By default you can configure analytics to fit any format, but that doesn't make them responsive to your browser resolution.

When you enable responsive sizing, you ensure the analytic size adjusts to the screen size on your device. This ensures that you view an analytic in as much screen space as possible without distorting the image. Not only does the window adjust to maximize the screen display on the device, but it enables a scroll in the cases where the analytic rows extend beyond the screen size.

This is an analytic before responsive sizing is set up.

Responsive sizing normal view

This is an analytic fully sized to fit the screen with responsive sizing.

Responsive sizing enabled

This is a tabular report before responsive sizing is set up.

Tabular report before responsive sizing

This is a tabular report after responsive sizing is set up. Note how the report now uses all the available screen space.

Tabular report with responsive sizing

This shows how with responsive sizing set up, the graph size changes in size to respond to the browser size.

Graph with responsive sizing change matching browser
size change

Things to Keep in Mind

You can't opt into responsive sizing globally. And Prebuilt analytics can't be set for responsive sizing unless you make a copy. There are a few steps to opt in for each analytic you want enabled.

If you have multiple BI objects on a page, responsive sizing doesn't work. But you can embed a dashboard, or layout quadrant, which can then express multiple analytic objects with responsive sizing. For table views, if it has a large number of columns it will scroll.

You need to set every analytic that you want to be responsive. In some cases you configure the page the analytic is on. This summarizes the pages and steps for setting responsive sizing.

Page Name Setup Requirements

Object Landing or Object Edit Page tabs

  • In BI, set analytic dimensions, and if the analytic is in a dashboard set the dashboard dimensions as well.

  • Working in a sandbox, edit the container parameter and display options.

BI Dashboards

  • In BI, set analytic dimensions, and if the analytic is in a dashboard set the dashboard dimensions as well.

  • In BI, set column and container properties so that dashboard container is larger than the analytic container.

Sales and Service Pages

  • In BI, set analytic dimensions, and if the analytic is in a dashboard set the dashboard dimensions as well.

  • Working in a sandbox , edit the container parameter and display options.

These ares the pages that are available for responsive sizing.

Views that can be resized Views that can be partially resized Views that can't be resized

Columns / Sections

  • DVT graphs

  • Map

  • Tree map view

  • Table, pivot table

  • Trellis

  • Title

  • View selector

Ticker - horizontal only

  • Gauge

  • Some graph prompts

  • Performance tile

  • Funnel

  • Filter

  • All others

Responsive Sizing In Analytics and Dashboards

To create or edit a table with responsive sizing you provide the view and container dimensions. The dimensions can't be blank. You set dimensions to optimize viewing and to ensure the container is larger than the view canvas when it sizes dynamically to fit the device screen size.

These are the component levels to set for analytics sizing:

  • Level 1 -View container (Set in BI)

  • Level 2 - View (Set in BI)

For dashboards, four levels of layout sizing are needed:

  • Level 1 - Dashboard container (Set in dashboard)

  • Level 2 - Dashboard section (Set in dashboard)

  • Level 3 - View container (Set in BI)

  • Level 4 - View (Set in BI)

These are the sizing specifications for analytic components.

Responsive sizing analytic size requirements

These are the browser and related container sizes.

Browser (variable sizes) Content container (fixed sized)

1094 x 939

933 x 737

1302 x 939

1192 x 737

1468 x 939

1350 x 737

1790 x 939

1509 x 737

Set View Dimensions

  1. In the results view of your analytic, click View Properties.

    This shows the View Properties selection for an analytic.

    View properties for an analytic
  2. Choose the General tab.

  3. Set the height, and width of the analytic canvas. You must define the size of the analytic to fit the size you have available in the container that holds the analytic. It doesn't matter which device you use to view the analytic, as long as you have set the size of the analytic in your window in BI to maximize the space available in the container. Setting the height and width ensures that the view of this analytic is responsive on all devices. The default is set to not define a size. You need to define a size for responsive sizing to be set.

    This shows the General tab for graph properties, and the canvas width and height options.

    Graph properties width and height

Set Analytic View Container Dimensions

  1. In the results view of your analytic click Format Container.

  2. Adjust the sizing to make sure the container is larger than the canvas. Since we previously set canvas size to 830 and 265, we set the container to a larger size at 835 and 270. Note that if you also add title containers, the size needs to match the size set for the analytic container.

    This shows the Width and Height options for the Format Container dialog.

    Width and Height options for format container

Set the Dashboard Container Dimensions

If your analytic is in a dashboard you set the dashboard for responsive sizing. For BI dashboards that hold analytics you set each container component on a dashboard to be responsive.

Set the properties for width and height for the container components to be larger than the properties set for your analytic. In this case, since we previously set our analytic container to 830 and 265, we set our dashboard container to a size larger than the dimensions set for the analytic container.

To set the dashboard container dimensions:

  • Select the container. Click Column Properties.

    This shows the Column Properties option for a dashboard container.

    Column properties for dashboard containers.
  • Select the column. Click Format Section.

    This shows the Format Section option for a container in a dashboard.

    Format section in a dashboard.

    This shows the Height and Width options for Column Properties of a dashboard.

    Column properties

Compound View and View Editors

Compound views are also available for setting up responsive sizing.

This shows the edit container option.

Edit container

This shows options for setting the text properties in the fields. Set title cell properties using the A icon to the right of the field.

Set title orientation.

In the Cell property dialog set the vertical alignment to Center to set the title to float vertically in the resized container. This setting is recommended.

Set vertical alignment to center.

For tables, set the following:

  • Select "Fixed headers with scrolling content" to add sizing values.

  • Set Vertical Alignment = "Center" in the Table's view container if you want the table to float vertically in the middle of the resized container.

This figure shows a table, with the option to edit the table view container properties.

Edit view container in a table.

For pivot tables select "Fixed headers with scrolling content" to add sizing values.

This shows a pivot table with the option to edit the pivot table view container properties.

Edit view container for pivot table.

Responsive Sizing on Interface Pages

Analytics and analytic interface components all must have the sizing set for responsive sizing to work.

Set the Analytics Tabs on Interface Pages

Once your analytic is set with the proper sizing, the next step is to add the analytic to your interface and set the layout specifications.

  1. Add the analytic to the object tab.

  2. Open a sandbox.

  3. Under Setting and Actions choose Edit Pages.

  4. In the Edit Pages dialog, select internal.

  5. Click OK.

  6. Navigate to the page to set up.

  7. Click Change Layout.

  8. Navigate to the analytic and click Add.

  9. Click Edit.

    This shows the edit option for a dashboard container.

    Dashboard layout layers
  10. Under the Parameters tab, change the sizing to "content" and remove any height and width values so that the field is empty.

    This shows the Height and Width options as well as the Sizing option.

    Dashboard compound properties dialog
  11. Click the Display Options tab.

  12. Click the Advanced tab.

  13. Under Stretch Content, set the value to "false".

Best Practices For Sizing

Traditional BI Content typically doesn't have all these sizes specified. The following are some recommendations for getting the best sizing results.

  • Use original content as a guide and size from the inside out., Start adding sizes for views first. Follow this by adding sizes to view containers. Save the report then make adjustments to Dashboard Sections, and then Dashboard Columns. When tweaking dashboard containers, set their size to the specific size then tweak to minimize scroll bars.

    An inspector tool like Firebug can make this process much easier by allowing temporary edits in place. You can then go back and add the values in the dialog. Add 20 pixels to dashboard container heights as this gets deducted by the dashboard code (presumably to reserve space for the collapsible icon).

    When you're done tweaking, set the dashboard, columns, and sections to the minimum size setting. This setting removes the overflow behavior and prevents scroll bars from appearing on BI content.

  • Measure pixels in original content to obtain starting size values. Use a pixel measuring tool (like Measure or others) to measure pixels on the screen to find starting sizes for views. Similarly, measure pixels on the screen to help figure how many pixels to add or deduct for components that can't be resized within views. For example, the View Selector widget needs approximately 40 pixel height.

  • Build in padding sizes. BI styles typically have some padding built in to their CSS. The BI resizing code works best when taking this into account. Moving from sections to columns, try adding 3 pixels per border. For example, if you have two sections in a single dashboard column, they contribute four borders. So make the column value 12 pixels larger than the sum of the sections. When working up from views to view containers, try adding the same 3 pixels per border. Note that the 3 pixel padding recommendation is suitable for the Alta style. Custom styles may need more or less padding to be built into the math. You can validate the dashboard behavior using the specific size setting. In general, more padding is safer but could contribute marginally to less predictable behavior.

  • Make sure the math works out. BI builds up the sizing map based on nested layout objects. Resizing falls apart if any parent container size is sized smaller than the content that it contains. For example, if a graph size is 300 x 200 and its view container is 350 x 250, then section and column containers must be larger than 350 x 250. If the section were set to 300 x 200, for instance, resizing wouldn't work.

    This shows a dashboard with an analysis that has a compound layout with titles and two views to choose from. Colors added to highlight the layout components.

    Figure shows the sections for sizing

Currency Settings for Analytics

Currency and Exchange Rate Settings for Analytics

CX Sales applications let you to decide how currency is shown in the application, as well as preferences for how analytics show currency and calculate exchange rates. Currency can be set in different regional currency types, depending on where you do business and what currency types you want to see.

There are three ways you set up currency:

  • User Currency - Set by the business user in Regional settings. This setting applies to the entire application interface for that user only. The available currency options are set by your application administrator.

  • Analytics Currency - Set by the business user in BI in My Account settings in the Reports area. The setting applies to that user only and is only relevant for analyses.

  • Corporate Currency - Set by the application administrator. This setting applies to all users in that company.

Note: The time zone preferences that you set in your fuse simplified user interface are inherited in OTBI and will be used as the time zone setting for your existing and new analytics.

Set General User Currency

User currency settings determine the currency used as the default for what you see in your application. User currency applies to your entire interface for your signed-in session.

  1. Navigate to Tools, Set Preferences.

  2. Select General Preferences > Regional.

  3. Select the preferred currency to be used. Available currencies include those set up for your company by your application administrator.

Set Analytics Currency

The analytics currency settings determine the currency type that's displayed in all your analytics. It also determines how and when your currency conversion rates are calculated.

  1. Navigate to Business Intelligence.

  2. Click Analytics in the navigator menu.

  3. Click Browse Catalog.

  4. Click your user name and select My Account.

  5. Go to the Preference.

  6. Select your choice in Currency.

This shows the currency display options for users:

Currency Display Type Description

Entered Currency

Currency used on a transaction.

<Application> Currency

Currency set up in each respective Cloud application as the common Corporate currency used company-wide.

User Preferred Currency using Simple Currency Management

Conversion to User Preferred Currency is performed at the time your run the report, and is calculated from the Corporate currency based on the last time the record was updated and saved or closed.

User Preferred Currency using Advanced Currency Management

Conversion to User Preferred Currency happens on the date your run the report, and uses the currency indicated on the record.

Set a Global Currency Conversion Profile

Set a global currency conversion method for all your users by creating a currency profile. Only administrators can create currency profiles.

  1. In Setup and Maintenance, go to Manage Profile Options.

  2. Enter the following values:


    • Profile Display Name : BI Default Currency Conversion Method

    • Application

    • Module

    • Start Date : Provide previous day's date to proceed to next step to define values.

  3. Click Save and Close.

  4. In the Manage Profile Options dialog box, you see your new profile. Check the Enabled box for Site.

  5. Click Save and Close.

Define Currency Profile Values

After you create your currency profile, the last step is to define the profile value. This step defines which currency management option is assigned to that profile.

  1. In the Setup and Maintenance work area, useManage Administrator Profile Values.

  2. In Profile Option Code search for your profile: BI_DEFAULT_CURRENCY_CONVERSION_METHOD.

  3. In Manage Administrator Profile Values, Click Add (+ icon).

  4. Select Site as the Profile level.

  5. Enter "User Preferred Currency 2" in Profile Value.

  6. Click Save and Close.

How User Preferred Currency Exchange Works

The simple and advanced user-preferred currency choices determine how and when your currency exchange rates are calculated for your reports. For both simple and advanced currency management, when you save or close a report, the application sets the exchange rate at that time. The option you choose impacts how quickly your reports are generated at run time. Each case includes trade-offs, as detailed in the examples.

User Preferred Currency using Simple Currency Management

The advantage of this option is performance - the application doesn't have to look up the rate for each transaction because when you close or save a record, the application converts it to your corporate currency at that day's rate. When you run the opportunity report, the application multiplies that value by your preferred currency exchange rate for the date you run the report. This eliminates the need for the application to cycle through each record, and calculate the corresponding exchange rate to your preferred exchange rate at the time that record was closed or last saved. It simply takes the value on record for the original transaction exchange to corporate currency, and multiplies it by your preferred currency exchange rate at the time your run the report.

As an example of user preferred currency using simple currency management, a user updates and saves or closes an opportunity record with associated revenue of one million Indian Rupees on January 31st with an exchange rate of 0.01401 Rupees to one US Dollar. The user then runs an opportunity report in US Dollars on March 31st. In the report, the US Dollar Corporate Currency is set at the January 31st rate it was saved at, in this case reporting as $14,010, or one million multiplied by 0.01401. Finally, an opportunity report on March 31st in Euros uses the March 31st conversion rate for US Dollars to Euros of 0.75017 to convert the recorded US Dollar amount into Euros, in this example one million multiplied by 0.01401, which is the January 31st Rupee to US Dollar exchange rate, multiplied by 0.75013, which is the March 31st rate for Euros. This requires less processing, because the January 31st Rupee to US Dollar exchange rate, while not exact on March 31st, is used as the basis for the calculation of the March 31st opportunity revenue conversion to Euros at the later exchange rate.

The following figure describes an example of user preferred currency using simple currency management.

User preferred currency using simple currency management.

User Preferred Currency using Advanced Currency Management

This option provides a more precise exchange rate, since it goes through each record to determine the rate on the date the record was updated or closed. The downside of this option is performance. Your reports will take longer to run. The application has to cycle through each record and match currency exchange rates to the date the record was closed or updated and saved.

As an example of user preferred currency using advanced currency management, a user updates and saves or closes an opportunity record with associated revenue of one million Indian Rupees on January 31st, when an exchange rate of 0.01050 Rupees to one Euro applies. The user then runs an opportunity report on March 31st. In the report, the User Preferred Currency of Euros is applied, using the January 31st Rupee to Euro rate of 0.01050, requiring calculation during report processing to resolve the opportunity to 10,500 Euros. Note that running the opportunity report on March 31st doesn't change the calculation and the close date of January 31st is used.

The following figure describes an example of user preferred currency using advanced currency management.

User Preferred Currency using advanced currency

Why do I see amounts of zero in analyses?

The currency exchange rates might not be set up correctly. For example, you choose EUR as your preferred currency in general preferences, and your corporate currency is USD. Amounts in analyses are displayed in EUR after conversion from USD, based on the current exchange rate. But if the exchange rate between EUR and USD isn't set up, or if the conversion fails for any reason, then the amounts show as zero.