3Setup and Configuration

This chapter contains the following:

Managing Analytics with the BI Administrator Role

The Sales Cloud Administrator is a role that has the permissions to create and manage analytics for end users. Although the Sales Administrator role has many privileges in BI, if administrators or other users want to perform high-level tasks in BI, they must be assigned the BI Administrator duty role by the Security Administrator. BI Administrator tasks include but are not limited to managing the following:

  • Catalog Groups

  • Privileges

  • Sessions

  • Publisher Scheduling and Delivery

Assigning the BI Administrator Role

Security Administrators assign the BI Administrator role in the security console.

To 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 tab, if the tab is not already selected by default.

  4. Click Create Role.

  5. Fill in the required information.

    This figure shows 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 figure shows 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 all users that must have the BI Administrator role assigned to them. You can assign the BI administrator role to users later as necessary.

  12. Click Next.

  13. Click Save and Close.

Assigning Additional Users to the BI Administrator Role

Once the BI Administrator role is created, additional users are easily added to this role in the security console.

To add additional users to the BI Administrator 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.

Managing Sales Cloud User Adoption Analytics

Sales Cloud can track and monitor system usage on the application. User activity or user adoption is stored in two new subject areas which can be used to build analytics which provide information about user activity.

To enable the user adoption features administrators must do the following:

  • Enable user adoption tracking in Setup and Maintenance

  • Assign or be assigned the role of FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY

New Subject Areas for User Adoption

Two new subject areas are available for building analytics for user adoption:

  • User System Usage: This subject area provides the key user adoption metric at the application user level.

  • Sales - CRM Resource: This subject area provides the mapping between the user and the Sales Cloud specific resource object.

Key Metrics for User Adoption Subject Areas

The primary metric that is used in the user adoption subject areas is # of Active Days. This metric provides information about an activity such as when a user signed in on a mobile device has used the application for three days without logging out. The # Active Days metric show a value of 1 for each of the three days. The value is not a sign-in count. In addition, the day boundary is based on the Sales Cloud server time zone.

Additional characteristics of the key metrics for user adoption subject areas are the following:

  • The retention period for information is set at 12 months.

  • Sales Cloud sessions can be tracked for usage channels for web and mobile.

  • Tracking differentiates between user activities made directly by the user, or through a proxy user.

Apart from this, there are two additional Metrics which are # of Active Users/Resource and # of Users/Resource.

Note: To ensure that existing reports that you created in R12 work after you upgrade to 18A+, you must apply the # of Active Days > 0 filter to your analytics.
Note: The User System Usage subject area has been designed to show usage for all Time Period and Users/Resources. The functionality is designed this way to allow reporting on time periods where the user has used the system and there have been activities, as well as those months where there were no activities/system usage. For this reason, when a custom report is built that includes a Time Period at either Year or Month, you must restrict the report result by that specific time period. in this case, for the current year. Without this filter, the report shows results for the complete 100 years Time dimension that Oracle Sales Cloud supports.

Follow these guidelines for reporting with the User System Usage Subject Area:

  • Add a filter for a specific year.

  • Avoid reporting by date. Instead use Month or Quarter.

  • Consider filtering by group of users, instead of individual users.

For the best performance, Oracle recommends that you apply a filter on the # of Active Days fact > than 0 to ensure the report shows up with positive reporting values.

Enabling User Adoption

Administrators or implementation users enable the user adoption system tracking process in Setup and Maintenance.

To enable user adoption system tracking:

  1. Go to Setup and Maintenance.

  2. Search for Manage Administrator Profile Values.

  3. Search for profile option code FND_TRACK_USER_ACTIVITY and ensure that it is enabled.

    This figure shows the profile value as "ENABLED" for FND_TRACK_USER_ACTIVITY profile.

    Profile enabled for BI User System Usage Duty role

Assigning User System Usage Duty Role

The User System Usage subject area holds all the activity information for all the users of the Oracle Sales Cloud system. This subject area is secured and can be accessed by users who have the role FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY or by users who have the BI Administrator role.

To assign the User System Usage Duty role:

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

  2. Click Tools > Security Console.

  3. Select the Roles tab, if the tab is not already selected by default.

  4. Click Create Role.

  5. Fill in the required information.

  6. Click Next until you come to the Role Hierarchy page.

  7. Click the role name and then click Add Role Membership.

  8. Search for the BI Duty Role by name or code: FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY .

    This figure shows the Add Role Membership dialog with the new duty role content.

    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. Click Add User and search for the users to assign this role. Click Add user to Role.

  12. Click Next.

  13. Click Next to go to the Summary and Impact Report. Click Save and Close.

Assigning Additional Users

Once the new role is created, additional users are easily added to this role in the security console.

To add additional users to the BI Administrator 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 role.

  5. Select the user and choose Edit.

  6. Click Add Role.

  7. Search for role you want to assign, in this case the BI System Usage SA Custom Role.

  8. Select the Role and click Add Role Membership.

    This figure shows the search roles, and the Add Role Membership.

    Add role membership.
  9. Click Done.

  10. Click Save and Close.

Understanding Analytics Security and Access

Permissions are authorizations that are granted to a user or role to perform a specific action or group of actions on analytics objects. Permissions are a part of the security model, and how permissions are initially assigned is based on how users, roles, and groups were 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. As the person responsible for administering analytics, your permissions enable you to access all of the analytics work areas. You have access to the BI catalogs, dashboards, and tools to create, edit, and add analytics to your sales team's work areas.

Tools for Administering Analyses and Reports: Explained

You can use several different tools to manage and administer analyses and reports.

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: Explained

Reports, analyses, dashboards, and other business intelligence (BI) objects are stored and administered in the business intelligence catalog.

Navigating to the Catalog

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

Identifying 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 primarily by dashboards.

Report Components folder

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 created in Business Intelligence Publisher.

Reporting group folder

Data Model

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

Data Models folder

Subtemplate

Subtemplates are used by reports created in Business Intelligence Publisher.

Reporting group folder

Understanding Responsive Sizing

Responsive Sizing for Sales Cloud Analytics: Overview

Responsive sizing ensures that analytics are displayed on your laptop, mobile, or tablet browser in the best possible way. By default, BI allows users to configure the report to fit any particular format they want. However, this technique does not allow the report or chart to be responsive to the user screen resolution.

Enabling responsive sizing for your analytics ensures that when users are viewing an analytic, the analytic size adjusts to the screen size on device they are using. This ensures that users view the analytic in as much of the screen space as possible without distorting the image. Not only does it 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 figure shows an example of an analytic before responsive sizing is set up.

Responsive sizing normal view

This figure shows an analytic fully sized to fit the screen in which it is being viewed.

Responsive sizing enabled

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

Tabular report before responsive sizing

This figure shows 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 figure 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

Responsive Sizing Page and Setup Requirements

There is no way to opt into responsive sizing globally. Prebuilt analytics cannot be set for responsive sizing. You must do a few steps to opt in for each analytic you want enabled. To enable responsive sizing for prebuilt analytics, you must make a copy, and enable the copy with the same steps for enabling custom analytics.

If you have multiple BI objects on a page, responsive sizing does not work. In this case, 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 must set every analytic that you want to be responsive. This makes the analytic responsive on any device on which users will view it. In addition, in some cases you must configure the page on which the analytic is viewed. The following table shows a summary of the pages and steps for setting responsive sizing on that page.

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

The following table shows pages that are available for responsive sizing.

Views that can be resized Views that can be partially resized Views that cannot 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

Setting Responsive Sizing for Sales Cloud Analytics

There are a few steps to enabling an analytic for responsive sizing in BI. When you create or edit the table or chart, and you want responsive sizing, you must provide the view and the container dimensions. The dimensions cannot be blank. The reason you are setting these dimensions is to optimize the analytic for viewing, and to ensure the container is larger than the view canvas when it sizes dynamically to fit the user's device screen size.

The following 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)

This table shows the sizing specifications for analytic components.

Responsive sizing analytic size requirements

This table shows the browser size and the related container size.

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

Setting Analytic View Dimensions

To set up the analytic for responsive sizing go to BI, open the analytic and set the view dimension.

To set the analytic view properties:

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

    This figure 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 your users 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 no defined size and you must define a size for responsive sizing to be set for that analytic.

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

    Graph properties width and height

Setting Analytic View Container Dimensions

To set analytic container dimensions:

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

  2. Adjust the sizing to make sure that the container is larger than the canvas. In this case, 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 will need to match the size you have set for the analytic container.

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

    Width and Height options for format container

Setting the Dashboard Container Dimensions

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

Set the properties for width and height for the container components so that they are 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 figure shows the Column Properties option for a dashboard container.

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

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

    Format section in a dashboard.

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

    Column properties

Working with Compound View and View Editors

Compound views are another consideration for setting up responsive sizing.

This figure shows the edit container option.

Edit container

This figure 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 figure shows a pivot table with the option to edit the pivot table view container properties.

Edit view container for pivot table.

Setting Responsive Sizing on Sales Cloud Interface Pages

Analytics and the dashboards and the interface pages that hold the analytics and dashboards all must have the sizing set for responsive sizing to work.

Setting the Analytics Tabs on Interface Pages

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

  1. Add the analytic to the object tab.

  2. Open a sandbox.

  3. Under Setting and Actions choose Customize Pages.

  4. In the Customize Pages dialog, select internal.

  5. Click OK.

  6. Navigate to the page you are setting up.

  7. Click Change Layout.

  8. Navigate to the analytic and click Add.

  9. Click Edit.

    This figure 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 figure 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".

Recommendations and Specifications

Traditional BI Content typically does not 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 are 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.

    For analytics, two levels of layout sizing are needed:

  • 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 cannot 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 would not work.

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

    Figure shows the sections for sizing

Setting Up Currency

Setting Currency Preferences for Analytics: Overview

Oracle Transactional Business Intelligence gives you the ability to set your personal currency preferences, as well as set currency preferences which determine how your analyses display currency and calculate exchange rates.

The user preferences for your cloud offering are set in the cloud environment, and the currency preferences for analyses are set in Oracle Business Intelligence (BI). Both user preferences impact how your report currency is calculated and displayed. Your application administrator sets the corporate currency as the common currency basis for all users.

There are three ways currency is set in cloud and BI environments:

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

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

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

Setting Your General User Currency: Explained

User currency settings govern the currency that is used as the default for your application interface. User currency is set in the application and applies to your entire interface for your signed-in session.

To set your user currency:

  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.

Setting Your Personal Analysis Currency

The analysis currency determines the currency that is used in reports and analyses. It also determines how and when your currency conversion rates are calculated.

To set your currency for reports and analyses:

  1. Navigate to Business Intelligence.

  2. Click Analytics in the navigator menu.

  3. Click Browse Catalog.

  4. Click your user name and and select My Account.

  5. Go to the Preference.

  6. Select your choice in Currency.

The following table describes the currency menu options.

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

Setting a Default Currency Conversion Option for All Users: Explained

The default setting for the way currency conversion is handled for analytics is the User Preferred Currency Using Simple Currency Management. This simple currency management setting provides the best run-time performance when dealing with currency exchange rate management. But there are cases when your organization might want to standardize the setting for all system users, by setting the default preference to another option, such as CRM Currency or User Preferred Currency Using Advanced Currency Management.

To change the default currency setting for all users, administrators need to add a profile option and a corresponding value. Note that when administrators change the default currency setting for users in their organization, individual users can still override that setting and select their preferred currency in My Account.

The following table shows the profile option code parameters to override the default currency setting.

Profile Code Profile Value Description

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

CRM Currency - Defaults to Application Currency.

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

User Preferred Currency 1 - Defaults to User Preferred Currency Simple Currency Management.

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

User Preferred Currency 2 - Defaults to User Preferred Currency Advanced Currency Management.

Adding a Currency Profile: Explained

To set default global currency conversion types for all users, administrators create a currency profile. Currency profiles are added in Setup and Maintenance, one of the options available when you click your user name in the Home Page. Only administrators can change global currency preferences by creating profiles.

To Add a currency profile:

  1. Go to Setup and Maintenance.

  2. Search for Manage Profile Options.

  3. Click the +(New icon) in Search Results: Profile Options.

  4. Enter the following values:

    • Profile Option Code : BI_DEFAULT_CURRENCY_CONVERSION_METHOD

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

  5. Click Save and Close.

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

  7. Click Save and Close.

Defining Currency Profile Values: Explained

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

To define a currency profile value:

  1. Go to Setup and Maintenance.

  2. Search for "Manage Administrator Profile Values".

  3. Click Manage Administrator Profile Values.

  4. In Profile Option Code search for your profile: BI_DEFAULT_USER_CURRENCY

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

  6. Select Site as the Profile level.

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

  8. Click Save and Close to close the dialog.

User-Preferred Currency Reporting and Exchange Rates: Points to Consider

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.01403 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,030, or one million multiplied by 0.01403. 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.1403, 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 March 31st Rupee to Euro rate of 0.01052, requiring calculation during report processing to resolve the opportunity to 10,520 Euros. Finally, an opportunity report on March 31st in Euros again uses the March 31st conversion rate for Euros.

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

User Preferred Currency using advanced currency
management.

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. If this happens, contact your help desk.

Scheduling Snapshots of Your Sales Historical Pipeline

Use the Generates Sales Historical Snapshots scheduling process to get daily snapshots of your sales pipeline. This feature helps you stay informed about your pipeline opportunity and revenue trends over time, so you can keep your eye on your bottom line.

Snapshots are only supported if the enterprise calendar is configured to be either a Monthly or Weekly based calendar. No other calendar period frequencies are supported. Set up enterprise calendar before using snapshots.

The Generates Sales Historical Snapshots feature uses the Sales - CRM Historical Pipeline subject area to cull information on your key pipeline data. For more information on sales subject areas see Chapter 3," Building Analytics with Business Intelligence."

Managing Your Sales Historical Snapshot

The Generates Sales Historical Snapshots scheduled process captures opportunity and revenue snapshots for open opportunities and opportunities closed within the time period you specify. You can set up a snapshot to run once, or set it up to run daily, weekly, monthly, yearly, or on your own time frame. You can also choose the number of days after which opportunities have been closed to continue to take a snapshot of the opportunity and its corresponding revenue information.

To configure your Sales Historical Snapshots scheduled process:

  1. Navigate to Setup and Maintenance, All Tasks.

  2. Under Name, search for Manage Opportunity Profile Options.

    The search results returns the Manage Opportunity Profile Option in the bottom of the window.

  3. Click Go to Task on the row that holds the Manage Opportunity Profile Options search result. The Manage Opportunity Profile Options page appears.

  4. Under Profile Option Code, enter MOO_MANAGE_SALES_HISTORICAL_SNAPSHOT_CONFIGURATION. Search for that profile.

  5. Under Profile Values on the right ensure that the value are C=120,D=120,W=58,M=14,Q=5.

    The Profile Values are defined the following ways:

    • C is number of create snapshots for closed opportunities closed within the last C days. This value must be greater than zero.

    • D is number of days to retain daily snapshots. This value must be greater than zero.

    • W is umber of weeks to retain weekly snapshots if the enterprise calendar is a week based calendar.

    • M is number of months to retain monthly snapshots if the enterprise calendar is a month based calendar.

    • Q is number of quarters to retain a quarterly snapshot.

Note: An upper limit of 10M snapshot records (opportunity and revenue records combined) is supported and once the record limit is reached, the snapshot process automatically purges records by oldest snapshot date until the record count is brought under the limit. The snapshot process only supports capturing snapshots if the enterprise calendar is configured to be either a Month or Week based calendar. No other calendar period frequencies are supported. To use the snapshot feature you must configure your calendar first.

Scheduling Your Sales Historical Snapshots

You can schedule your Sales Historical Snapshots processes either from the SUI, or from the desktop UI.

To schedule your sales historical snapshots processes:

  1. From the menu options choose More then Scheduled Processes.

  2. Click the Schedule New Process tab.

    This figure shows the Schedule New Process option from the Scheduled Process window.

    Scheduled Process Scheduling window
  3. If you haven't already run this process, in which case it will show under the search results on the Scheduled Processes starting page, then you will search in the Scheduled New Process dialog. Click to view all of the choices. At the bottom there is a Search option. Click Search and enter Generates Sales Historical Snapshots. In Search Results highlight Generates Sales Historical Snapshots and click OK. The Schedule New Process dialog appears. Click OK again.

    This figure shows the Search and Select dialog for choosing your Generate Sales Historical Snapshots process.

    Search and select
  4. In the Process Detail dialog click the Advanced tab.

    Here you are going to set when you want your process to run, that is, daily, weekly, or monthly, and so on. You will also set the start and end date.

    This figure shows the scheduling options for your Sales Historical Snapshots processes.

    Scheduling for Sales Historical Snapshots processes.
  5. Click the Notification tab and define whom you want to be notified if the process run is successful, if it generates an error, or if there are warnings.

  6. When you are finished with your scheduling process details for times, frequency, and notifications, click Submit. Your Generate Sales Historical Snapshot is now completed.