Oracle Sales Cloud Creating Analytics and Reports

Oracle
Sales Cloud
Creating Analytics and
Reports
Release 10
Oracle Sales Cloud Creating Analytics and Reports
Part Number E61241-02
Copyright 2011-2015, Oracle and/or its affiliates. All rights reserved.
Author: Penny Anderson
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to
us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following
notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/
or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating
system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products,
or services.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Sales Cloud
Creating Analytics and Reports
Contents
Preface i
1 Introduction 1
About This Guide ...................................................................................................................................................... 1
Related Documents and Training .............................................................................................................................. 1
2 Overview 3
The Essentials of Creating Analytics .......................................................................................................................... 3
Saving Analytics and Reports: Points to Consider .................................................................................................... 4
Analytics and Reports Terms: Explained ................................................................................................................... 5
Oracle Business Intelligence Architecture .................................................................................................................. 7
3 Building Analytics with Business Intelligence 9

Creating Analytics Using Subject Areas .................................................................................................................... 9
Working with Custom Subject Areas ....................................................................................................................... 14
Creating and Viewing an Analysis for a Custom Subject Area ................................................................................. 31
Creating and Editing Analyses Using a Wizard: Procedure ...................................................................................... 32
An Example in Greater Detail - Building Analyses to Monitor Sales Trends .............................................................. 33
Viewing Analytics in the Catalog: Procedure ........................................................................................................... 39
Cross-Subject Area Analyses .................................................................................................................................. 41
Data Structure for Analytics: Explained ................................................................................................................... 41
Customizing Data Models: Procedure ..................................................................................................................... 43
Oracle Sales Cloud
4 Creating Analytics as Reports 45

Creating and Editing Reports .................................................................................................................................. 45
Reporting Tools for Creating Custom Reports ........................................................................................................ 48
Creating Custom Reports: Procedure ..................................................................................................................... 48
A Simple Example of How to Build an Opportunity Report ..................................................................................... 49
Making Reports Available for Online Viewing: Procedure ......................................................................................... 51
Accessing Report Components to Customize: Points to Consider .......................................................................... 51
Using the Customize Option for Predefined Reports: Points to Consider ................................................................. 52
Links Between Original and Custom Reports: Points to Consider ........................................................................... 53
What happens to customized analytics and reports when a patch is applied? ........................................................ 54
Working with report Layouts ................................................................................................................................... 55
5 Reporting in Multiple Currencies 63

Setting Currency Preferences and Exchange Rates ................................................................................................ 63
6 Performance Tuning 69
Performance Tuning for Analytics and Reports: Points to Consider ......................................................................... 69
7 Keeping Your Analytics Secure 71

Security for Sales Cloud Analytics and Reports: Overview ...................................................................................... 71
Securing Permissions for Sales Cloud Analytics and Reports .................................................................................. 72
Business Intelligence Roles: Explained .................................................................................................................... 73
Delivered Roles for Sales Cloud Analytics and Reports ........................................................................................... 74
Viewing Reporting Roles: Procedure ....................................................................................................................... 77
Customizing Security for Oracle Transactional Business Intelligence: Explained ....................................................... 78
How can I customize Oracle Transactional Business Intelligence duty roles? ........................................................... 79
8 Scheduling, Printing, and Sharing Your Reports 81

Printing and Sharing Reports: Overview .................................................................................................................. 81
Scheduling Analytics and Briefing Books: Procedure .............................................................................................. 82
Scheduling Snapshots of Your Sales Historical Pipeline .......................................................................................... 82
Scheduling Reports: Procedure .............................................................................................................................. 85
Setting Reports Up to Run as Scheduled Processes: Points to Consider ................................................................ 86
Setting Up Reports for Scheduling in the Reports and Analytics Pane: Procedure ................................................... 87
Oracle Sales Cloud Preface
Preface
This Preface introduces information sources available to help you use Oracle Applications.
Oracle Applications Help

Use the help icon to access Oracle Applications Help in the application.
Note
If you don't see any help icons on your page, click the Show Help button in the global area. Not all pages have
help icons.
You can also access Oracle Applications Help at https://fusionhelp.oracle.com/.
Oracle Applications Guides

To find other guides for Oracle Applications, go to:
Oracle Applications Help, and select Documentation Library from the Navigator menu.
Oracle Help Center at http://docs.oracle.com/
Other Information Sources

My Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you
are hearing impaired.
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs (if you are hearing impaired).
Oracle Enterprise Repository for Oracle Fusion Applications

Oracle Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com) provides details on assets (such
as services, integration tables, and composites) to help you manage the lifecycle of your software.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
i
Oracle Sales Cloud Preface
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides!
Send e-mail to: oracle_fusion_applications_help_ww_grp@oracle.com.
Click your user name in the global area of Oracle Applications Help, and select Send Feedback to Oracle.
ii
Oracle Sales Cloud Chapter 1
Creating Analytics and Reports Introduction
1 Introduction
About This Guide

This guide is intended for report builders tasked with modifying and saving custom analytics and reports as well as creating
new content in custom folders. The guide contains both conceptual and procedural information intended to help users
build high impact analytics, reports, and dashboards that are tailored to the content needs of a specific line of business or
company.
Related Documents and Training

For additional Sales Cloud learning resources, refer to the Oracle Help Center, application online help, and Oracle University.
For Oracle Sales Cloud analytics and reports, consult the following resources:
Oracle Sales Cloud - Getting Started with Analytics and Reports
This guide gives a quick overview of Sales Cloud analytics and reports and provides links to videos of the top 10
reports in action.
Oracle Sales Cloud - Using Analytics and Reports
This guide explains how to access, understand, and use some of the key Sales Cloud reports. This guide also
provides a listing of prebuilt Oracle Sales Cloud dashboards and reports.
Oracle Cloud - Administering Transactional Analyses
This guide describes general administrative procedures and concepts for reports and analytics.
Oracle Sales Cloud - Subject Area Documents
Refer to Oracle Sales Cloud Subject Area Documents on the Oracle Help Center for more detail on the use, security,
dimensions, and calculations of Sales Cloud reports.
1
Creating Analytics and Reports Introduction
2
Creating Analytics and Reports Overview
2 Overview
The Essentials of Creating Analytics

Oracle Sales Cloud comes with over 150 out-of-the-box analyses and reports. Still your organization will likely need to
create their own custom analytics. You can quickly and easily create a variety of different types of analytics using the Oracle
Business Intelligence (BI) tools, as well as view, publish and print, and share them in ways that work best for your particular
business needs.
This figure shows the New dropdown option for Analytic under the interactive reporting options in BI.
An analytic is a overall term for a bucket of selected details assembled from your current and historical sales information.
This sales data is stored in your database as data objects, and when a analytic is compiled subject-specific data objects
are chosen depending on what you want to see on that analytic. So for example, if you are a sales representative, and you
enter the name of your contact, her phone number, and company name, you have just created three new data objects.
These objects are then stored in your database with a table name like "Customers". Now you have hundreds of contacts, and
thousands of data objects for your customers, these are all available through BI to use for creating both analyses and reports.
They are bundled in Subject Areas and data models to make it easier for you when you create or edit analytics. Both Subject
Areas and data models can be customized.
3
This figure shows the Subject Area options for an analysis in BI. Selected is the Sales - CRM Customers and Contacts Real
Time.
In the SUI, all of the analytics are built as analyses. You can build both analyses and reports in BI. Although both an analysis
and a report are technically a type of analytic, from the point of view of creating these buckets, a report is different from an
analysis because it is created in way which makes it easy to publish online or email, and distribute across your organization.
Analyses are more for your infolets, dashboards, and laptop, mobile, or tablet viewing of key metrics and performance
indicators. Your reports are created using Report from the dropdown menu, instead of Analysis. Although both analyses
and reports are created using subject areas and data models, you build your reports in a way which includes defining the
layout, and format, such as PDF, XLS, or RTF.
The out-of-the box and the custom analysis you create in BI are used for the data shown on your interactive devices to get
instant access to your key sales data. You can also customize the out-of-the box analyses in BI and show the metrics you
need most in the Simplified UI, on your mobile device, or on your tablet.
Note
For more information on creating reports using Business Intelligence, see "Fusion Middleware Report Designer's
Guide for Oracle Business Intelligence Publisher".
For more information on customizing your Sales Infolet pages, see "Oracle Sales Cloud Using Analytics and
Reports: Getting Key Performance Indicators at Your Fingertips."
Saving Analytics and Reports: Points to Consider

You save analyses, dashboards, and reports in the Oracle BI Presentation Catalog along with other items. The catalog has
a hierarchy of folders, with My Folders and Shared Folders at the top. One important folder is Custom, which you find under
Shared Folders.
My Folders
You're the only one who can access anything that you save in My Folders.
When you save a new analysis, dashboard, or report in this folder, it's available in My Folders on the Reports and Analytics
work area. But you won't see it in My Folders in the Reports and Analytics pane on any other work area.
4
Note
The only exception is when you create an analysis using the wizard in the Reports and Analytics pane, in which
case the analysis is available in the pane on all work areas.
Shared Folders
If you have the appropriate roles, you can also save in Shared Folders so that your custom analytics or reports are available to
anyone with the right access. Usually you can save under the Custom subfolder, which has subfolders organized by product
family.
Important
Regarding predefined analytics and reports:
You can save a copy of the predefined analysis or dashboard in the corresponding product family subfolder
under the Custom folder, and edit only the copy. Directly edit predefined analytics only when necessary, to make
sure that anything referencing the analysis or dashboard still works properly.
For predefined reports only, there's a special Customize option that lets you copy the report and also the folder
structure and permissions. The copy is linked to the original, so editing the copy is like directly editing the original.
Custom Folder
Keeping all custom reports and dashboards in the Custom folder has the following benefits:
If updates are applied to predefined analytics and reports through patch upgrades outside the Custom folder, you
ensure that customized versions of those items are not affected. You might lose customizations saved outside the
Custom folder during upgrades.
You can easily locate and identify customized reports, dashboards, folder names and so on.
You can edit reports, dashboards and folder names in the Custom folder without compromising security on the
original objects.
Note
When you copy an item such as a report or dashboard into the Custom folder, the copied items inherits the
permission settings of the Custom folder. If you want to change the inherited permissions, then your administrator
must reset the permissions on the item and the folder where that item resides.
Analytics and Reports Terms: Explained

There are many terms used in the application, help, and guides for analytics and reports. This table explains the key terms
you might see.
Note
Some of these terms are applicable only if you're creating or editing analytics and reports.
5
Term Definition
agent An object that defines how analyses, dashboards,

or briefing books run on a schedule and how other
automated tasks are performed.

analysis A graph or table displaying select data to provide

answers to business questions.

analytics Business intelligence (BI) objects such as analyses and

dashboards that provide meaningful data to help with
decision making.

business intelligence catalog The repository where all BI objects, including analytics,
reports, briefing books, and agents, are stored. The
catalog contains separate folders for personal, shared,
and custom objects.

business intelligence repository The metadata that determines all of the columns, or
pieces of data, that you can include in analytics. You can
also use the repository as a source of data for reports.

business intelligence object Any item in the BI catalog, including analyses,

dashboards, reports, data models, and so on.

dashboard A collection of analyses and other content, presented

on one or more pages to help users achieve specific
business goals. Each page is a separate tab within the
dashboard.

data model The metadata that determines where data for a report
comes from and how that data is retrieved.

job definition The metadata that determines what a job does and
what options are available to users when they submit
the scheduled process. A job is the executable for a
scheduled process.

layout The report component that determines what the report

output looks like.

layout template The actual file, for example, RTF file contains the report
layout information.

6
Term Definition
prompt A parameter that you set when you use analytics,

limiting the data in the analysis or in all analyses on the
dashboard or dashboard page (tab).

report An output of select data in a predefined format that is

optimized for printing.

report component One of the various parts that make up a report, including
its data model, layout, and properties.

scheduled process A program that you schedule and run to process data
and, if appropriate, generate output as a report.

style template An RTF template containing style information that is

applied to other RTF layouts to achieve a consistent look
and feel across reports.

subject area A set of columns, or pieces of data, related to a specific

business object or area.

subtemplate A piece of formatting that is defined once and used

multiple times within a single report layout or across
multiple layout files.

view A specific way to present the results of an analysis, for

example, as a table or graph. Other types of views, such
as the title view, show other components of the analysis.

Oracle Business Intelligence Architecture

The source data from the transactional database is abstracted by way of an Oracle Business Intelligence (BI) view or an
Oracle Business Intelligence view object in the Oracle Cloud service. The data is then fed into the Oracle Business Intelligence
layer on the Semantic Model. The various Oracle BI Applications (such as Territory Management and Sales Prediction Engine)
and the prebuilt reports and dashboards then reference the Oracle Business Intelligence model.
7
The following figure shows a high-level mapping of the Oracle Business Intelligence architecture in Oracle Sales Cloud.
Analytics are available throughout Oracle Sales Cloud as embedded analytics and also in standalone mode by way of the
transactional work areas. Administrators can create custom reports using Oracle BI Answers. BI Composer is the tool for
users to do their own self-service report creation. For more information about these tools, see Reporting Tools for Creating
Custom Reports.
The access points for reports are by way of the embedded analytics on work area pages as well as the Reports and Analytics
pane and the Reports and Analytics work area.
8
Creating Analytics and Reports Building Analytics with Business Intelligence
3 Building Analytics with Business Intelligence

Creating Analytics Using Subject Areas
Subject areas are designed to help you build analytics to use to answer your key business questions. To create a real-
time analysis using Oracle Transactional Business Intelligence (BI) , you begin by determining which subject area contains
the questions you are trying to answer. Once you've chosen a subject area, you are going to build an analysis using the
information available in that subject area. For example, the CRM Customer Overview Subject Area is designed to address the
following business questions:
What are the top ten accounts by revenue?
What are my most active accounts? Where are these located?
How can I identify up-sell and cross-sell opportunities within my existing accounts?
What are my best performing product lines by customer geographies?
How actively are my sales reps engaged with customers?
Where are the white spaces for me to sell a specific product?
How well am I winning against competition?
What percentage of my revenue is exposed to competition?
For more detail on the subject areas, go to http://www.oracle.com/technetwork/documentation/otbi-sales-2225536.html
The following table lists the subject areas available for creating analytics in BI.
Column A - Sales Subject Areas Column B - Territory, Partner, Marketing Subject

Areas
Sales - CRM Account Relationship Territory Management - CRM Leads

Sales - CRM Activity Contact Territory Management - CRM Quota

Sales - CRM Activity Objective Territory Management - CRM Forecast

Sales - CRM Activity Resource Territory Management - CRM Pipeline

Sales - CRM Customer Classification Partners - CRM Leads and Opportunities Real Time

Sales - CRM Customer Overview Partners - CRM Opportunities and Product Real

Sales - CRM Customers and Contacts Real Time Partners - Partner Classification

Sales CRM Customers and Sales Resources Real Time Partners - CRM Partner Overview

9

Areas
Sales - CRM Deal Registration Partners - CRM Partner Contact

Sales - CRM Deal Registration Product Partners - CRM Partner Performance Real Time

Sales - CRM Forecasting Partners - CRM Partners Programs

Sales - CRM forecasting and Pipeline Revenue Real Partners - CRM Partner Resource
Time

Sales - CRM Historical Forecasting Partners - CRM Partner Territory

Sales - CRM Historical Pipeline Partners - CRM Partner and Product Real Time

Sales - CRM Lead Contact Partners - CRM Program Enrollments Real Time

Sales - CRM Lead Product Partners - CRM Program Performance Real Time

Sales CRM Lead Resource Partners - CRM Registered Leads Real Time

Sales - CRM Lead Territory Marketing - CRM B2B Customers

Sales - CRM Opportunities and Competitors Real Time Marketing - CRM B2C Customers

Sales - CRM Opportunities and Partners Real Time Marketing - CRM Campaign Launch

Sales - CRM Opportunities and Products Real Time Marketing - CRM Campaign Performance

Sales - CRM Opportunity Assessments Marketing - CRM Campaigns and Contacts Real

Sales - CRM Opportunity Contact Marketing - CRM Campaigns and Leads Real Time

Sales - CRM Opportunity Resource Marketing - CRM Campaigns and Opportunities Real
Time

Sales - CRM Opportunity Sales Stage Snapshot Marketing - CRM Lead to Order
10

Areas

Sales - CRM Opportunity Territory Marketing - CRM Leads

Sales - CRM Partner Relationship Marketing - CRM Leads Real Time

Sales - CRM Pipeline Marketing - CRM Leads and Opportunities Real Time

Sales - CRM Quota Management

Sales - CRM Resource Territory

Sales - CRM Sales Account Resource

Sales CRM Territory Resource

Sales CRM Sales Activity

Working with Subject Areas

Subject areas contain related objects that can be grouped together in a way that provides meaningful information for
a specific context. The context correlates to the business questions that the subject area is intended to answer. So for
example, let's take the subject area Sales - CRM Pipeline. This is a key subject area that affords analysis across all stages of
the sales cycle. Areas of analysis span lead management, opportunity pipeline management, win-loss, sales cycle, activities
and quota management. Reports and other analyses created using this subject area are relevant for all key roles including
sales reps, sales managers, and sales executives. Both individual and team performance can be accessed across resource
and territory hierarchies. Depending on your requirements, the focus of a CRM Pipeline analysis can be lead, opportunity,
customer, competitor, sales resource/team or product activity, or any combination of these.
The business questions that are answered with the CRM Pipeline Subject Area are:
Are my sales reps moving their opportunities fast enough?

How is each member of my team performing on deal size, account coverage, and win rate?
Is my sales team converting leads to opportunities fast enough?
Is our overall pipeline healthy enough to meet sales goals?
What are my top stalled opportunities and who are the sales reps working on them?
What are the most likely reasons we lose against our key competitors?
What are the top 10 opportunities? What are the target close dates and revenues for these opportunities?
What is the buying trend of our biggest customers? Are there any up-sell or cross-sell opportunities?
What is the value trend of high value opportunities? Do they show a positive or negative trend?
Who are my top competitors and what is our revenue exposure to them?
11
How effective are our current references? Has their participation meant a difference to us in wins?
Now let's go into BI and explore the CRM Pipeline Subject area. Go to the option to create new analytics on the upper right.
Here you can create analysis and reports, as well as many other features. When you choose to create an analysis or report
here, you see all the subject areas available for Sales Cloud Analytics. Using the New option, you can explore the data objects
available in a subject area, as well as create analytics from a subject area.
This figure shows the Sales - CRM Pipeline subject area which is available when you click New >Analysis in BI.
Let's go ahead and click Sales - CRM Pipeline subject area, as if we are creating a new analysis. The interface now shows
all of the folders on the left under the CRM Pipeline subject area. Each subject area has one fact folder and a number of
dimension folders. Fact folders contain attributes that can be measured, meaning that they are numeric values such as sales
forecasts and quotas. A special folder, called a Degenerate Dimension, is also associated with the fact folder. Each dimension
folder is joined to the fact folder within a subject area. Fact folders are usually at the bottom of the list of folders and are
usually named after the subject area. If you are creating an analysis, your next step is to drag your columns onto the Selected
Columns palette.
12
This figure shows the interface for creating analysis based on the facts and dimensions available for the CRM Pipeline subject
area.
When you drag a column onto the Selected Columns area, you are building an analysis that shows all the information related
to that subject area. The information can be from the Facts folder, which contain information that can be measured, like
available discount and unpaid amount, or the information can be from the columns in the dimension folders, which contain
attribute and hierarchical columns like bank account number and due date. Let's drag Account Type from Customers to our
report palette.
This figure shows the Selected Columns area with the Customer Account Type - Person column added.
Once you have a new analysis with your column added, you can save it to your catalog folders and open it up and view real-
time details from your subject areas any time. In addition to building reports using subject areas, this is a great way to explore
your subject areas, and what facts and dimensions are available.
13
Working with Custom Subject Areas
Creating and Editing Custom Subject Areas: Explained

This topic covers how you create and edit custom subject areas, and how you can activate or inactivate a custom subject
area while editing.
You cannot modify a predefined report subject area that is delivered with Oracle Sales Cloud; however, you can create
custom subject areas to meet your reporting needs.
Note
Before you create a custom subject area, review all the included subject areas to see if the one you want is
already available.
Creating a Custom Subject Area

You create custom subject areas using train stops that appear at the top of the page. These train stops enable you to move
back and forth during the configuration process. You can also save your configuration at a logical point and then continue to
create later.
To start create a custom subject area using train stops:
1. Navigate to Application Composer.

2. Select an application from the Application list.
3. Click Custom Subject Areas on the Overview page of the Application Composer.
4. Select Actions - Create.
Create Custom Subject Area: Define Custom Subject Area page opens.
This figure shows the first page in the guided process for creating custom subject areas.
Here are the steps in the train stops that you can use for configuring your custom subject area:
1. Define Custom Subject Area

In this step, you provide the name for your subject area and select the primary object that is the basis for the
reports you create later using the custom subject area. Subject areas usually have names or labels that correspond
to the type of information they contain, such as service requests and orders. Display labels have the Custom: prefix
added automatically.
2. Select Child Objects
14
In this step, you select the child objects whose data you want to use in your reports. You can add child objects only
if the primary object has child objects. Else, the add icon is disabled. When you select child objects for your custom
subject area, consider the following points:
For a one-to-many primary-child relationship, you can add multiple child objects if required. The parent-child-
grandchild-grand grandchild hierarchy supports adding only up to three levels of child objects, for example,
parent-child1-child1.1-child1.1.1.
For a many-to-one primary-related relationship, you can add as many related objects as you want.
3. Configure Fields
In this step, you select the fields that you want to display on your reports. You typically add at least one field from
each of the objects that you have selected for your custom subject area.
Select the desired measures to generate for number, date, or currency fields from all the available objects so that
the subject area includes only those measures that you want to analyze. Also, define at least one measure.
In the Select Aggregations column, select an option from the list of predefined formulas that you can apply to the
Measure field. When you select the formula, the application applies the selected formulas to the selected field and
measures.
You can change the display labels of the fields that you select in this step. Additionally, you can use the Select
Fields dialog to remove fields that belong to the primary object, or add fields from the related objects. The Select
Fields dialog appears when you click Select Fields when configuring fields for your custom subject area.
This figure shows the Select Fields dialog.
After you publish your custom subject area, the fields you have selected for your subject area are automatically
added to their owning object's folder. If you have also defined measures, those fields are automatically added to the
Facts folder.
For more information on measures, see Measures in Custom Subject Areas: Explained topic.
This figure shows the fact folder and the object folder whose fields are selected.
15
4. Configure Implicit Fact
Use the mostly used measure as the Implicit Fact.
For more information on implicit fact, see Implicit Fact Column in Custom Subject Areas: Explained topic.
5. Configure Marketing Segmentation
For more information on marketing segmentation, see Marketing Segmentation: Functional Overview and its related
topics.
6. Configure Date Leveling
If required, select the Date columns for date leveling. For more information on date levelling, see Date Levelling in
Custom Subject Areas: Explained topic.
7. Configure Security
Select the required security level for the Everyone Role Name, which is added by default or add additional Role
Names by clicking in the + icon and define the security level for each one of them.
Note
The security definition here only control who can access the custom subject area definition to create
reports. It doesn't control data visibility which is automatically controlled based on the user running the
reports.
For more information on securing custom subject areas, see Securing Custom Subject Areas: How It Works topic.
8. Review and Submit
16
Review the custom subject area configuration for all added objects, attributes, and measures, and if satisfied, click
Submit. If changes are required click on Back to navigate back to the required screen.
After you submit, the custom subject area configuration is prepared for publishing. You can create and submit a
custom subject area either immediately or save and close the custom subject area at any point and submit it later.
You must first submit a custom subject area for publishing before you can select it from within Oracle BI Composer.
After you save or submit a custom subject area, you cannot modify its primary object.
To access the published custom subject area in BI:
From the Navigator menu, select Tools - Reports and Analytics.
In the Contents pane, click Create.
Select the published custom subject area and start creating your report.
17
This figure shows a sample custom subject area. Note the custom: prefix.
Editing Custom Subject Areas

You can edit a published or saved custom subject area and then republish it when your changes are done. Modifying a
custom subject area does not affect the reports that you had created using that custom subject area before making the
changes. You can use the modified custom subject area if you need to enhance existing reports.
To edit a custom subject area:
1. On the Overview page of the Application Composer, click Custom Subject Areas.
2. From the Application list, select the application depending on the object you used for creating the custom subject
area.
3. Locate the custom subject area that you want to edit, and click the Edit icon.
Note
You can filter out inactive custom subject areas in Application Composer by viewing custom subject
areas in Active status. This is safer than deleting them, because the inactive subject areas are still
available and can be found by searching.
4. Make the desired changes and then click Submit to republish the custom subject area.
While you can edit a custom subject area in any status, there are considerations on what you can or can't do when editing.
When editing a published custom subject area, it is not possible to:
Change the primary object.

Add or remove child objects.
18
Remove previously added measures.

Add more aggregation types for measures that are already published.
Note
You cannot modify a predefined report subject area that is delivered with Oracle Sales Cloud. Instead, you must
create separate custom subject areas to meet your reporting needs. Before you create a custom subject area, be
sure to review all the included subject areas to see if the one you want is already available.
Activating or Inactivating Custom Subject Areas

When editing custom subject areas, you can activate or inactivate custom subject areas when your reporting or business
requirements change. This enables you to control what information is displayed on the reports that use the information from
custom subject areas.
Note
You can inactivate only those custom subject areas that are published and have OK status, and can activate only
previously inactivated custom subject areas.
To inactivate a custom subject area, select it in the list and then click the Inactivate button. To activate an inactive custom
subject area, select it and click Activate.
Note
If no custom subject area is selected in the list, the button doesn't appear.
This graphic shows an active custom subject area selected, and the Inactivate button.
When searching for custom subject areas, you can filter out inactive custom subject areas in Application Composer by
viewing only those in Active status. Inactivating a custom subject area is safer than deleting it, because the inactive subject
areas are still available and can be found by searching.
Related Topics
Custom Subject Areas: Explained
Date Leveling in Custom Subject Areas: Explained
Objects in Custom Subject Areas: Explained

This topic covers how you use various types of objects in the Application Composer to create custom subject areas.
19
Objects in Oracle Sales Cloud can be classified under broad categories of custom objects and standard objects. The objects
that you create are called custom objects and those delivered with Oracle Sales Cloud are standard objects.
For more information on the various types of objects in Oracle Sales Cloud, see Defining Objects Explained topic.
Before designing of your custom subject area, use Application Composer to identify or create the objects and fields that you
want to use.
Primary Objects
A primary object is any reportable top-level object. You create a custom subject area based on this primary object.
Additionally, the primary object is the focus of the report that you create based on the custom subject area.
The list of available primary objects includes all reportable objects, which are either top-level, custom objects, or standard
objects that are configured as reportable by the owning Oracle Sales Cloud application. After you save your custom subject
area, you can't change its primary object; however, you can create another custom subject area using a different primary
object.
Note
You cannot include common object Notes and Tasks in a custom subject area. They are not reportable.
Based on how you want to configure your custom subject area, you can add multiple child objects under the primary object.
But you can't add more than three levels of child objects to a primary object.
Child Objects
A child object is an object that has one-to-many relationship with a parent object and can be a parent object of another child
object. If an object's parent object is already a child object (of another parent object) then the object is a grandchild object.
Custom subject areas support parent-child-grandchild-grand grandchild objects.
This figure shows the parent-child-grandchild-grand grandchild hierarchy.
You can add multiple child objects to the primary object as required, as long as there are child objects available. If there are
no child objects for the chosen primary object, the list that enables selecting child objects does not appear.
The parent-child-grandchild-grand grandchild hierarchy supports adding only up to three levels of child objects, for example,
parent-child1-child1.1-child1.1.1.
20
Note
Once you publish a custom subject area, you cannot add or remove child objects.
Related Objects
A related object is any object with a many-to-one relationship with its parent object. Custom subject areas support objects
related to parent, child, grandchild or grand grandchild objects. It is possible to add one or more related objects to a custom
subject area.
For example, when configuring a custom subject area, you can select Opportunity object, which is a primary object and then
click Fields From to add related objects.
This figure shows how you add related objects.
You can also add or remove opportunity fields, or add or remove related objects and its fields from the custom subject area.
This figure shows how you add or remove fields from primary or related objects.
You follow a similar process for adding or removing fields for any other child object that you add to the custom subject
area. After you publish a custom subject area, you cannot remove related objects; however, you can create another custom
subject area and then use the applicable related objects.
For an example of how you configure a custom field and create a custom subject area using that field, see Creating a Custom
Object and Associating it With a Custom Dynamic Choice List Field: Worked Example topic.
21
Related Topics
Extensibility and Reporting: Example
Associating Custom and Standard Objects and Creating Reports: Worked Example
Fields or Attributes in Custom Subject Areas: Explained

This topic explains the various types of fields or attributes that you use for configuring your custom subject area.
Fields or attributes store entity information in Oracle Sales Cloud. Fields can be standard or custom. Standard fields are
delivered with Oracle Sales Cloud, and custom fields are the ones that you create.
Types of Reportable Fields

The fields using which you can create reports are as follows:
Text
Number
Date
Percentage
Date time
Currency
Check box
Fixed choice lists
Dynamic choice lists
When you create a custom field, you can create reports for the following data types:
Boolean
Note
If you are using Boolean data type for fields other than check boxes, those fields are displayed as either 0
or 1 on your custom reports.
Number
Currency
Date
22
String
Percentage
Phone
Date time
Creating Reports Using Extension Fields

For key objects in Oracle Sales Cloud, predefined extension dimensions exist which include custom or extended fields. These
fields enable you to create reports on extensions that are made to standard objects.
Note
Extension dimension fields are not available for reporting until custom fields have been specified.
Here's a summary of the steps for creating a report using extension dimension fields:
1. Using Application Composer, create custom fields for standard objects, and ensure that the custom fields are
exposed on the user interface.
2. Publish the sandbox.
3. In the navigator menu, select Reports and Analytics under Tools to navigate to Oracle Business Intelligence (BI)
Composer.
4. Select a real time or Oracle Transactional Business Intelligence (OTBI) subject area that includes the predefined
extension dimension.
5. Create a report.
When you specify the columns for your report, you can select the extension fields from the extension dimension folder, which
appears as <Object Name> Extension folder. For example, Opportunity Extension.
Related Topics
Extensibility and Reporting: Example
Measures in Custom Subject Areas: Explained

Measures are a set of functions. Measure columns allow business users to see a summary of how their business processes
are working so far. Examples include a SUM of the Revenue in Euros, or a COUNT of the number of Opportunities worth
over $500,000. The designer defines the aggregation function (SUM, COUNT, and so on) for custom Measures, so end users
don't need to do so themselves when they create an analysis. You can apply these functions on fields of type Date, Numeric,
or Currency.
Measures available to a particular type of field may differ depending on the field type. After you define the measures for the
required fields and publish the custom subject area, you can select these fields and the applied measures when creating your
report in the Oracle Business Intelligence Composer. You can only specify aggregate formulas to apply to a measure when
creating a custom subject area. It is not possible to edit a measure in an already published custom subject area.
23
Here are some measures you can apply to fields of type numeric, currency, or date.
For numeric and currency fields, a measure can be:
All
Note
All is not a measure, but an option in the UI that selects all of the measures.
Sum: Calculates the sum of the values.
Average: Calculates the mean value.
Count: Calculates the number of rows that are not null.
Count Distinct: Calculates the number of rows that are not null. Each distinct occurrence of a row is counted
only once.
Note
Although Count Distinct is usually used in cases requiring a count on a foreign key (because a count
of distinct rows is what's wanted), it is not required. If your requirements allow multiple instances
of the same foreign key value to be counted multiple times, you can use Count rather than Count
Distinct.
Maximum: Calculates the highest numeric value.
Minimum: Calculates the lowest numeric value.
First: Selects the first occurrence of the item.
Last: Selects the last occurrence of the item.
Median: Calculates the middle value.
Standard Deviation: Calculates the standard deviation to show the level of variation from the average.
Standard Deviation Population: Calculates the standard deviation using the formula for population variance and
standard deviation.
For date fields, a measure can be:
All
Maximum
Minimum
24
You can select measures based on your reporting needs. For example, you can use measures to view product sales per
store, state, or country. Or, to view the number of support tickets opened or closed per day, week, or month, and so on.
Related Topics
Implicit Fact Column in Custom Subject Areas: Explained

When you run a report with only dimension attributes from a subject area that has measures from different facts or entities,
the Implicit Fact column defines the join path that must be used.
In the following representation, there are several paths to be chosen when reporting only on attributes from the included
dimensions. The implicit fact column tells the desired path that represents the data and joins all the three entities correctly.
Oracle Sales Cloud applications use this fact as part of the query during dimensional browsing. Typically, the most frequently
used fact or the functionally most relevant fact is specified as the implicit fact. For example, a revenue fact is stamped as the
implicit fact in the Pipeline subject area, and a sales account fact is marked as an implicit fact in the Customers subject area.
Note
Only one implicit fact column can be selected per custom subject area.
Related Topics
Publishing Custom Subject Areas: Explained

This topic covers what happens when you submit a custom subject area for publishing, and what the submission statuses
indicate.
After you successfully publish your custom subject area, you can start building reports using Oracle Business Intelligence (BI)
Composer based on your published subject area.
25
What Happens When you Submit for Publishing

When you submit a custom subject area for publishing, two processes occur in the background. The first process is
synchronous and creates Oracle Applications Development Framework (Oracle ADF) artifacts. You must wait until this first
process is over. The second process is asynchronous and creates centralized metadata repository (RPD) fragments and
submits them to the Oracle BI server.
Note
You must refresh the status to know whether the custom subject area is submitted successfully. You may have to
refresh the status multiple times, because the creation of Oracle ADF and RPD artifacts may require some time.
A custom subject area can have one of the following statuses:
Pending: This status indicates either of the following:
You saved and closed the configuration process for a custom subject area before submitting it for publishing.
A failure occurred in the background processes when creating Oracle ADF and RPD artifacts.
In Process: This status indicates that the data is in the process of being published to Oracle BI.
Note
If the in-process status does not change to OK, even after multiple refresh attempts, then there could be
an error in publishing. If an error occurs, the details are displayed, as well as information about how to fix
problems, where applicable. These error status details allow you to pinpoint and fix problems quickly.
OK: This status indicates that the custom subject area has been published successfully. You can use Oracle BI
Composer to create reports using the objects, attributes, and measures that you have configured in the subject area.
Configuring Custom Subject Areas for Segmentation: Points to

Consider
This topic outlines the setup required to target some organization contacts using criteria from a custom object that has a
relationship with an Organization Customer (B2B). It also specifies some setup variations for configuring custom objects
related to B2C Customers (Consumers) and custom objects related to contacts.
Configuring Custom Subject Areas in Segments

The following example is used to illustrate your task. You are a B2B Company and want to target Organization Contacts in a
marketing campaign. The contacts work for Organizations that have placed an order with your company in the past month.
Before You Begin

The following lists the tasks that you must perform before you begin to configure the custom subject area for segmentation:
Create a custom object named Orders and include custom fields such as date, amount, product and so on using
the dynamic choice list. Select Account as the target object for the dynamic choice list to allow you to select the
customer for which each new order is required. This action creates a relationship between Order and Account.
Create a work area for the custom Order object and expose the necessary fields in the Overview, Create and Detail
pages.
26
Create data records for the Order object either through the UI, through Import or through web services. When
creating records, make sure that you select the Account for which each Order is required.
Create a custom subject area for the Order object and expose that subject area for segmentation. When selecting
fields to include in the custom subject area you must choose the Party ID from the Account object.
Custom Subject Area Segment Configuration

Do the following to configure the custom subject area for segmentation:
1. Associate the subject area to one or multiple Target Levels.
In this example, the custom object has a relationship to Account only, so it must be related to the Real Time
Customers target level only. The Qualifying Identifier must be set to the same level as the target level
(Customers Real Time) and the Mapped Field must be set to the Party ID of the Account object. This association
ensures that Marketing Segmentation uses the Party ID to identify and count individual customers.
2. Map to List Exports.
Set the Qualifying Identifier to the same level as the target level (Real Time Customers) and set the mapped field
to the Party ID of the Account object. This association ensures that Marketing Segmentation uses the Party ID as
the input parameter when querying the database for the set of customer data to include in the segment.
Using Custom Subject Areas in Segments

Now that the custom subject area has been set up and Marketing Segmentation has been configured, you can now use the
custom subject area when creating segments. Using our example, the target for the segment is individual contacts that work
for organizations which have an order. You need to create a segment that targets Real Time Customers and then nest (relate)
the Real Time Contacts subject area.
Perform the following steps:
1. Navigate to the Audience work area and select Create Segment. Enter a name for your segment, select the Real
Time Contacts target level, and click Save and Design. The Segmentation UI will is displayed.
2. Click the Select Another Target Level icon in the upper right corner (next to the Save icon) and select the Real
Time Customers target level.
3. Select the Add/Remove Subject Areas icon in the upper left corner of the screen (in the Subject Area section
next to Refresh icon). Select the new custom Orders subject area that you previously created.
4. Create the segment criteria for the set of Organizations that you want to target (based on orders, or customer
attributes), then save the segment.
Note
This segment will not appear in Marketing Segmentation UI at any time. It is a nested segment used by
the Contacts Real Time segment that is being created.
5. Once the Customer level segment is saved, click Go back to segment_name link in the upper left of the
Segment Designer section. The segment_name is the name of the segment that you are designing. This action
returns to the original segment that is at the Contact level and the Customer level segment will be nested as the first
criteria.
6. Add any other criteria necessary to the segment, can be at the customer or contact level (customer name, contact
e-mail, and so on).
27
7. Save the segment and update counts.
The counts should reflect the number of contacts that are related to the companies which meet the Orders criteria
(plus any other criteria input into the segment).
Custom Objects Related to B2C Customers (Consumers)

The set up and process for creating the custom subject area for custom objects related to Consumers is almost identical to
the process outlined in the previous example with a few exceptions as follows:
When creating the custom object and inserting the dynamic choice list, the target object must be the Contact
object. This object relates the Person Customer to the custom object (instead of an Account).
When setting up the custom subject area, the Party ID of the Contact object must be added to the subject area in
the Field selection step.
When configuring segmentation on the custom subject area, the target level should be set to Real Time
Consumers. The Qualifying Identifier must be set to Consumers Real Time and the Party ID from the
Contact object must be used as the mapped field in both steps.
A nested segment is not needed when you create a segment. The custom subject area is related directly to the
person customer (consumer) so that object can be used in a segment that is targeting consumers.
Custom Objects Related to Contacts

The set up and process for creating the custom subject area for custom objects related to Contacts is almost identical to the
process outlined in the previous example with a few exceptions as follows:
When creating the custom object and inserting the dynamic choice list, the target object must be the Customer
Contact Profile object. This object relates the Contact to the custom object (instead of an Account or Person
Customer).
When setting up the custom subject area, the Party ID of the Customer Contact Profile object must be added to
the subject area in the Field selection step.
When configuring segmentation on the custom subject area, the target level should be set to Real Time Contacts.
The Qualifying Identifier must be set to Contacts Real Time and the Party ID from the Customer Contact
Profile object must be used as the mapped field in both steps.
A nested segment is not needed when you create a segment. The custom subject area is related directly to the
customer contact (contact) so that object can be used in a segment that is targeting contacts.
Custom Subject Area Based on a Pair of Seeded Custom

Objects: Tutorial
In this tutorial we will discuss how to create a custom subject area based on a pair of seeded custom objects.
Examine the Custom Objects for the Subject Area

Custom objects are the focus of a custom subject area, which you can later select in Oracle Business Intelligence (BI)
Composer to build a report. The list of values for custom objects includes all top-level, reportable objects that belong to the
application you selected to customize using the Oracle Fusion CRM Application Composer.
1. Navigate to Application Composer.
28
2. In the regional area, set Application = Sales.
3. Expand Custom Objects.
4. Notice that the list includes two custom objects: EXT Child and EXT SalesParent..
Examine the Structure of the Parent

A parent object is any reportable top-level object that a custom subject area is based on. Parent objects can have child
objects which can be used when build custom subject reports.
1. In the regional area, notice that EXT SalesParent is a parent object, as indicated by its icon. You can also recognize
parent objects by expanding them and noting that they have Pages. Child objects do not have Pages in Oracle
Application Composer
2. Expand EXT SalesParent.
3. Click Fields.
4. Observe that there are five custom fields of varying types; in particular, there is one number field and one currency
field. These fields are candidates for fact or measure columns.
5. Observe that there is a dynamic choice list field that references the Opportunity object. This indicates that the
Opportunity object is a related object. You can add fields from a related object to your custom subject area.
6. Examine the structure of EXT Child.
Examine the Structure of EXT Child

A child object is an object that has one-to-many relationship with a parent object and can be a parent object of another child
object. Child objects are used in the Business Intelligence (BI) Composer when building a custom subject area report.
1. In the regional area, expand EXT Child.
2. Click Fields.
3. Observe there are five custom fields of varying types, including one number field, one date, and one currency field.
These fields are candidates for fact or measure columns.
Create the Custom Subject Area

You create a custom subject area by selecting a parent object, related objects, and specific fields. When you later build
a report within the BI Composer, the custom subject area that you choose as the basis for the report controls the data
displayed on the report.
1. Click the Add Child Object icon at the right of the EXT SalesParent section.
2. Set Child Object = EXT Child
3. Click OK.
4. Click Next.
29
Select the Child Fields for the Subject Area

Child object are objects whose data you want to use i n your reports. You can only add child objects if the parent object have
child objects. These object aree used in building custom subject area reports.
1. Set Fields From = EXT Child.In the Selected Fields pane.
2. Click the Select Fields button.
3. In the Selected Fields pane, Ctrl-click to select the following and move them to Available Fields pane. This should
leave Graduated, EXTSalesParent_Id_c, Age, Role, Salary, and Name as selected fields.
Record ID
EXT Child Name
Last Update Date
Last Updated By
Creation Date
Created By
4. Click OK.
5. In the local area, expand EXT Child.
6. Observe that the date, number, and currency fields are designated as measures.
7. Select the Age row.
8. Set Measure Aggregation to Average and Median
9. Leave the other measure aggregations blank.
10. Click Next.
Set an Implicit Fact

Implicit facts are used for summary and roll-up reports. To set an implict fact, perform the following steps.
1. In the Implicit Fact section, expand EXT SalesParent.
2. Expand Value
3. Select the AVG row.
4. Select the Implicit Fact check box.
5. Click Next.
30
Date Leveling
Date leveling is used to roll up data by date.
1. In the local area, expand EXT Child.
2. Observe that only date fields for the objects are displayed. You can designate a date field for date leveling.
3. Select the Graduated row.
4. Select the Allow Leveling check box to allow date leveling for this field.
5. Click Next.
Configure the Custom Object Security

You can secure a custom subject area by granting or revoking access rights from role names. Configuring security for custom
object determines which role names can or cannot access a custom subject area.
1. Accept the default of Read for all roles.
2. Click Next.
After you configure the custom object security, you can publish your Custom Subject Area Based on a Pair of
Seeded Custom Objects. Once you publish your Custom Subject Area Based on a Pair of Seeded Custom Objects,
these custom object can be used when creating and configuring your custom reports.
Creating and Viewing an Analysis for a Custom

Subject Area
In this section, you first create a report using the published custom subject area and then view it.
Creating an Analysis for a Custom Subject Area
The following process describes how to create an analysis in Oracle Business Intelligence Composer (BI Composer) using the
Sales - CRM Pipeline subject area.
1. Click the Navigator menu item.
2. Under the Tools category, click Reports and Analytics.
3. Click Create, and then click Analysis.
4. Under Select Subject Area, locate and select the published Custom: Opportunity Winning Partners custom
subject area.
5. Review the custom subject area: Expand each folder and review its attributes and measures.
31
6. Follow the steps in the report creation wizard to create a report:
a. Add the attributes and measures to the selected columns list.
b. Click Next.
c. Select Table and Graph to be included in the report.
d. Click Next.
e. Define the Table layout options.
f. Click Next.
g. Define how data will be sorted or filtered in the report.
h. Click Next.
i. Define any desired column format.
j. Click Next
k. Enter the Analysis Name as Opportunity Winning Partners.
l. Click Submit and wait until the Confirmation screen is displayed.
7. Run the created report by navigating to the folder where you saved the report.
8. Select Opportunity Winning Partners.
9. Click View to run the report.
Creating and Editing Analyses Using a Wizard:

Procedure
You can use a wizard that guides you through creating and editing analyses. Even though the wizard doesn't give you all
available features, you can still use it to make typical changes, for example, adding views or filters.
Restriction
The wizard isn't available for dashboards, and you can't use it to delete analyses.
Creating an Analysis
1. Open the Reports and Analytics pane in any work area.
2. Click Create and select Analysis.
3. Select the subject area that has the columns you want for your analysis.
32
4. Optionally add more subject areas or remove any that you no longer need.
5. Select the columns to include, set options for each column, and click Next.
6. Optionally enter a title to appear at the top of the analysis, above the analysis name which you enter in the last step.
7. Select the type of table or graph (or both) to include, specify the layout of the views, and click Next.
Tip
At any point after this step, you can click Finish to go to the last step, to save your analysis.
8. Optionally set more options for the table or graph, and click Next.
9. Optionally add sorts or filters based on any of the columns you included, and click Next.
10. If you have a table, optionally define conditional formatting for select columns, for example, to display amounts over
a certain threshold in red. Click Next.
11. Enter the name of your analysis and select a folder to save in.
12. Click Submit.
Editing an Analysis
1. Open the Reports and Analytics pane in any work area where the analysis is available.
2. Select your analysis in the pane and click Edit.
3. Perform steps 4 through 10 from the preceding Creating an Analysis task, as needed.
4. Save your analysis with the same name in the same folder.
Tip
You can create a copy of the analysis, whether you edited it or not, just by saving it either with a new
name or in a new folder.
5. Click Submit.
An Example in Greater Detail - Building Analyses to

Monitor Sales Trends
Historical Trending Analysis: Overview

Oracle Sales Cloud offers a new reporting feature for analytics that allows users view and compare current with past reporting
data. Before you can take advantage historical trending features you need to first verify historical trending reports are enabled
on your system. You can determine if have historical trending data by verifying the appropriate profile options and processes.
33
Historical Trending Analytics Profile Options

In this section we discuss how verify historical trending reports are enabled on your system using the profile options
associated with the historical trending report.
Review Profile Options Associated with Historical Trending Analysis

To review profile options associated with historical trending analysis, preform the following steps.
1. Navigate to Setup and Maintenance.
2. Set Name = Manage Opportunity Profile Options.
3. Click Search
4. Click the Go to Task icon next to Manage Opportunity Profile Options.
5. In the Manage Opportunity Profile Options page, set Profile Display Name = Sales Historical Snapshot
Configuration.
6. Click Search.
7. Verify that a single profile with Profile Option Code =

MOO_MANAGE_SALES_HISTORICAL_SNAPSHOT_CONFIGURATION is down.
8. In the Profile Values section, verify:
Profile Level = Site
Profile Value = C=120,D=120,W=58,M=14,Q=5
The profile value here specifies the retention policy. This profile option allows a sales administrator to tune the how
long the system should retain daily, weekly, monthly and quarterly snapshots.
The following table lists the profile codes.
Code Description
C: Closed period (in days) Tells the system to create snapshots for
opportunities closed within the last C days. This
value must be greater than zero.

D: Daily snapshots (in days) The number of days to retain daily snapshots. This
value must be greater than zero

W: Weekly snapshots (in weeks) The number of weeks to retain weekly snapshots.
This only applies if the enterprise calendar is a
week-based calendar

M: Monthly snapshots (in months) The number of months to retain monthly snapshots.
This only applies if the enterprise calendar is a
month-based calendar
34
Code Description

Q: Quarterly snapshots (in quarters) The number of quarters to retain quarterly

snapshots.

An upper limit of 10,000,000 snapshot records (opportunity and revenue records combined) is supported. Once
the record limit is reached, the snapshot process will automatically purge 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. It is a prerequisite to set up
the enterprise calendar before using historical snapshots.
9. Click Cancel to close the profile options page without altering any values.
Creating a Historical Trending Analysis: Worked Example

Using historical trending features, sales reps and managers can see how the pipeline and opportunities are trending. You can
also use historical trending to detect any anomalies and manage the pipeline more effectively.
Creating Historical Trending Reports

To create historical trending reports, perform the following steps.
1. Navigate to Reports and Analytics.
2. In the regional area, click the Browse Catalog icon.
3. In the upper left, expand the New drop-down.
4. Select Analysis.
5. Drill down on the Sales - CRM Historical Pipeline subject area. You may need to scroll down.
This subject area is specifically designed for reporting on opportunities and revenues against their daily, weekly or
monthly (depending on the enterprise calendar period setup), quarterly and yearly trends or to compare opportunity
and revenue data against specific points in time. The other historical snapshot subject area is Sales - CRM
Opportunity Sales Stage Snapshot, that includes the following:
Term Definition
Historical Opportunity Dimension contains historical snapshot data on standard

opportunity attributes

Historical Opportunity Extension Dimension contains historical snapshot data on custom

opportunity attributes

35
Term Definition
Historical Revenue Dimension contains historical snapshot data on standard

revenue attributes

Historical Revenue Extension Dimension contains historical snapshots data on custom

revenue attributes

Pipeline Snapshot Date Dimension contains opportunity/ revenue snapshot frequency.

An attribute from this dimension is a must for
reporting on data from any of the historical
dimensions and facts

Opportunity Dimension contains real time opportunity data

Opportunity Extension Dimension contains real time opportunity custom data

Revenue Dimension contains real time revenue data

Revenue Extension Dimension contains real time revenue custom data

Other dimensions contains real time data

Historical Pipeline Facts Similar to pipeline facts in the Sales - CRM Pipeline
Subject Area. Here, the measurements are
calculated based on historical opportunity snapshot
data (at opportunity granularity)

Historical Pipeline Detail Facts Similar to pipeline detail facts in the Sales - CRM
Pipeline Subject Area. Here, the measurements
calculated based on historical opportunity and
revenue snapshot data (at revenue granularity)

Select the columns for your analysis:
6. In the regional area, expand Opportunity.
7. Double-click Opportunity Name to add it to the Selected Columns section. You may need to scroll down to locate
Opportunity Name
8. Add Owner First Name.
9. Add Owner Last Name.
10. Expand Customer and add Customer Name.
36
11. Collapse Customer and expand Industry.
12. Add Industry Name and collapse Industry.
13. Expand Product and add Product Name.
14. Collapse Product and expand Revenue.
15. Add Revenue ID and collapse Revenue.
16. Expand Pipeline Snapshot Date.
Notice that you can choose a pipeline date, period (week or month), quarter, or year.
17. Add Pipeline Snapshot Date and collapse Pipeline Snapshot Date.
18. Expand Historical Pipeline Detail Facts.
Notice that you can add facts on revenue lines, open or closed opportunities, or both.
19. Add Opportunity Line Revenue.
20. Verify your columns.
After you create an historical trending report, you should create filters for your report. The next section describes
this process
Filtering Historical Reports

1. Click Create a filter for the current Subject Area, in the local area, under Filters.
2. In the drop-down, click More Columns.
3. In the pop-up, expand Opportunity.
4. Select Opportunity Status Category.
5. Click OK.
6. Verify that Operator = is equal to / is in.
7. Select Value = OPEN.
8. Click OK to close the New Filter dialog box.
After creating your filters for your historical trending report, you should save your reports. The next section describes
how to save your historical trending reports.
Saving Historical Analyses

The section describes how to save your historical trending analyses.
Saving Historical Trends Analyses

To save historical trends analyses, perform the following steps.
1. In the upper-right corner, click the Save As icon.
37
2. In the Save As pop-up, expand Shared Folders > Custom > Customer Relationship Management > user id
nn, where nn is your id number.
3. Set Name = OpportunityLineRevenue -nn, where nn is your id number.
4. Click OK.
Generate Sales Historical Snapshots: Tutorial

Sales Cloud allows customers to capture a daily snapshot of opportunity and revenue data using a scheduled process called
Generates Sales Historical Snapshots. After the daily snapshot is captured you can then create sales historical pipeline
reports to view opportunity and revenue data trends over time using the Analytics subject area Sales - CRM Historical
Pipeline. Sales Administrators can login to the application and schedule the start of the Generates Sales Historical Snapshot
process on a daily basis to capture opportunity and revenue snapshots.
The Generates Sales Historical Snapshots process capture opportunity and revenue snapshots for open opportunities
and opportunities closed within the last C days where C is configured via the profile option Sales Historical Snapshot
Configuration. The snapshot is captured for the date the process is scheduled to run and after capturing snapshots, it will
purge previous snapshots based on the retention policy defined in the profile option Sales Historical Snapshot Configuration.
Scheduling Generates Sales Historical Snapshots

The Sales Historical Snapshot process provides the ability to configure the following:
Number of days after which opportunities have been closed to continue to snapshot the opportunity and its
corresponding revenue information
The timeframe that the system should retain daily, monthly, weekly, and quarterly snapshots.
To scheduled to capture historical snapshot data on a daily basis, perform the following steps.
1. Login to the Application as a Sales Administrator.
2. Select Scheduled Processes in the Navigator menu.
3. Click the Schedule New Process button on the Scheduled Processes page.
38
This will launch the Schedule New Process dialog.
4. Click the Search link in theName drop down. Search for the Generates Sales Historical Snapshots job.
5. Search for the job Generates Sales Historical Snapshots.
6. Select Generates Sales Historical Snapshots and click OK.
7. Click the OK button in the Schedule New Process dialog.
8. Click the Advanced button.
9. Configure a schedule interval in the Schedule Tab. ,
10. Select Run option Using a scheduleDaily frequency which runs every 1 Days, and specify Start and End dates.
11. 10Click the Submit button after specifying information.
12. Click the OK button in the confirmation dialog.
13. Click the Close button in the Process Details dialog.
14. Search for the Generates Sales Historical Snapshots in the Scheduled Processes UI to see the scheduled jobs.
The entry without a scheduled time can be used to edit the job schedule using the Edit Schedule button in the
Details section.
Viewing Analytics in the Catalog: Procedure

You can view any of the sales reports from the Reports and Analytics Catalog in BI.
Viewing Analytics in the Catalog

Use the following procedure to view your analytics from the Catalog. Many of the reports have options to view as a bar chart,
table, or funnel.
To view a report, in this case the opportunity and revenue analysis:
1. Navigate to Reports and Analytics
2. In the regional area, expand Shared Folders.
39
3. Expand Sales. You might need to scroll down in Contents to see sales.
4. Expand Analytic Library > Embedded Content > Opportunity and Revenue Management. These are as-
delivered reports intended to be included in opportunity and revenue management pages.
5. Click Opportunity List Report..
6. Click View. In the local area, notice that a new tab labeled "Opportunity List Report" is created. After a few
moments, observe that a tabular report with opportunities grouped by year, Sales Method, Sales Stage, and
Customer is shown.
Opportunity List Report view in BI
Use the following procedure to sort your report after it has been generated.
1. The as-generated report is sorted by customer name in ascending order. Move the cursor over the "Customer
Name" column header until the sort ascending and sort descending icons appear.
40
2. Click the sort descending, and verify that the rows are restored. Oracle Sales Cloud reports group similar values of
a column together.
Cross-Subject Area Analyses
About Cross-Subject Area Analyses

You can create analyses that combine data from more than one subject area. This type of query is referred to as a cross-
subject area analysis. Cross-subject area analyses can be classified into three broad categories:
Using common dimensions
Using common and local dimensions
Combining more than one result set from different subject areas using set operators such as union, union all,
intersection and difference.
Common Dimensions
A common dimension is a dimension that exists in all subject areas that are being joined in the report. Dimensions are
categorizations of data, and the categorizations reflect how a business analyst wants to analyze data. When analysts say they
want to see numbers "by" something or "over" something, they are identifying the dimensions of the data. Some common
dimensions that exist in Sales subject areas are geography, product, customer, and time.
Data Structure for Analytics: Explained

Oracle Business Intelligence repository contains the metadata that defines which columns (or piece of data) are available for
you to include in analyses, and where data for each column originates. The repository is organized into subject areas, which
contain folders with the columns.
Note
You can also use the Oracle BI repository as a data source for reports.
Columns
This table describes the three types of columns.
Column Type Description Example Icon for Column Type
Fact Provides a measure of Total Yellow ruler

something, meaning that
the values are numbers.

Attribute Represents a piece of Start Date Gray paper

information about a
business object, with
41
Column Type Description Example Icon for Column Type

values that are dates,
IDs, or text.

Hierarchy Holds data values Time, with sublevels: Column: Hierarchy of

that are organized in a blue squares
hierarchical manner. Year Sublevel: Blue or white
square
Quarter
Month
Subject Areas
When you create an analysis, you first select a subject area, which contains columns related to a specific business object or
area. You then open folders within the subject area to find the columns to include in your analysis.
Folders
Each subject area has one fact folder and a number of dimension folders. Folders can have subfolders.
Fact folders:
Contain fact columns.
Are usually at the bottom of the list of folders and are usually named after the subject area.
Dimension folders:
Contain attribute and hierarchical columns.
Are joined to the fact folder within a subject area.
For example, if your analysis has the Currency attribute from a dimension folder, you see currencies in the
results. If you also add the Total fact, then your analysis includes only records with both a currency and a total
amount. The more columns you add, the smaller the query set for your analysis.
Can be common folders or common dimensions that appear in more than one subject area.
Important
If your analysis has columns from multiple subject areas, then you:
Include columns only from dimension folders that are common to all of those subject areas. At
least one such column is mandatory.
Must include one column from the fact folder in each of those subject areas.
42
Customizing Data Models: Procedure

A data model defines where data for a report comes from and how that data is retrieved. If a data model can't give you all the
data that you need in your report, then you can either copy and edit an existing data model or create a new one.
Creating a Data Model
1. In the Oracle BI Presentation Catalog, click the New button and select Data Model under Published Reporting.
2. Optionally click the Data Model node in the Data Model pane to set properties for the data model.
3. Click the Data Set node in the Data Model pane to create or edit data sets, which determine where and how to
retrieve data.
4. Click the New Data Set button and select a data set type.
Tip
It's recommended that you use the BI repository as a data source, so select either:
Oracle BI Analysis: To use columns from a selected analysis.
SQL Query: To use a Query Builder tool to define what to use from the repository. Select Oracle BI
EE as the data source.
5. Optionally click the Parameters node in the Data Model pane to define variables that users can set when they use
the report, to limit the data included in the report output.
Important
The order of parameters is important if there are job definitions defined for reports that use your data
model. If you change the order in the data model, the job definitions also need to be updated.
6. Optionally define other components of the data model.
7. Save your data model.
Editing a Data Model
1. To edit a predefined data model:
a. Find the data model in the BI catalog and click Copy.
b. Paste within Shared Folders - Custom in a subfolder that has a folder path similar to the folder that stores
the original data model.
43
c. For the data model you pasted, click More, and select Edit.
2. Optionally click the Data Model node in the Data Model pane to set properties for the data model.
3. Click the Data Set node in the Data Model pane to create or edit data sets.
Most predefined data models are of type SQL Query, and are set up to get application data from the following
tables:
ApplicationDB_FSCM: Financials, Supply Chain Management, Project Management, Procurement, and

Incentive Compensation
ApplicationDB_CRM: Sales
ApplicationDB_HCM: Human Capital Management
4. Perform steps 5 through 7 from the preceding Creating a Data Model task, as needed.
44
Creating Analytics and Reports Creating Analytics as Reports
4 Creating Analytics as Reports

Creating and Editing Reports
There are many predefined reports you can use to generate and print documents for internal operations, external business
transactions, or legal requirements. But, for specific requirements, you might need to create or edit reports to capture
different data or present it in another way.
A report consists of a data model, a layout, and a set of properties. Optionally, a report may also include a style template and
a set of translations. You build your reports using the following ways:
Design the layout for the report. The layout can be created using a variety of tools. The output and design
requirements of a particular report determine the best layout design tool. Options include the Layout Editor, which
is a Web-based layout design tool and enables interactive output, Microsoft Word, Adobe Acrobat, Microsoft Excel,
and Adobe Flexbuilder.
Set runtime configuration properties for the report.
Design style templates to enhance a consistent look and feel of reports in your enterprise.
Create sub templates to reuse common functionality across multiple templates.
Enable translations for a report.
Report Layout Types

BI Publisher offers several options for designing layouts for reports. The following formats are supported. Note that the layout
type determines the types of output documents supported:
Report Component Description
BI Publisher layout (XPT) BI Publisher's Layout Editor is a Web-based design tool

for creating layouts. Layouts created with the Layout
Editor support interactive viewing as well as the full
range of output types supported by RTF layouts.

Rich Text Format (RTF) BI Publisher provides a plug-in utility for Microsoft
Word that automates layout design and enables you
to connect to BI Publisher to access data and upload
templates directly from a Microsoft Word session.
The RTF format also supports advanced formatting
commands providing the most flexible and powerful of
the layout options. RTF templates support a variety of
output types including: Excel (mhtml), Excel (html), Excel
(*.xlsx), HTML, MHTML, PDF, PowerPoint, RTF, and
Zipped PDF.

Portable Document Format (PDF) PDF templates are used primarily when you must use
a predefined form as a layout for a report (for example,
a form provided by a government agency). Because
many PDF forms already contain form fields, using
the PDF form as a template simply requires mapping
45
Report Component Description

data elements to the fields that exist on the form. You
can also design PDF templates using Adobe Acrobat
Professional. PDF templates support only PDF output.

Microsoft Excel (XLS) Excel templates enable you to map data and define
calculations and formatting logic in an Excel workbook.
Excel templates support Microsoft Excel (.xls) output
only. If you must only view report data in Excel, then
you can also use BI Publisher's Analyzer for Microsoft
Excel to download report data to an Excel worksheet.
Create a layout for the data in Excel and then upload
the spreadsheet back to BI Publisher to save as a report
layout.

XSL Stylesheet Layouts can also be defined directly in XSL formatting

language. Specify whether the layout is for Data (CSV),
Data (XML), FO Formatted XML, HTML, Text, or XML
transformation.

eText These are specialized RTF templates used for creating

text output for Electronic Data Interchange (EDI) or
Electronic Funds Transfer (EFT) transactions.

Flash BI Publisher's support for Flash layouts enables you to

develop Adobe Flex templates that can be applied to BI
Publisher reports to generate interactive Flash output
documents.

Tasks That You Can Do in Reports

This table gives just a few examples of creating or editing reports.
Task Example
Edit the layout of a report. Add your company logo to the report output.

Add a new layout to a report. Design a new layout template that provides less detail
than the existing template.

Edit a data model. Add two fields to the data model used by a report so
that you can add those new fields to a custom layout for
the report.

46
Task Example
Create a new report based on a new data model. Create a new data model based on data from an
external system, and create new reports using the
custom data model.

Report Components
Each report has components that you can customize, as described in this table:
Report Component Description Tool for Customizing
Data model Defines the data source, data Data model editor in the application
structure, and parameters for the
report. Multiple reports can use the
same data model. Each report has
one data model.

Layout Defines the presentation, Depending on the template file

formatting, and visualizations of the type:
data. A report can have multiple
layouts. There are different types XPT: Layout editor in the
of layout templates, for example, application
Excel and RTF.
RTF: Microsoft Word
PDF: Adobe Acrobat

Professional
Excel: Microsoft Excel
eText: Microsoft Word
Properties Specifies formatting and other Report editor in the application

settings for the report.

Tasks That You Can Do in Reports

This table gives just a few examples of creating or editing reports.
Task Example
Edit the layout of a report. Add your company logo to the report output.

Add a new layout to a report. Design a new layout template that provides less detail
than the existing template.
47
Task Example

Edit a data model. Add two fields to the data model used by a report so
that you can add those new fields to a custom layout for
the report.

Create a new report based on a new data model. Create a new data model based on data from an
external system, and create new reports using the
custom data model.

Reporting Tools for Creating Custom Reports

Oracle Sales Cloud provides tools to help you create your own custom reports. These tools are designed for all types of
users, from novice to expert report builders.
Oracle BI Answers
Oracle BI Answers is a report creation tool that allows users create both simple and complex reports. Some reports might
include formulas, compound layouts, and joining of multiple subject areas. You can also create custom dashboards and
scorecards using this tool.
For more detailed information about Oracle BI Answers, see Oracle Business Intelligence Answers, Delivers, and Interactive
Dashboards User Guide.
BI Composer
BI Composer is a web-based report wizard designed for novice users. It guides you through the steps to create a report, and
at the end of the flow, you can save the report to the Oracle BI Presentation Services Catalog. You can launch BI Composer
from either the Reports and Analytics pane or the Reports and Analytics work area.
For more detailed information about Oracle BI Composer, see the chapter on Using BI Composer to Work with Analyses in
Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Creating Custom Reports: Procedure

Create a custom report when the predefined reports don't provide the data you need. Or, if you want to use a predefined
data model, and also want to change other aspects of the report other than layout. Save your custom report to Shared
Folders - Custom in the Oracle BI Presentation Catalog.
Creating a Report
2. Click Create and select Report.
3. Select the data model to use as the data source for your report.
48
4. Continue with the wizard to create the report layout, or choose to use the layout editor and close the wizard.
5. Define the layout for the report.
6. Click the Properties button in the report editor to set specific formatting, caching, and processing options for your
report.
Setting Up Access
You or your administrator can:
Create a job definition so that users can run your custom report as a scheduled process.
Set up the report for scheduling in the Reports and Analytics pane.
Secure general access to your report and its job definition, if any.
A Simple Example of How to Build an Opportunity

Report
Creating a New Sales Report: Worked Example

Creating new reports in Oracle Sales Cloud is similar for the various functional areas, although available features might differ.
It is recommended, at least for novice users, that you use the predefined dashboards and reports on which you can base a
new report. Both administrators and users can create their own personal reports and can choose to share them.
This section provides one example of creating a new report that shows opportunities by sales stage. You might use this
feature differently depending on your business needs.
To create a new opportunity by sales stage report

1. Sign in to Oracle Sales Cloud.
2. From the Welcome page, click Navigator, and under the Tools section, select Reports and Analytics.
The Reports and Analytics work area appears.
3. Click Create.
This action launches BI Composer.
4. Select the Sales - CRM Pipeline subject area.
5. Select the following attributes for the report, and then click Next:
Employee Name
Opportunity Name
Sales Stage Name
Status
49
In the Pipeline Facts subject area, select # of Opportunities
6. Select the following views (which is the visualization for the report), and then click Next.
For Graph, select Bar.
For Title, enter Opportunity Count by Sales State (the name of the report)
For Layout, and Table, keep the defaults (Table Above Graph and None, respectively).
By default the application moves all the dimensional attributes into the Group By section (depicts the bars for
the bar graph)
Exclude Employee and Opportunity Name to further define the graph to include only sales stage related bars.
Note
Use the Move To drop-down list to exclude a view.
7. Add a filter to show only certain sales stages in the report by selecting the following sales stages column values:
Closed
Discovery
Negotiation
Short List
Solution Presentation
Note
Filtering is an optional feature.
8. Click Preview to see how the bar graph will appear.

9. Add another filter to show only opportunities specific to a customer such as Pinnacle Technologies (using the
Customer Name column).
Note
In the preview, notice the bars are now shorter because the additional filter was applied.
10. Click Next.

11. Save the report by doing the following:
Click My Folders if you do not want others to view the report. Otherwise, click Shared Folders.
Enter the report name as Opportunities by Sales Stage.
50
Click Submit.
A dialog box appears confirming the report was saved successfully.
Click OK to exit.
To watch a video that walks you through this example, see the following article ID 1474869.1 on My Oracle
Support:
https://support.oracle.com/epmos/faces/ DocumentDisplay?_afrLoop=363802483569580=1474869.1=
18555ity9z_41#REF_PURPOSE
Making Reports Available for Online Viewing:

Procedure
Some reports are set up so that you can only view them through another application or submit them as a scheduled process.
To view your report online while you're editing it, you need to define a few settings. When you're done editing your report,
make sure that you reset these settings as needed.
Updating Report Properties

1. Select your report in the Oracle BI Presentation Catalog and click Edit.
2. In the report editor, click Properties at the top of the page.
3. In the Report Properties dialog box, select Run Report Online and deselect Report is Controlled by External
Application.
Updating Layout Settings

1. Back in the report editor, click the View a list link.
2. Make sure that the View Online check box is selected.
Accessing Report Components to Customize: Points

to Consider
To create or edit reports, you need to access the Oracle BI Presentation Catalog. In the catalog, objects of type Report
represent the report definition, which includes report properties and layouts. Data models are separate objects in the catalog,
usually stored in subfolders called Data Models.
Accessing the Oracle BI Presentation Catalog

You have the following options:
In the Reports and Analytics pane, click the Browse Catalog button to open the Oracle BI Presentation Catalog,
and find your report or data model in the Folders pane.
51
In the Reports and Analytics pane, find your report and select More to go to the report directly in the catalog. The
data model associated with the report should be in the Data Models subfolder within the same folder as the report.
Sign in to the application directly (for example: http://host:port/analytics/saw.dll) to open the catalog.
Sign in to the BI Server directly (for example: http://hostname.com:7001/xmlpserver) to open the catalog.
Alternatively, once you are in the catalog using another method, for example, through the Reports and
Analytics pane, change the final node of the URL (http://host:port/analytics/saw.dll) to xmlpserver. So the URL
you use would be: http://host:port/xmlpserver.
Predefined Reports
A special Customize option is available only:
For predefined reports, not data models.
Through direct access to the Oracle Business Intelligence server using the /xmlpserver URL. When you find your
report in the Oracle BI Presentation Catalog, select Customize from the More menu.
The Customize option automatically creates a custom copy of a predefined report and stores it in the Shared Folders -
Custom folder within the catalog. The new report is linked to the original, so that when users open or schedule the original,
they are actually using the custom version.
If you don't have access to the Customize option or don't want the original version linked to the new report, then make a
copy of the predefined report and save it in the Custom folder.
Predefined Data Models

Don't edit predefined data models. Instead, copy the data model into the Custom folder and edit the copy.
Using the Customize Option for Predefined Reports:

Points to Consider
The Customize option automatically creates a custom copy of a predefined report and stores it in the Shared Folders -
Custom within the Oracle BI Presentation Catalog. The report definition, folder structure, and original report permissions are
copied.
This custom copy is linked internally to the original report. You can edit the custom copy of the report, leaving the original
report intact. When users open or schedule the original report, they are actually using the custom version.
Benefits of the Customize Option

Aside from conveniently copying a predefined report to the Custom folder, the Customize option:
Makes it unnecessary to update processes or applications that invoke the report. For example, if the original report
is set up to run as a scheduled process, then don't change the setup. When users submit the same scheduled
process, the custom report runs instead of the original.
Automatically copies the security settings of the original report.
Removes the risk of patches overwriting your edits. If a patch updates the original report, the custom report is not
updated in any way.
52
Note
The custom report still references the original data model. The data model is not copied. A patch that
updates the data structure of the data model might affect your custom report.
Accessing the Customize Option

To access the Customize option:
1. Sign in to the BI Server (for example, http://hostname.com:7001/xmlpserver).
2. In the Folders pane, select the predefined report.
3. Select Customize from the More menu for the report.
4. The copied report in the Custom folder opens, so proceed to edit this report.
To edit the custom report again later, you don't need to be in the BI Server. Just go to the Oracle BI Presentation Catalog and
either:
1. Select the Customize or Edit option for the original report.

2. Find your custom report in the Custom folder and select Edit.
Links Between Original and Custom Reports: Points

to Consider
The Customize option for predefined reports creates a custom copy of the report that is linked to the original. Consider the
following points when you work with both the original and custom versions.
Maintaining the Link Between Reports

The link between the predefined and custom report is based on the name of the custom report and its location within the
Custom folder in the Oracle BI Presentation Catalog.
If you manually create a report with the same name as a predefined report, and give it the same folder path under
the Custom folder, then the new report becomes a custom version of the original predefined report. This action
would be as if you had used the Customize option to create the custom report.
The link to the original report is broken if you rename the custom or original report.
You can edit the custom report so that it uses a different data model. But if the original data model is updated later,
then your custom report doesn't benefit from the change.
Tasks Performed on Original Reports

This table describes what happens when you use the original report and a corresponding custom report exists
Task Performed on the Original Report Result When There's a Custom Report
Open Opens the custom report.

53
Task Performed on the Original Report Result When There's a Custom Report
Schedule Creates a report submission for the custom report.

Edit Edits the custom report.

Delete Deletes the original report only. If you delete the custom
report, the original report is not deleted.

Copy Copies the original report.

Cut and Paste Cuts and pastes the original report.

Rename Renames the original report. The custom report name is

not changed.

Warning
This action breaks the link between the
original and custom reports.

Download Downloads the custom report.

Customize Edits the custom report.

History Opens the job history of the custom report.

What happens to customized analytics and reports

when a patch is applied?
All custom analytics and reports are preserved if you save them in the Custom subfolder within Shared Folders or in My
Folders in the Oracle BI Presentation Catalog.
Changes to predefined analytics and reports outside the Custom folder are preserved only if no new versions of BI objects
are contained in the patch. If the patch does include a new version of a predefined object that you edited outside the Custom
folder, then:
The new version overwrites the existing predefined object.
A copy of the existing object (with your edits) is automatically created in the same folder, with a new name that
indicates it's a custom version.
54
If the patch includes a new version of both the predefined object and a folder in its file path, then:
The new folder, along with the new version of the object, overwrites the existing predefined folder and object.
A copy of the existing folder (along with your edited object) is automatically created. The folder is renamed to indicate
that it's a custom version, but your edited object is not renamed.
Note
Future patches won't affect renamed custom objects within a renamed custom folder.
Working with report Layouts
Creating and Editing Report Layouts: Overview

The layout determines what and how data is displayed on report output. All predefined reports have at least one predefined
layout template file.
Layout Templates
To customize a layout, you edit the layout template, which:
Defines the presentation components, such as tables and labeled fields.
Maps columns from the data model to these components so that the data is displayed in the right place.
Defines font sizes, styles, borders, shading, and other formatting, including images such as a company logo.
Layout Template Types

There are a few types of template files to support different report layout requirements.
RTF: Most of the predefined templates are rich text format (RTF) templates created using Microsoft Word.
XPT: Created using the application's layout editor, these templates are for interactive and more visually appealing
layouts.
eText: These templates are specifically for Electronic Data Interchange (EDI) and Electronic Funds Transfer (EFT).
You can also create and edit other types of templates using Adobe PDF, Microsoft Excel, Adobe Flash, and XSL-FO.
Overall Process to Create or Edit Layouts

Editing or creating report layout, for example, using Microsoft Word or the layout editor, involves making the actual changes
to the template file. But that task is just one part of the entire process for customizing layouts.
1. Copy the original report and save the custom version in Shared Folders - Custom in the Oracle BI Presentation
Catalog. You create or edit templates for the custom copy of the report.
55
Tip
You can use the Customize option if the original is a predefined report.
2. Review report settings for online viewing.
3. Generate sample data for the report.
4. Edit or create the layout template file.
5. Upload the template file to the report definition.
Note
You don't need to do this if you're using the layout editor.
6. Configure the layout settings.
Deleting Layout Templates

To remove a layout template for a report:
2. In the report editor, click View a list.
3. Select the layout template and click Delete.
Generating Sample Report Data: Procedure

Depending on the type of report layout changes you're making, sample data can be mandatory or helpful. You generate
sample data, and then load it for use with your layout, so that you can map data fields to layout components. For example,
for the Start Date table column in your layout, you can set it so that the data displayed in that column comes from the Start
Date field in the sample data.
You can generate sample data from the:
Report data model
Report viewer
Scheduler
Generating Data from the Data Model

To generate sample data from the data model:
1. Select your data model in the Oracle BI Presentation Catalog and click Edit.
56
Tip
If you're not sure which data model is the source for your report, find the report in the catalog and click
Edit. The data model is displayed in the upper left corner of the report editor.
2. In the data model editor, click View Data.
3. Enter values for any required parameters, select the number of rows to return, and click View.
4. To save the sample data to the data model, click Save As Sample Data.
If you're designing an RTF template, click Export to save the file locally.
5. Save the data model.
Saving Data from the Report Viewer

To save sample data from the report viewer:
Note
This procedure requires that the report is enabled for online viewing.
1. Select the report in the Oracle BI Presentation Catalog.
2. Click Open to run the report in the report viewer with the default parameters.
3. On the Actions menu, click Export, then click Data.
4. Save the data file.
Saving Data from the Scheduler

To save sample data from the scheduler:
Note
This procedure requires that the report is enabled for scheduling (not as a scheduled process).
1. Select the report in the Oracle BI Presentation Catalog.
2. Click Schedule.
3. On the General tab, enter values for any report parameters.
4. On the Output tab, ensure that Save Data for Republishing is selected.
5. Click Submit.
6. Open the Report Job History page.
57
7. On the global header, click Open, then click Report Job History.
8. Select your report job name in the Job Histories table.
9. On the details page, under Output and Delivery, click the XML Data Download icon button.
Creating and Editing Report Layout Templates Using the

Layout Editor: Procedure
The layout editor in the application provides an intuitive, drag-and-drop interface for creating pixel-perfect reports with PDF,
RTF, Excel, PowerPoint, and HTML output. The layout template files you create with this tool have an .xpt extension.
This tool is the only one that can give you dynamic HTML output. Users can interact with this output in a browser, for
example, by sorting, applying filters, and so on.
Prerequisite
Make sure that sample data is generated from the data model that your report is using.
Using the Layout Editor

To customize XPT templates:
1. Select the report in the Oracle BI Presentation Catalog and click Edit.
2. In the report editor, click Edit to update a template.
Or, click Add New Layout and select a template type under the Create Layout section.
3. Create or edit the layout.
4. Click Save to save the layout to the report definition.
Setting Up for RTF and Excel Report Layout Templates:

Procedure
Other than using the layout editor in the application to work on report layout templates, you can also use Microsoft Word or
Microsoft Excel to create or edit RTF and Excel layout templates. You must download and install the appropriate add-in so
that the Microsoft application has the features you need to design report layouts.
Note
If you're designing a new layout for your report, consider using the layout editor.
Installing the Add-In
2. Click the Browse Catalog button.
58
3. Click Home.
4. Under the Get Started pane, click Download BI Desktop Tools.
5. Select the add-in for the type of template you're working with.
Template Builder for Word: RTF templates
Analyzer for Excel: Excel templates
6. Save and then run the installer.
Creating and Editing RTF Report Layout Templates: Procedure

Most predefined report layout templates are RTF templates. An RTF template is a rich text format file that contains the layout
instructions to use when generating the report output. Use Microsoft Word with the Template Builder for Word add-in to
design RTF templates.
Prerequisites
Install the Template Builder for Word add-in, and generate sample data.
Using Template Builder for Word

To customize an RTF template:
1. If you are editing a predefined layout:
a. Select your report in the Oracle BI Presentation Catalog and click Edit.
b. In the report editor, click the Edit link of the layout to download the RTF file.
If you are creating a new layout, skip this step.
2. Open the downloaded RTF template file in Microsoft Word. Or, if you're creating a new template, just open
Microsoft Word.
3. Load the sample data that you generated.
4. Edit or create the layout template.
5. Save the file as Rich Text Format (RTF).
Uploading the Layout Template File to the Report Definition:

Procedure
If you're creating or editing a report layout using the layout editor, the layout is automatically saved to the report definition, so
you can skip this step. For all other layout types, for example, RTF, upload the template file to the report definition after you're
done making layout changes.
59
Uploading the Template File
3. In the table that lists the layouts, click Create.
4. Under Upload or Generate Layout, click Upload.
5. In the Upload Template File dialog box:
a. Enter a layout name.
b. Browse for and select the layout template file that you created or edited.
c. Select the template file type.
d. Select the locale, which you can't change once the template file is saved to the report definition.
e. Click Upload.
6. Save the report definition.
Configuring Layout Settings for Reports: Procedure

As part of creating or editing layout, you can set report properties related to layout. These settings determine, for example,
which layouts users can choose from when viewing or scheduling the report. The settings apply only to your report.
Setting Layout Properties
3. Set layout properties, some of which are described in this table.
Setting Description
Output Formats Depending on the requirements for a report,

you may want to limit the output file formats (for
example, PDF or HTML) that users can choose
from. The available output formats vary depending
on the template file type.

Default Format When multiple output formats are available for the
report, the default output format is generated by
default when users open the report in the report
viewer.
60
Setting Description

Default Layout When multiple layouts are available for the report,
you must select a default layout to present it first in
the report viewer.

Active Active layouts are available for users to choose

from when they view or schedule the report.

Tip
To hide a predefined layout from users,
inactivate it.

View Online Select this check box so that layouts are available
to users when they view the report. Otherwise, the
layout is available only for scheduling the report.

4. Click the Save Report button.
61
62
Creating Analytics and Reports Reporting in Multiple Currencies
5 Reporting in Multiple Currencies
Setting Currency Preferences and Exchange Rates

Oracle Sales Cloud gives you the ability to set your personal currency preferences, as well as set currency preferences which
determine how your reports display currency and calculate exchange rates.
The user preferences for Sales Cloud are set in the Sales Cloud environment, and the currency preferences for reporting are
set in Oracle Business Intelligence (BI). Both user preferences impact how your report currency is calculated and displayed.
Your system administrator sets the corporate currency as the common currency basis for all users.
There are three ways currency is set in the Sales Cloud and BI environments:
1. User Currency - Set by the business user in Oracle Sales Cloud, Regional settings. This setting applies to the entire
application interface for that user only. The currency options available in the dropdown are set by your system
administrator.
2. Reports Currency - Set by the business user in BI under My Account in the Reports area. The setting applies to that
user only and only relevant for report production.
3. Corporate Currency - Set by the system administrator. This setting applies to all users in that company.
Setting Your General User Currency

User currency settings govern the currency that is used as the default for your application interface. User currency is set in the
Oracle Sales Cloud application and applies to your entire interface for your signed-in session.
To Set Your user currency:
1. Navigate to Personalization > Set Preferences.
2. Select Regional from the Task list in the left pane.
3. Select the preferred currency to be used. The currency drop-down list includes currencies that were set up in
Oracle Sales Cloud for your company by your system administrator.
63
The following image shows the user currency preferences option for Sales Cloud.
Setting Your Reports Currency

The reports currency feature determines the currency that is used for creating your sales reports. This currency setting also
determines how and when your currency conversion rates are calculated.
To Set Your Reports Currency:
1. Navigate to Business Intelligence.
2. Click Reports and Analytics in the navigator menu.
3. Click Browse Catalog.
4. Click the drop-down arrow and Choose My Account.
5. Go to the Preferences.
6. Select your choice in Currency.
64
The following image shows the currency options in BI. For reporting, only Entered, CRM, and the User Preferred options
apply.
The following table describes the currency dropdown menu options.
Currency drop-down Name Description
Entered Currency Currency used on a transaction (Opportunity, Lead,

etc.).

CRM Currency Currency set up in Oracle Sales Cloud application as the

common Corporate currency used company-wide.

User Preferred Currency using Simple Currency Conversion to User Preferred Currency is performed at
Management 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 Conversion to User Preferred Currency happens on
Management the date your run the report, and uses the currency
indicated on the record.

Understanding User-Preferred Currency Reporting and

Exchange Rates
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
system sets the exchange rate at that time. The option you choose impacts how quickly your reports are generated at run
time. To understand how this works, let's take a closer look at each case.
65
User Preferred Currency using Simple Currency Management

The advantage of this option is performance - the system doesn't have to look up the rate for each transaction because
when you close or save a record, the system converts it to your corporate currency at that day's rate. When you run the
opportunity report, the system multiplies that value by your preferred currency exchange rate for the date you run the report.
This eliminates the need for the system 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.
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 system
has to cycle through each record and match currency exchange rates to the date the record was closed or updated and
saved.
66
67
68
Creating Analytics and Reports Performance Tuning
6 Performance Tuning
Performance Tuning for Analytics and Reports: Points

to Consider
When you create analytics and reports, don't use blind queries and include sufficient filters when creating analytics or reports
with hierarchies.
Blind Queries
Avoid blind queries because they are performed without filters and therefore fetch large data sets. Performance could be
an issue with these queries and can easily overload the application. All Transactional Business Intelligence queries on large
transaction tables must be time bound. For example, include a time dimension filter and additional filters to restrict by key
dimensions such as worker. In addition, apply filters to columns that have database indexes in the transaction tables. This
ensures a good execution plan is generated for the Business Intelligence query.
Hierarchies and Trees in Transactional Business Intelligence

Queries on trees and hierarchical dimensions such as manager can have an impact on performance. Transactional Business
Intelligence uses a column-flattening approach to quickly fetch data for a specific node in the hierarchy. Still, because there
is no pre-aggregation for the different levels of the hierarchy, carefully craft any query involving hierarchies to ensure that
sufficient filters are applied to keep the result set small.
69
Creating Analytics and Reports Performance Tuning
70
Creating Analytics and Reports Keeping Your Analytics Secure
7 Keeping Your Analytics Secure

Security for Sales Cloud Analytics and Reports:
Overview
Analytics are available throughout Oracle Sales Cloud as embedded analytics and also in standalone mode by way of
the transactional work areas. Oracle Sales Cloud users interact with information in Oracle BI Applications and Oracle
Transactional Business Intelligence using Oracle Business Intelligence Enterprise Edition (Oracle BI EE) components, such as
Dashboards.
The analytics and reports that are delivered with Oracle Sales Cloud are secured based on the roles that use each report.
For example, sales managers can access sales analytics and reports that salespeople don't have access to. If you want to
create new analytics or reports or edit existing ones, you should become familiar with Sales Cloud security concepts and how
access is secured to Oracle Transactional Business Intelligence subject areas, Oracle BI Presentation Catalog folders, and
Oracle Business Intelligence reports.
Subject Areas
Subject areas are functionally secured using duty roles. The supplied user roles include the necessary duty roles to access
the Oracle Business Intelligence content. The names of duty roles that grant access to subject areas include the words
Transaction Analysis Duty (for example, Sales Managerial Transaction Analysis Duty). Access to a subject area is needed to
run or create reports for that subject area.
Note
The BI Author Role is required to create new OTBI reports. By default, the Sales Representative job role is not
assigned the BI Author role.
BI Presentation Catalog Folders

BI Presentation Catalog folders are functionally secured using the same duty roles that secure access to the subject areas.
Therefore, a user who inherits the Sales Managerial Transaction Analysis Duty can access both the Sales Manager folder in
the BI Presentation Catalog and the Sales Manager subject areas.
Oracle Business Intelligence Reports

Analyses are secured based on the folders in which they're stored. If you haven't secured BI reports using the report
permissions, then they're secured at the folder level by default. You can set permissions against folders and reports for
application roles, catalog groups, or users.
For More Information

When you receive your Oracle Sales Cloud implementation, access to its functionality and data is secured using role-based
access control (RBAC). For more information about securing subject areas, BI catalog folders and reports, see the following
guides:
Oracle Sales Cloud Security Reference
71
Available from the Oracle Cloud Documentation library, this guide describe the Oracle Sales Cloud applications
security reference implementation and includes descriptions of all the predefined data that is included in the security
reference implementation for an offering. The security reference implementation can be customized to fit divergent
enterprise requirements.
Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
This guide provides information about using Transactional Analysis Duty roles to secure access to the BI catalog.
Securing Permissions for Sales Cloud Analytics and

Reports
Sales objects display only if the proper privileges are assigned to the user, group, or role. Note that the owner of an object
or folder cannot automatically access the object or folder. To access an object or folder, the user must have the proper
permission assigned in the object or folder's permission dialog.
What Are Permissions?

An object's owner or a user who has been given the proper privileges and permissions can assign permissions to catalog
objects. Permissions are authorizations that you grant to a user or role to perform a specific action or group of actions on
a catalog object. For example, if you work in the sales department and created a dashboard that contains quarterly sales
projections, then you can give read access to this dashboard to all sales people, but give read, write, and delete access to
sales directors and vice presidents.
Note
Permissions are a part of the Oracle BI EE security model, and how permissions are initially assigned is based on
how users, roles, and groups were set up on your application, and which privileges the Oracle BI EE administrator
granted those users, roles, and groups.
Permission Definitions
To control access to objects (such as a folder in the catalog or a section in a dashboard), you assign permissions to
application roles, catalog groups, and users. The permissions that you can assign vary depending on the type of object with
which you are working.
The following are the main types of permissions encountered for Sales Cloud users:
Permission Definition
Full Control Use this option to give authority to perform all tasks
(modify and delete, for example) on the object.

Modify Use this option to give authority to read, write, and

delete the object.

Traverse Use this option to give authority to access objects

within the selected folder when the user does not have
72
Permission Definition
permission to the selected folder. Access to these
objects is required when the objects in the folder, such
as analyses, are embedded in a dashboard or Oracle
WebCenter Portal application page that the user has
permission to access.

For example, if you grant users the Traverse permission
to the /Shared Folders/Test folder, then they can
access objects, through the BI Presentation Catalog or
embedded in dashboards or Oracle WebCenter Portal
application pages, stored in the/Shared Folders/ Test
folder and stored in sub-folders, such as the /Shared
Folders/ Test/ Guest folder However, users cannot
access (meaning view, expand, or browse) the folder
and sub-folders from the Catalog.

Open Use this option to give authority to access, but not

modify, the object. If you are working with an Oracle BI
Publisher object, this option enables you to traverse the
folder that contains the object.

No Access Use this option to deny access to the object. Explicitly

denying access takes precedence over any other
permission.

Custom Use this option to display the Custom Permissions

dialog, where you grant read, write, execute, and delete
permissions.

For information on application roles, see Oracle Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
For information on catalog groups, see "Working with Catalog Groups" in Oracle Middleware Security Guide for Oracle
Business Intelligence Enterprise Edition.
Business Intelligence Roles: Explained

Business Intelligence roles apply to both Oracle Business Intelligence Publisher (Oracle BI Publisher) and Oracle Transactional
Business Intelligence (OTBI). They grant access to Business Intelligence functionality, such as the ability to run or author
reports. Users need one or more of these roles in addition to the roles that grant access to reports, subject areas, Business
Intelligence catalog folders, and Oracle Sales cloud data. This topic describes the Business Intelligence roles.
Business Intelligence roles are defined as application roles in Oracle Entitlements Server. This table identifies those roles.
Business Intelligence Role Description
BI Consumer Role Runs Business Intelligence reports.

73
Business Intelligence Role Description
BI Author Role Creates and edits reports.

BI Administrator Role Performs administrative tasks such as creating and

editing dashboards and modifying security permissions
for reports, folders, and so on.

BI Publisher Data Model Developer Role Creates and edits Oracle Business Intelligence Publisher
data models.

BI Consumer Role
The predefined OTBI Transaction Analysis Duty roles inherit the BI Consumer Role. You can configure custom roles to inherit
BI Consumer Role so that they can run reports but not author them.
BI Author Role
BI Author Role inherits BI Consumer Role. Users with BI Author Role can create, edit, and run OTBI reports.
All predefined Sales job roles that inherit an OTBI Transaction Analysis Duty role are also assigned the BI Author Role at the
job role level, except for the Sales Representative job role which is not assigned the BI Author role.
BI Administrator Role
BI Administrator Role is a superuser role. It inherits BI Author Role, which inherits BI Consumer Role.
The predefined Sales Cloud job roles do not have BI Administrator Role access.
BI Publisher Data Model Developer Role

BI Publisher Data Model Developer Role is inherited by the Application Developer role, which is inherited by the Application
Implementation Consultant role. Therefore, users with either of these predefined job roles can manage BI Publisher data
models.
Delivered Roles for Sales Cloud Analytics and

Reports
Oracle Transactional Business Intelligence secures reporting objects and data through a set of delivered OTBI Transaction
Analysis Duty roles. These OTBI Transaction Analysis Duty roles control which subject areas and analyses that a user can
access and what data a user can see in Oracle Sales Cloud.
Your administrator can select users, application roles, and catalog groups to:
Receive the delivery content of an agent.

Have permission to access a section or alert section in a dashboard.
Have permission to use a saved customization.
Add or edit for an existing catalog group.
74
Assign permissions to a catalog object.

For information about setting the necessary security, see Oracle Middleware Security Guide for Oracle Business Intelligence
Enterprise Edition.
The following is a list of some OTBI Transactional Analysis Duty roles for Sales:
Partner Channel Transaction Analysis Duty
Partner Channel Administrative Transaction Analysis Duty
Sales Administrative Transaction Analysis Duty
Sales Executive Transaction Analysis Duty
Sales Managerial Transaction Analysis Duty
Sales Transaction Analysis Duty
The following table lists analytics and reports available in Oracle Sales Cloud. It also shows the predefined job roles that can
access the different analytics and reports, and the OTBI Transactional Analysis Duty roles that provide the access.
Analytic or Report Name Job Role OTBI Transactional Analysis

Duty Role
Forecast vs. Quota Sales VP Sales Executive Transaction

Analysis Duty
Sales Stage by Age
Sales Performance Trend
Top Open Opportunities
Forecast Vs Open Pipeline: Sales Manager Sales Managerial Transaction

My Team Analysis Duty

My Team's Activities (By
Type)
My Team's Leads
My Team's Performance
My Team's Pipeline
My Team's Tasks on Open

Opportunities
My Team's Top Open

Opportunities
Team Leadership Board
Top Accounts by My Team's

Activities
My Open Leads by Age Sales Representative Sales Transaction Analysis Duty
75
Analytic or Report Name Job Role OTBI Transactional Analysis

Duty Role
My Top Open Opportunities
My Forecast vs. Open

Pipeline
My Open Leads by Source
My Open Tasks
My Performance
My Pipeline
My Stalled Opportunities
My Top Accounts by Open

Opportunities
My Unaccepted Leads by
Age
My Won Opportunities
Top Accounts by My Activities
Evaluating My Partners' Channel Account Manager Partner Channel Transaction

Pipeline Analysis Duty

Evaluating My Partners'
Quarterly and Yearly Closed
Revenue
Evaluating My Partners'
Current Quarterly Sales
Evaluating My Partners' Win

Rate
Note
The predefined Transaction Analysis Duty roles provide permissions to view but not create analyses and reports.
Permissions to create reports are assigned at the job role level using Business Intelligence roles.
76
Viewing Reporting Roles: Procedure

Viewing reporting roles can help you to understand Oracle Transactional Business Intelligence (OTBI) security. This topic
explains how to view the following:
1. OTBI roles that a job role inherits
2. All of the duty roles you are assigned
Note
A user must be assigned the Transactional Analysis Duty role to run queries and reports. You can verify that a
user, or the job role assigned to a user, has the Transactional Analysis Duty by performing the procedures in this
topic. The Transactional Analysis Duty role is inherited by the Transactional Business Intelligence Worker abstract
role.
Viewing OTBI Duty Roles Assigned to a Job Role

To view all the duty roles assigned to a job role, perform the steps in the following procedure.
1. Sign in with the IT Security Manager job role.
2. Select Navigator - Tools - Setup and Maintenance to open the Setup and Maintenance work area.
3. On the All Tasks tab of the Overview page, search for and select the Manage Duties task.
The Oracle Entitlements Server Authorization Management page opens. On the Home tab:
a. In the Application Name section, select crm.
b. In the Search and Create section, click Search - External Roles.
The Search - External Roles page opens.
4. In the Display Name field, enter the name of the job role. For example, enter Sales Manager, then click Search.
5. In the search results, select Sales Manager, then click Open Role.
The Sales Manager page opens.
6. Select the Application Role Mapping tab.
7. Expand the obi folder.
Notice the Transaction Analysis Duty roles that the Sales Manager job role inherits. Note also that the Sales
Manager job role inherits BI Author Role.
8. Expand the Sales Managerial Transaction Analysis Duty role.
It inherits BI Consumer Role.
77
9. Close the Authorization Management page and sign out.
Viewing the Duty Roles You Are Assigned

To view all of the duty roles that you are assigned, including Business Intelligence roles and Transactional Analysis Duty roles,
perform the following steps.
1. Sign in to Oracle Sales Cloud using your user ID and password.
2. Select Navigator - Tools - Reports and Analytics to open the Reports and Analytics work area.
3. In the Contents pane, click the Browse Catalog icon. The Business Intelligence Catalog page opens.
4. Click your user name in the global header, then select My Account.
5. Click the Roles and Catalog Groups tab.
All the duty roles you are assigned are listed, including Transaction Analysis Duty roles and Business Intelligence
roles.
6. Click OK.
7. Return to the Oracle Fusion Applications window and sign out.
Customizing Security for Oracle Transactional

Business Intelligence: Explained
Oracle Transactional Business Intelligence (OTBI) secures reporting objects and data through a set of delivered OTBI
Transaction Analysis Duty roles. You cannot customize the OTBI duty roles provided with Oracle Sales Cloud, or the
associated security privileges. However, you can customize OTBI reporting security according to your security requirements
as follows:
Create a custom job role and assign the required OTBI Transaction Analysis Duty roles to it.
Modify Business Intelligence role assignments.
Creating a Custom Job Role with OTBI Access

If you want to customize the OTBI subject areas that users have access to, create a custom job role, then provide the role
with access to OTBI reports by assigning OTBI Transaction Analysis Duty roles.
The following are the high-levels steps in creating a custom job role and assigning it access to OTBI reports.
1. Sign in to Oracle Sales Cloud with the IT Security Manager job role.
2. Create a custom job role in Oracle Identity Manager (OIM) using the Manage Job Roles task.
3. Save the new custom role, then configure the role to inherit the Transactional Business Intelligence Worker BI
abstract role.
78
The Transactional Business Intelligence Worker role inherits the Transactional Analysis Duty which is required to run
reports and execute queries.
4. Assign duty roles to the new custom job role in Authorization Policy Manager using the Manage Duties task.
5. Assign the appropriate OTBI Transaction Analysis Duty role to the custom job role. Transaction Analysis Duty roles
are located in the obi application in Authorization Policy Manager.
For example, if you want your custom job role to have access to the subject areas that are secured by the Sales
Transaction Analysis Duty role, search for this duty role in the obi application, then assign it to the custom job role.
6. Run the Retrieve Latest LDAP Changes process. This process makes your custom role available in Oracle Sales
Cloud.
Note
Most changes you make to the standard security settings using Authorization Policy Manager take
immediate effect and can be viewed after you return to the Authorization Management Home page.
Changes to the role hierarchy can, however, take up to 20 minutes to take effect.
Modifying Business Intelligence Role Assignments

The Business Intelligence roles enable users to perform tasks within Business Intelligence tools such as Oracle Business
Intelligence Publisher. The default Business Intelligence roles used in Oracle Sales Cloud are BI Consumer and BI Author.
The delivered OTBI Transaction Analysis Duty roles inherit the BI Consumer role, which provides view-only access to analyses
and reports. You assign the BI Author role at the job role level, giving you flexibility in granting the BI Author privilege to only
those job roles that you want to have access to create and edit analyses and reports.
All predefined Sales Cloud job roles that inherit an OTBI Transaction Analysis Duty role are also assigned the BI Author Role
by default, except for the Sales Representative job role. However, you can optionally remove or add the BI Author role from a
job role if required.
How can I customize Oracle Transactional Business

Intelligence duty roles?
If you are using Oracle Sales Cloud, you can't customize the delivered OTBI duty roles or the associated security privileges.
You can customize Oracle Transactional Business Intelligence reporting security by assigning different OTBI duty roles to a
job role according to your needs.
79
80
Creating Analytics and Reports Scheduling, Printing, and Sharing Your Reports
8 Scheduling, Printing, and Sharing Your Reports
Printing and Sharing Reports: Overview

Oracle Sales Cloud data analysis sometimes requires reports that are highly formatted. For example, you may need to share
or print a report that displays opportunities and their open revenue, with additional information about sales stages, customers,
products, and so on.
Printing Reports and Analytics

You can print most reports in either PDF or HTML format. The PDF version provides a report you can download and save to
your hard drive. The HTML version displays in your web browser.
Sharing Reports and Analytics

Reports and analytics can be shared in the following ways.
Method or Tool Description
Export and share You can export reports and analytics in a variety of
formats, such as Microsoft Excel or PowerPoint,
PDF, .csv, and web archive. After you've exported and
saved the reports to your hard drive, you can easily
attach them to an e-mail or upload to a web site.

Briefing books A briefing book is a collection of analyses or dashboard

pages (which can contain reports). The static snapshots
give you a picture of what's going on at the time that
the analysis or dashboard page is added to the briefing
book. You can create new briefing books and update
existing ones.

Agent An agent is an action that you set up to deliver a

scheduled report or analysis and then define who
receives it and the delivery method for it.

Note
Your access to these options for sharing analytics and reports depend upon your permissions within the
application.
81
Scheduling Analytics and Briefing Books: Procedure

Analytics and briefing books can run based on a schedule that you define. You can set up other automated tasks, for
example, to deliver results to specific recipients or send notifications.
You create what's called an agent to set this all up for an analysis, dashboard, or briefing book. The agent itself is saved as
an object in the business intelligence (BI) catalog.
Creating an Agent
Use the following procedure to create an agent.
2. Click the Browse Catalog icon.
3. Click the Create icon then click Agent under the Actionable Intelligence category.
4. Define criteria for the agent using the appropriate tabs, including the Delivery Content tab to specify the analysis,
dashboard, or briefing book to run.
5. Save the agent in My Folders.
Note
To edit an agent, repeat steps 1 and 2 and find the agent in the BI catalog.
Scheduling Snapshots of Your Sales Historical

Pipeline
Use the Generates Sales Historical Snapshots scheduling process to get daily snapshots of your sales pipeline delivered
right to your desktop doorstep. The feature helps you stay informed on your pipeline opportunity and revenue trends over
time, so you can keep a close eye on your bottom line at all times.
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".
Configuring 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 immediately as a
one time thing, set it up to run daily, weekly, monthly, yearly, or on a custom timeframe. You can also customize the number
of days after which opportunities have been closed to continue to snapshot the opportunity and its corresponding revenue
information.
To configure your Sales Historical Snapshots scheduled process:
1. Go 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.
82
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= create snapshots for closed opportunities closed within the last C days. This value must be greater than zero.
D= number of days to retain daily snapshots. This value must be greater than zero.
W= number of weeks to retain weekly snapshots if the enterprise calendar is a week based calendar.
M= number of months to retain monthly snapshots if the enterprise calendar is a month based calendar
Q= number of quarters to retain a quarterly snapshot
This figure shows the configurations for scheduling sales historical snapshots.
Note
An upper limit of 10M snapshot records (opportunity and revenue records combined) will be supported
and once the record limit is reached, the snapshot process will start to automatically purge 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. It is a pre-
requisite to setup the enterprise calendar before this feature can be used.
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. Choose the Schedule New Process tab.
83
This figure shows the Schedule New Process option from the Scheduled Process window.
3. If you havent 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. Choose the dropdown
option to view all of the choices. At the bottom there is a Search option. Choose 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.
4. In the Process Detail dialog click the Advanced tab.
Here you are going to set when you want your process to run, i.e., daily, weekly, monthly, etc. You will also set the
start and end date.
84
This figure shows the scheduling options for your 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 throws 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.
Scheduling Reports: Procedure

Reports can run based on a schedule that you define. You can set up other automated tasks, for example to deliver results to
specific recipients or send notifications.
You submit a report with the schedule and criteria for other automated tasks defined. Some reports are set up as scheduled
processes, in which case you submit the process as you would any scheduled process.
Submitting a Report as a Scheduled Process

Use the following procedure to schedule a report.
1. Open the Reports and Analytics pane in any work area where the report is available.
2. Navigate to the report within the folders.
3. Click the name of your report.
4. Open the More link to navigate to the business intelligence (BI) catalog.
5. In the More popup menu, click Schedule to set the report up as a scheduled process.
6. In the Agent window, define criteria for the agent using the appropriate tabs, including entering a schedule.
85
Note
For reports set up as scheduled processes, you can also:
Schedule them from any work area where there's a link to the report.
Use the Navigator to open the Scheduled Processes work area, where you can submit all processes that you
have access to.
You can also schedule reports from the Reports and Analytics work area that you access using the Navigator.
Setting Reports Up to Run as Scheduled Processes:

Points to Consider
You can create a job definition for predefined or custom reports so that users can run them as scheduled processes.
Otherwise, users can open reports (which are set up to be run online) through the Reports and Analytics pane, or open and
schedule them from the Oracle BI Presentation Catalog.
Use the Define Custom Enterprise Scheduler Jobs task in the Setup and Maintenance work area to create job definitions.
General Job Definition Information

This table describes the general information to enter for your job definition.
Field What You Enter
Job Type BIPJobType

Report ID The path to the report in the catalog, starting with the
folder beneath Shared Folders, for example: Custom/
<Family Name>/ <Product Name>/<Report File
Name>.xdo.

Tip
Make sure to include the .xdo extension for
the report definition.

Default Output A default output format.

Parameters
You can define parameters to be available to users when they submit scheduled processes based on your job definition.
When users run the scheduled process, the values they enter for the parameters:
Are passed to the data model that the report is using.
86
Determine the data to be included in the report.
The parameters that you define must be in the same order as parameters in the data model.
For example, the data model has parameters in this order:
P_START_DATE
P_END_DATE
P_CURRENCY
You create parameters as follows:
Start Date
End Date
Currency
Note
Because you define parameters using the list of values sources from the Define Custom Enterprise Scheduler
Jobs task, you do not define lists of values in the data model.
User Property
The only user property you need to define is EXT_PortletContainerWebModule. Only lists of values associated with the
application that you select are made available for parameters in this job definition.
Setting Up Reports for Scheduling in the Reports and

Analytics Pane: Procedure
You can set up reports as scheduled processes, which means users can submit them from the Scheduled Processes and
other work areas. If you want users to also submit these scheduled processes from the Reports and Analytics pane, then you
must configure properties for the corresponding reports.
Enabling a Report for Scheduling

To enable scheduling in the Reports and Analytics pane:
1. Select the report in the Oracle BI Presentation Catalog and click Edit.
2. Click Properties.
3. On the General tab in the Properties dialog box, enter the following fields:
Field Value
Enterprise Scheduler Job Package Name The path for the job definition, for example: / oracle/
apps/ ess/<product family>/ <product>/ <business
area>/ Jobs
87
Field Value

Enterprise Scheduler Job Definition Name The job definition name (not the display name), for
example: ABCDEFG

88
Oracle Sales Cloud Glossary
Glossary
analysis
A selection of data displayed in one or more views, such as a table or chart, to provide answers to business questions.
analytics
Business intelligence objects such as analyses and dashboards that provide meaningful data to help with decision making.
business intelligence repository

The metadata that determines all of the columns, or pieces of data, that you can include in analytics. You can also use the
repository as a source of data for reports.
dashboard
A collection of analyses and other content, presented on one or more pages to help users achieve specific business goals.
Each page is a separate tab within the dashboard.
data model
The metadata that determines where data for a report comes from and how that data is retrieved.
EDI
Abbreviation for electronic data interchange.
EFT
Acronym for Electronic Funds Transfer. A direct transfer of money from one account to another, such as an electronic
payment of an amount owed a supplier by transferring money from a payer's disbursement bank account into the supplier's
bank account.
job definition
The metadata that determines what a job does and what options are available to users when they submit the scheduled
process. A job is the executable for a scheduled process.
job role
A role, such as an accounts payable manager or application implementation consultant, that usually identifies and aggregates
the duties or responsibilities that make up the job.
89
Oracle Sales Cloud Glossary
report
An output of select data in a predefined format that's optimized for printing.
scheduled process
A program that you run to process data and, in some cases, generate output as a report.
subject area
A set of columns, or pieces of data, related to a specific business object or area.
view
A specific way to present the results of an analysis, for example as a table or graph. Other types of views, such as the title
view, show other components of the analysis.
work area
A set of pages containing the tasks, searches, and other content you need to accomplish a business goal.
90

Oracle Sales Cloud Creating Analytics and Reports

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Oracle Sales Cloud Creating Analytics and Reports

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle

Part Number E61241-02

Copyright 2011-2015, Oracle and/or its affiliates. All rights reserved.

Author: Penny Anderson

3 Building Analytics with Business Intelligence 9

4 Creating Analytics as Reports 45

5 Reporting in Multiple Currencies 63

7 Keeping Your Analytics Secure 71

8 Scheduling, Printing, and Sharing Your Reports 81

Oracle Applications Help

You can also access Oracle Applications Help at https://fusionhelp.oracle.com/.

Oracle Applications Guides

Oracle Help Center at http://docs.oracle.com/

Other Information Sources

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs (if you are hearing impaired).

Oracle Enterprise Repository for Oracle Fusion Applications

Comments and Suggestions

Send e-mail to: oracle_fusion_applications_help_ww_grp@oracle.com.

About This Guide

Related Documents and Training

Oracle Sales Cloud - Getting Started with Analytics and Reports

Oracle Sales Cloud - Using Analytics and Reports

Oracle Cloud - Administering Transactional Analyses

Oracle Sales Cloud - Subject Area Documents

The Essentials of Creating Analytics

Saving Analytics and Reports: Points to Consider

Analytics and Reports Terms: Explained

agent An object that defines how analyses, dashboards,

analysis A graph or table displaying select data to provide

analytics Business intelligence (BI) objects such as analyses and

business intelligence object Any item in the BI catalog, including analyses,

dashboard A collection of analyses and other content, presented

layout The report component that determines what the report

prompt A parameter that you set when you use analytics,

report An output of select data in a predefined format that is

style template An RTF template containing style information that is

subject area A set of columns, or pieces of data, related to a specific

subtemplate A piece of formatting that is defined once and used

view A specific way to present the results of an analysis, for

Oracle Business Intelligence Architecture

3 Building Analytics with Business Intelligence

Column A - Sales Subject Areas Column B - Territory, Partner, Marketing Subject

Sales - CRM Account Relationship Territory Management - CRM Leads

Sales - CRM Activity Contact Territory Management - CRM Quota

Sales - CRM Activity Objective Territory Management - CRM Forecast

Sales - CRM Activity Resource Territory Management - CRM Pipeline

Column A - Sales Subject Areas Column B - Territory, Partner, Marketing Subject

Sales - CRM Deal Registration Partners - CRM Partner Contact

Sales - CRM Forecasting Partners - CRM Partners Programs

Sales - CRM Historical Forecasting Partners - CRM Partner Territory

Sales - CRM Lead Territory Marketing - CRM B2B Customers

Column A - Sales Subject Areas Column B - Territory, Partner, Marketing Subject

Sales - CRM Opportunity Territory Marketing - CRM Leads

Sales - CRM Partner Relationship Marketing - CRM Leads Real Time

Sales - CRM Quota Management

Sales - CRM Resource Territory

Sales - CRM Sales Account Resource

Sales CRM Territory Resource

Sales CRM Sales Activity

Working with Subject Areas

Are my sales reps moving their opportunities fast enough?

Working with Custom Subject Areas

Creating and Editing Custom Subject Areas: Explained

Creating a Custom Subject Area