Daily Business Intelligence (DBI)
- Out-of-the-box reporting and analysis application that enables senior managers and executives to see relevant, accurate and timely information using self-service overview pages.
- DBI overview page is designed for a particular functional, management responsibility. Managers can drill down from the summarized information on each page to detailed reports or to specific transactions in underlying applications, e.g. the Profit and Loss page is designed for a profit centre manager. his page summarizes profit and loss information using the Revenue, Expenses and Operating margin KPIs.
- DBI architecture simplifies the reporting process and ensures the managers are looking the most accurate and up-to-date data.
- DBI only updates the data that has changes since the last refresh.
Overview Page: An overview page is designed to meet the needs of a particular responsibility.
Responsibilty: Is designed for a particular business function or user such as Expense Manager.
Region: A region is a unique set of information on a page.
5 types of regions in DBI are:
4. KPI, and
KPI: A KPI is a business metric used for reporting such as Revenue or Operating margin. Managers can use KPIs to compare and judge their performance.
* DBI setup steps need to be performed before using an overview page.
- DBI provides cross-enterprise functionality that is not available as part of standard Oracle reports.
Technical Componets of DBI-
1. Single Oracle Instance: DBI resides in a single instance, which is same as transactional instance. Which reduces the need for a separate maintenance and administration team and optimize reporting performance.
- Materialized views and incremental refresh capabilities enable DBI to summarize a large amount of data efficietly.
2. E-Business Suite Tables: Changes in E-Business suite tables are reflected in DBI whenever incremental request set is run.
3. Base Summary tables and Materialized Views: Used to store summarized DBI data thats serve as the source of the data on each page.
4. Metadata: Used to define the complex relationship between the dimensions, responsibilities, menus, request sets, KPIs, pages, and reports. Metadata is predefined and can not be modified.
5. Rendering technology: Used to render the pages based on the data that is defined in the base summaries, materialized views, and the metadata layer.
6. Request Set generator: Enables to create initial and incremental request sets for each page using the definitions in the metadata layer. The generated request sets include all of the concurrent programs that you need to load or refresh a page.
- A dimension defines a hierarchical relationship between data. YOu can use dimesions to view data at different level of details.
- Dimensions can be either flat or recursive.
1. Flat Dimension: Can be hierarchical but does not display the hierarchy between items.
2, Recursive Hierarchy: Displays a hierarchy between items.
- Each page has a dimesion that is considered the primary dimension. It determines which values are compared in the KPI region.
- Common DBI dimensions are:
1. Currency Dimension
2. Organization Dimension
3. Item Dimension
4. Person Dimension
5. Sales Group Dimension
6. Operating Unit Dimension
7. Time Dimension
8. Inventory Organization Dimension
1. Currency Dimension: Flat dimension that allows to see financial data across all organization units in a common currency. This dimension is populated based on the currencies and daily exchange rates that are defined in Oracle General Ledger.
2. Organization Dimension: Flat dimension that defines the hierarchical relationship between organizations in an enterprise.