As business intelligence (BI) architects, data modelers, ETL business analysts, or report developers, you can use the RevPro BI views for modeling, extraction, and development of your own analytical business intelligence for your organization.
The BI views provided by RevPro are a set of logical and physical database entities. Before you start designing your own analytical business intelligence by using RevPro BI views, it is necessary to understand the data structures and table relationships among these RevPro BI views.
The data entities for RevPro BI views are based on the key physical tables. Some BI views are similar to the physical tables on which they are based. Other BI views are derived from calculations based on the physical tables.
Derived BI views are mainly used to guide the development of the upstream ETL/ELT logic. Although derived BI views can be directly used for reports and data extraction, it is recommended that you extract the source data entities from RevPro and then carry out data transformation outside RevPro in dedicated ETL/ELT environments. After that, you can upload data to the target warehouse systems such as EDW or ODS for business analysis.
RevPro BI views do not have any security filtering applied. When you use the BI views, you should determine the best method to secure and segregate the data in your organization.
The following table lists the data entities and the physical tables on which RevPro BI views are based. Account Summary and Waterfall are derived entities.
|Data entity||Physical table|
|Acct Summary (Derived)||RPRO_BI3_LN_ACCT_SUMM_V|
Logical data model
The following diagram illustrates the relationship between the BI views in RevPro. The BI views in the dashed line boxes indicate that the BI views might be used by multiple roles.
Physical data model
The following diagram illustrates the relationship between the physical tables used by RevPro BI views. The physical tables in the dashed line boxes indicate that the tables might be used by multiple roles.