Oracle BI Applications – Overview
Oracle Business Intelligence Applications are a set of prebuilt solutions that deliver business intelligence across an organization, giving users the key information they need to maximize effectiveness. These solutions transform and integrate data from a range of enterprise sources, including Siebel, Oracle E-Business Suite, as well as corporate data warehouses.
Oracle BI Applications includes the following modules:
1. Oracle Financial Analytics
2. Oracle Human Resources Analytics
3. Oracle Supply Chain and Order Management Analytics
4. Oracle Procurement and Spend Analytics
5. Oracle Project Analytics
6. Oracle Sales Analytics
7. Oracle Service Analytics
8. Oracle Contact Center Telephony Analytics
9. Oracle Marketing Analytics
10. Oracle Loyalty Analytics
2. Oracle Human Resources Analytics
3. Oracle Supply Chain and Order Management Analytics
4. Oracle Procurement and Spend Analytics
5. Oracle Project Analytics
6. Oracle Sales Analytics
7. Oracle Service Analytics
8. Oracle Contact Center Telephony Analytics
9. Oracle Marketing Analytics
10. Oracle Loyalty Analytics
The BI Applications are built upon the foundation of Oracle BI Enterprise Edition which means that they allow extension of the suite with additional data sources and own-built dashboards and reports.
The Oracle BI Applications pre-packaged content comes with three main pre-built repositories:
1. The OBIEE repository and catalog
2. The ETL repository tailored for the source applications
3. The Data Warehouse model
2. The ETL repository tailored for the source applications
3. The Data Warehouse model
The figure below diagram presents a functional overview of OBIA.
The pre-built ETL repository includes not only routines for changed data capture, extract to staging area and the load into data warehouse tables, but also seed data for common dimensions like the time dimension or dimension lookup files with domain values or dimension value sets to support sources independent metric calculation.
The pre-built Business Analytics Warehouse is one single but modular data warehouse model to support one or a combination of the source systems.
The pre-built OBIEE repository and web catalog are aligned with the Business Analytics Warehouse and contain the domain specific and end user facing dashboards, reports and KPI’s.
The below diagram shows the Architecture of the OBI Apps
Data Flow Description
1. 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.
2. The DAC server uses the object and configuration data stored in the DAC repository to issue commands to the informatica Server.
3. The informatica server executes the commands issued from DAC, and uses the objects and configuration data stored in the informatica repository.
4. Then the data are extracted, transferred and loaded from the transactional databases into the OBAW target tables.
5. After the ETL is complete and OBAW is online, an OBIEE end user runs a dashboard or report in the Answers or Interactive dashboard.
6. The request comes through the web server and interacts with the presentation server.
7. 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.
8. The presentation server formats the data into the required format and through web server, the request is presented to the end user.
2. The DAC server uses the object and configuration data stored in the DAC repository to issue commands to the informatica Server.
3. The informatica server executes the commands issued from DAC, and uses the objects and configuration data stored in the informatica repository.
4. Then the data are extracted, transferred and loaded from the transactional databases into the OBAW target tables.
5. After the ETL is complete and OBAW is online, an OBIEE end user runs a dashboard or report in the Answers or Interactive dashboard.
6. The request comes through the web server and interacts with the presentation server.
7. 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.
8. The presentation server formats the data into the required format and through web server, the request is presented to the end user.
Oracle BI Applications Vs OBIEE Implementation Approach
An OBIA implementation differs from a traditional data-warehouse build, in that it is complete with pre-built, pre-mapped and pre-packaged insights based upon best practice principles. When building a traditional data warehouse, a significant amount of time and effort is given over to the analysis and build of the warehouse.
The diagram below shows a comparative approach to a traditional data warehouse against OBIA.
This pre-built approach differs from the OBIEE manifests itself in the application layer as can be seen from the screenshots below. The upper image is of the BI Administration Tool and as can be seen the platform is installed but there is no content, this all needs adding manually after an analysis and design stage. The lower image is of the same tool but as installed with OBIA. Here all the content of the Physical, Business and Presentation Layers comes already mapped thus removing the need for the design, analysis and build stages.
Due to the large amount of pre-built content and pre-defined structures, implementation time is greatly reduced, upgrade paths guaranteed and integration with your source systems assured. The following diagram shows a comparative of OBIEE implementations versus OBIA.
Posts
