Oracle Fusion Intelligence For E-Business Suite IG - R12
Oracle Fusion Intelligence For E-Business Suite IG - R12
Oracle Fusion Intelligence For E-Business Suite IG - R12
April 2007
Oracle Fusion Intelligence For E-Business Suite Implementation Guide, Release 12 Part No. E05295-02 Copyright 2007, Oracle. All rights reserved. Primary Author: Steven Schaefer Contributing Author: Abhay Kulkarni, Amit Mittal, Anirban Majumdar, Anurag Garg, Hal Kazi, Imran Ali, Julian Challenger, Karuna Mukherjea, Kathryn Chen, Luis Tong, Marilyn Crawford, Niraj Kumar, Olga Basman, Penelope Brown, Rajesh Dharamshi, Ramana Nidugondi, Roshni Rajesh, Russell Stohr, Sayekumar Arumugam, Sourish Chatterjee, Senthil Thangaperumal, Srinivasan Swaminathan, Stanley Cheung, Stephen Sherlock, Subodh Diwakar, Sudhakar Babu, Sudhanshu Das, Swarnali Bag, Veena Bhandarkar, Venkataraman Ramakrishnan The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Contents
Security
Security Overview..................................................................................................................... 3-1 Responsibilities......................................................................................................................... 3-3 Menus and Functions................................................................................................................ 3-6
iii
iv
10
Request Sets
Steps to Generate Request Sets................................................................................................ A-1 Generating Request Sets........................................................................................................... A-1 Data Loading Shared Data Sources.......................................................................................... A-5
Index
Send Us Your Comments
Oracle Fusion Intelligence For E-Business Suite Implementation Guide, Release 12
Part No. E05295-02
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Applications Release Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: [email protected] Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12 of the Oracle Fusion Intelligence For E-Business Suite Implementation Guide. This guide refers to the following Fusion Intelligence For E-Business Suite applications: Fusion Financials Intelligence For E-Business Suite Fusion Governance, Risk, and Compliance Intelligence Fusion Human Resources Intelligence For E-Business Suite Fusion Supply Chain and Order Management Intelligence For E-Business Suite Fusion Procurement Intelligence For E-Business Suite Fusion Service Intelligence For E-Business Suite Fusion Marketing and Sales Intelligence For E-Business Suite
See Related Information Sources on page xi for more Oracle Applications product information.
ix
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .
Structure
1 Introduction
This chapter gives an overview of the application, covering integrations, terminology, and architecture.
2 Set Up Fusion Intelligence
This chapter discusses setups required to use Fusion Intelligence for E-Business Suite, including Daily Business Intelligence setups and configuration of OBIEE and the BI Server.
3 Security
This chapter discusses the security configurations and new seeded BI responsibilities used in Fusion Intelligence for E-Business Suite.
4 Fusion Financials Intelligence
This chapter discusses setting up the Fusion Marketing and Sales repository. For this release, no dashboards or reports are seeded or shipped.
8 Fusion Supply Chain and Order Management Intelligence
This chapter discusses Fusion Supply Chain and Order Management Intelligence dashboards and catalogs.
9 Fusion Procurement Intelligence
This chapter discusses the Procurement Analysis dashboard and the Procurement Catalog.
10 Fusion Service Intelligence
This chapter discusses the Customer Support Catalog, which you can use to create reports and dashboards.
A Request Sets
This appendix lists the subject areas in Fusion Intelligence For E-Business Suite for which you can create request sets.
For E-Business Suite User Guide, documents the delivered, prebuilt dashboards, reports, subject areas, and security setup for Fusion Intelligence applications for the Oracle E-Business Suite. Before reading this guide, read the Oracle Business Intelligence Enterprise Edition documentation for information on the underlying architecture of Fusion Intelligence applications. Also read the related Oracle E-Business Suite guides for a more detailed, field-level explanation of the data that is used in these applications.
This table lists the books that are cross-referenced in this document. All of these documents are available on OracleMetaLink:
xi
Cross-Referenced Books in This Document Document Oracle Business Intelligence Infrastructure Installation and Configuration Guide Description This guide provides information on installing and configuring the infrastructure or platform components of Oracle Business Intelligence on approved operating system platforms and deployments. This version of the guide applies to infrastructure (platform) releases of Oracle Business Intelligence Enterprise Edition.
This is an infrastructure guide that contains post-installation and configuration content that pertains to setting up the Oracle Business Intelligence Server (Oracle BI Server). The guide discusses how to plan, create, and administer the Physical, Business Model and Mapping, and Presentation layers in the Oracle BI Repository. The guide primarily covers tasks that are performed in the Oracle BI Administration Tool utility. This guide provides post-installation configuration and administration procedures for Oracle BI Presentation Services, Oracle BI Answers, Oracle BI Delivers, Oracle BI Interactive Dashboards, and the Oracle BI Presentation Catalog and Catalog Manager. Additionally, the guide discusses Oracle BI Presentation Services security, logging, user interface, and integrations using HTTP. This guide is for Oracle BI report and dashboard designers and end users of Fusion Intelligence applications.
Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide
xii
Description This guide describes the common concepts for Daily Business Intelligence. It describes the product architecture and provides information on the common dimensions, security considerations, and data summarization flow. It includes a consolidated setup checklist by page and provides detailed information on how to set up, maintain, and troubleshoot Daily Business Intelligence pages and reports. This guide provides you with information for using Fusion Intelligence applications, including dashboard content and flows. Refer to the About Documents for information about your release, including new features, new components, and installation information.
About Fusion Intelligence For E-Business Suite, Release 12.0 Also included are application-specific About Documents for Financials; Governance, Risk, and Compliance; Human Resources; Sales; and Supply Chain Management.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
xiii
data and you lose the ability to audit changes to your data. Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications. When you use Oracle Applications to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.
xiv
1
Introduction
This chapter gives an overview of the application, covering integrations, terminology, and architecture. This chapter covers the following topics: Overview of Fusion Intelligence For E-Business Suite Common Terminology Used in this Guide Subject Areas Architecture Repository Physical Layer Business Model and Mapping Layer Presentation Layer Oracle BI Presentation Services
Introduction 1-1
The applications contain prebuilt, role-based dashboards that help you quickly analyze key performance indicators, reports, and metrics to spot trends and determine if your area of the business is on track. The applications also provide a library of prebuilt reports, prompts, and filters that present data in interactive charts, graphs, and grids. From a dashboard or report, you can drill into the source data in the transaction processing application to view transaction details and take corrective action. Security rules ensure that personalized content is generated for specific users and roles. The dashboards are tailored for an end user's role in an organization. You can grant each role with access to specific objects, such as subject areas, dashboards, and reports. Additionally, you can control access to specific data rows by using secured dimensions. Fusion Intelligence applications include a single, prebuilt repository that contains the metadata that maps to intelligence areas in the DBI repository. The Oracle BI Repository consists of Physical, Business Model and Mapping, and Presentation metadata layers that contain common definitions of metrics, hierarchies, and calculations against the data. The servers, programs, and tools in OBIEE provide the infrastructure foundation for Fusion Intelligence applications. The metadata repository file, and dashboard and report catalog file, are objects in OBIEE. Oracle BI Answers, Delivers, and Interactive Dashboards are used to create the dashboards, requests, and business monitoring activity in the Fusion Intelligence applications.
A guided drill path is built into the analytic model so you can view aggregated data to understand trends. From summary reports, you can drill to detailed reports to investigate exceptions or problems. From there you can drill to the underlying transaction system to act upon the source data to resolve problems.
Note: This release of Fusion Intelligence supports only site-level
configuration of dashboards.
DBI Repository
Introduction 1-3
Term Dimensions
Description Represents the organization of logical columns (attributes) that belong to a single logical dimension table. Examples of dimensions are time periods, products, markets, customers, suppliers, promotion conditions, raw materials, manufacturing plants, transportation methods, media types, and time of day. In dimensions, you can organize attributes into hierarchical levels. These levels represent your business reporting requirements. Common dimensions contain a set of dimensional attributes that can be shared by all subject areas or marts. The Fusion Intelligence applications share 17 common dimensions:
Company Cost Center Currency Customer Financial Category Geography HR Organization Inventory Organization Item Ledger Manager Hierarchy Operating Unit Person
Term
Description
Facts
A logical collection of measures, or calculated data, such as the sum of salaries relating to workforce compensation. Facts can be specified in terms of dimensions. For example, you might want to determine the sum of revenue dollars for a given product in a given market over a given time period. Filters are built into requests and are used to limit the results that appear on a dashboard. A report that appears on a dashboard shows only those results that match the filter criteria. Filters are applied on a column-level basis. Certain filters inherit the values that users specify in dashboard prompts. A prompt is another kind of filter that can apply to all items in a dashboard. Some prompts, such as date or period, can be common to all dashboards. Other prompts, such as commodity, are unique to a specific dashboard. Prompts are synonymous with parameters. See: Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide, "Filtering Requests in Oracle BI Answers."
Folders
In the Oracle BI Presentation Services user interface, folders provide the ability to organize an Oracle BI Web Catalog and its contents, such as reports.
Introduction 1-5
Fusion Financials Intelligence For E-Business Suite Fusion Governance, Risk, and Compliance Intelligence Fusion Human Resources Intelligence For E-Business Suite Fusion Marketing and Sales Intelligence For E-Business Suite Fusion Supply Chain and Order Management Intelligence For E-Business Suite Fusion Procurement Intelligence For E-Business Suite Fusion Service Intelligence For E-Business Suite
Guided Navigation
A link to navigate to the transaction processing application, another dashboard, or a URL. This link can be set up to appear conditionally based on the results of a report or key performance indicator. Strategic business factors that are used for reporting. KPIs are designed to monitor performance on strategic business factors such as Revenue or Operating Margin. A component within the Oracle BI Enterprise Edition technology that is used to create ad hoc queries into an organization's data. Oracle BI Answers provide a set of graphical tools to create and execute requests for information. Requests can be saved in the form of reports, and shared, modified, formatted, or embedded in a dashboard.
Description A comprehensive suite of enterprise business intelligence products that contain the programs, servers, and tools to support broad, self-service access across the organization. OBIEE is the foundation for Fusion Intelligence For E-Business Suite applications. A proactive intelligence solution that provides business activity monitoring and alerting for out-of-tolerance situations to target owners and subscribers. Collections of content that are designed to meet the needs of particular user roles. A dashboard is the user interface that provides a knowledge worker with intuitive, interactive access to information that is actionable and dynamically personalized, based on the individual's role and identity. A collection of subject areas that are defined in the metadata repository layer. The building blocks of business intelligence dashboards. Requests (reports) are created by using Oracle BI Answers to retrieve and display an organization's data. Data can be displayed in a variety of graphical formats. Links can be established in the chart or table of a report to launch another report to offer guided analysis. A data warehouse schema in which a fact table is associated with a series of dimension tables.
Oracle Business Intelligence Presentation Catalog (Oracle BI Presentation Catalog) Requests (Reports)
Star Schema
Subject Areas
This section provides an overview of the delivered Presentation catalogs (which are also called subject areas) in Fusion Intelligence applications. When you click the Answers link from any location in a Fusion Intelligence application, the Oracle Answers start page appears with a list of subject areas in the workspace. A subject area contains columns and filters that represent information about the areas of
Introduction 1-7
your organization's business, or about groups of users within your organization. The metadata in Fusion Intelligence subject areas maps to data that is stored in these intelligence areas in the DBI repository: Financials Intelligence Regulatory Compliance Intelligence Human Resources Intelligence Supply Chain Intelligence Procurement Intelligence Customer Support Intelligence Sales Intelligence
Note: To fully understand subject areas, familiarize yourself with the
Fusion Intelligence For E-Business Suite provides insight into information in these subject areas, which are grouped by intelligence area:
Subject Areas Intelligence Area Fusion Financials Intelligence Subject Area Folders Payables Operations Analysis Profit and Loss Analysis Receivables Operations Analysis Fusion Governance, Risk, and Compliance Intelligence Fusion Human Resources Intelligence Financial Statement Certifications
Intelligence Area Fusion Service Intelligence Fusion Supply Chain and Order Management Intelligence
Subject Area Folders Customer Support Catalog Inventory Catalog Manufacturing Catalog Order Booking and Fulfillment Catalog Product Margin Catalog Quality Catalog
Architecture
This diagram depicts the relationship between the Oracle DBI repository, Oracle BI components such as Oracle Answers, Oracle Delivers, and the Administration Tool, and interactive dashboards such as the ones in Fusion Intelligence applications:
Introduction 1-9
Repository
Prebuilt metadata content is maintained in the metadata repository file named EBSAnalyticMaster.rpd that is shared by all Fusion Intelligence For E-Business Suite applications. The repository contains the Physical, Business Model and Mapping, and Presentation layers that are discussed in the following sections. The Oracle BI Administration Tool is the user interface into the layers in the repository, as shown in this example:
Physical Layer
A Physical table is an object in the Physical layer of the Oracle BI Administration Tool that corresponds to an object in a Physical database. The Physical layer folder stores the shortcuts (references) to physical tables. Physical tables are typically imported from a database or another data source, and they provide the metadata necessary for the Oracle BI Server to access the tables. The Physical layer represents the physical structure of the data sources to which the Oracle BI Server submits queries.
Introduction 1-11
fact tables for PROCESS_DETAIL, ORG-CERT_SUMMARY, PROC_CERT_SUMMARY, and ORG_PROC_DEFICIENCY. The logical display folder should contain all of the dimensions and facts that are required for the given star schema. This is an example of the star schema for the Financial Certification Result logical folder:
Financial Certification Result Star Schema
Dimensional Hierarchies
Many of the results that appear in Fusion Intelligence applications represent hierarchical data structures. A hierarchy is a set of parent-child relationships between certain attributes within a dimension. The hierarchy attributes, called levels, roll up from child to parent. For example, months can roll up to years. Therefore, if an aggregate table exists at the month level, that table can be used to answer questions at the year level by summing all of the month-level data for a year. Fusion Intelligence applications deliver metadata with prebuilt hierarchies.
Presentation Layer
The Presentation layer represents subject areas in Fusion Intelligence applications. This layer provides a way to present a customized view of a business model, known as Presentation catalog, to different sets of users. The Presentation layer appears in the left pane of the Oracle BI Administration Tool. For each subject area that appears in the Oracle Answers pane, dimensions appear at the top followed by facts. The Presentation layer simplifies the business model and makes it easy for users to understand and query. It exposes only the data that is meaningful to the users, and organizes the data in a way that aligns with the way that users think about the data. Each subject area must be populated with contents from a single business model; the contents cannot span business models. The name of the subject area is the same as the corresponding logical display folder.
See: Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide.
Oracle BI Answers
Oracle BI Answers is a user interface that is part of the Oracle BI Presentation Services component of OBIEE. Oracle BI Answers is the embedded reporting tool that allows users with the appropriate permissions to build and modify reports that let end users explore and interact with information, and drill to source data. You can access these reports either from the delivered dashboards, or from the Oracle Answers Catalog pane on the Oracle Answers page. On the Oracle Answers page, you can also access the subject area folders that coincide with Oracle BI Presentation Catalog folders. The fact and dimension folders and columns appear in a subject area folder, just as they do in the Presentation Catalog. See: Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide, "Basics of Working with Requests in Oracle BI Answers."
Oracle BI Dashboards
Oracle BI Dashboards is another user interface that is part of the Oracle BI Presentation Services component of OBIEE. Interactive Dashboards provide points of access for analytics information. A dashboard is made up of sections of information that can contain items such as results from Oracle BI Answers, external Web content, HTML text, graphics, and links to other dashboards. Dashboard content is logically organized into pages. The pages appear as tabs across the top of the screen in Oracle BI Interactive Dashboards. A dashboard page is designed to meet the needs of a particular role. For example, the Financial Performance Trend dashboard page is designed for financial executives and managers who want to analyze historical performance for various financial items on a periodic basis. To access a dashboard, your EBS Responsibility Key must be assigned to the appropriate Presentation Catalog group in OBIEE. Your EBS application security settings determine the data that you can see on each dashboard. For example, procurement managers can view purchases only for the operating units for which they
Introduction 1-13
are responsible. Every dashboard or report can have a set of prompts that determine the data that appears. When you change the value of a prompt on a dashboard, and click the Go button, the system automatically refreshes the data on the dashboard. Changing a prompt can affect the amount of data, the column headings, the KPI values, and the graph formats. See: Oracle Business Intelligence Answers, Delivers, and Interactive Dashboards User Guide, "Using Oracle BI Interactive Dashboards."
Web Catalog
The Oracle BI Web Catalog stores the application dashboards and report definitions, and contains information regarding permissions and accessibility of the dashboards by groups. Prebuilt web catalog content is maintained in a folder called EBSAnalyticMaster, which the instanceconfig.xml file references.
2
Set Up Fusion Intelligence
This chapter discusses setups required to use Fusion Intelligence for E-Business Suite, including Daily Business Intelligence setups and configuration of OBIEE and the BI Server. This chapter covers the following topics: Prerequisites Set Up Daily Business Intelligence Configure OBIEE
Prerequisites
The following software is required to use Fusion Intelligence For E-Business Suite applications. You must complete the installation of this software before you implement Fusion Intelligence For E-Business Suite applications: Oracle Daily Business Intelligence, release 12. Oracle Business Intelligence Enterprise Edition, release 10.1.3.2.
Even if Daily Business Intelligence is already installed, for Fusion Procurement Intelligence, you must run Load Item Dimension Hierarchy. This creates new columns in the ENI_OLTP_ITEM_STAR table for Procurement Intelligence.
Verify hardware and software prerequisites. Create an implementation plan. Assign responsibilities to implementers.
Note: New responsibilities are delivered with OBIEE.
Set up multiple organization architecture. Set up global parameters. Administer dashboards and reports. Set up geography dimension. Set up operating unit security. Upgrade item dimension. Set up the product catalog hierarchy. Run DBI item dimension setup request set. Define source ledger group. Define financial dimensions. Manage dimension values and hierarchies. Set up budgets and forecasts. Set up security for general ledger and expense reporting data. Set up general ledger profile options. Set up payables profile options. Set up inventory organization security. Set up users as employees. Review POA: DBI implementation profile options. Set up document views. Set up commodities.
Set up DBI for financials profile options and source ledger group assignment. Set DBI for sales profile options. Run initial load of opportunity log tables concurrent program. Set up sales group hierarchy for DBI for service contracts. Determine collection start date. Set up financial category dimension. Synchronize financial data. Map financial accounts. Set up item dimension. Set OM: DBI installation profile option. Associate item with inventory category set, product category set. Ensure complete subledger postings. Set reporting units of measure. Set up resource groups. Identify time based resources. Identify the unit of measure representing hours. Set baseline plan. Set up request type security. Set up the planning instance. Set up Oracle Process Manufacturing resource warehouses (required for the Manufacturing catalog). Run plans in Oracle Advanced Supply Chain Planning (required for the Manufacturing catalog).
This is a summary of the post setup steps: Update sales group and district hierarchies. Create initial and incremental request sets for the installed dashboards.
Run initial request set for the installed dashboards. Set up users, including the new Fusion Intelligence responsibilities. Schedule incremental request sets.
Configure OBIEE
A major feature of Fusion Intelligence applications is the establishment of a security bridge between Oracle E-Business Suite applications and OBIEE to allow a single login for transactional pages and analytic dashboards. To support this, the Oracle BI Presentation Server uses an external authentication mechanism, which allows the Oracle BI Presentation Server to collect parameters from HTTP queries, HTTP cookies, and HTTP headers, and submit these to the Oracle BI Server. Users are required to log in through E-Business Suite.
Configuration Steps
These are the high level steps that are required to configure OBIEE for Fusion Intelligence applications: Update the Oracle BI Server configuration file. Initialize static repository variables. Set the password property for connection pools. Update the Oracle BI Presentation Server configuration file. Specify the Oracle BI Presentation Server URL profile option value. Start/restart Oracle BI Services.
EBSAnalyticMaster.rpd repository file: Star = EBSAnalyticMaster.rpd, DEFAULT; Initialization Blocks The system uses initialization blocks to initialize dynamic repository variables, system session variables, and non-system session variables. These initialization blocks have been created for authentication:
Name FndGetSecContext Purpose Used to set the EBS security context. Session Variables RESP_ID RESP_APPL_ID SEC_GROUP_ID RESP_NAME EMPLOYEE_ID USER USER_ID FndGetResp Used to map OBIEE Admin group context to EBS responsibility context. GROUP
See: Oracle Business Intelligence Server Administration Guide, "Creating and Administering the Physical Layer in an Oracle BI Repository," Setting Up Connection Pools. Repository Variables The following static repository variables have been created in the Fusion Intelligence application: Static_DSN_OLTP: Refers to the user's data source for connecting to the Fusion Intelligence database. The EBS_Authentication_Pool and EBS_Query_Pool connection pools use this value to connect to the database. Static_USER_ID: Refers to the APPS user ID that is used to connect to the Fusion Intelligence database.
After installation of the Fusion Intelligence application, the Administrator must: Go to the Variable Manager in the Oracle BI Administration tool and update the Default Initializer values for the above repository variables to supply the
connection information for the Fusion Intelligence transactional database. Update the APPS password to connect to the Fusion Business Intelligence database by setting the password property in the Physical layer of the repository for both the EBS_Authentication_Pool and EBS_Query_Pool connection pools.
Session Variables Session variables are created and assigned a value when each user logs on. They obtain their values from initialization blocks and are primarily used when authenticating users against external sources, such as the FND security model. The following session variables have been created to authenticate Fusion Intelligence application users and match the OBIEE security context to the E-Business Suite security context:
OBIEE Session Variable Name USER GROUP USER_ID RESP_ID RESP_NAME SEC_GROUP_ID EMPLOYEE_ID Oracle Applications Variable Name USER_NAME N/A USER_ID RESP_ID RESP_NAME SEC_GROUP_ID EMPLOYEE_ID Initialization Block
Connection Pools In Fusion Intelligence applications, the DBI repository provides the data source for the Physical layer. A Physical layer can have multiple data sources. Each data source must have at least one corresponding connection pool, which contains data source information that the system uses to connect to a data source, the number of connections allowed, timeout information, and other connectivity-related administrative details. Connection pools allow multiple concurrent data source requests (queries) to share a single database connection, reducing the overhead of connecting to a database. Oracle delivers two connection poolsEBS_Query_Pool and EBS_Authentication_Pool. The EBS_Query_Pool connection pool is used by Presentation Services queries. The default properties are:
Property Name Call Interface Data Source Name Shared Logon User Name Password Enable Connection Pooling Parameters Supported
Value EBS_Query_Pool Default (OCI 8i/9i) VALUEOF(Static_DSN_OLTP) Yes VALUEOF(Static_USER_ID) <user specified> Yes No
For performance reasons, the system uses the EBS_Authentication_Pool connection pool exclusively for authentication initialization blocks. The default properties are:
Property Name Call Interface Data Source Name Shared Logon User Name Password Enable Connection Pooling Parameters Supported Value EBS_Authentication_Pool OCI 8i/9i VALUEOF(Static_DSN_OLTP) Yes VALUEOF(Static_USER_ID) <user specified> Yes Yes
The EBS_Authentication_Pool has been set up to validate the user's EBS session and to apply the appropriate Oracle Application's security context within the OBIEE layer.
The EBS_Query_Pool and EBS_Authentication_Pool connection pools refer to the Static_DSN_OLTP and Static_USER_ID static repository variables. The Administrator must: Update these variables in the Variable Manager to match to the Fusion Intelligence application database and Oracle Applications APPS user ID, as documented in the Repository Variables section above. Update the password property for each connection pool to match the Oracle Applications APPS password. The password value will be encrypted.
Oracle BI Presentation Server URL Fusion Intelligence applications use one EBS profile optionFND: Oracle Business Intelligence Suite EE base URL. The profile option is used by the OracleOasis.jsp logic to build the Presentation Services URL.
Upon installation, the installer must set the value using the format <protocol>://<machine.domain>.<port> to point to the machine where the Oracle BI Presentation Services server is installed; for example, http://yourname.oracle.com:8080. You can configure this profile at any level. Because cookies are used to authenticate the EBS session within the OBIEE layer, OBIEE and EBS must reside in the same cookie domain. Also, the above profile option should include the full domain to build the Presentation Services URL. Using the ipaddress in the URL will not allow the browser to pass the cookie value to the OBIEE layer.
Cache Management
For this release of the OBIEE, if you run an initial or incremental load without first clearing the query cache, it is possible that reports that you run after the load process will reuse the cache that existed prior to the load process. This can result in inconsistencies between reports. There are several alternatives to mitigate this situation, such as: Configure the query cache to expire daily. Clear the cache tables manually as needed; for example, after you complete a load process. Schedule the system to clear the cache tables at the same frequency as the incremental load process.
Open the Oracle BI Administration Tool in online mode. Click Manage, Cache to access the Cache Manager page and select all cache entries. Click Action, Refresh.
Locate this configuration file: <root directory>\OracleBI\server\Config\NQSConfig.INI. In the Query Result Cache Section, change the [ CACHE ] setting from ENABLE = YES; to ENABLE = NO;. Save the NQSConfig.INI configuration file and restart the Oracle BI Server service.
2.
3.
See: Oracle Business Intelligence Server Administration Guide, "Query Caching in the OracleBI Server" chapter for more information on query caching in OBIEE.
3
Security
This chapter discusses the security configurations and new seeded BI responsibilities used in Fusion Intelligence for E-Business Suite. This chapter covers the following topics: Security Overview Responsibilities Menus and Functions
Security Overview
Security in Fusion Intelligence applications can be broadly classified into three configuration types---user authentication, dashboard object security, and data access security. All three configuration types play a vital role in securing data. This table discusses the security configurations that are delivered with Fusion Intelligence For E-Business Suite applications:
Security Configurations Security Configuration User authentication Description Users access Fusion Intelligence applications by signing on to Oracle E-Business Suite and navigating directly to Fusion Intelligence dashboards, without encountering a secondary signon page for Fusion Intelligence. The system leverages the existing Oracle Applications FND security model to authenticate users and permit access to Oracle Applications, including Fusion Intelligence applications, with a single user signon.
Security 3-1
Description The user's membership in Oracle BI Server groups controls the user's access to Oracle BI Administration Tool objects, such as subject areas, presentation tables, and presentation table columns in the repository. The user's membership in Presentation Catalog groups controls the user's access to Oracle BI Presentation Catalog objects, such as dashboards, reports, and catalog folders. When a user logs into the system, and the user's EBS responsibility matches an Oracle BI Server group or Presentation Catalog group, the system automatically assigns the appropriate object permissions to the user. This release of Fusion Intelligence applications delivers Oracle BI Server groups and Presentation Catalog groups that match delivered EBS responsibilities for Fusion Intelligence content. Object security is assigned in Fusion Intelligence applications to the predefined groups.
Description EBS secures dimension and fact table data using the FND user context, responsibility context, or a combination of the two. The system maintains existing data security that is defined in EBS when users access the same data in OBIEE. As with user security, the FND security model leverages existing data security with VPD, RBAC and/or MOAC in the EBS application. You can establish additional data security between Fusion Intelligence applications and Oracle online transaction applications by creating Oracle BI Server groups in the BI Administration Tool that match user responsibilities in EBS. When a user navigates to a report, the data that appears is based on permissions that are granted to the user's responsibilities, and any additional group filters and restrictive conditions that are applied to the Oracle BI Server group. When an Oracle BI Server group maps exactly to a Presentation Catalog group, the Presentation Catalog group inherits the permissions from the Oracle BI Server group. The system does not require that every Oracle BI Server group map exactly to a Presentation Catalog group.
Responsibilities
A user's role in the organization controls the user's access to objects (such as dashboards, reports, and catalog folders) in the Oracle BI Presentation Catalog. Presentation Catalog groups are defined by the system or by an administrator. For this release of Fusion Intelligence, the supported setup is for the user's assignment to EBS responsibilities to filter through to the OBIEE layers. Security on users is not suggested in OBIEE for this release of Fusion Intelligence. Several new business intelligence responsibilities are seeded in Oracle applications for Fusion Intelligence. Matching responsibilities with the same RESPONSIBILITY_KEY (to support translation) are created in the BI Server repository file. You can create new responsibilities; however, you must also set up a matching Oracle BI Server group and Presentation Catalog group, and assign permissions to the appropriate subject areas and Presentation Catalog objects.
Security 3-3
This table lists the delivered sample Presentation Catalog groups and the subject areas that users in those groups can access:
Delivered Sample Presentation Catalog Groups and Business Areas EBS Responsibility Financial Statement Analysis Payables Operations Analysis Profit and Loss Analysis Receivables Operations Analysis Customer Support Manager Department Manager Catalog Group RCI_OBIEE_FINSTM TCERT FII_OBIEE_AP_RESP Subject Area Financial Statement Certifications Payables Operations Analysis Profit and Loss Analysis Receivables Operations Analysis Customer Support Catalog Workforce Management (Organization) Workforce Management (Manager) Workforce Management (Organization) Workforce Management (Manager) Procurement Catalog Shared Folder Compliance Intelligence Financials Intelligence Financials Intelligence Financials Intelligence Human Capital Intelligence Human Capital Intelligence
FII_OBIEE_PL_RESP
FII_OBIEE_AR_RESP
Human Capital Management Analyst (Manager) Human Capital Management Analyst (Organization) Line Manager
HRI_OBIEE_WRKFC _MGRH
HRI_OBIEE_WRKFC _ORGH
HRI_OBI_ALL_MGR H
POA_DBI_VP_PROC
ISC_QT_DBIEE_QUA LITY
Quality Catalog
EBS Responsibility Supply Chain Manager Supply Chain Manager Supply Chain Manager Supply Chain Manager Sales Analysis
Shared Folder Supply Chain Intelligence Supply Chain Intelligence Supply Chain Intelligence Supply Chain Intelligence None
ISC_DBI_VP_OPS
Manufacturing Catalog Order Booking and Fulfillment Catalog Product Margin Catalog Sales Intelligence
ISC_DBI_VP_OPS
ISC_DBI_VP_OPS
Oracle BI Administrators
The BIS_OBIEE_ADMIN security group in OBIEE corresponds to the Oracle Business Intelligence Administrator responsibility in EBS. There are two menu options for this responsibilityOracle BI Answers and Oracle BI Dashboards. As part of setup, if you enable integration with EBS, you must assign this responsibility to users who administer the Oracle BI Presentation Services. This responsibility has access to all web and repository content, such as shared folders, subject areas, and so on.
Users
You can create users using the traditional forms interfaces. These users are stored in the FND_USERS database table and do not need to be created in the OBIEE application.
Security 3-5
as a starting point for their work. As delivered, the content in Fusion Intelligence For E-Business Suite is set up with read-only access. Oracle discourages you from overwriting the delivered content. Instead, use it as a starting point to create company-specific dashboards and answers.
4
Fusion Financials Intelligence
This chapter discusses the three Fusion Financials Intelligence dashboards. This chapter covers the following topics: Prerequisites Understanding Fusion Financials Intelligence Profit and Loss Analysis Dashboard and Catalog Receivables Operations Analysis Catalog Payables Operations Analysis Catalog Securing Data
Prerequisites
Before you implement the Fusion Financials Intelligence For E-Business Suite application, you must implement Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete. Additional, catalog-specific prerequisites are discussed further in this chapter. See the Oracle Daily Business Intelligence Implementation Guide, "Daily Business Intelligence for Financials" for more information.
users to view aggregated data and understand trends. This application also offers a prebuilt dashboard and accompanying reports, providing an at-a-glance analysis of profit and loss by company and cost center. This information helps managers stay informed, empowering them to track whether the company's revenue, cost of goods sold, and expenses are meeting the forecasted and budgeted amounts, and how well the company is meeting financial goals. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the intelligence catalogs.
Select the dimensions that you want to use in your ad hoc report. Select Filters. Select Company Cost Center Security Filter. Click OK to reference the filter into your report.
On the Company Cost Center Security Filter screen, you can check either of two option boxes: Clear all existing filters before applying: This removes any filters that you have already applied previously. Apply contents of filter instead of a reference to the filter: This adds the filter itself to your query rather than referencing it. If you later make changes to the Company Cost Center Security Filter, those changes will not be applied to this query.
Implementation Tasks
The Profit and Loss Analysis dashboard and catalog share the same set up steps with Oracle Daily Business Intelligence for Financials: Profit and Loss Analysis, release 12.
Implementation Tasks
The Receivables Operations Analysis catalog shares most of the same setup steps with Oracle Daily Business Intelligence for Financials: Receivables Reporting, release 12, with one exceptionthe Receivables Intelligence Setup page. The Receivables Intelligence Setup page has two parts: Data Collection Selection Criteria Days Sales Outstanding Definition
The Receivables Intelligence Setup page has limited impact on the Receivables Operations Analysis catalog in the following ways: The Data Collection Selection Criteria affects the following dimensions in the Receivables Operations Analysis catalog: Time - Transaction Filter Date Time - Receipt Filter Date Time - Transaction Date Time - Receipt Date
The Days Sales Outstanding Definition affects the Open Receivables and Receipts Summary fact - Billed Amount measure in the Receivables Operations Analysis catalog.
Implementation Tasks
The Payables Operations Analysis catalog shares the same setup steps with Oracle Daily Business Intelligence for Financials: Payables Reporting, release 12.
Securing Data
These responsibilities are set up as Oracle BI Server groups and Oracle Presentation Catalog groups, and delivered with the Fusion Financials Intelligence application: FII_OBIEE_AP_RESP - Use this group to access the Payables Operations Analysis catalog. FII_OBIEE_PL_RESP - Use this group to access the Profit and Loss Analysis catalog. FII_OBIEE_AR_RESP - Use this group to access the Receivables Operations Analysis catalog.
5
Fusion Governance, Risk, and Compliance Intelligence
This chapter discusses Fusion Governance, Risk, and Compliance Intelligence. This chapter covers the following topics: Prerequisites Understanding Fusion Governance, Risk, and Compliance Intelligence Securing Data
Prerequisites
Before you implement Fusion Governance, Risk, and Compliance Intelligence and the Financial Statement Certifications dashboard, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle's E-Business Suite online transaction applications, release 12, that supply compliance data to the DBI repository.
Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the Financial Statement Certifications Catalog.
Securing Data
The responsibility named Financial Statement Certification Analysis (RCI_OBIEE_FINSTMTCERT) is set up as an Oracle BI Server group and Oracle Presentation Catalog group. These security groups are delivered with the Fusion Governance, Risk, and Compliance Intelligence application. See: Oracle Applications System Administrator's Guide - Security.
6
Fusion Human Resources Intelligence
This chapter discusses the Human Capital Management (Manager) dashboard. This chapter covers the following topics: Prerequisites Understanding Fusion Human Resources Intelligence Human Capital Management (Manager) Dashboard Securing Data Implementation Tasks System Profiles Additional Setup Tasks
Prerequisites
Before you implement the Fusion Human Resources Intelligence For E-Business Suite application, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle Daily Business Intelligence, release 12. Oracle's E-Business Suite online transaction applications, release 12, that supply data to the DBI repository.
Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
self-service management reporting for executives and managers dealing with workforce, absence, salary, and recruitment. Using this tool, you can generate standard reports with multiple options to monitor enterprise activities. The Fusion Human Resources Intelligence For E-Business Suite application contains metadata that maps to the Oracle DBI repository. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the Workforce Management (Manager) Catalog and Workforce Management (Organization) Catalog.
See the Oracle Fusion Intelligence for E-Business Suite User Guide for more details.
Securing Data
These responsibilities are set up as Oracle BI Server groups and Oracle Presentation Catalog groups, and delivered with the Fusion Human Resources Intelligence application: HRI_OBI_ALL_MGRH - Use this group to access the Workforce Management (Manager) catalog using the Line Manager responsibility. HRI_OBI_ALL_ORGH - Use this group to access the Workforce Management (Organization) catalog using the Department Manager responsibility. HRI_OBIEE_WRKFC_MGRH - Use this group to access the Workforce Management (Manager) catalog using the Human Capital Management Analyst (Manager) responsibility.
HRI_OBIEE_WRKFC_ORGH - Use this group to access the Workforce Management (Organization) catalog using the Human Capital Management Analyst (Organization) responsibility.
See: Oracle Business Intelligence Server Administration Guide, "Security in Oracle BI." Fusion Human Resources Intelligence uses organization security or supervisor security to determine users' access to the workforce data at the organization and manager level. As part of your implementation plan, identify who will use Fusion Human Resources Intelligence and the information that they require, and determine the security method that you want to use.
Supervisor-Based Security
With supervisor-based security, you can restrict a manager's security permissions so that the manager can only access the records for those workers within a manager hierarchy. This restriction enables secure, reliable data access, and ensures that only people with the correct permissions can access data. Managers cannot view information about their supervisor or peer managers. You define supervisor-based security when you set up the supervisor hierarchy in Oracle Human Resources. Fusion Human Resources Intelligence supports the following responsibilities to implement supervisor-based security: Line Manager: Assign this responsibility to enable managers to view data of their reports. When managers log in with this responsibility, Fusion Human Resources Intelligence uses the person defined in the Users window to determine which data to display. Human Capital Management Analyst (Manager): Assign this responsibility to users to analyze data at the manager level..
Note: Ensure that you set the HRI: HCM Analyst (Manager View) Top
Supervisor-Based Security Example A. Mathew is the Recruitment Manager in Staffing Inc. You need to set up Fusion Human Resources Intelligence access for A. Mathew to enable him to: View details of workers who report to him. View recruitment data in the Staffing Inc organization so that he can analyze recruitment processes. C. Reed is the VP of Staffing Inc organization.
Assign the Line Manager responsibility to A. Mathew to enable him to access the
Assign the Human Capital Management Analyst (Manager) responsibility to A. Mathew and set the HRI: HCM Analyst (Manager View) Top profile option value to C. Reed at the user level. With this setting, A. Mathew can access C. Reed's manager hierarchy.
Organization-Based Security
With organization-based security, you can restrict a user's security permissions so that the user can only access the records for those workers within an organization hierarchy. Fusion Human Resources Intelligence supplies the following organization responsibilities and user profiles to implement organization-based security: Department Manager: Assign this responsibility to line managers to enable them to view information of their departments or organizations. The profile that you set for this responsibility is HRI: Line Manager (Organization View) Top at the user level. Human Capital Management Analyst (Organization): Assign this responsibility to users for the purpose of data analysis at the organization level. Set the HRI: HCM Analyst (Organization View) Top profile for this responsibility at the responsibility or user level.
Organization-Based Security Example 1: Restricting Managers' Access to Their Departments In Vision Corporation, C. Ray manages the Sales department and F. Lee manages the Finance department. You need to restrict the managers' access to their relevant departments. To set up the organization security, complete the following steps:
1. 2.
Assign the Department Manager responsibility to users: C. Ray and F. Lee. Set the HRI: Line Manager (Organization View) Top profile option for C. Ray and F. Lee at the user level, selecting their respective organizations.
Organization-Based Security Example 2: Setting Up Organization Security for a Single User A. Harris is the Human Resources Manager for Vision Corporation and needs to analyze workforce information. To enable him to complete the task:
1.
Assign the Human Capital Management Analyst (Organization) responsibility to A. Harris. Set the profile option HRI: HCM Analyst (Organization View) Top to Vision Corporation at the user level for A. Harris.
2.
In addition, to A. Harris, B. Brown (Benefits Manager), and C. Smith (Payroll Manager), need to access records in the Vision Corporation. To enable these managers to access Vision Corporation:
1.
Assign the Human Capital Management Analyst by Organization responsibility to the users. Set the profile option HRI: HCM Analyst (Organization View) Top to Vision Corporation at the responsibility level.
2.
Implementation Tasks
Perform the implementation steps that are discussed in this section to use Fusion Human Resources Intelligence.
Enable reports by using the Daily Business Intelligence Administrator responsibility, Administer Content page: Global, Administer Content. Query for Report and select the Human Resources functional area. See: Oracle Daily Business Intelligence Implementation Guide, "Set Up Daily Business Intelligence," Enable Dashboards and Reports.
Set Up Users
Set up users and assign appropriate responsibilities to enable them to use Fusion Human Resources Intelligence. Fusion Human Resources Intelligence delivers the following responsibilities: Responsibilities to view information by Manager hierarchy: Line Manager Human Capital Management Analyst (Manager)
When you set up users, you can also control the data that they can access by using system profile options delivered in Fusion Human Resources Intelligence. An analysis of your working practices will help you decide how to set up users and assign Fusion Human Resources Intelligence responsibilities and profiles based on the roles in your enterprise. Set up users by using the System Administrator responsibility, Users window: Security, User, Define. See: Oracle Daily Business Intelligence Implementation Guide, "Set Up Daily Business Intelligence," Set Up Users. See: Securing Data, page 6-2 for more information.
See: Oracle Daily Business Intelligence for HRMS Implementation Guide, "Deploy DBI for HRMS," Setting Up the Job Hierarchy.
Categorize Workers
Create the HRI_MAP_WORKER_TYPE formula to specify which person types you want to report on. See: Oracle Daily Business Intelligence for HRMS Implementation Guide, "Deploy DBI for HRMS," Categorizing Workers.
Create the formula using the Oracle Super HRMS Manager responsibility, Formula window: Total Compensation Basic, Write Formulas. See Setting Up the Promotion Formula, page 6-15.
TEMPLATE_HEAD BIS_DAYS_TO_HOURS BUDGET_FTE BUDGET_HEAD GLOBAL_BUDGET_FTE GLOBAL_BUDGET_HEAD HRI_MAP_WORKER_TYPE HR_MOVE_TYPE NORMALIZE_APPRAISAL_RATING NORMALIZE_REVIEW_RATING HRI_MAP_PROMOTION_EVENT HRI_MAP_REC_APPL_STATUS HRI_MAP_REC_APPL_TERM_TYPE PROMOTION
Compile the formulas using the Oracle Super HRMS Manager responsibility, Formula window: Total Compensation Basic, Write Formulas. See: Oracle HRMS FastFormula User Guide, "FastForward," Writing or Editing a Formula, which is available on the Oracle Applications Online Documentation CD.
Manage Multi-threading
If your system uses multi-processor machines, there are two profile options that you can use to manage multi-threading.
See: Oracle Daily Business Intelligence for HRMS Implementation Guide, "Deploy DBI for HRMS," Managing Multi-Threading.
See: Oracle Daily Business Intelligence for HRMS Implementation Guide, "Deploy DBI for HRMS," Running the Diagnostics Setup Reports.
Recruitment Analysis Subject Area (HRI_RECRUITMENT_SUBJECTAREA). Absence Analysis Subject Area (HRI_ABSENCE_SUBJECTAREA).
Important: If you implemented DBI for HR, you must also add all of the
DBI for HR dashboards when you generate request sets for Fusion Human Resources Intelligence.
See: Oracle Daily Business Intelligence Implementation Guide, "Set Up Daily Business Intelligence," Run Initial Request Sets. See also Appendix A Request Sets, page A-1
System Profiles
Use the System Administrator responsibility to check system profiles. Before you run the Fusion Human Resources Intelligence reports, check that the relevant system profiles are set up to suit your enterprise. To check the system profiles for Fusion Human Resources Intelligence reports: Use the System Profile Values window. In the Find System Profile Values window, find each of the following system profiles:
System Profiles Profile Name Description Default Value Configurable Levels Site
Set this profile option to Yes, if you use Oracle HRMS for recruitment purposes. This profile option enables Fusion Human Resources Intelligence to use the person defined in the Recruiter or the Raised By field of the Requisition and Vacancy window as a recruitment manager to collect recruitment data. If you use iRecruitment, then set this profile option to No.
Yes
Set this profile option to Yes if you want to use headcount measure to collect workforce values. Set this profile option to Yes if you want to use FTE measures to collect workforce values. Define whether Fusion Human Resources Intelligence populates the incremental update queue for the organization hierarchy events. The default value is Yes. DBI and Fusion Human Resources Intelligence customers must not set this profile option to No.
Yes
Site
Yes
Site
Yes
Site
Yes
Site
Profile Name
Description
Default Value
Indicate whether DBI has been installed. Select the organization hierarchy for Fusion Human Resources Intelligence to collect data on workforce measures. If you do not select the organization hierarchy, then Fusion Human Resources Intelligence uses the primary global organization hierarchy as the default hierarchy.
Yes
Site, Responsibility
HRI: Line Manager (Organization View) Top HRI: HCM Analyst (Organization View) Top HRI: Line Manager (Organization View) Top Select the organization that line managers can access to view Fusion Human Resources Intelligence data. You can set this profile option only for the Department Manager responsibility. See Securing Data, page 6-2.
User
Profile Name
Description
Default Value
Identify the organization that Fusion Human Resources Intelligence users can access to view reports. You can set this profile option only for the Human Capital Management Analyst (Organization) responsibility. When you set this profile option to a specific user, the recipient can log in to view the organization hierarchy data. You can set this profile option at the responsibility level to enable multiple users to access data of a specific organization hierarchy.
Identify the manager hierarchy that users can access to view Fusion Human Resources Intelligence reports. Set this profile to enable users to view other managers' reports. For example, Vincent Price (deputy sales manager) needs to view dashboard and reports as Nick Right (chief sales manager). You set the profile option value for Vincent Price to Nick Wright at the user level. If you want to set this profile option at the responsibility level, ensure that you set the profile for the Human Capital Management Analyst (Manager) responsibility.
Responsibility, User
For the Set Up business group, use your local HR Manager responsibility to navigate to the Formula window. Set your effective date to the date when you want to begin using the formula. Enter HRI_MAP_PROMOTION_EVENT as the formula's name. Select QuickPaint as formula type. Click the Edit button to open a blank Edit Formula window. Use the following sample formula as a guide. Evaluate each promotion to decide whether you want to include the promotion in the Fusion Human Resources Intelligence promotion reports.
2. 3. 4. 5. 6.
When you finish writing the formula, click the Verify button to compile it.
When the formula is verified successfully, save it. Information About the Promotion FastFormula The PROMOTION formula determines whether or not an employee has received a promotion using the assignment change reason. To create the PROMOTION formula, you must copy the systems default promotions functionality from the PROMOTION_TEMPLATE formula and configure it accordingly. To use different criteria for promotion, add the required codes in the EMP_ASSIGN_REASON look up type. For example, you can add change reasons such as HQ Move, Position Change as criteria for promotion so that the formula records a promotion when there is a change reason of Promotion, HQ Move, or Position Change. The formula returns a count of 1 if a promotion occurs according to the rules, and a count of 0 if there is no promotion.
the recruitment events that you want Fusion Human Resources Intelligence to report on as lookup codes to the HRI_REC_PIPLN_EVENTS lookup type. For example, to report on metrics related to third interview, add this event as a lookup code.
See: Oracle HRMS Configuring, Reporting, and System Administration Guide, "Extending Oracle HRMS," User and Extensible Lookups, which is available on the Oracle Applications Online Documentation CD. To set up the recruitment status formula:
1.
For the Set Up business group, use your local HR Manager responsibility to navigate to the Formula window.
2. 3. 4. 5. 6.
Set your effective date to the date when you want to begin using the formula. Enter HRI_MAP_REC_APPL_STATUS as the formula's name. Select QuickPaint as formula type. Click the Edit button to open a blank Edit Formula window. Use the following sample formula as a guide. Evaluate each stage of the applicant to decide whether you want to include it in the Fusion Human Resources Intelligence recruitment reports.
Information About the Recruitment Status Formula Stage_code represents values that are defined in the HRI_REC_PIPLN_STAGES lookup type. Event_code represents values that are defined in the HRI_REC_PIPLN_EVENTS lookup type. When you finish writing the formula, click the Verify button to compile it. When the formula is verified successfully, save it.
For the Set Up business group, use your local HR Manager responsibility to navigate to the Formula window. Set your effective date to the date when you want to begin using the formula. Enter HRI_MAP_REC_APPL_TERM_TYPE as the formula's name. Select the user defined FastFormula type. Click the Edit button to open a blank Edit Formula window. Use the following sample formula as a guide. Evaluate termination reasons in the business group to decide whether you want to include the reasons in the Fusion Human Resources Intelligence recruitment reports.
2. 3. 4. 5. 6. 7.
When you finish writing the formula, click the Verify button to compile it. When the formula is verified successfully, save it.
7
Fusion Marketing and Sales Intelligence
This chapter discusses setting up the Fusion Marketing and Sales repository. For this release, no dashboards or reports are seeded or shipped. This chapter covers the following topics: Prerequisites Understanding Fusion Marketing and Sales Intelligence Responsibilities Implementation Considerations Securing Data
Prerequisites
Before you implement the Fusion Marketing and Sales Intelligence For E-Business Suite application, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle Daily Business Intelligence for Sales, release 12. Oracle's E-Business Suite online transaction applications, release 12, that supply data to the DBI repository.
See: Oracle Daily Business Intelligence Implementation Guide, "Daily Business Intelligence for Sales." Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
sales managers: Visibility into the pipeline of all active sales opportunities. Sales managers can track the value, probability of closing, and expected close date. An understanding of past activities that produced results. Sales managers can analyze potential sales by sales group, product catalog, date, and currency. The ability to repeat past successes. Managers can view projected amount, probability of closing the sale, and weighted amount for each opportunity. To accomplish this goal, sales managers need to track sales opportunities before they result in booked sales. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the Sales Intelligence Catalog.
Responsibilities
To access the Sales Intelligence subject area, log into the EBS application with the Sales Analysis responsibility. Users who are assigned the Sales Analysis responsibility are automatically assigned to the Sales Intelligence subject area. For more information, see the Security chapter, Responsibilities section, in the Oracle Fusion Intelligence for E-Business Suite Implementation Guide.
Implementation Considerations
This section discusses implementation considerations for Fusion Marketing and Sales Intelligence.
incremental request set. Therefore, create and run the OBIEE incremental request set only. If you use DBI, want to implement OBIEE, and want to view DBI and OBIEE reports simultaneously: The DBI request set consists of the Opportunity Management, Sales Management, and Forecast Management dashboards. You must recreate the DBI request set by adding the Sales Analysis subject area (report) in addition to the three dashboards. To view DBI and BI reports simultaneously, users have to run the recreated DBI incremental request set only.
Profile Options
Profile options remain the same as profile options in Sales DBI.
Request Sets
Request sets, when run, display data at the report level. Refer to Appendix A Request Sets, page A-1 to run the request set for the Sales Analysis subject area.
Securing Data
The Sales Group hierarchy determines the hierarchy of an organization's sales force. After authentication, users can view sales data rolled up to the Sales Group to which they belong. They can view data of assigned sales groups and subordinate sales groups. Users can drill into the sales group hierarchy to the fifth level. Based on the sales group hierarchy setup in the Resource Manager, users can traverse the hierarchy to analyze the performance of subordinates. Access to peer data is not allowed by the security model. The default value is the sales group of the logged in user, whose role is Manager. If there is more than one qualifying group, for the first login, the default sales group is the first sales group in the list. The default login for successive logins is the previous selected value.
Note: Because the Sales group hierarchy has rolled up and non-rolled
up data at any given level, building an answer starting at an arbitrary level other than Level1 can result in incorrect data. Always build an answer starting at Level1 (which automatically brings in the logged-in level).
8
Fusion Supply Chain and Order Management Intelligence
This chapter discusses Fusion Supply Chain and Order Management Intelligence dashboards and catalogs. This chapter covers the following topics: Prerequisites Understanding Fusion Supply Chain and Order Management Intelligence Implementation Considerations Securing Data
Prerequisites
Before you implement the Fusion Supply Chain and Order Management Intelligence E-Business Suite application, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle Daily Business Intelligence for Supply Chain, release 12. Oracle's E-Business Suite online transaction applications, release 12, that supply data to the DBI repository.
See: Oracle Daily Business Intelligence Implementation Guide, "Daily Business Intelligence for Supply Chain." Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
application delivers prebuilt dashboards with reports that provide an at-a-glance analysis of booking and fulfillment of orders, and manufacturing performance. This information helps managers keep track of key performance indicators such as booked value, fulfilled value, book to fulfill ratio, return value, plan adherence, production value, and scrap percentage. The Fusion Supply Chain and Order Management Intelligence For E-Business Suite application also contains metadata in the form of intelligence catalogs in the areas of order booking and fulfillment, manufacturing, inventory, product margin, and quality that maps primarily to DBI for Supply Chain in the Oracle DBI repository. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the intelligence catalogs.
Implementation Considerations
This section discusses implementation considerations for Fusion Supply Chain and Order Management Intelligence.
Inventory Subject Area Manufacturing Subject Area Margin Subject Area Order Booking and Fulfillment Analysis Subject Area Quality Subject Area
Enable reports by using the Daily Business Intelligence Administrator responsibility, Administer Content page: Setup: Global, Administer Content. Search using Report and Supply Chain functional area. See: Oracle Daily Business Intelligence Implementation Guide, "Set Up Daily Business Intelligence," Enable Dashboards and Reports.
Securing Data
These responsibilities are set up as Oracle BI Server groups and Oracle Presentation Catalog groups, and delivered with the Fusion Supply Chain and Order Management Intelligence application: Supply Chain Manager (ISC_DBI_VP_OPS) - Use this group to access the Order Booking and Fulfillment Analysis and Manufacturing Analysis dashboards; Inventory, Manufacturing, Product Margin, and Order Booking and Fulfillment catalogs. Quality Intelligence (ISC_QT_DBIEE_QUALITY) - Use this group to access the Quality catalog.
Fusion Supply Chain and Order Management dashboards and catalogs are secured by the Inventory Organization dimension. The Quality catalog has role-based security based only on the responsibility Quality Intelligence. As quality analysis normally requires a broad set of business-wide data, this role has access to manufacturing scrap, customer returns, and procurement returns and rejections data from all organizations. See: Oracle Applications System Administrator's Guide - Security.
9
Fusion Procurement Intelligence
This chapter discusses the Procurement Analysis dashboard and the Procurement Catalog. This chapter covers the following topics: Prerequisites Understanding Fusion Procurement Intelligence Implementation Considerations Securing Data
Prerequisites
Before you implement the Fusion Procurement Intelligence For E-Business Suite application, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle Daily Business Intelligence for Procurement, release 12. Oracle's E-Business Suite online transaction applications, release 12, that supply data to the DBI repository.
See: Oracle Daily Business Intelligence Implementation Guide, "Daily Business Intelligence for Procurement." Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
measuring procurement performance. This information helps managers keep track of how effectively the procurement process is running. The Fusion Procurement Intelligence For E-Business Suite application also contains metadata in the form of an intelligence catalog called the Procurement catalog that maps to requisitions, purchases, receipts, and spend facts in the Oracle DBI repository. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the Procurement catalog.
Implementation Considerations
This section discusses implementation considerations for Fusion Procurement Intelligence.
Enable reports by using the Daily Business Intelligence Administrator responsibility, Administer Content page: Global, Administer Content. Query for Report and select the Procurement functional area. See: Oracle Daily Business Intelligence Implementation Guide, "Set Up Daily Business Intelligence," Enable Dashboards and Reports.
Securing Data
The responsibility named Procurement Manager Administration Group (POA_DBI_VP_PROC) is set up as an Oracle BI Server group and Oracle Presentation Catalog group. These security groups are delivered with the Fusion Procurement Intelligence application. The Fusion Procurement dashboard is secured by the Operating Unit. See: Oracle Applications System Administrator's Guide - Security.
10
Fusion Service Intelligence
This chapter discusses the Customer Support Catalog, which you can use to create reports and dashboards. This chapter covers the following topics: Prerequisites Understanding Fusion Service Intelligence Securing Data
Prerequisites
Before you implement the Fusion Service Intelligence For E-Business Suite application, you must implement: Oracle Business Intelligence Enterprise Edition, release 10.1.3.2. Oracle Daily Business Intelligence for Customer Support, release 12. Oracle's E-Business Suite online transaction applications, release 12, that supply data to the DBI repository.
See: Oracle Daily Business Intelligence Implementation Guide, "Daily Business Intelligence for Customer Support." Review About Fusion Intelligence For E-Business Suite, Release 12.0, which is available on OracleMetaLink, and ensure that all hardware and software prerequisites are complete.
Closure. Please see Appendix A in the Oracle Fusion Intelligence for E-Business Suite User Guide for a list of facts and dimensions that are contained in the Customer Support Catalog.
Securing Data
The BIV_DBI_CUST_SUPP_MGMT responsibility is set up as Oracle BI Server group and Oracle Presentation Catalog group, and delivered with the Fusion Service Intelligence application. Use this group to access the Customer Support Catalog. The Customer Support Catalog is secured by Request type. See: Oracle Applications System Administrator's Guide - Security.
A
Request Sets
This appendix lists the subject areas in Fusion Intelligence For E-Business Suite for which you can create request sets. This appendix covers the following topics: Steps to Generate Request Sets Generating Request Sets Data Loading Shared Data Sources
Navigate to Data Summarization: Request Sets, Administer Request Sets, Generate Request Set, Add Content. Search for report by functional area and select a subject area.
Note: Fusion Human Resources Intelligence uses multiple subject
2.
areas.
3.
Choose Clear and Load All Summaries to create an initial load; choose Incremental Load to create an incremental load.
Fusion Financials Intelligence Catalog Profit and Loss Analysis Report Name Profit and Loss Analysis Subject Area Profit and Loss Analysis Subject Area Details Receivables Operations Analysis Subject Area Payables Operations Analysis Subject Area Internal Name FII_GL_PL_ANALYSIS_SA
FII_GL_PL_DETAILS_SA
FII_AR_OPERATIONS_ANALYSIS_SA
FII_AP_OPERATIONS_ANALYSIS_SA
Fusion Governance, Risk, and Compliance Intelligence Catalog Financial Statement Certifications Report Name Financial Statement Certifications Subject Area Internal Name RCI_OBIEE_FNSTMTC_SUBAREA
Fusion Human Resources Intelligence Catalog Workforce Management (Manager) Workforce Management (Organization) Workforce Management (Manager) Workforce Management (Organization) Workforce Management (Manager) Workforce Management (Organization) Workforce Activity and Deployment Subject Area HRI_WORKFORCE_SUBJECTAREA Recruitment Analysis Subject Area HRI_RECRUITMENT_SUBJECTAREA Report Name Absence Analysis Subject Area Internal Name HRI_ABSENCE_SUBJECTAREA
Fusion Marketing and Sales Intelligence Catalog Sales Intelligence Report Name Sales Analysis Subject Area Internal Name BIL_OBI_SALES_SUBJECT_AREA
Fusion Supply Chain and Order Management Intelligence Catalog Inventory Catalog Report Name Inventory Subject Area Internal Name OPI_INVENTORY_SUBJECT_AREA
Report Name Manufacturing Subject Area Order Booking and Fulfillment Analysis Subject Area Margin Subject Area Quality Subject Area
ISC_ORDER_MGMT_SUBJECT_AREA
OPI_MARGIN_SUBJECT_AREA
ISC_QT_QUALITY_SUBJECTAREA
dashboard, run the request set for the Order Booking and Fulfillment Catalog.
Fusion Procurement Intelligence Catalog Procurement Catalog Report Name Procurement Subject Area Internal Name POA_PROCUREMENT_SUBJECT_AREA
Fusion Service Intelligence Catalog Customer Support Catalog Report Name Customer Support Subject Area Internal Name BIV_CS_SUBJECTAREA
Order Booking and Fulfillment Catalog Manufacturing Catalog Product Margin Catalog
Quality Catalog
If you installed and are using DBI, include the corresponding DBI dashboards in the initial and incremental loads. To find out which entities share common data sources, you can view DBI object dependencies screen under the Daily Business Intelligence Administrator responsibility.
Index
B
Business Model and Mapping layer, 1-11 Profit and Loss Analysis Dashboard and Catalog, 4-2 Receivables Operations Analysis Catalog, 4-3 securing data, 4-5 understanding, 4-1 Fusion Governance, Risk, and Compliance Intelligence prerequisites, 5-1 securing data, 5-2 understanding, 5-1 Fusion Human Resources Intelligence application termination reasons formula, 6-18 compiling formulas, 6-8 defining profile options, 6-6 generating request sets, 6-10 Human Capital Management (Manager) Dashboard, 6-2 implementation tasks, 6-5, 6-15 prerequisites, 6-1 promotion formula, 6-15 recruitment status formula, 6-16 securing data, 6-2 system profiles, 6-11 understanding, 6-1 Fusion Intelligence For E-Business Suite architecture, 1-9 integrations, 1-2 prerequisites, 2-1 understanding, 1-1 Fusion Marketing and Sales Intelligence generating request sets, 7-3 implementation considerations, 7-2 prerequisites, 7-1
C
connection pools, 2-5
D
Daily Business Intelligence setup, 2-1 database management, 2-9 data source, 2-5 DBI intelligence areas, 1-7 diagram Fusion Intelligence architecture, 1-9 Oracle BI Administration Tool, 1-11 star schema, 1-12 dimensions hierarchical dimensions, 1-12
E
EBS_Authentication_Pool, 2-7 EBS_Query_Pool, 2-6 EBSAnalyticMaster.rpd, 1-10
F
FND profile option, 2-8 functions, 3-6 Fusion Financials Intelligence implementation tasks, 4-3 Payables Operations Analysis Catalog, 4-4 prerequisites, 4-1, 4-3
Index-1
profile options, 7-3 responsibilities, 7-2 securing data, 7-3 understanding, 7-1 Fusion Procurement Intelligence implementation considerations, 9-2 prerequisites, 9-1 securing data, 9-3 understanding, 9-1 Fusion Service Intelligence prerequisites, 10-1 securing data, 10-2 understanding, 10-1 Fusion Supply Chain and Order Management Intelligence implementation considerations, 8-2 prerequisites, 8-1 understanding, 8-1 Fusion Supply Chain and Order Management Intelligence securing data, 8-3
repository file, 1-10 Oracle BI Answers, 1-13 Oracle BI Dashboards, 1-13 Oracle BI Presentation Server configuration file, 2-8 Oracle BI Presentation Server Configuration, 2-8 Oracle BI Presentation Server URL, 2-8 Oracle BI Presentation Services Oracle BI Answers, 1-13 Oracle BI Dashboards, 1-13 web catalog, 1-14 Oracle BI Server Configuration, 2-4 OracleOasis.jsp, 2-8, 3-6
P
Physical layer, 1-11 prerequisites, 4-1, 4-3, 5-1, 6-1, 7-1, 8-1, 9-1, 10-1 Presentation layer, 1-12 profile options, 6-6 Profit and Loss Analysis Dashboard, 4-2
H
Human Capital Management (Manager) Dashboard, 6-2
R
Receivables Intelligence Setup page, 4-4 repository file, 1-10 repository variables, 2-5 request sets Fusion Financials Intelligence, A-1 Fusion Governance, Risk, and Compliance Intelligence, A-2 Fusion Human Resources Intelligence, 6-10 Fusion Marketing and Sales Intelligence, 7-3 Fusion Procurement Intelligence, A-4 Fusion Service Intelligence, A-4 Fusion Supply Chain and Order Management Intelligence, A-3 generating request sets, A-1 list of request sets, A-1 responsibilities, 3-3, 7-2
I
initialization blocks, 2-5 instanceconfig.xml, 1-14
M
menus, 3-6
N
NQSConfig.ini, 2-4
O
Oracle BI Administration Tool, 1-11 Business Model and Mapping layer, 1-11 cache management, 2-9 connection pools, 2-6 dimensional hierarchies, 1-12 initialization blocks, 2-5 Physical layer, 1-11 Presentation layer, 1-12
S
security data-level, 3-3 object-level, 3-2 responsibilities, 3-3 securing Fusion Financials Intelligence, 4-5
Index-2
securing Fusion Governance, Risk, and Compliance Intelligence, 5-2 securing Fusion Human Resources Intelligence, 6-2 securing Fusion Marketing and Sales Intelligence, 7-3 securing Fusion Procurement Intelligence, 9-3 securing Fusion Service Intelligence, 10-2 securing Fusion Supply Chain and Order Management Intelligence , 8-3 types, 3-1 user authentication, 3-1 session variables, 2-6 setup steps application termination reasons formula, 6-18 configuring OBIEE, 2-4 configuring Oracle BI Presentation Server, 2-8 configuring Oracle BI Server, 2-4 Daily Business Intelligence, 2-1 Fusion Human Resources Intelligence, 6-5 prerequisites, 2-1 promotion formula, 6-15 recruitment status formula, 6-16 Static_DSN_OLTP, 2-5 system profiles, 6-11
T
terminology, 1-3
W
web catalog, 1-14
Index-3