Oracle Business Intelligence Applications (OBIA 7.9.6.3) Details as of now from my knowledge

Oracle Business Intelligence Applications (OBIA) are complete, prebuilt BI solutions that deliver intuitive, role-based intelligence for everyone in an organization from front line employees to senior management that enable better decisions, actions, and business processes. Designed for heterogeneous environments, these solutions enable organizations to gain insight from a range of data sources and applications including Siebel, Oracle E-Business Suite, PeopleSoft, and third party systems such as SAP.

Oracle BI Applications are built on the Oracle BI Suite Enterprise Edition, a comprehensive, innovative, and leading BI platform. This enables organizations to realize the value of a packaged BI Application, such as rapid deployment, lower TCO, and built-in best practices, while also being able to very easily extend those solutions to meet their specific needs, or build completely custom BI applications, all on one common BI architecture.

Oracle BI Applications includes the following:
■ Oracle Financial Analytics
■ Oracle Human Resources Analytics
■ Oracle Supply Chain and Order Management Analytics
■ Oracle Procurement and Spend Analytics
■ Oracle Project Analytics
■ Oracle Sales Analytics
■ Oracle Service Analytics
■ Oracle Contact Center Telephony Analytics
■ Oracle Marketing Analytics
■ Oracle Loyalty Analytics
■ Oracle Price Analytics
and more

Oracle BI Applications is a prebuilt business intelligence solution.
Oracle BI Applications supports Oracle sources, such as Oracle E-Business Suite Applications, Oracle's Siebel Applications, Oracle's PeopleSoft Applications, Oracle's JD Edwards Applications, and non-Oracle sources, such as SAP Applications. If you already own one of the above applications, you can purchase Oracle Business Intelligence Enterprise Edition and Oracle BI Applications to work with the application.
Oracle BI Applications also provides complete support for enterprise data, including financial, supply chain, workforce, and procurement and spend sources. These enterprise applications typically source from both Oracle data sources, such as Oracle EBS and PeopleSoft and non-Oracle data sources, such as SAP


Topology for an Oracle BI Applications Deployment

Oracle BI Applications and Informatica PowerCenter can be deployed flexibly across a wide range of topologies on different platforms and combinations of platforms.



Machine A (Windows-only)
Machine A is a machine that has installed Oracle Business Intelligence Enterprise Edition, on which you run the Oracle BI Applications installer to install the Oracle BI Applications files.
Note: The instance of Oracle Business Intelligence Enterprise Edition does not need to be the functional version of Oracle Business Intelligence Enterprise Edition that you will use to deploy dashboards in your live system. This instance is only required to enable the Oracle BI Applications installer to install the Oracle BI Applications files on a machine
After the Oracle BI Applications files have been installed on Machine A, the DAC Client is installed on Machine B, and the DAC Server is installed on Machine C.
In addition, the following files are copied from the installation machine (Machine A) to the Business Intelligence Deployment Tier (Machine Group F) as follows:
- The OracleBI\Server\Repository\OracleBIAnalyticsApps.rpd file is copied from Machine A to the machine that runs the BI Server in Machine Group F.
- The OracleBIData\Web\Catalog\EnterpriseBusinessAnalytics\*.* files are copied from Machine A to the machine that runs the BI Presentation Services Catalog in Machine Group F.


• ETL Tier (Functional)
o Machine B (Windows-only)
Runs the DAC Client and Informatica PowerCenter Client Tools.
o Machine C (Windows, UNIX, Linux)
Runs the DAC Server and Informatica PowerCenter Services.
o Machine D (Windows, UNIX, Linux)
Hosts the transactional (OLTP) database.
o Machine E (Windows, UNIX, Linux)
Hosts the Oracle Business Analytics Warehouse database


• BI Deployment Tier (Functional)
The BI Deployment tier is used to deploy the business intelligence dashboards.
o Machine Group F (Windows, UNIX, Linux)
Machine Group F is a group of machines that runs the Oracle Business Intelligence Enterprise Edition components. For example, one machine might run the BI Server and another machine might run the BI Presentation Services


Oracle Business Analytics warehouse architecture when deployed with Informatica PowerCenter and DAC

High-level analytical queries, like those commonly used in Oracle Business Intelligence, scan and analyze large volumes of data using complex formulas. This process can take a long time when querying a transactional database, which impacts overall system performance.
For this reason, the Oracle Business Analytics Warehouse was constructed using dimensional modeling techniques to allow for fast access to information required for decision making. The Oracle Business Analytics Warehouse derives its data from operational applications and uses Informatica PowerCenter to extract, transform, and load data from various supported transactional database systems (OLTP) into the Oracle Business Analytics Warehouse.



• The Client tier contains the Informatica PowerCenter client tools and the Oracle BI Data Warehouse Administration Console (DAC). DAC is a command and control interface for the data warehouse to allow for set up, configuration, administration, and monitoring of data warehouse processes.

• The Server tier contains the following:
o DAC Server. Executes the instructions from the DAC Client. The DAC Server manages data warehouse processes, including scheduling, loading of the ETL, and configuring the subject areas to be loaded. It dynamically adjusts its actions based on information in the DAC Repository. Depending on your business needs, you might incrementally refresh the Oracle Business Analytics Warehouse once a day, once a week, once a month, or on another similar schedule.
o DAC Repository. Stores the metadata (semantics of the Oracle Business Analytics Warehouse) that represents the data warehouse processes.
o Informatica PowerCenter Services:
 Integration Services - The Integration Service reads workflow information from the repository. The Integration Service connects to the repository through the Repository Service to fetch metadata from the repository.
 Repository Services - The Repository Service manages connections to the PowerCenter Repository from client applications. The Repository Service is a separate, multi-threaded process that retrieves, inserts, and updates metadata in the repository database tables.
o Informatica Repository. Stores the metadata related to Informatica workflows.
• The Database tier contains the OLTP and OLAP databases.


The Informatica Repository stores all of the Informatica object definitions for the ETL mappings that populate the Oracle Business Analytics Warehouse. It is a series of repository tables that are stored in a database, which can be a transactional, analytical, or separate database

Oracle BI Applications Components (with Informatica/DAC)




Oracle Business Analytics Warehouse Overview
The Oracle Business Analytics Warehouse is a unified data repository for all customer-centric data, which supports the analytical requirements of the supported source systems.
The Oracle Business Analytics Warehouse includes the following:
• A complete relational enterprise data warehouse data model with numerous prebuilt star schemas encompassing many conformed dimensions and several hundred fact tables.

• An open architecture to allow organizations to use third-party analytical tools in conjunction with the Oracle Business Analytics Warehouse using the Oracle Business Intelligence Server

• A set of ETL (extract-transform-load) processes that takes data from a wide range of source systems and creates the Oracle Business Analytics Warehouse tables.

• The Oracle Business Intelligence Data Warehouse Administration Console (DAC), a centralized console for the set up, configuration, administration, loading, and monitoring of the Oracle Business Analytics Warehouse

Important points

The metadata for a source system is held in a container
The PowerCenter Services can be installed on UNIX or on Windows.

The PowerCenter Client Tools must be installed on Windows.
You must co-locate the DAC Client with the Informatica PowerCenter Client Tools.
■ You must co-locate the DAC Server with Informatica PowerCenter Services.
DAC produces parameter files that are used by Informatica. If an execution plan
fails in DAC and you want to debug the workflow by running it directly from
Informatica, then the parameter file produced by DAC should be visible to
Informatica. This is one reason for the requirement to co-locate the DAC and
Informatica components as stated above
The DAC installer installs the DAC Client and DAC Server on Windows.

DAC Client only runs on Windows.
DAC Servers runs on Windows, UNIX, and Linux.
The DAC Server can run on Linux, but it must first be installed on a Windows
machine, then copied over to a Linux machine. Oracle does not provides an installer
for DAC on UNIX

The DAC Client can only be installed and run on Windows.
■ The DAC Client must be installed on the machine where Informatica PowerCenter
Client Tools was installed.
■ The DAC Server must be installed on the machine where Informatica PowerCenter
Services was installed.
■ You must install Informatica PowerCenter Services before you install DAC.
■ The correct version of the JDK is installed by the DAC installer.
■ The DAC installer installs DAC in the DAC_HOME\bifoundation\dac directory.


The DAC Client uses the Informatica pmrep and pmcmd command line programs
when communicating with Informatica PowerCenter. The DAC Client uses pmrep to
synchronize DAC tasks with Informatica workflows and to keep the DAC task source
and target tables information up to date.
In order for the DAC Client to be able to use the pmrep and pmcmd programs, the
path of the Informatica Domain file 'domains.infa' must be defined in the environment
variables on the DAC Client machine.
When you install DAC using the DAC installer, the Informatica Domain file is defined
in the environment variables on the DAC Client machine.

INFA_DOMAINS_FILE
C:\Informatica\9.0.1\clients\PowerCenterClient\domains.infa
The DAC Server uses the following command line programs to communicate with
Informatica PowerCenter:
■ pmrep is used to communicate with PowerCenter Repository Services.
■ pmcmd is used to communicate with PowerCenter Integration Services to run the
Informatica workflows.

The pmrep and pmcmd programs are installed during the PowerCenter Services
installation in the INFA_HOME\server\bin directory on the Informatica PowerCenter
Services machine


Oracle Business Intelligence Applications V7.9.6.3 requires Oracle Business
Intelligence Enterprise Edition V11.1.1.5.0.
■ Oracle Business Intelligence Applications V7.9.6.3 requires Informatica
PowerCenter V9.0.1. Hotfix 2.
■ Oracle Business Intelligence Applications V7.9.6.3 requires Oracle Data Warehouse
Console V10.1.3.4.1.

The OBIEE server uses the metadata to generate the SQL queries. It is stored in the
Repository or often referred to as .rpd. The repository has three layer as shown below, the physical layer, logical layer and the presentation layer.

Metadata maps the OBAW physical tables to a generic business model and includes more than 100 presentation catalogs (aka subject areas) to allow queries using Oracle BI clients such as Answers, Dashboards




High Level Data Flow
• Source – eBS (Raw Data)
• ETL – Extraction Transform and Load (Informatica – PowerCenter or
ODI)
• OBAW - Business Analytics Warehouse
• OBIEE Metadata
• OBIEE Content – Reports and Dashboards




• A prebuilt Informatica repository which includes mappings (wrapped in workflows) to extract data from the supported source systems (various versions of standard applications such as Siebel CRM - yes it was first - , Oracle eBusiness Suite, Peoplesoft, JDEdwards and SAP (BI Apps version 7.8.4) ) and load the data into the Oracle Business Analysis Warehouse. (Note: Oracle BI Applications version 7.9.5.2 includes a repository for the Oracle Data Integrator instead of Informatica but supports only Oracle Financials).


• The Oracle Business Analysis Warehouse (OBAW), a prebuilt schema (stars that is) which serves as a turnkey data warehouse including dozens of stars and accompanying indexes, aggregates, time dimensions and slowly changing dimension handling (and yes, it can be optimized).
• A prebuilt repository for the Data Warehouse Administration Console (DAC) server which is the orchestration engine behind the ETL process. The DAC client and server were included until version 7.9.5. Since then it is a separate installer.
• A prebuilt Oracle BI Server repository (rpd file) which maps the OBAW physical tables to a generic business model and includes more than 100 presentation catalogs (aka subject areas) to allow queries and segmentation using Oracle BI clients such as Answers, Dashboards and Segment Designer. Did I mention that it also takes care of authentication and data security?
• A prebuilt presentation catalog (repository) containing hundreds of requests and ready-to-use dashboards which enable tight integration between the source applications and the BI infrastructure (example: Click the Service Analytics screen in Siebel CRM, work with the dashboard data, drill down to details and click an action button to navigate back to the Siebel CRM record).

Oracle BI EE 10g is the successor of Siebel Analytics and Oracle BI Applications is the successor of Siebel Analytics Applications.


Detailed Data flow



First, the DAC scheduler kicks off jobs to loadrefresh the OBAW at regular intervals or alternatively, these jobs could be kicked off manually from the DAC client.
The DAC server uses the object and configuration data stored in the DAC repository to issue commands to the informatica Server.
The informatica server executes the commands issued from DAC, and uses the objects and configuration data stored in the informatica repository.
Then the data are extracted, transferred and loaded from the transactional databases into the OBAW target tables.
After the ETL is complete and OBAW is online, an OBIEE end user runs a dashboard or report in the Answers or Interactive dashboard.
The request comes through the web server and interacts with the presentation server.
The presentation server interacts with OBI Server and OBI server will understand the requests and hits the OBAW if it’s not cashed and extracts the data and provides it to the presentation server.
The presentation server formats the data into the required format and through web server, the request is presented to the end user



ETL process




ETL mappings are split into two main mappings, SDE mappings and SIL mappings.
2 SDE mappings load the staging tables,then SIL mappings (SILOS, SIL_Vert, PLP) load the final physical warehouse tables
3 SILOS SIL mappings are for all sources except Siebel Verticals. SIL_Vert SIL mappings are for Siebel Verticals only
4 Staging tables are suffixed with S, so W_AP_XACTS_F is the final table and the staging table is W_AP_XACTS_FS

OBIA documentation at the following loc

You can find the most important OBIA documentation at the following locations :

Oracle Business Intelligence Applications (OBIA) Release 7.9.6.3 Documentation Library 

Major topics :

• Install Guide
• Configuration Guide

Oracle Business Intelligence Applications ETL Data Lineage Guide Release 7.9.6.2 and 7.9.6.3

Oracle Business Analytics Warehouse Data Model Reference Version 7.9.6.3

Major Topics :

• Naming conventions
• Domain values
• Star schema diagrams
• Table and column descriptions

Oracle Business Intelligence Applications Product Guides Release 7.9.6.3

Product Guides for:

• Contact Center Analytics
• Financial Analytics
• Human Resources Analytics
• Loyalty Analytics
• Marketing Analytics
• Price Analytics
• Procurement and Spend Analytics
• Project Analytics
• Sales Analytics
• Service Analytics
• Supply Chain and Order Management Analytics

The product information center is also helpful :

Oracle Business Intelligence Applications (OBIA) Product Information Center (PIC)

Informatica SDE and SIL mapping

Source Dependent extract(SDE) and Source Independent loading mappings(SIL)? 
you know they are informatica mappings used for specific requirements. 
SDE loads data to stage area, whereas bulk load is used, 
SIL loads data from srage area to target area, whereas normal load is used. 
Have you guys ever worked with these types of mapping? What are the key transformations used in these mappings?  

SDE_* - Workflow loads data into the staging table.Staging table will 
not have any index defined on them and always the load into the staging 
table will be a truncate and load.Since there are no index defined "Bulk" 
load mode is being used. 

SIL_* - You can find two SIL_* workflows in the Workflow Manager.During 
a full load the workflow (SIL_*_Full) will be invoked from DAC and the 
target table is truncate ,indexes are dropped ,data is loaded in 'Bulk' mode 
and then the indexes are rebuild.Durring incremental load , the workflow 
(SIL_*) will be invoked which would just insert/update the incremental 
data.Since the amount of data during incremental load is minimal compared to 
full load this would run in 'Normal' mode.If indexes are present on a table 
"BULK" mode does not work. 


SDE 
During ETL, the preconfigured Informatica workflows/mappings, identified as the SDE (Source Dependent Extract) mappings, extract data from source OLTP database tables by querying views created by DAC with names starting with V_* and load the data into staging tables on the SRMW database. The view definition will change depending on whether the ETL run is a full load or incremental load run. In case of a full load, it would be a SELECT * FROM <base table>”. While in the case of an incremental load, the view definition joins the base table with the Image tables. This is done to minimize the impact and duration of the ETL process on the OLTP database. 
DAC drops and creates these views during each run (unless specified explicitly in one of the System properties called Drop Create Views Always . These views can be dropped any time and DAC will create them when necessary. 
SIL 
Query data from the staging tables, perform final transformations, and load the dimension and fact tables. Because these processesare independent of the original OLTP database, they are used for data loading from any sources when the staging tables have been populated.  


"Are both types of mapping predefined? Or we have to create mappings in informatica, if so, what are the key transformations?" 

All of these mappings are pre-built as part of the Oracle BI Apps. The BI Apps provides a complete data warehouse data model and the ETL routines to load this data model plus the logical content in OBI EE to query and present this data to users. The only reason you would create your own mappings is to map to sources that are not already supported by the BI Apps to load into the existing data warehouse tables or to load into brand new data warehouse tables that you may build to meet gaps in the BI Apps. 

Very Basic of OBIA

ANSWERS

1) What are the Oracle Business Intelligence Applications (BI Apps)?
It is a complete, end-to-end BI environment covering the BI platform and pre-packaged analytic applications.

The platform includes a server and end user tools such as dashboards, query and analysis, enterprise reporting, disconnected access to the data -- all supported by a unified, model-centric server architecture.

On top of this platform, we have a set of analytic applications consuming the operational data sources and delivering greater insight to larger user communities across the organization via dashboards, query and analysis, and alerts.


2) What technology components do I need to buy to run the BI Apps?
- A database to host the Datawarehouse
- Oracle BI Suite EE Plus or Oracle BI Suite SE1 (OBIEE)
- ETL component options to OBIEE, either Oracle Data Integrator* or Informatica
- Application content per application

*Oracle Data Integrator (ODI) is currently only available for certain release against a specific release of a source system. Future plans are to have ODI fully available.


3) What Application content is available for the BI Apps?

ERP Analytics  - Oracle Financial Analytics - Oracle Procurement and Spend Analytics - Oracle Human Resources Analytics - Oracle Supply Chain and Order Management Analytics - Oracle Spend Classification Analytics - Oracle Project Analytics CRM Analytics - Oracle Sales Analytics - Oracle Service Analytics - Oracle Marketing Analytics - Oracle Contact Center Analytics - Oracle Loyalty Analytics - Oracle Price Analytics Industry Applications - Oracle US Federal Financial Analytics 4) Which systems can BI Apps source its data from? Oracle provides pre-built adapters for Oracle eBusiness Suite, Peoplesoft, JD Edwards, SAP and Siebel. In additional to these pre-built adapters Oracle provides the Universal adapters that enable any other source system to be a source for the Datawarehouse. 5) I have customised my source system; can I extend the BI Apps for these customisations? Oracle has designed the BI Apps to be extendable, from the source system mappings, the warehouse model, the BI Modelling layer to the Presentation objects. Oracle provides a methodology for extensions in the supplied guides. One of the most common extensions is the inclusion of descriptive flexfields for eBusiness suite sources. 6) How do I deploy the BI Apps? The BI Apps can be deployed as follows - Standalone mode - Integrated with Portal via JSR-168/WSRP - Embedded with the transaction system within a dashboard view - Embedded with the transaction system contextually within a transactional view 7) Can I have the same security as my transactional system? The BI Apps can be integrated with the source system to enable a smooth transition for users maintaining the user’s security context as they move from the transactional system to BI Apps and back into the transactional system. 8) Does a BI Apps implementation take as long as a traditional Datawarehouse implementation? A traditional Datawarehouse implementation will typically take in the region of 18 months + to deliver, because much of the time consuming effort has already been developed. A BI Apps project will usually have release cycles every 100 days or so. A minimal configuration implementation can have a development system up and running in a few weeks. 9) What is the DAC? DAC stands for Data Warehouse Application Console. It is an essential component of Oracle BI application architecture. DAC serves the following purposes: - DAC is a metadata driven administration and deployment tool for ETL and data warehouse objects - It is used by warehouse developers and the ETL Administrator - Manages Application Configuration - Manages the execution of warehouse loads - Provides a monitoring facility 10) Where can I get some more information about the content of the BI Applications? The following links on the Oracle support site are a good starting point: Content Guide: https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=832690.1 Oracle® Business Intelligence Applications Metrics Reference Guide Release 7.9.6 https://metalink3.oracle.com/od/faces/secure/km/DocumentDisplay.jspx?id=846917.1 Oracle® Business Intelligence Applications ETL Data Lineage Guide Release 7.9.6,7.9.6.1 (Doc ID 829385.1) https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=829385.1

11) How is BI Apps made aware of my source system configurations?
During the configuration of the BI Apps configurations are entered as parameters in the DAC and by completing CSV files that define your source system configs. These CSVs are then picked up during the ETL run and used to populate the warehouse.


12) Does my warehouse have to be an Oracle database?
No, the BI Apps are certified against many databases including DB2 and Terradata.


13) Can I view my data indifferent currencies?
The BI Apps hold both the transactional and local currency amounts. In addition there is the possibility to have up to 3 reporting currencies with basic configuration. The data model stores five currency versions in each fact as follows:

- Group Amount (x3) : Corporate Currency Amount
- Local Amount : Local Country / Region Currency Amount
- Document Amount : Actual Transaction Currency Amount

Support for different exchange rate types through ETL configuration

- Corporate
- User


14) I am a multi-country organisation and would like to have the ability to display the BI Apps in the local language, is this possible?
Yes, there is the facility to have the OBIEE components displayed in multi-language and the BI Apps can be configured to display the objects in multi-language. To display the data in multi-language is a customisation effort that will require extending the warehouse to include translation tables.

Configuration Steps for Financial Analytics for Oracle EBS

Configuration Steps for Financial Analytics for Oracle EBS

This section contains configuration steps before you do a full data load that apply to Oracle EBS. It contains the following topics:

• Section 5.2.2.1, "About Configuring Domain Values and CSV Worksheet Files for Oracle Financial Analytics"
• Section 5.2.2.2, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R12)"
• Section 5.2.2.3, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R11i)"
• Section 5.2.2.4, "How to Specify the Ledger or Set of Books for which GL Data is Extracted"
• Section 5.2.2.5, "Oracle EBS Currency Balance Types"

Basic of Oracle Financial Analytics

Why use Oracle Financial Analytics?
In additon to the above benefits, Financial Analytics integrates with Oracle E-Business Suite (EBS), Peoplesoft, JD Edwards, and SAP, which allows companies to implement the technology, filled with years of research and best practices, quickly and with a LOT less risk.

What is Oracle Financial Analytics comprised of?
By listing some of the content of the BI module, without going into too much detail, you will be able to get a sense for the type of information and see the vast amount of content included.

————————
6 Dashboards
————————
General Ledger: provides information about the key areas of required for financial management including balance sheet, cash flow, liquidity, expenses, working capital and liquidity.

Payables: provides information about how effectively and efficiently the company is meeting its payment obligations.

Receivables: provides information about effectively and efficiently the company is collecting payment from sales.

Projects: provides financial information about projects.

Profitability: provides imformation for the key areas for profitability including margins by customer and product, profit and loss statements, revenues, and the various “Return-On metrics” such as ROA, ROI, ROE.

US Federal Financial Performance: provides information about budgets and payments

————————
36 dashboard pages – broken out by dashboard below:
————————
General Ledger: Overview, Balance Sheet, Cash Flow, Budget vs Actual, Asset Usage, Liquidity, Financial Structure, GL Balance, Trial Balance

Payables: Overview, AP Balance, Payments Due, Effectiveness, Payment Performance, Supplier Report, Invoice Details, All AP Transactions

Receivables: Overview, AR Balance, Payments Due, Effectiveness, Payment Performance, Customer Report, Invoice Details, All AR Transactions

Projects: Project Invoices

Profitability: Overview, P&L, Margins, Revenue, Products, Customers

US Federal Financial Performance: Budget Summary, Budget Details, Budget Spending, Payables

————————
255 Reports – A small sampling of the reports include:
————————
Cash Flow Summary
Monthly & Quarterly Cash Flow
Net Working Capital Summary
Operating Cycle and Cash Cycle
Monthly & Quarterly Balance Sheet
Budget vs Actual – Current & YTD Operating Expenses
Top 10 Categories by Expense Variance -and- Top 10 Cost Centers by Expense Variance
Payables Turnover -and- Receivables Turnover
Cash Ratio
Days Cash in Hand
Quick Ratio -and- Current Ratio
Debt Coverage
Debt to Asset -and- Debt to Equity
GL Account Balance -and- Trial Balance

————————
488 Metrics – A small sampling of the metrics include:
————————
Receivables 
AR Balance: • DSO • Closing Group Amt • Credit Limit Used % • Total AR Overdue Amt
AR Aging: • AR Aging 1-30 Amt • AR Due 1-30 Amt • AR Overdue 1-30 Amt
Payment Performance: • AR Payment Days • AR Weighted Days • Times Paid Before Due
AR Transactions: • AR Avg Invoice Amt • AR Credit Memo Amt

Payables 
AP Balance: • DPO • Closing Group Amt • Total AP Overdue Amt • Overdue Amt to Total %
AP Aging: • AP Aging 1-30 Amt • AP Due 1-30 Amt • AP Overdue 1-30 Amt
Payment Performance: • AP Payment Days • AP Weighted Days • Times Paid Before Due
AP Transactions: • AP Avg Invoice Amt • AP Avg Payment Amt

General Ledger 
Balance Sheet: • Cash • Accounts Receivable • Debt to Equity Ratio • Current Ratio
Asset Turnover: • AR Turnover • AP Turnover • Inventory Turnover • Cash Cycle • Fixed Assets Turnover
Cash Flow: • Operating Cash Flow • Investing Cash Flow • Financing Cash Flow • Net Cash Flow

Profitability 
Profitability Returns: • Return on Equity • Return on Assets • Return on Capital
Margins: • Gross Margin % • Operating Margin % • EBT Margin % • Net Income Margin %
Product Profitability: • Revenue • Product Gross Profit • Product Operating Profit
Customer Profitability: • Revenue • Customer Gross Margin

Who will use and benefit from Financial Analytics?
CFOs, Controllers, Accounting Managers, Finance Analysts, Department Heads, Payables and Receivables Managers, Payables & Receivables Analysts, Project Managers, Project Accountants, and much more.

Where can I find more information?
More information about Oracle Financial Analytics can be found here:
http://www.oracle.com/us/solutions/business-analytics/analytic-applications/business-role/financial-analytics/overview/index.html
And more information about Oracle Business Intelligence in general can be found here:
http://www.oracle.com/us/solutions/business-analytics/overview/index.html

Customizing the Oracle Business Analytics Warehouse

• Section 17.1, "Overview of Customization in Oracle Business Intelligence Applications"
• Section 17.2, "Oracle Business Analytics Warehouse Customization Scenarios"
• Section 17.3, "Category 1 Customizations: Adding Columns to Existing Fact or Dimension Tables"
• Section 17.4, "Other Types of Customizations Requiring Special Handling"
• Section 17.5, "Category 2 Customizations: Adding Additional Tables"
• Section 17.6, "Category 3 Customizations: Adding New Data as a Whole Row into a Standard Dimension Table"
• Section 17.7, "Configuring Extracts"
• Section 17.8, "Configuring Loads"
• Section 17.9, "Configuring Slowly Changing Dimensions"
• Section 17.10, "About Stored Lookups"
• Section 17.11, "Codes Lookup"
• Section 17.12, "About Resolving Dimension Keys"
• Section 17.13, "About Domain Values"
• Section 17.14, "Configuring the Domain Value Set with CSV Worksheet Files"
• Section 17.15, "Configuring the Domain Value Set Using Informatica PowerCenter Designer"
• Section 17.16, "Configuring Conformed Dimensions"