Oracle - Cloud R 11.1.11 - Administering Transactional Analyses (E68922-01) (OATBI)

Oracle Cloud
Administering Transactional Analyses

Release 11.1.11
E68922-01
January 2016
This guide describes administrative procedures and topics for
reports and analytics.
Oracle Cloud Administering Transactional Analyses, Release 11.1.11

E68922-01
Copyright 2015, 2016, Oracle and/or its affiliates. All rights reserved.
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, then 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 agencyspecific 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 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 about 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 unless
otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface ............................................................................................................................................................... vii
Audience ......................................................................................................................................................
vii
Related Documents.....................................................................................................................................
vii
Conventions.................................................................................................................................................
vii
Introduction
Reports and Analytics in Oracle Fusion Applications ........................................................................
1-1
Tools for Administering Reports and Analytics ..................................................................................
1-2
The Catalog: Where You Maintain Your Reports and Analytics.......................................................
1-2
Identifying Objects in the Catalog .................................................................................................
1-3
Functional Setup Tasks for Transactional Business Intelligence

Displaying Tasks in the Functional Setup Manager............................................................................
2-1
Completing Required Tasks in the Functional Setup Manager .........................................................
2-1
Assigning Security Profiles to Job Roles................................................................................................
2-2
Configuring Flexfields for Business Intelligence

Configuring Key Flexfields for Transactional Business Intelligence ................................................
3-1
Enabling Key Flexfields for Business Intelligence Reporting ....................................................
3-1
Mapping Non-Qualified Segments to BI Objects ........................................................................
3-3
Identifying Supported Key Flexfields ...........................................................................................
3-4
Setting up the GL Accounting Flexfields ..............................................................................................
3-4
Understanding Accounting Key Flexfields ..................................................................................
3-5
Identifying Accounting Key Flexfield Segments .........................................................................
3-5
Assigning Unique Segment Labels ................................................................................................
3-6
Performing Column Flattening ......................................................................................................
3-7
Designating GL Accounting Segment Instances as BI-Enabled ................................................
3-7
Deploying Accounting Key Flexfields ..........................................................................................
3-8
Configuring Descriptive Flexfields for Transactional Business Intelligence ...................................
3-9
Configuring Descriptive Flexfield Segments ...............................................................................
3-9
Designating Descriptive Flexfields as BI-Enabled..................................................................... 3-10

Configuring Extensible Flexfields for HCM ....................................................................................... 3-11
iii
Designating Extensible Flexfields as BI-Enabled....................................................................... 3-15

Essbase Rule File and Cubes ................................................................................................................. 3-16
Importing Changes to Flexfields Automatically ................................................................................ 3-18
Overview of Importing Flexfield Changes ................................................................................. 3-18
Running the Import Job................................................................................................................. 3-18
Disabling Flexfields as BI-Enabled....................................................................................................... 3-20
Disabling Key Flexfields as BI-Enabled ...................................................................................... 3-20
Disabling Descriptive Flexfields as BI-Enabled ......................................................................... 3-21
Disabling Extensible Flexfields as BI-Enabled ........................................................................... 3-22
Managing Reports and Analytics

Managing Catalog Folders ......................................................................................................................
4-1
Creating Folders ...............................................................................................................................
4-1
Setting Folder Properties.................................................................................................................
4-2
Mapping Reports to Work Areas ...........................................................................................................
4-3
Moving Reports and Analytics ...............................................................................................................
4-5
Unarchiving a File in a New Location...........................................................................................
4-7
About Warehouse Column Errors in Transactional Analyses ...........................................................
4-8
Setting Default Currency Formatting for Columns .............................................................................
4-8
Securing Reports and Analytics

Security Levels in Reports and Analytics..............................................................................................
5-1
About Object-Level Security...........................................................................................................
5-1
About Roles in Reports and Analytics...................................................................................................
5-2
About Security Configuration Tools in Reports and Analytics .........................................................
5-3
Using Oracle Identity Management to Manage Users and Enterprise Roles ..........................
5-3
Using Oracle Authorization Policy Manager to Configure Roles and Privileges...................
5-3
Using the Oracle BI Administration Page to Configure Duty Role Privileges........................
5-4
Securing Analytics ....................................................................................................................................
5-8
Creating Users and Assigning Them to Job Roles.......................................................................
5-8
Assigning Enterprise Roles (or Job Roles) to Duty Roles ...........................................................
5-8
Creating Duty Roles.........................................................................................................................
5-9
Assigning Duty Role Privileges to Catalog Objects .................................................................. 5-10

Securing BI Publisher Reports and Related Components ................................................................ 5-10
Setting Catalog Permissions ......................................................................................................... 5-11
Granting Permissions to the Oracle Enterprise Scheduler Job Definition ............................. 5-14
iv
Managing Business Intelligence Publisher Reports

Managing Report Delivery Servers........................................................................................................
6-1
Navigating to the Oracle BI Publisher Administration Page .............................................................
6-2
Configuring Report Delivery Servers ....................................................................................................
6-2
Understanding the Report and Delivery Processors ...........................................................................
6-3
Managing Report Processing and Delivery Server Load....................................................................
6-4
Diagnosing Report Processing Issues ....................................................................................................
6-5
Configuring System Properties for Reporting......................................................................................
6-5
Supported Descriptive Flexfields
vi
Preface
Administering Transactional Analyses explains how to administer Oracle Transactional
Business Intelligence, a real-time, self-service analysis and reporting solution offered
to Oracle Fusion application users to create ad hoc analyses and analyze them for daily
decision-making.
Audience
Administering Transactional Analyses is intended for Administrators who are
responsible for configuring and maintaining Oracle Transactional Business
Intelligence.
Related Documents
Additional resources are available for more information.
See these Oracle resources:
Oracle Public Cloud
http://cloud.oracle.com
Getting Started with Oracle Cloud
Conventions
These text conventions are used in this document.
Convention
Meaning
boldface
Boldface type indicates graphical user interface elements

associated with an action, or terms defined in text or the
glossary.
italic
Italic type indicates book titles, emphasis, or placeholder

variables for which you supply particular values.
monospace
Monospace type indicates commands within a paragraph, URLs,

code in examples, text that appears on the screen, or text that you
enter.
vii
1
Introduction
Oracle Transactional Business Intelligence is a real-time, self-service analysis and
reporting solution offered to Oracle Fusion application users to create ad hoc analyses
and analyze them for daily decision-making.
Topics:
Reports and Analytics in Oracle Fusion Applications
Tools for Administering Reports and Analytics
The Catalog: Where You Maintain Your Reports and Analytics
Identifying Objects in the Catalog
Reports and Analytics in Oracle Fusion Applications

Oracle Business Intelligence provides analyses and dashboards that report on realtime Fusion transactional data and historical data using different Oracle BI
technologies.
Reports and analytics in Oracle Fusion Applications are built using Oracle Business
Intelligence tools and technologies. When you installed and configured Oracle Fusion
Applications you installed the Oracle Business Intelligence components to enable the
reporting and analytical features of your applications.
Oracle Fusion applications provide different report types to satisfy different reporting
requirements. Oracle Business Intelligence provides several tools to meet the various
reporting requirements in Oracle Fusion Applications.
Analytics (analyses or analytical reports) are visualizations (such as charts and tables)
of a specific set of data. An analysis can be embedded into an application page, or
included as a component of a dashboard. Analyses are generally interactive and
provide ad hoc analysis capabilities to enable the user to customize the presentation of
the data in real-time.
Dashboards are a collection of analyses grouped together to return data. Some
examples include:
Absence and Accrual dashboard in Oracle Human Capital Management
Employee Expenses dashboard in Oracle Fusion Financials
Project Management dashboard in Oracle Project Portfolio Management
The analyses and dashboards embedded in your applications can report on real-time
transactional data or on historical data. Reports based on real-time data use Oracle
Transactional Business Intelligence.
Introduction 1-1
Oracle Transactional Business Intelligence reports are constructed queries and reports
executed in real-time against the transactional schema supported by a layer of view
objects. These are configured and deployed during provisioning.
Operational reports are static reports that meet operational and statutory reporting
requirements. Operational reporting includes the generation of high-volume business
documents such as payroll and invoices. Oracle Business Intelligence Publisher is the
tool that provides this functionality within Oracle Fusion Applications. Many reports
are delivered with your applications. Examples include:
Total Compensation Statement Report (Human Capital Management)
Purchase Agreement Report (Procurement/Purchasing)
Journals Check Report (Financials/General Ledger)

Oracle Business Intelligence includes several components, each providing specific
functionality that enables you to modify and administer your Oracle Fusion
Applications reports and analytics.
These components support modification and administration of your reports and
analytics:
The Oracle BI Presentation Services Catalog is where you interact directly with
your Oracle Fusion Applications reports and analyses. Use this interface to manage
permissions, properties, and organization of your reporting components.
Use the Oracle Business Intelligence Publisher administration pages to configure
settings specific to the running and scheduling of BI Publisher reports, such as
setting up your delivery servers, managing scheduler work load, and setting runtime properties for reports.

Reports, analyses, and dashboards used in Oracle Fusion applications pages are stored
in the catalog, which you navigate to administer these objects.
The catalog stores the applications content in a directory structure of individual files.
To administer reports in Oracle Fusion applications you must understand how to
navigate and identify object in the catalog.
To navigate the catalog:
1. On the Navigator, under Tools, click Reports and Analytics.
2. In the Reports and Analytics pane, click Browse Catalog.
1-2 Administering Transactional Analyses
You are redirected to the catalog within Oracle Business Intelligence.
Identifying Objects in the Catalog

Oracle Fusion Applications reporting objects are organized by product family in the
catalog.
Reporting objects are organized as follows:
Top Level: Shared Folders
Product Family Folder (example: Financials)
Product folder (example: Payables)
--Report group folders (example: Invoices)
-- Dashboard Report Folders
-- Data Models folder
- Report Components folders
- BI Publisher Reports
Introduction 1-3
The following table describes the common reporting components that you find in the
catalog:
Catalog Object
Description
Analysis
Located in the Report Components folder.
Analyses are used primarily by dashboards.
Dashboard folder
Located in the reporting group folder
Dashboard Prompt
Located in the Prompts folder
Used in dashboards
Filter
Located in Prompts folder
Used in dashboards and analyses
Report (Operational report created by Business Intelligence

Publisher)
Catalog Object
Description
Data Model
Located in the Data Models folder
Used by reports created with Business Intelligence Publisher
Subtemplate
Used by reports created with Business Intelligence Publisher
Introduction 1-5
2
Functional Setup Tasks for Transactional
Business Intelligence
Some configuration tasks may be required after you install Oracle Fusion
Applications.
Topics:
Displaying Tasks in the Functional Setup Manager
Completing Required Tasks in the Functional Setup Manager
Assigning Security Profiles to Job Roles
Displaying Tasks in the Functional Setup Manager

After you install Oracle Fusion Applications, go to the Setup and Maintenance page to
view tasks for Oracle Transactional Business Intelligence.
To view the tasks in the Setup and Maintenance page:
1. Click the Navigator and from the Tools menu, select Setup and Maintenance.
2. In the Setup and Maintenance page, search for Transactional Business
Intelligence.
Completing Required Tasks in the Functional Setup Manager

Some of the required Functional Setup Manager tasks for Transactional Business
Intelligence are automatically performed and require no further action.
The following tasks are automated during provisioning. No further action is required
to configure your system:
Optimization is automated during the provisioning process. No further action is
required to configure the system.
Manage Transactional Business Intelligence Connections.
Functional Setup Tasks for Transactional Business Intelligence 2-1
Connections are set up as part of the provisioning process. No Further action is

required to configure the system.
Manage Security for Transactional Business Intelligence.
To change the default security configuration, see Securing BI Publisher Reports and
Related Components.
Configure Key Flexfields for Transactional Business Intelligence.
See Configuring Key Flexfields for Transactional Business Intelligence.
Configure Descriptive Flexfields for Transactional Business Intelligence.
See Configuring Descriptive Flexfields for Transactional Business Intelligence.

Default security is configured automatically.
To make changes to the default security configuration, see Securing Reports and
Analytics.
Users of Transactional Business Intelligence must access some person data to
successfully run certain reports. To provide this access, assign a predefined security
profile to the relevant job or abstract roles. Use the Oracle Human Capital
Management setup task Manage Data Role and Security Profiles in the Setup and
Maintenance work area. For more information, see Oracle Human Capital Management
Cloud Securing Oracle HCM Cloud.
The following example shows how to assign a security profile to a job or abstract role
to enable users with that role to access person data. This task is required for users of
Transactional Business Intelligence who do not also use Oracle Human Capital
Management (HCM).
Prerequisite: You must have the IT Security Manager role.
1. Select Navigator.
2. Under Tools, select Setup and Maintenance.
3. On the Overview page, search for the task Manage Data Role and Security
Profiles.
4. Search for the job or abstract role.
5. Assign the relevant security profile to the job or abstract role.
6. On the Manage HCM Data Roles page, enter the job name (for example,
Warehouse Manager) in the Role field and click Search.
7. In the search results, select the job role (for example, Warehouse Manager) and
click Edit.
8. On the Edit Data Role: Role Details page, click Next.

9. In the Person Security Profile field on the Edit Data Role: Security Criteria page,
select the security profile View All Workers.
10. Click Review.

11. On the Edit Data Role: Review page, click Submit.
Upon completion of this task, Oracle Fusion Data Security is updated automatically
for roles being used to access Transactional Business Intelligence.
The following table identifies, by Oracle Fusion product, the roles that access person
data and the predefined security profile that you assign to each role.
Product
Job or Abstract Role
Security Profile
Assets
Asset Accountant
View All Workers
Assets
Accounting Manager
View All Workers
Enterprise Planning and

Budgeting
Budget Analyst
View All Workers
Enterprise Planning and

Budgeting
Budget Manager
View All Workers
Financial Consolidation Hub
Consolidation Accountant
View All Workers
Financial Consolidation Hub
Consolidation Manager
View All Workers
Financials Common Module
Intercompany Accountant
View All Workers
General Ledger
Financial Analyst
View All Workers
General Ledger
General Accountant
View All Workers
General Ledger
General Accounting Manager
View All Workers
Incentive Compensation
Incentive Compensation
Participant Manager
View Manager Hierarchy
Inventory Management
Warehouse Manager
View All Workers
Project Foundation
Project Accountant
View All Workers
Project Foundation
Project Administrator
View All Workers
Project Foundation
Project Billing Specialist
View All Workers
Purchasing
Buyer
View All Workers
Sourcing
Category Manager
View All Workers
Sourcing
Sourcing Project Collaborator
View All Workers
For example, as part of their Transactional Business Intelligence setup:

Oracle Assets implementers must assign the predefined security profile View All
Workers to the Asset Accountant and Asset Accounting Manager job roles.
Oracle Incentive Compensation implementers must assign the predefined security
profile View Manager Hierarchy to the Incentive Compensation Participant
Manager abstract role.
Functional Setup Tasks for Transactional Business Intelligence 2-3
Note:
The security profiles that Oracle Human Capital Management roles use to
access Transactional Business Intelligence are assigned during the setup of
Oracle Human Capital Management data security. No additional setup is
required for Transactional Business Intelligence purposes.
3
Configuring Flexfields for Business
Intelligence
To include flexfields in Transactional Business Intelligence reporting, you must enable
them and import them into Oracle Business Intelligence.
Topics:
Configuring Key Flexfields for Transactional Business Intelligence
Setting up the GL Accounting Flexfields
Configuring Descriptive Flexfields for Transactional Business Intelligence
Configuring Extensible Flexfields for HCM
Essbase Rule File and Cubes
Importing Changes to Flexfields Automatically
Disabling Flexfields as BI-Enabled

To include flexfields in your Transactional Business Intelligence reporting, you must
enable them for Business Intelligence. Extensibility of analysis using flexfields is used
for Enterprise Resource Planning and Human Capital Management. For Customer
Relationship Management, the Extensibility Framework supports this.
Topics:
Enabling Key Flexfields for Business Intelligence Reporting
Mapping Non-Qualified Segments to BI Objects
Identifying Supported Key Flexfields
Enabling Key Flexfields for Business Intelligence Reporting

Designate key flexfields as BI-enabled so you can include them in your BI reports.
To designate key flexfields as BI-enabled:
1. Navigate to Manage Key Flexfields in Oracle Fusion Applications.
2. Enter your search value in Key Flexfield Code.
3. Click Manage Structure Instances.
Configuring Flexfields for Business Intelligence 3-1
4. Enter your search value in Structure Instance Code.

5. Click Edit to display the Edit Key Flexfield Structure Instance dialog box.
6. Select the BI Enabled option. then click OK

7. For each flexfield segment instance, repeat steps 5 through 6.
8. Click Save.
9. Populate the BI Object Name for each of the segment labels:
a. Query the Key Flexfield Code in the Manage Key Flexfields window.
b. From the Actions menu, select Manage Segment Labels.
c. Populate the BI Object Name for each segment label to be mapped.
The BI Object Name for the following qualified segment labels should not be
modified:
Segment Label Code
BI Object Name
FA_COST_CTR
Dim - Cost Center
GL_BALANCING
Dim - Balancing Segment
Segment Label Code
BI Object Name
GL_ACCOUNT
Dim - Natural Account Segment
Note:
Before you deploy a flexfield, you must access the Chart of Accounts Instance
and assign the newly created segment label to the appropriate segment in the
Chart of Accounts. For more information, see Assigning Unique Segment
Labels.
d. Click Deploy Flexfield.
e. Click Save and Close.
Mapping Non-Qualified Segments to BI Objects

Some non-qualified segments must be mapped and used in Oracle Transactional
Business Intelligence.
For non-qualified segments that need to be mapped and used in Oracle Transactional
Business Intelligence, create a new label and associate a BI object with the label.
Associate this new segment label with the segment code.
To map non-qualified segments to BI Objects:
1. From Manage Key Flexfields, search for the appropriate key flexfield code.
2. From the Actions menu, select Manage Segment Labels.
3. Click the Add Row icon (green plus sign).
4. Enter the details for the Segment Label Code, including name, description, and BI
Object name.
Key Flexfield
BI Object Name
Accounting (GL)
Dim - GL Segment1 through Dim - GL Segment10
Budgetary Control (XCC)
Dim - XCC Segment1 through Dim - XCC Segment10
Revenue Management (VRM)
Dim - VRM Segment 1 through Dim - VRM Segment 10
Note:
Enter the BI Object names carefully and note whether there is a space between
"Segment" and the number.
5. Complete the mapping by Assigning Unique Segment Labels to the key flexfields.
Identifying Supported Key Flexfields

Key flexfields are used to store internally defined codes unique to a particular
business, specifying part numbers, general ledger accounts, and other business
entities.
Supported Descriptive Flexfields provides a list of supported key flexfields and their
corresponding key flexfield dimensions.
Product Area
Key Flexfield
Dimension
Fixed Assets
Category (CAT#)
Dim - Asset Category
Fixed Assets
Location (LOC#)
Dim - Asset Location
General Ledger
Accounting (GL#)
Dim - Balancing Segment

Dim - Cost Center
Dim - Natural Account
Payroll
Costing
Dim - Costing Segments
Supply Chain
Management
Locator
Dim - Inventory Org
Supply Chain
Management
Item Category
Dim - Item
Revenue
Management
Pricing Dimensions
(VRM)
Dim - VRM Segment
Budgetary Control
Budgeting (XCC)
Dim - XCC Segment

This is the workflow for setting up Accounting key flexfields but these steps also
apply for other key flexfields.
Topics:
Understanding Accounting Key Flexfields
Identifying Accounting Key Flexfield Segments
Assigning Unique Segment Labels
Performing Column Flattening
Deploying Accounting Key Flexfields
Understanding Accounting Key Flexfields

The Accounting Key Flexfield is used to identify GL accounts.
A chart of accounts segment is a component of the Accounting Key Flexfield. Each
segment has a value set attached to it to provide formatting and validation of the set of
values used with that segment. The combination of segments creates the account
combination used for recording and analyzing financial transactions.
Note:
You must set up your Chart of Accounts (COA) as part of implementing

Oracle Fusion Applications or Oracle Fusion Accounting Hub.
Examples of segments that may be found in a chart of accounts structure include
Company, Cost Center, Department, Division, Region, Account, Product, Program,
and Location.
The Natural Account segment of the General Ledger Accounting Key Flexfield defines
the account used in the account combination to record transactions.
The logical segment dimensions in the Oracle BI metadata are Dim Cost Center,
Dim Balancing Segment, Dim Natural Account Segment and all Dim
GL Segmentn dimensions. These dimension tables are populated from a Tree value
object or from a Value Set value object depending on whether a tree was associated
with the segment in the Fusion Applications setup:
For each segment associated with trees, two value objects are generated (Tree and
TreeCode) with the following naming structure:
FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_segmentlabel_VI &
FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_segmentlabel_VI
For each segment without trees, one view object are generated with the following
naming structure:
FscmTopModelAM.AccountBIAM.FLEX_VS_ XXX_VI
In addition to the segment dimension tables, the BI Extension process also extends
Flex BI Flattened VO;
FscmTopModelAM.AccountBIAM.FLEX_BI_Account_VI. This view object has a
pair of columns for each segment; segmentlabel _ and segmentlabel _c.
For example, for your Cost Center segment which has the segment label
FA_COST_CTR, there are two columns in this view object, named FA_COST_CTR_ and
FA_COST_CTR_c.
Identifying Accounting Key Flexfield Segments

Identify and map segments of the chart of accounts.
For each Chart of Accounts (Accounting Key Flexfield) used to analyze Transactional
Business Intelligence facts, identify the segments of the chart of accounts and map
them to the Transactional Business Intelligence GL Accounting Segment logical
dimensions.
Accounting Key Flexfield Segment Label

Segment
Transactional Business
Intelligence GL Accounting
Segment Logical Dimension
Balancing
GL_BALANCING
Dim Balancing Segment
Natural Account
GL_ACCOUNT
Dim Natural Account Segment
Cost Center
FA_COST_CTR
Dim Cost Center
Other segments to be
equalized across the
charts of accounts
Other unique segment

label
Dim GL Segment n where n is an

integer from 1 to 10
Assigning Unique Segment Labels

You must assign a unique segment label to the charts of accounts segments that are the
balancing segments or the natural account segments, and that are used for specific
purposes.
For example, assign the Primary Balancing segment label to the segment used for your
company or legal entities in order to provide a correct recording of intercompany
transactions and company analysis. Other segment labels are optional and can be
assigned as needed.
To assign unique segment labels to charts of accounts segments:
1. Launch the Manage Charts of Accounts task and then navigate to the Manage
Chart of Accounts window.
2. In the Search section, enter the GL# for the Key Flexfield Code and then click the
Search button.
3. In the Search Results section, select Accounting Flexfield and then click the
Manage Structures button to navigate to Manage Key Flexfield Structures.
4. In the Search section, enter the chart of accounts code or the name for Structure
Code or Name, and then click the Search button.
5. In the Search Results section, select the chart of accounts and then click Edit to
navigate to the Edit Key Flexfield Structure window.
6. Select the Enabled check box to code-enable the Structure code.

7. In the Segments section, select the applicable segments and then click Edit to
navigate to the Edit Key Flexfield Segment window.
8. Select the Enabled check box to enable the segments.

9. In the Segment Labels section, select the unique segment labels to equalize the
segments across the charts of accounts, and then click the right arrow to move the
segments to the selected list.
10. Click Save and Close to return to the Edit Key Flexfield Structure window.
11. Click Done to return to the Manage Key Flexfields window.
Performing Column Flattening

Perform column flattening for the account hierarchies needed for analysis in Oracle
Column flattening of Trees is required in order for OTBI hierarchy analyses to be
populated with correct data.
To flatten columns for account hierarchies:
1. Launch Manage Trees and Tree Versions and navigate to the Manage Trees and
Tree Versions window.
2. In the Search section, enter GL_ACCT_FLEX for the Tree Structure Code and the
involved tree code or name, and click Search.
3. In the Search Results section, select the tree version you want to flatten.
If the status of the Tree Version is Draft, to make the Tree Version active, select
Actions, then Status, and then Active.
4. (Optional): After the tree version is specified, perform an audit on the Tree Version
to ensure its integrity before launching the flattening job.
Select Actions and then Audit. See the section on working with Trees in the Oracle
Fusion Application Developer's Guide.
5. Choose Column Flattening from the Actions drop-down menu.
6. Click the Online Flattening button to launch the flattening job immediately, or
click the Schedule Flattening button to schedule the flattening job according to
your requirements.
Designating GL Accounting Segment Instances as BI-Enabled

Specify the applicable chart of accounts segment instances that are BI-enabled to make
them available for use in Transactional Business Intelligence.
To specify the chart of accounts segment instances as BI-enabled:
1. In the Search Results section of the Manage Key Flexfields window, select
Accounting Flexfield, and then click the Manage Structure Instances button to
navigate to the Manage Key Flexfield Structure Instances window.
2. In the Search section, select the chart of accounts for Structure Name and click the
Search button.
3. In the Search Results section, select the structure instance and click Edit to
navigate to the Edit Key Flexfield Structure Instance window.
4. Check the Enabled check box to code-enable the structure instance.

5. In the Segment Instances section, select the segment instances and click Edit to
update.
Note:
Each segment instances must be selected individually.
6. Check the Business Intelligence enabled check box in the Edit Key Flexfield
Segment pop-up window and click OK to return to Edit Key Flexfield Structure
Instance window.
7. After you have enabled all applicable segment instances for Business Intelligence,
click Save and Close to save the changes and return to the Edit Key Flexfield
Structure Instance window.
8. Repeat steps 2 - 6 for each chart of accounts to enable all the applicable segment
instances for Business Intelligence.
9. Click Done to return to the Manage Key Flexfields window.

10. After you have configured all the charts of accounts, click the Deploy Flexfield
button to deploy Accounting Flexfield and make the latest definition available for
use.
Deploying Accounting Key Flexfields

After you have set up accounting key flexfields, you must deploy them.
Deployment Status
Accounting key flexfields have one of the following statuses:
Edited The flexfield definition has not been deployed or changes have been
made to the structure, the structure instances, or the value sets.
Patched The flexfield definition has been modified through a patch, but the
flexfield has not yet been deployed so the patched definition is not reflected.
Deployed to Sandbox The flexfield is deployed and available in a flexfieldenabled sandbox.
Deployed The flexfield definition is deployed and available to end users.
Error The deployment attempt failed.
To deploy accounting key flexfields:
1. Access Manage Chart of Accounts from Setup and Maintenance.
2. Click Search.
3. Use the horizontal scroll bar (if necessary) to find the column Deployment Status.
4. Click the icon under the heading.
5. Select Edited.
6. Click Deploy Flexfield.
7. Monitor the Deployment Status.
8. When 100% is reached in the deployment status, click OK.
9. Verify that a green check mark displays under the Deployment Status column.
10. Click Done.

Configure descriptive flexfields to track unique information not typically found on
business forms.
Descriptive flexfields capture details that are vital, yet would clutter a form if present.
For example, an asset form could become unwieldy if it contained many specific
details about the asset, yet the user still needs access to the details. Descriptive
flexfields provide a place to store these details.
Descriptive flexfields provide a way for you to add custom attributes to entities and to
define validation and display properties for them. A descriptive flexfield is a logical
grouping of attributes (segments) that are mapped to a set of extension columns which
are shipped as part of Oracle Fusion Applications tables.
Topics:
Configuring Descriptive Flexfield Segments
Designating Descriptive Flexfields as BI-Enabled
Configuring Descriptive Flexfield Segments

If a descriptive flexfield is enabled for Oracle Business Intelligence, you can enable
global and context segments for Oracle Business Intelligence, and you can select
segment labels. Not all descriptive flexfields are supported for Business Intelligence.
To configure available descriptive flexfield segments:
1. Navigate to the Setup and Maintenance window.
2. Navigate to the Manage Descriptive Flexfields window.
3. If the BI Enabled option is cleared, select it.
If the option is unavailable, the flexfield is a non-supported entity.

4. Select the options for deployment of the descriptive flexfields.
Designating Descriptive Flexfields as BI-Enabled

If a descriptive flexfield is already defined, you can enable it for use in Business
Intelligence reports. Not all descriptive flexfields are supported for Business
Intelligence.
To designate available descriptive flexfields as BI-enabled:
1. Access Oracle Fusion Applications.
2. Navigate to Setup and Maintenance.
3. Navigate to the Edit Descriptive Flexfields window.
4. Enter the Descriptive Flexfield Name.

5. Optional: Enter a Description.
6. Check the BI Enabled option on the desired descriptive flexfields.
If the option is unavailable, the flexfield is a non-supported entity.

7. Click OK.
8. Click Save.

You can use extensible flexfields to configure more segments.
An extensible flexfield is similar to a descriptive flexfield in that it provides a
customizable expansion space that an implementation team, such as Oracle Fusion
Applications customers, can use to configure additional attributes (segments) without
additional programming. As with descriptive flexfields, each segment is represented
in the database as a single column. However, with extensible flexfields, the context
values and context-sensitive segments are stored in an extension table.
Categories and Contexts
An implementation team can combine and arrange the segments into attribute groups
that are tailored to a customer's specific needs. For example, they can group related
segments so that they appear together on the page. The attribute groups are referred to
as contexts. You can optionally set up an extensible flexfield to enable implementation
team to group contexts into categories.
For more information, please refer to Using Extensible Flexfields" in Oracle Fusion
Applications Developer's Guide.
List of EFFs in HCM (CoreHR and Payroll)
EFF
Number of Categories
Number of Contexts
PER_JOBS_EIT_EFF
0 (none seeded)
PER_LOCATION_INFORMAT
ION_EFF
5 (none are multi-row context)
PER_POSITIONS_EIT_EFF
0 (none seeded)
PER_PERSON_EIT_EFF
9 (2 multi-row contexts)
PER_ASSIGNMENT_EIT_EFF
PAY_ELEMENT_INFORMATI
ON_EFF
PER_JOBS_LEG_EFF
PER_LOCATION_LEG_EFF
PER_POSITIONS_LEG_EFF
PER_ORGANIZATION_INFO
RMATION_EFF
Category - Department
4 (1 multi-row context)
Category - Enterprise
4 (no multi-row contexts)
EFF
Number of Categories
Number of Contexts
Category - Disability
Organization
Category - Division
Category - Legal Employer
Category - Professional
Body
Category - Payroll
Statutory Unit
76 (1 multi-row context)
Category - Reporting
Establishment
Category - Tax Reporting

Unit
You can add contexts and segments to EFFs just like the DFFs. To see the EFFs in OTBI
Answers, they need to be deployed and followed by a BI Extender Essbase job.
To configure extensible flexfields:
1. Launch the Manage Extensible Flexfield task.
2. Search for the EFF you want to configure, then highlight it and click the Edit icon.
3. In the Edit Extensible Flexfield dialog, highlight the category Display Name, then
select Manage Contexts.
4. In the Manage Context dialog, search for the context that contains the segment you
want to configure, highlight it, then click the Edit icon.
5. In the Edit Context dialog, click the Edit icon.
6. Edit the segment, as required, then click Save.
Designating Extensible Flexfields as BI-Enabled

Extensible flexfields are BI enabled if at least one segment in a context is BI enabled.
To designate extensible flexfields as BI-enabled:
3. Navigate to Manage Extensible Flexfields.
4. Enter the extensible flexfield Name; for example, "Organization Information EFF."
5. Select the applicable extensible flexfield, and then click Edit to navigate to Edit
Extensible Flexfield.
6. Select the applicable Category.
The category contexts are populated automatically.

7. Click Manage Contexts to navigate to Manage Contexts.
8. Select the applicable Context, and then click Edit to navigate to Edit Context.
9. Select the applicable Segment, and then click Edit to navigate to Edit Segment.
10. Check the BI Enabled check box displayed at the bottom of the screen.
11. Click Save.

Generate the Essbase rule file by running the Fusion Applications job Create Rules
XML File for BI Extender Automation.
The Essbase rule file must be generated for all Oracle Essbase cubes mapped in the
repository file (RPD).
To generate the ESSBASE rule:
1. In Fusion Applications, access the Scheduled Processes window:
2. Select Search and Select: Name.

3. Highlight Create Rules XML File for BI Extender Automation.
4. Click OK.
5. Schedule the job.
Job Status Conditions

The job status displays one of these conditions.
INIT: The job has just begun and is waiting for the extender command line JAR to
update the status with more details.
COMPLETED_NO_EXTENSION_NEEDED: No new Flex changes were detected in
any of the fusion sources; because the RPD is already synchronized with all FLEX
changes, no changes were made in the RPD.
COMPLETED: The RPD was successfully updated with Flex changes and uploaded
into the Oracle Business Intelligence server.
FAILED: Error conditions exist which require manual intervention.

You can automate the process for importing flexfield changes.
Topics:
Overview of Importing Flexfield Changes
Running the Import Job
Overview of Importing Flexfield Changes

You can use the Import Oracle Fusion Data Extensions for Transactional Business
Intelligence job to import your flexfield changes.
Use the Import Oracle Fusion Data Extensions for Transactional Business Intelligence
job to automatically import the following types of changes:
Key Flexfield changes
Descriptive Flexfield changes
Extensible Flexfield changes
The Import Oracle Fusion Data Extensions for Transactional Business Intelligence job
imports extensible data, including data in descriptive flexfield segments, key flexfield
segments, and General Ledger balances in Essbase cubes, into Transactional Business
Intelligence.
If you have changes to key flexfields and descriptive flexfields, you can import all the
changes in the same job.
The Import Oracle Fusion Data Extensions for Transactional Business Intelligence job
is an Oracle Fusion Applications job; it is not a BI Applications job. Detailed
information on this job can be found in Oracle Cloud Applications documentation.
Caution:
We strongly recommend that you backup the Oracle Business Intelligence

Enterprise Edition prior to importing any flexfield changes.
Running the Import Oracle Fusion Data Extensions for Transactional Business
Intelligence job disconnects all users from the server. You should not run this
job when maintenance operations or system updates are being performed on
the server.
Running the Import Job

Run the Import Oracle Fusion Data Extensions for Transactional Business Intelligence
job in Fusion Applications.
1. In Fusion Applications, access the Scheduled Processes window:
2. Select Search and Select: Name.

3. Highlight Import Oracle Fusion Data Extensions for Transactional Business
Intelligence.
4. Click OK.
5. Schedule the job.
Job Status Conditions

When the job is finished, the biExtenderCMDUtility.jar writes the status of the
job into the JNDI file ess_biExtenderEssJob_jobStatus, which can be viewed in
Oracle WebLogic Server.
The job status displays one of the following conditions:

INIT The job has just begun and is waiting for the extender command line JAR
to update the status with more details.
COMPLETED_NO_EXTENSION_NEEDED No new Flex changes were detected
in any of the fusion sources; because the Oracle Business Intelligence is already
synchronized with all FLEX changes, no changes were made in the Oracle Business
Intelligence.
COMPLETED Oracle Business Intelligence was successfully updated with Flex
changes and uploaded into the Oracle Business Intelligence server.
COMPLETED: PROCESS_ERRORS Oracle Business Intelligence was updated
with the Flex changes but with some warnings that require manual intervention.
FAILED Error conditions exist that require manual intervention.
Successful Import Job

If the Import Job is successful, you can perform the following actions:
Query subject areas by segment dimensions such as Balancing Segment and Cost
Center.
Access DFF attributes for analyses.
Use the General Ledger - Balances Real Time subject area to query Essbase cubes.

If you created a flexfield that you no longer want to use or report against, you can
disable the flexfield as BI-enabled.
There may be times (such as during development phases) when you try using a
flexfield and later determine it is no longer needed.
Note:
If you are considering disabling flexfields, keep in mind that any flexfields
created in Oracle Fusion Applications must be designated as BI-enabled to be
exposed in Transactional Business Intelligence. If you disable a flexfield, it
cannot be deployed. Also, error conditions may occur if you disable a
descriptive flexfield that has been implemented in BI Applications.
If error conditions arise from disabling flexfields as BI-enabled,
troubleshooting the errors can be difficult and time-consuming.
Topics:
Disabling Key Flexfields as BI-Enabled
Disabling Descriptive Flexfields as BI-Enabled
Disabling Extensible Flexfields as BI-Enabled
Disabling Key Flexfields as BI-Enabled

If you are considering disabling key flexfields, keep in mind that any flexfields created
in Oracle Fusion Applications must be designated as BI-enabled to be exposed in
To disable key flexfields as BI-enabled:
1. Navigate to Manage Key Flexfields in Oracle Fusion Applications.

2. Enter your search value in Key Flexfield Code.
3. Click Manage Structure Instances.
4. Enter your search value in Structure Instance Code.
5. Click Edit.
The Edit Key Flexfield Structure Instance dialog box displays.
6. In Edit Key Flexfield Segment Instance, deselect the BI Enabled option.

7. Click OK, then Save.
Disabling Descriptive Flexfields as BI-Enabled

If you are considering disabling descriptive flexfields, keep in mind that any flexfields
created in Oracle Fusion Applications must be designated as BI-enabled to be exposed
in Transactional Business Intelligence.
To disable descriptive flexfields as BI-enabled:
3. Navigate to the Edit Descriptive Flexfields window.
4. Enter the Descriptive Flexfield Name.

5. Deselect the BI Enabled option on the desired descriptive flexfields.
6. Click OK.
7. Click Save.
Disabling Extensible Flexfields as BI-Enabled

If you are considering disabling extensible flexfields, keep in mind that any flexfields
created in Oracle Fusion Applications must be designated as BI-enabled to be exposed
in Transactional Business Intelligence.
To disable extensible flexfields as BI-enabled:
2. Navigate to Setup and Maintenance, then Manage Extensible Flexfields.
3. Enter the extensible flexfield Name; for example, "Organization Information EFF."
4. Select the applicable extensible flexfield, and then and Edit to navigate to Edit
Extensible Flexfield.
5. Select the applicable Category.
The category contexts are populated automatically.

6. Click Manage Contexts to navigate to Manage Contexts.
7. Select the applicable Context and click Edit to navigate to Edit Context.
8. Select the applicable Segment and click Edit to navigate to Edit Segment.
9. Clear the BI Enabled option displayed at the bottom of the screen.

10. Click Save.
4
Managing Reports and Analytics
Administration tasks include managing the organization and availability of your
reports and analyses, understanding common issues, and setting default currencies for
appropriate subject area columns.
Topics:
Managing Catalog Folders
Mapping Reports to Work Areas
Moving Reports and Analytics
About Warehouse Column Errors in Transactional Analyses
Setting Default Currency Formatting for Subject Area Columns

The catalog is organized into folders that are either shared or personal.
Topics:
Creating Folders
Setting Folder Properties
Creating Folders
Create a folder to organize reports.
To create a folder:
1. In the catalog, navigate to the desired location of the new folder in the Folders
pane.
2. In the catalog toolbar, click New, and select Folder.

3. In the New Folder dialog, enter the folder name, and click OK.
Managing Reports and Analytics 4-1
Note:
"If you upgrade or patch Oracle Business Intelligence, and conflicts are
detected during those processes, the system creates backup_nnn folders in the
catalog. After reviewing and resolving any conflicts found in the backup_nnn
folders, Oracle recommends that you manually delete the folders from the
catalog.
You can contact Oracle support to request an automated removal if you have a
large number of folders to delete.
Setting Folder Properties

You can use folder properties to control folder permissions and attributes.
You can access the properties of any object or folder to perform tasks such as viewing
system information or changing ownership. All other users can only access and
modify the properties of the objects that they create or own.
To set folder properties:
1. In the catalog, select the folder to which you want to assign properties.
2. In the Tasks pane click Properties.
3. In the Properties dialog, select these field values:
Attributes
Hidden Specifies that the object is hidden.
System Specifies that the object is a system object.
Read Only Specifies that the object is read-only.
Do not Index Excludes the object from the index used by the full-text
catalog search. Excluded objects do not display in the results of any full-text
catalog search; the object can still be found using the basic catalog search.
Ownership
Use this area in the Properties dialog to take ownership of a folder or object in
the catalog. This area displays only if the proper privileges were assigned to the
user, group, or role. Note that the owner of an object or folder cannot
automatically access the object or folder.
Set Ownership of this item Click to become the owner of the folder.
Set Ownership of this item and all subitems Click to become the owner of
the folder and any sub folders or sub items contained within the item. For
example, if you click this link for a dashboard folder, then you take
ownership of all of the dashboard's components.

To display reports in the Reports and Analytics Pane for a specific user or role, you
map the reports to the work area to which the user or role is a member.
For a user to view or run the report, they must first have permissions set on the report
in the catalog. You can also restrict access to specific reports for specific users by
setting permissions on the reporting objects in the catalog. For more information, see
Securing BI Publisher Reports and Related Components.
Any mapping changes you make apply to all users with access to the mapped work
areas.
Oracle Business Intelligence Publisher reports must be registered as processes to be
submitted from the Reports and Analytics pane.
To map reporting objects to work areas:
1. Click Navigator and then select Setup and Maintenance.
2. In the Setup and Maintenance page, search for Map Reports to Work Areas.
3. In the Search Results table, click Go to Task.
4. Select an Application and a Work Area and click Search.
5. Click Select and Add.
6. Click All to navigate down the folder structure to find the reporting object you
wish to map to the work area.
7. Select the report and click Apply.

8. Click OK.
9. In the Map Reports to Work Areas task, click Save.

You can archive to bundle the entire catalog, specific folders, or multi-component
objects as a .catalog file and upload the .catalog file to unarchive the data to another
location in the catalog.
The archive process enables you to transfer specific data across environments. For
example, you can use this feature to transfer data from a development environment to
a production environment.
To create an archive file:
1. Locate the object in the catalog.
2. Select More and then select Archive.
3. In the Archive dialog, select one or more of the following options:
Keep Permissions Use this option to maintain the object or folder's existing
permissions. If you do not select this option, then the archiving process does not
include any permissions. Upon unarchiving, the system assigns the parent
folder's permissions to all of the objects and folders.
Keep Timestamps Use this option to maintain the CreationTime,
LastModified, and LastAccessed timestamps assigned to the object or folder.
Upon unarchiving, the LastModified timestamp is updated to indicate the time
at which the object or folder is unarchived. If you select this option, the Old
option in the Paste Overview area of the Preferences dialog is available when
unarchiving. You use the Old option to overwrite existing catalog items that are
older than the catalog items in the archive.
If you do not select this option, then the archiving process does not include
timestamp information and the Old option in the Paste Overview area of the
Preferences dialog is not available.
4. Click OK to download the archive file.
Unarchiving a File in a New Location

Select the folder in the catalog where you want to upload the archive file.
1. In the Tasks pane click Unarchive.
2. In the Unarchive dialog, select the following field values:
Archive File Browse for and select the archive file.

Replace Use to specify whether to replace existing folder or object with the
same name.
All Select this option to replace any existing folders or objects with the
same names as folders or objects included in the archive file that you are
uploading.
Old Select this option to replace folders or objects except those folders or
objects that exist, unless they are older than the source.
None Select this option to add any new folders or objects, but preserve
any existing folders or objects.
Force Select this option to add and replace all folders or objects.
ACL
Use to specify how the folders or objects are assigned permissions using Access
Control Lists (ACLs) when unarchived.
Inherit Inherits the folder or object's permissions (ACL) from its new
parent folder.
Preserve Preserves the folder or object's permissions (ACL) as it was in the
original, mapping accounts as necessary.
Create Preserves the folder or object's permissions (ACL) as it was in the
original, creating and mapping accounts as necessary.
3. Click OK.

In some OTBI analyses and dashboards, users may encounter errors on some columns
in their analyses in cases where non-transactional data sources are being queried.
Some subject areas and analyses in the OTBI catalog for offerings including Oracle
Customer Experience include analyses which query subject area columns which map
to data warehouse data, which is part of Oracle BI Applications and Oracle
Transactional Business Intelligence Enterprise (OTBI-E) and is used for historical
analysis. In cases where historical warehouse data is included in transactional
analyses, users may encounter errors on these columns if the warehouse is not set up
and configured.
In some cases, but not all, these conditions are managed by Business Intelligence
repository (RPD) metadata which supports switching from warehouse to transactional
sources using variables.
Setting Default Currency Formatting for Columns

You can set default currency formatting for subject area columns so that users do not
have to set currency formats each time they create a new analysis using them.
When creating analyses that use columns with currency amounts, in order to prefix
values with the correct currency symbols, for example $, set the data format on the
report column. To ensure that the formatting is automatically applied when using the
column in an analysis, set a default format.
To set default currency formatting for a subject area:
1. Log in to Oracle Business Intelligence with Administrator privileges.
2. Create an analysis with all of the relevant currency columns in any subject area.
a. Click New and select Analysis and select a subject area.
b. Select a subject area.
c. Explore the subject area and identify the columns that display currency, most of
which should be found in the Facts folder.
d. Add each identified currency column to the analysis.

3. Change the data format for each column from its default, which is usually Number,
to Custom.
a. Click the Properties icon for a column in your analysis and, in the Data Format
tab of the Column Properties dialog, select Override Default Data Format.
b. Select Custom in the Treat Numbers As drop-down.

c. Enter [$:currencyTagColumn= <<BI currency code column in the
subject area>>>>] in the Custom Numeric Format field.
d. Click Save as Default and, in the drop-down, select Save as the system-wide
default for <column>.
e. Click OK.
f. Repeat these steps for each column in the analysis.
4. Save the analysis in a development folder in the catalog and give it a descriptive
name so that its purpose is clear.
5. Run the analysis and, in the results, verify that amounts appear as currency, with
the expected prefix.
5
Securing Reports and Analytics
There are many tasks that you must perform to secure reports and analytics within
Oracle Fusion Applications.
Topics:
Security Levels in Reports and Analytics
About Roles in Reports and Analytics
About Security Configuration Tools in Reports and Analytics
Securing Analytics
Securing BI Publisher Reports and Related Components
Security Levels in Reports and Analytics

Security in reports and analytics are classified broadly into the following three levels,
user-level, object-level, and data-level.
The levels of security include:
User-level security (authentication of users) User-level security concerns the
authentication and confirmation of the identity of a user based on the credentials
provided, such as user name and password.
Object-level security Object-level security controls the visibility to business
logical objects based on a user's role. You can set up object-level security for Web
objects, such as dashboards and dashboard pages, which are defined in the catalog.
For more information, see About Object-Level Security.
Data-level security Data-level security controls the visibility of data (content
rendered in subject areas, dashboards, Oracle BI Answers, and so on) based on the
user's association to data in the transactional system.
About Object-Level Security

Object-level security is the specification of Duty Role permissions on catalog objects,
such as dashboard pages.
You secure these objects using Duty Roles and their associated policies and privileges.
Duty Roles are stored in the Fusion Policy Store, which is accessed by the catalog.
For information about default mappings for Duty Roles, Job Roles, and Data Roles, to
secure objects in the catalog, see Document 1333454.1 Oracle Business Intelligence
Applications Duty Role Assignments for Fusion Applications on My Oracle Support:
https://support.oracle.com.
Securing Reports and Analytics 5-1

Roles fall into two classes, application-wide roles (Duty Roles), and enterprise-wide
roles (Job Roles, Data Roles, and Abstract Roles).
Application-wide roles are defined in terms of the tasks that are needed to perform a
job, and are held in the policy store with associated reporting privileges.
Enterprise-wide roles are defined in terms of an occupation within an enterprise, and
are held in the identity store with associated users.
Note:
Oracle BI duty roles inherit the BI Consumer role by default and the BI Author
role is assigned at the Fusion job role level to select Fusion job roles.
For more information about Oracle Sales Cloud Abstract Roles, see Oracle Sales Cloud
Securing Oracle Sales Cloud.
For more information about Oracle Human Capital Management Cloud Abstract
Roles, see Oracle Human Capital Management Securing Oracle HCM Cloud.
Four common role types are used in reports and analytics.
Job Roles (enterprise-wide roles, also referred to as Fusion Applications
Enterprise Roles)
A Job Role represents the job definition of a person in your organization, for example,
AP manager, HR specialist. Users are assigned to Job Roles. A Job Role inherits one or
more Duty Roles, and therefore, users inherit Duty Roles through Job Roles. For
example, the Job Role AP_ACCOUNTS_PAYABLE_MANAGER_JOB might be
associated with the Duty Role RUN_ACCOUNTS_PAYABLE_REPORT_DUTY.
Duty Roles (application-wide roles, also referred to as Application Roles)
A Duty Role represents a specific task needed to do a job, and comprises the privileges
required to perform that job. For example, the Duty Role
RUN_ACCOUNTS_PAYABLE_REPORT_DUTY enables a user to run the Accounts
Payable report. The privileges assigned to a Duty Role are defined in application
policies within the policy store. For more information, see Using Oracle Authorization
Policy Manager to Configure Roles and Privileges.
Data Roles (enterprise-wide roles)
A Data Role is implemented as Job Roles for a defined set of data. This role describes
the job a user does within that defined set of data. The Data Role inherits a Job Role
and is granted applicable data security privileges.
Data Roles grant specific data to users. For example, HR Admin UK has access to
all UK employees, or Sales Rep West Coast can access West Coast customer
accounts. Data Roles are built at the customer site as they are data dependant.
Data Roles are built using Job Role and permission grants on custom data. For
example:
An Accounts Payables Specialist might be assigned the Data Role 'Accounts
Payables Specialist - US Business Unit'. This Data Role inherits the Job Role
'Accounts Payable Specialist' and grants access to transactions in the US Business
Unit.
A Benefits Administrator is assigned the Data Role 'Benefits Administrator Surname A-E'. This Data Role inherits the Job Role 'Benefits Administrator' and
grants access to Employees with the Surname starting from A to E. Typically, a
person is hired into a job, which might trigger an event to automatically assign a
Job Role without being assigned a defined set of data. A person in a functional
department might at a later point in time assign his staff a Data Role that describes
the job of that person within that defined set of data.
Data roles can be provisioned to a user on request. Data Roles can be formed by
declaring child Duty, Abstract, and Job Roles.
Abstract Roles (enterprise-wide roles)
These roles are associated with a user irrespective of their job or job function, and are
not associated with a job or duty. For example, Employee (Human Resources),
Manager (Human Resources), Customer, Supplier etc. Abstract Roles are normally
assigned by the system (based on user attributes) but can be provisioned to a user on
request.

There are many tools that enable you to configure security in reports and analytics.
Topics:
Using Oracle Identity Management to Manage Users and Enterprise Roles
Using Oracle Authorization Policy Manager to Configure Roles and Privileges
Using the Oracle BI Administration Page to Configure Duty Role Privileges
Using Oracle Identity Management to Manage Users and Enterprise Roles

Oracle Identity Management enables you to manage authenticated users, Job Roles,
and Data Roles in the LDAP directory.
For more information about managing Users and Groups (Job Roles, Abstract Roles,
Data Roles), see Creating Users and Assigning Them to Job Roles.
Using Oracle Authorization Policy Manager to Configure Roles and Privileges

Oracle Authorization Policy Manager (APM) enables you to create and manage Duty
Roles that control access privileges to Oracle Business Intelligence resources.
Job Roles (or Fusion Applications Enterprise Roles) in the LDAP directory are mapped
by default to the pre-configured Duty Roles. For detailed steps on mapping Enterprise
Roles to Duty Roles, see Assigning Enterprise Roles (or Job Roles) to Duty Roles.
In Oracle APM, you can search on roles related to a specific functional area. To do so,
navigate to the Search Role tab of the Role Catalog page, and select the appropriate
functional area from the Category list.
Using the Oracle BI Administration Page to Configure Duty Role Privileges

Use the Oracle Business Intelligence Administration Manage Privileges page to grant
access and privileges to dashboards and other content to Duty Roles.
You can use the Oracle Business Intelligence Administration Manage Privileges page
to grant specific privileges, for example to:
Manage device types.
Access a subject area within BI Answers (for example, Subject Area: General
Ledger - Balances Real Time).
View a dashboard prompt.
To configure catalog Duty Role privileges:

1. Log in to Oracle Business Intelligence with Administrator privileges.
2. Select the Administration link to display the Administration page.
3. Select the Manage Privileges link to display the Manage Privileges page.
4. In the Manage Privileges page, click a link to display the Privilege dialog, where
you can grant or deny the privilege to the currently selected role.
5. Click the Add users/roles icon (+) to display the Add Application Roles, Catalog
Groups, and Users dialog.
6. Click OK.
7. To configure permissions for Duty Roles on functional dashboards and reports:
a. In the top, click Catalog and expand Shared Folders in the left pane.
b. Click the required pillar or functional area folder to open it.
For example, select the Workforce Deployment dashboard under the Human
Capital Management shared folder.
c. Click the More link for the Workforce Deployment dashboard to open the
Permissions dialog box.
d. Use the Permission dialog box to add or modify role permissions for the
Workforce Deployment dashboard.
Securing Analytics
Note:
Similar steps can be taken to configure security for other objects in the catalog.
Securing Analytics
Set up security using the Job Roles and Duty Roles that are installed.
Topics:
Creating Users and Assigning Them to Job Roles
Assigning Enterprise Roles (or Job Roles) to Duty Roles
Creating Duty Roles
Assigning Duty Role Privileges to Catalog Objects
Creating Users and Assigning Them to Job Roles

When you create a new user you must assign them to one or more Job Roles or Data
Roles using Oracle Identity Management to assign appropriate privileges.
A new user inherits appropriate privileges from the Duty Roles that are associated
with the Job Role or Data Role. New users are automatically added to the Fusion
Applications Identity Store.
For Fusion Business Intelligence, Oracle Business Intelligence authenticates against
Fusion Applications Identity Store at runtime.
To create a new user and assign the user to a Job Role or Data Role:
1. Use Oracle Identity Management as described in Using Oracle Identity
Management to Manage Users and Enterprise Roles.
2. Create a new user.

3. Assign the new user to a Job Role or Data Role.
If the default Job Roles or Data Roles do not meet your business requirements, then
create your own Job Roles or Data Roles.
Assigning Enterprise Roles (or Job Roles) to Duty Roles

If the default security settings do not meet all of your business needs, you can alter the
role mappings.
If the default security settings do not meet your needs, then you might:
Edit the default Duty Roles and map them to different Enterprise Roles.
Create new Duty Roles and map them to Enterprise Roles.
Follow the steps below to map an Enterprise Role to a Duty Role.
To map an Enterprise Role to a Duty Role:
Prerequisite: Before you start, the Enterprise Role must already exist in the LDAP
directory, and the Duty Role must already exist in the Role Catalog. You can either use
Securing Analytics
one of the pre-configured Enterprise Roles or you can use OID to create your own
Enterprise Roles.
1. In Oracle APM, navigate to the 'obi' Application and use the Search options to
locate the Duty Role that you want to map.
2. Select the Duty Role, then click Open to display the Application| Application Role
dialog.
3. Display the External Role Mapping tab. You use this tab to search for and select the
Enterprise Roles that you want to map to that Duty Role.
4. Click Add to display the External Role Search dialog.
5. Click Map Roles to map the Enterprise Roles selected for the Duty Role, and return
to the External Role Mapping tab.
Creating Duty Roles

If the default Duty Roles do not meet all of your business needs, you can create new
ones and map them to Job Roles.
To create a Duty Role:
1. Log in to Oracle Authorization Policy Manager, and select the 'obi' Application
area.
2. In the Applications pane\Create area select the New Application Role link to
display the Application| Application Role dialog.
3. In the General tab, use the Display Name field to specify the Duty Role name.
4. In the General tab, use the Role Name field to specify the Duty Role name in
upper-case.
Leave the Role Category field blank.

5. Click Save.
The other tabs only become active after you click Save.
At this point, you might want to map Job Roles to the new Duty Role by following
the steps in Assigning Enterprise Roles (or Job Roles) to Duty Roles, or you might
want to map Job Roles to the new Duty Role at a later date.
Assigning Duty Role Privileges to Catalog Objects

You assign Duty Role privileges to catalog objects to enable users associated with that
Duty Role to be granted specific query permissions (for example, dashboard and other
content).
For more information, see Using the Oracle BI Administration Page to Configure Duty
Role Privileges.

Select catalog permissions and then grant permissions through Oracle Enterprise
Scheduler.
Topics:
Setting Catalog Permissions
Granting Permissions to the Oracle Enterprise Scheduler Job Definition
Setting Catalog Permissions

For a user to run a report, you must grant appropriate permissions on each catalog
object used in the report.
Each report always includes at least two objects: the report and the data model. If your
report also references a subtemplate or a style template, you must also grant Read
permissions on those objects. The report object requires additional grants to run,
schedule, and view output.
To grant permissions in the catalog:
1. Navigate to the report in the catalog, click More and then click Permissions to
display the Permissions dialog.
2. In the Permissions dialog, click Add users/roles.
3. In the Add Application Roles, Catalog Groups and Users dialog, search for your
custom role and use the shuttle buttons to move it to the Selected Members list. In
the Set Permission to list, select Custom, and then click OK.
4. In the Permissions dialog, locate the role you added, and click Edit.
5. In the Custom Permissions dialog, select the permissions to enable. Typically, you
enable the following for a BI Publisher report:
Read gives authority to access, but not modify, the report

Traverse gives the authority to copy the report
Run Publisher Report gives authority to read, traverse the folder that
contains the report, and run the report.
Schedule Publisher Report gives authority to read, traverse the folder that
contains the report, and schedule the report
View Publisher Output enables the user to view the report output generated
by the scheduler
Granting Role Permissions to the Data Model and Other Referenced Objects
Next, grant role permissions to the data model and other referenced objects.
1. Navigate to the data model in the catalog, click More and then click Permissions to
display the Permissions dialog.
2. Follow the steps to grant permissions, but in the Custom Permissions dialog,
enable the Read and Traverse permissions.
3. Repeat this procedure for any other referenced objects (subtemplates or style
templates).
Deleting Permissions
You can remove custom report inherited permissions from a report.
1. Navigate to the object in the catalog, click More and then click Permissions. The
Permissions dialog launches and the inherited permissions are shown.
2. Select the permission to delete and then click the Delete toolbar button.
Granting Permissions to the Oracle Enterprise Scheduler Job Definition

If the custom report is to be scheduled through Oracle Enterprise Scheduler, execution
permissions must also be granted to enable users belonging to the role to submit the
job.
6
Managing Business Intelligence Publisher
Reports
If you want to use Oracle Business Intelligence Publisher with Oracle Fusion
applications, there are some administrative tasks that you must perform.
Topics:
Managing Report Delivery Servers
Navigating to the Oracle BI Publisher Administration Page
Configuring Report Delivery Servers
Understanding the Report and Delivery Processors
Managing Report Processing and Delivery Server Load
Diagnosing Report Processing Issues
Configuring System Properties for Reporting
Managing Report Delivery Servers

Oracle Business Intelligence Publisher, the report generation and delivery engine for
Oracle Fusion Applications, requires post-installation configuration and tuning to
deliver reports to users.
Oracle BI Publisher receives report requests in the following ways:
Through Oracle Enterprise Scheduler
Through the Reports and Analytics pane
From an application page
Requests submitted through Oracle Enterprise Scheduler are processed by the Oracle
BI Publisher scheduler. Requests submitted through the Reports and Analytics pane
can be either real-time online requests or scheduled requests. Requests submitted
through an application may invoke Oracle Enterprise Scheduler or may return report
request results directly back to the application page.
After installing Oracle Fusion Applications, Oracle BI Publisher is configured to accept
requests from Oracle Fusion Applications. However, before you can deliver report
documents to their destinations you must define the delivery servers in Oracle BI
Publisher. Use the Oracle BI Publisher Administration page to define your delivery
servers.
After setup, you can then further configure the number of report processor and
delivery threads to best handle your processing and delivery requirements. In
Managing Business Intelligence Publisher Reports 6-1
addition, you can configure report properties for the system or at the report level to
tune performance of your reports. To diagnose report processing issues, BI Publisher
provides a set of scheduler diagnostics.

Use the Oracle BI Publisher Administration page to:
Configure delivery servers
Manage report and delivery processors
View scheduler diagnostics
Set system properties and report runtime configuration properties
Request the Fusion Applications security administrator to assign the BI Platform
Administrator duty role (BI stripe) to the person responsible for administering BI
analyses, dashboards, and BI Publisher reports. Administration tasks include security
permissions for objects, organizing objects into folders , accessing log files, and several
other tasks.
To navigate to the Oracle BI Publisher Administration page:
1. From the Oracle Fusion Applications Navigator, under Tools, click Reports and
Analytics.
2. In the Reports and Analytics pane, click Catalog to display the catalog page.
3. Click Administration, then click Manage BI Publisher.
Configuring Report Delivery Servers

Set up the report delivery servers to support printing.
To configure delivery servers:
1. From the BI Publisher Administration page, click Delivery Configuration.
2. Enter values in the Delivery Configuration Options tab to set general properties
for email deliveries and notifications.
3. To configure a delivery server, click the appropriate tab.
The following table lists the report delivery channels supported by Oracle BI
Publisher.
Delivery Type
Section
Printer and Fax
Adding a Printer or Fax Server
E-mail
Adding an E-mail Server
WebDAV
Adding a WebDAV Server
HTTP
Adding an HTTP Server
FTP
Adding an FTP Server
Note:
Printing is supported through Internet Printing Protocol (IPP). If Oracle BI

Publisher is operating in a UNIX environment, you must set up the Common
Unix Printing Service (CUPS) and then define your CUPS server to Oracle BI
Publisher. For a Windows environment, you must set up Windows Print
Server for IPP.

When Oracle Enterprise Scheduler initiates a job, it is picked up by the BI Publisher
scheduler queue.
Job Processor listens for requests from the scheduler queue. When the job
information is received, the job processor executes the data model (and splits the
data for bursting jobs), stores the data in the shared temporary folder, and sends
the report metadata to the report queue.
Report Processor listens for requests from the report queue. When the report
information is received, the report processor generates the report documents, stores
it in the shared temporary folder and puts the delivery information in the delivery
queue.
Delivery Processor listens to the delivery queue and handles the delivery of
reports for its channel. The delivery processors are:
Email Processor
File Processor
FTP Processor
Print Processor
WebDAV Processor
Fax Processor
You can configure the number of threads dedicated to each processor.

Manage the processors in the BI Publisher Scheduler Configuration page. By default,
each processor is enabled and the thread count for each is set to five. For each
managed server that is running in the BI cluster, a table for that instance's processors is
displayed. Use the table to enable or disable processors for the instance and configure
the thread counts.
To configure processor threads:
1. From the BI Publisher Administration page, click Scheduler Configuration.
2. On the Scheduler Configuration page, scroll to the Cluster Instances region.
3. Enter the Number Threads value in the processor configuration table.
Note:
All processors are automatically be set to use the number of threads defined in
the Threads Per JMS Processor value of the JMS Configuration region of the
page. Enter a value in the Number Threads column to change the value from
this default.
Next Steps:
After performing the scale-out procedure, follow the steps in Managing Report
Processing and Delivery Server Load to configure the processor threads for each
cluster instance.

The Scheduler Diagnostics page provides the runtime status of the scheduler. It
provides status of its JMS configuration, JMS queues, cluster instances, scheduler
Database, Toplink, and Oracle Enterprise Scheduler.
To access the Scheduler Diagnostics page:
1. Navigate to the Oracle Business Intelligence Publisher Administration page.
2. In the System Maintenance group, click Scheduler Diagnostics.

Use the Oracle BI Publisher Runtime Configuration page to set the system-level
runtime properties for reports.
To access the Runtime Configuration page:
1. Navigate to the Oracle Business Intelligence Publisher Administration page.
2. In the Runtime Configuration group, click Properties.
A
This table shows the dimensions supported by Oracle Transactional Business
Intelligence descriptive flexfields.
Product Area
DFF Code
Fact Name
Financials
AP_CHECKS
Dim - AP Disbursement Details
Financials
AP_HOLDS
Dim - AP Hold Details
Financials
AP_INVOICE_DISTR
IBUTIONS
Dim - AP Transaction Details
Financials
AP_INVOICE_LINES
Financials
AP_INVOICES
Financials
AP_PAYMENT_SCH
EDULES
Dim - AP Payment Schedule Details
Financials
AP_TERMS_B
Dim - AP Terms
Financials
AR_ADJUSTMENTS
Dim - AR Adjustment Details
Financials
AR_APPROVAL_AC
TION_HISTORY
Dim - AR Adjustment Approval Action

History Details
Financials
AR_CASH_RECEIPT
S
Dim - AR Standard Receipt Details
Financials
AR_MISC_CASH_DI
STRIBUTIONS
Dim - AR Miscellaneous Receipt Details
Financials
AR_PAYMENT_SCH
EDULES
Dim - AR Payment Schedule Details
Financials
AR_RATE_ADJUST
MENTS
Dim - AR Receipt Rate Adjustment Details
Financials
AR_RECEIPT_CLAS
SES
Dim - AR Receipt Method
Financials
AR_RECEIPT_METH
ODS
Dim - AR Receipt Method
Financials
AR_RECEIVABLE_A
PPLICATIONS
Dim - AR Standard Receipt Details
Supported Descriptive Flexfields A-1
Product Area
DFF Code
Fact Name
Financials
AR_REVENUE_AD
MUSTMENTS
Dim - AR Revenue Adjustment Details
Financials
CE_BANK_ACCOU
NTS
Dim - CE Bank Accounts
Financials
CE_EXTERNAL_TR
ANSACTIONS
Dim - CE External Cash Transaction Details
Financials
CE_STATEMENT_H
EADERS
Dim - CE Bank Statement Details
Financials
CE_STATEMENT_LI
NES
Dim - CE Bank Statement Details
Financials
FA_ADDITIONS
Dim - Fixed Asset
Financials
FA_ASSET_INVOIC
ES
Dim - Asset Source Lines Details
Financials
FA_BOOK_CONTRO
LS
Dim - Asset Book
Financials
FA_CALENDAR_TY
PES
Dim - Date Fixed Assets Calendar
Financials
FA_CATEGORIES
Dim - Asset Category
Financials
FA_CATEGORY_BO
OKS
Dim - Asset Category Book
Financials
FA_FISCAL_YEAR
Dim - Date Fixed Assets Calendar
Financials
FA_LOCATIONS
Dim - Asset Location
Financials
FA_RETIREMENTS
Dim - Asset Retirement Details
Financials
FA_TRANSACTION
_HEADERS
Dim - Asset Transaction History Details
Financials
FUN_DIST_LINES
Dim - Intercompany Transaction Distribution

Details
Financials
FUN_TRX_BATCHE
S

Details
Financials
FUN_TRX_HEADER
S

Details
Financials
GL_CODE_COMBIN
ATIONS
Dim - GL Account
Financials
GL_JE_BATCHES
Dim - GL Journal Details
A-2 Administering Transactional Analyses
Product Area
DFF Code
Fact Name
Financials
GL_JE_CATEGORIE
S
Dim - GL Journal Category
Financials
GL_JE_HEADERS
Financials
GL_JE_LINES
Financials
GL_JE_SOURCES
Dim - GL Journal Source
Financials
GL_LEDGERS
Dim - Ledger
Financials
GL_PERIOD_STATU
SES
Fact - Fins - GL Period Statuses
Financials
GL_PERIODS
Dim - Date Fiscal Calendar
Financials
Payroll Developer DF
Dim - Payroll
Financials
RA_CUST_TRX_LIN
E_GL_DIST
Dim - AR Transaction Details
Financials
RA_CUST_TRX_LIN
E_SALESREPS
Financials
RA_CUST_TRX_TYP
ES
Dim - AR Transaction Type
Financials
RA_CUSTOMER_TR
X
Financials
RA_CUSTOMER_TR
X_LINES
Financials
RA_RULES
Dim - AR Accounting Rule
Financials
RA_TERMS
Dim - AR Payment Terms
Financials
RA_TERMS_LINES
Dim - AR Payment Terms
Financials
VRM_FMV_LINES
Dim - VRM FMV Line Details
Financials
VRM_FMV_LINE_SE
TS
Dim - VRM FMV Set Details
Financials
VRM_FMV_TEMPL
ATES_B
Dim - VRM FMV Profile
Financials
VRM_FMV_TEMPL_
ASSIGNMENTS
Dim - VRM FMV Profile
Financials
VRM_ITEM_GROUP
S_VL
Dim - VRM FMV ItemType
Financials
VRM_MEA_DOC_C
ARVEOUT_LINES
Dim - VRM MEA Carveout Lines Details
Product Area
DFF Code
Fact Name
Financials
VRM_MEA_DOC_H
EADERS
Financials
VRM_MEA_DOC_LI
NES
Financials
VRM_MEA_RULES_
VL
Dim - VRM MEA Rules
Financials
VRM_PRICE_EFF_P
ERIODS_VL
Dim - VRM FMV Effective Period
Financials
VRM_REV_DOCUM
ENTS
Dim - VRM Recognition Details
Financials
VRM_REV_DOC_LI
NES
Financials
VRM_REV_DOC_LI
NE_SCHEDULES
Financials
VRM_REV_DOC_LI
NE_SPLITS_ALL
Financials
VRM_SOURCE_DO
CUMENTS
Dim - VRM Source Document Details
Financials
VRM_SOURCE_DO
C_LINES
Dim - VRM Source Document Details
Financials
XLA_AE_HEADERS
Dim - SLA Journal Details
Financials
XLA_AE_LINES
Dim - SLA Journal Details
Financials
XLE_ETB_INFO_DE
V
Dim - Legal Entity
Financials
XLE_LE_ADD_INFO
Dim - Legal Entity
Financials
XLE_LE_INFO_DEV
Dim - Legal Entity
Human Capital
Management
ANC_PER_ABS_EN
TRIES_DFF
Dim - Assignment Absences Details
Human Capital
Management
HRA_DOC_TYPES_
B
Dim - Document Type
Human Capital
Management
HRA_EVAL_ITEMS
Dim - Performance Document Section Item
Human Capital
Management
HRA_EVAL_RATIN
GS
Dim - Document and Rating Details
Product Area
DFF Code
Fact Name
Human Capital
Management
HRA_EVALUATION
S
Dim - Performance Document Status Details
Human Capital
Management
HRA_SECTION_DEF
NS_B
Dim - Performance Document Section
Human Capital
Management
HRA_TMPL_DEFNS
_B
Dim - Performance Template
Human Capital
Management
HRA_TMPL_SECTIO
NS
Dim - Performance Document
Human Capital
Management
HRG_GOAL_PLANS
_B
Dim - Performance Goal Plan
Human Capital
Management
HRG_GOALS
Dim - Performance Goals
Human Capital
Management
HRM_PLAN_CAND
IDATES
Dim - Succession Plan Candidates
Human Capital
Management
HRR_MEETINGS
Dim - Talent Review Meeting
Human Capital
Management
HRT_CONTENT_IT
EMS_B
Dim - Content Item
Human Capital
Management
HRT_PROFILE_ITE
MS
Dim - Person Profile Details
Human Capital
Management
HRT_RATING_LEVE
LS_B
Dim - Rating Level
Human Capital
Management
HRT_RATING_MOD
ELS_B
Dim - Rating Model
Human Capital
Management
PAY_ALL_PAYROL
LS_DDF
Dim - Payroll
Human Capital
Management
PER_ABSENCE_DFF
Dim - Assignment Absences Details
Human Capital
Management
PER_ACT_DFF
Dim - HR Action
Human Capital
Management
PER_ACT_LEG_DDF
Dim - HR Action
Human Capital
Management
PER_ACT_REASON
S_DFF
Dim - HR Action Reason
Human Capital
Management
PER_ADDRESSES_D
FF
Dim - Worker Location
Product Area
DFF Code
Fact Name
Human Capital
Management
PER_ALLOCATED_
CHECKLISTS_DFF
Dim - Checklist Task Details
Human Capital
Management
PER_ALL_PEOPLE_
DFF
Dim - Person Details
Human Capital
Management
PER_ASG_DFF
Dim - Worker Assignment Details
Human Capital
Management
PER_ASG_LEG_DDF
Dim - Worker Assignment Details
Human Capital
Management
PER_CHECKLISTS_
DFF
Dim - Checklist Task Template
Human Capital
Management
PER_CITIZENSHIPS
_DFF
Dim - Person Citizenship
Human Capital
Management
PER_CONTACT_RE
LSHIPS_DFF
Dim - Person Contact Relationship
Human Capital
Management
PER_CONTRACT_D
FF
Dim - Employment Contract Details
Human Capital
Management
PER_CONTRACT_L
EG_DDF
Dim - Employment Contract Details
Human Capital
Management
PER_DOCUMENTS_
OF_RECORD_DFF
Dim - Document of Record Details
Human Capital
Management
PER_DOC_OF_REC
ORD_LEG_DDF
Dim - Document of Record Details
Human Capital
Management
PER_DRIVERS_LICE
NSE_TYPES_DFF
Dim - Person Driver License
Human Capital
Management
PER_EMAIL_ADDR
ESSES_DFF
Dim - Person Email Addresses
Human Capital
Management
PER_ETHNICITIES_
DFF
Dim - Person Ethnicity
Human Capital
Management
PER_EVALUATION
_CRITERIA_DFF
Dim - Job
Human Capital
Management
PER_GRADES_DFF
Dim - HR Grade
Human Capital
Management
PER_JOB_FAMILY_
DFF
Dim - Job
Human Capital
Management
PER_JOBS_DFF
Dim - Job
Product Area
DFF Code
Fact Name
Human Capital
Management
PER_LOCATIONS_D
F
Dim - Worker Location
Human Capital
Management
PER_NATIONAL_ID
ENTIFIERS_DFF
Dim - Person National Identifiers
Human Capital
Management
PER_ORGANIZATI
ON_UNIT_DFF
Dim - Department
Human Capital
Management
PER_PERSONDRIVE
RS_LICENSE_LEG_
DDF
Dim - Person Driver License
Human Capital
Management
PER_PERSON_ADD
R_USG_DFF
Dim - Person Address
Human Capital
Management
PER_PERSON_ALL
OCATED_TASKS_D
FF
Dim - Checklist Task Details
Human Capital
Management
PER_PERSON_CON
TACT_RELATIONS
HIP_DDF
Dim - Person Contact Relationship
Human Capital
Management
PER_PERSON_DLV
RY_METHODS_DFF
Dim - Person Delivery Methods
Human Capital
Management
PER_PERSON_LEGI
SLATIVE_DATA_LE
G_DDF
Dim - Person Legislative Information
Human Capital
Management
PER_PERSON_LEGI
SLATIVE_DFF
Dim - Person Legislative Information
Human Capital
Management
PER_PERSON_NAM
E_DFF
Dim - Person Names
Human Capital
Management
PER_PERSON_NAM
E_LEG_DDF
Dim - Person Names
Human Capital
Management
PER_PERSON_PASS
PORT_LEG_DDF
Dim - Person Passport Details
Human Capital
Management
PER_PERSON_TYPE
_USG_DFF
Dim - Person Type
Human Capital
Management
PER_PERSON_VISA
_LEG_DDF
Dim - Person Work Permit
Human Capital
Management
PER_PERSONS_DFF
Fact - Person
Human Capital
Management
PER_PHONES_DFF
Dim - Person Phones
Product Area
DFF Code
Fact Name
Human Capital
Management
PER_POSITIONS_DF
F
Dim - HR Position
Human Capital
Management
PER_PPS_DFF
Dim - Work Relationship Details
Human Capital
Management
PER_PPS_LEG_DDF
Dim - Work Relationship Details
Human Capital
Management
PER_RATE_VALUES
_DFF
Fact - Grade Rate
Human Capital
Management
PER_RATES_DF
Dim - Grade Rate
Human Capital
Management
PER_RELIGIONS_D
FF
Dim - Person Religion
Human Capital
Management
PER_TASKS_IN_CH
ECKLIST_DFF
Dim - Checklist Task Template
Human Capital
Management
PER_VISA_PERMIT_
DFF
Dim - Person Work Permit
Incentive
Compensation
CN_COMP_PLANS_
DFF
Dim - Compensation Plan
Incentive
Compensation
CN_MEASURES_DF
F
Dim - Performance Measure
Incentive
Compensation
CN_PARTICIPANT_
DETAIL_DFF
Dim - Participant Details
Incentive
Compensation
CN_PLAN_COMPO
NENTS_DFF
Dim - Plan Component
Incentive
Compensation
CN_TP_BASETRAN
S_DFF
Dim - Participant Transaction Details
Procurement
PO_ATTRIBUTE_VA
LUES
Dim - Purchase Agreement Details
Procurement
PO_DISTRIBUTIONS
Dim - Purchase Order Details
Procurement
PO_DOCUMENT_T
YPES
Dim - Purchase Order Transaction Type
Procurement
PO_HEADERS
Procurement
PO_LINE_LOCATIO
NS
Procurement
PO_LINE_TYPES
Dim - Purchase Line Type
Product Area
DFF Code
Fact Name
Procurement
PO_LINES
Procurement
PO_NOTIFICATION
_CONTROLS
Dim - Agreement Notification Controls
Procurement
PON_AUCTION_HE
ADERS
Dim - Sourcing Negotiation Details
Procurement
PON_AUCTION_ITE
M_PRICES
Procurement
PON_AUCTION_SU
PPLIER_HEADERS
Procurement
POR_REQ_DISTRIB
UTIONS
Dim - Purchase Requisition Details
Procurement
POR_REQUISITION
_HEADERS
Procurement
POR_REQUISITION
_LINES
Procurement
POZ_SUPPLIER_SIT
ES_ALL_M
Dim - Supplier Sites
Procurement
POZ_SUPPLIERS
Dim - Supplier
Projects
Contract Deliverable
Flexfield
Dim - Project Contract
Projects
ContractHeaderFlexfi
eld
Projects
OKC_LINES_DESC_
FLEX
Projects
PJB_BILLING_EVEN
TS_FLEX
Dim - Project Invoice Details
Projects
PJB_INVOICE_HEA
DERS_FLEX
Projects
PJB_INVOICE_LINE
S_FLEX
Projects
PJC_EXP_ITEMS_DE
SC_FLEX
Dim - Project Costing Details
Projects
PJC_PRJ_ASSETS_D
ESC_FLEX
Dim - Project Capitalization Details
Projects
PJC_TXN_XFACE_D
ESC_FLEX
Dim - Project Unprocessed Transaction

Details
Product Area
DFF Code
Fact Name
Projects
PJF_CLASS_CATEG
ORIES_DESC_FLEX
Dim - Project
Projects
PJF_CLASS_CODES_
DESC_FLEX
Dim - Project
Projects
PJF_EVENT_TYPES_
DESC_FLEX
Fact Project ETL VOs - do not delete
Projects
PJF_EXP_CATEGORI
ES_DESC_FLEX
Dim - Financial Resource
Projects
PJF_EXP_TYPES_DE
SC_FLEX
Dim - Financial Resource
Projects
PJF_NONLAB_RES_
DESC_FLEX
Dim - Non Labor Resource
Projects
PJF_PROJECT_CLAS
S_CODE_DESC_FLE
X
Dim - Project
Projects
PJF_PROJECT_TYPE
S_DESC_FLEX
Dim - Project
Projects
PJF_PROJECTS_DES
C_FLEX
Dim - Project
Projects
PJF_TASK_STRUCT
URE_DFF
Dim - Task
Projects
PJF_WORK_TYPES_
DESC_FLEX
Dim - Work Type
Projects
PJO_PLAN_LINES_
DFF
Dim - Project Budget Details
Projects
PJO_PLANNING_O
PTIONS_DFF
Dim - Project Budget Version
Projects
PROJECTS_STD_CO
ST_COLLECTION
Dim - Project Costing Details
Projects
PROJECTS_STD_CO
ST_COLLECTION
Dim - Project Unprocessed Transaction

Details
Supply Chain
Management
CARRIER_ORGANI
ZATION
Dim - Shipping Method
Supply Chain
Management
CST_ANALYSIS_CO
DES_B
Dim - Cost Analysis Group
Supply Chain
Management
CST_ANALYSIS_GR
OUPS_B
Product Area
DFF Code
Fact Name
Supply Chain
Management
CST_COST_BOOKS_
B
Dim - Cost Organization Book
Supply Chain
Management
CST_COST_ELEME
NTS_B
Dim - Cost Element
Supply Chain
Management
CST_COST_ORG_BO
OKS
Dim - Cost Organization Book
Supply Chain
Management
CST_ELEMENT_AN
ALYSIS_GROUPS
Supply Chain
Management
CST_VAL_STRUCTU
RES_B
Dim - Cost Valuation Unit
Supply Chain
Management
CST_VAL_UNITS_B
Dim - Cost Valuation Unit
Supply Chain
Management
DOO_PROCESS_DE
FS_ADD_INFO
Dim - DOO Process
Supply Chain
Management
DOO_PROCESS_STE
PS_ADD_INFO
Dim - Step
Supply Chain
Management
DOO_TASK_TYPES_
ADD_INFO
Dim - Primary Task
Supply Chain
Management
EGO_CHANGE_LIN
E
Dim - New Item Request Line Details
Supply Chain
Management
EGO_ENGINEERIN
G_CHANGES
Dim - New Item Request Details
Supply Chain
Management
EGP_CATEGORY_D
FF
Dim - Item
Supply Chain
Management
EGP_CATEGORY_S
ETS_DFF
Dim - Item
Supply Chain
Management
EGP_COMPONENT
_DFF
Dim - PIM - Components Details
Supply Chain
Management
EGP_ITEM_CLASS_
DFF
Dim - PIM - Item Class
Supply Chain
Management
EGP_ITEM_RELATI
ONSHIPS_DFF
Dim - Cross Reference Item Details
Supply Chain
Management
EGP_ITEM_REVISIO
NS_DFF
Dim - PIM - Item and Revisions Details
Supply Chain
Management
EGP_REFERENCE_D
ESIGNATOR_DFF
Dim - PIM - Reference Designator
Product Area
DFF Code
Fact Name
Supply Chain
Management
EGP_STRUCTURE_
HEADER_DFF
Dim - PIM - Structure Details
Supply Chain
Management
EGP_SUBSTITUTE_
COMPONENT_DFF
Dim - PIM - Substitute Component
Supply Chain
Management
EGP_SYSTEM_ITEM
S_DFF
Dim - Item
Supply Chain
Management
EGP_TRADING_PA
RTNER_ITEMS_DFF
Dim - Trading Partner Item Details
Supply Chain
Management
GMS_AWARD_HEA
DERS_DFF
Dim - Award
Supply Chain
Management
GMS_AWARD_PERS
ONNEL_DFF
Dim - Personnel
Supply Chain
Management
GMS_AWARD_PROJ
ECTS_DFF
Dim - Award Project
Supply Chain
Management
GMS_INSTITUTION
S_DFF
Dim - Award
Supply Chain
Management
INV_GRADES
Dim - Inventory Grade
Supply Chain
Management
INV_ITEM_LOCATI
ONS
Dim - Storage Location
Supply Chain
Management
INV_LOT_ATTRIBU
TES
Dim - Inventory Lot
Supply Chain
Management
INV_LOT_NUMBER
S
Dim - Inventory Lot
Supply Chain
Management
INV_MATERIAL_TX
NS
Dim - Inventory Details
Supply Chain
Management
INV_ORG_PARAME
TERS
Dim - Inventory Org
Supply Chain
Management
INV_SECONDARY_I
NVENTORIES
Dim - Storage Location
Supply Chain
Management
INV_TRANSACTIO
N_REASONS
Dim - Receipt Transaction Reasons
Supply Chain
Management
INV_TRANSACTIO
N_TYPES
Dim - Movement Types
Supply Chain
Management
INV_TXN_SOURCE_
TYPES
Dim - Inventory Transaction Source Type
Product Area
DFF Code
Fact Name
Supply Chain
Management
RCV_SHIPMENT_H
EADERS
Dim - Inbound Shipment Details
Supply Chain
Management
RCV_SHIPMENT_LI
NES
Dim - Inbound Shipment Details
Supply Chain
Management
RCV_TRANSACTIO
NS
Dim - Receipt Details
Supply Chain
Management
WSH_CARRIERS
Dim - Carrier
Supply Chain
Management
WSH_DELIVERY_D
ETAILS
Dim - Sales Pick Details
Supply Chain
Management
WSH_NEW_DELIVE
RIES
Dim - Sales Pick Details

Oracle - Cloud R 11.1.11 - Administering Transactional Analyses (E68922-01) (OATBI)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Oracle - Cloud R 11.1.11 - Administering Transactional Analyses (E68922-01) (OATBI)

Enviado por

Direitos autorais:

Formatos disponíveis

Oracle Cloud

Administering Transactional Analyses

Oracle Cloud Administering Transactional Analyses, Release 11.1.11

Tools for Administering Reports and Analytics ..................................................................................

The Catalog: Where You Maintain Your Reports and Analytics.......................................................

Identifying Objects in the Catalog .................................................................................................

Functional Setup Tasks for Transactional Business Intelligence

Completing Required Tasks in the Functional Setup Manager .........................................................

Assigning Security Profiles to Job Roles................................................................................................

Configuring Flexfields for Business Intelligence

Enabling Key Flexfields for Business Intelligence Reporting ....................................................

Mapping Non-Qualified Segments to BI Objects ........................................................................

Identifying Supported Key Flexfields ...........................................................................................

Setting up the GL Accounting Flexfields ..............................................................................................

Understanding Accounting Key Flexfields ..................................................................................

Identifying Accounting Key Flexfield Segments .........................................................................

Assigning Unique Segment Labels ................................................................................................

Performing Column Flattening ......................................................................................................

Designating GL Accounting Segment Instances as BI-Enabled ................................................

Deploying Accounting Key Flexfields ..........................................................................................

Configuring Descriptive Flexfields for Transactional Business Intelligence ...................................

Configuring Descriptive Flexfield Segments ...............................................................................

Designating Descriptive Flexfields as BI-Enabled..................................................................... 3-10

Designating Extensible Flexfields as BI-Enabled....................................................................... 3-15

Managing Reports and Analytics

Creating Folders ...............................................................................................................................

Setting Folder Properties.................................................................................................................

Mapping Reports to Work Areas ...........................................................................................................

Moving Reports and Analytics ...............................................................................................................

Unarchiving a File in a New Location...........................................................................................

About Warehouse Column Errors in Transactional Analyses ...........................................................

Setting Default Currency Formatting for Columns .............................................................................

Securing Reports and Analytics

About Object-Level Security...........................................................................................................

About Roles in Reports and Analytics...................................................................................................

About Security Configuration Tools in Reports and Analytics .........................................................

Using Oracle Authorization Policy Manager to Configure Roles and Privileges...................

Using the Oracle BI Administration Page to Configure Duty Role Privileges........................

Securing Analytics ....................................................................................................................................

Creating Users and Assigning Them to Job Roles.......................................................................

Assigning Enterprise Roles (or Job Roles) to Duty Roles ...........................................................

Creating Duty Roles.........................................................................................................................

Assigning Duty Role Privileges to Catalog Objects .................................................................. 5-10

Managing Business Intelligence Publisher Reports

Navigating to the Oracle BI Publisher Administration Page .............................................................

Configuring Report Delivery Servers ....................................................................................................

Understanding the Report and Delivery Processors ...........................................................................

Managing Report Processing and Delivery Server Load....................................................................

Diagnosing Report Processing Issues ....................................................................................................

Configuring System Properties for Reporting......................................................................................

Supported Descriptive Flexfields

Boldface type indicates graphical user interface elements

Italic type indicates book titles, emphasis, or placeholder

Monospace type indicates commands within a paragraph, URLs,

Reports and Analytics in Oracle Fusion Applications

Tools for Administering Reports and Analytics

Tools for Administering Reports and Analytics

The Catalog: Where You Maintain Your Reports and Analytics

1-2 Administering Transactional Analyses

The Catalog: Where You Maintain Your Reports and Analytics

You are redirected to the catalog within Oracle Business Intelligence.

Identifying Objects in the Catalog

The Catalog: Where You Maintain Your Reports and Analytics