BI Apps has an Universal Data Warehouse
Posted by Dylan Wan on March 23, 2015
BI Apps data warehouse design is based on an assumption that the data warehouse schema design is independent from OLTP system.
The staging schema is an universal staging and the data warehouse is an universal data warehouse.
The assumption is that no matter what the source system you are using, the business questions the BI consumers have are similar. You want to see revenue, cost, and profitability, regardless if you are using Oracle E-Business Suite, PeopleSoft, or J.D. Edwards, revenue are still revenue, cost are still cost. The definitions of these metrics won’t vary too much from the OLTP systems you are using.
It is the BI Apps development team’s job to find where this numbers should be extracted from the source systems and to define the “map” between the source system and the target data warehouse system.
This universal data warehouse assumption does give BI Apps a unique advantage. It allows the teams develop the source adaptor independently from the data warehouse design and thus independently from the BI metadata.
In another way to view this, the application logics built in the BI tool and the knowledge of designing the data warehouse schema can be reused over time and over many projects.
Adding the support of the 1st adaptor to E-Business Suite may take sometime to analyze the analytic requirements. Adding the support of the PeopleSoft and JDE adaptors becomes a job of providing the source and target logical mapping and create the ETL jobs of loading the universal staging tables.