1 . In the Physical layer, expand D1 Time Quarter Grain.
2 . In the BMM layer, expand D1 Time.
|D1 Time Quarter Grain||D1 Time|
|DAYS_IN_QTR||Days in Qtr|
|JULIAN_QTR_NUM||Julian Qtr Num|
|PER_NAME_HALF||Per Name Half|
|PER_NAME_QTR||Per Name Qtr|
|PER_NAME_YEAR||Per Name Year|
This action creates a new logical table source named D1 Time Quarter Grain for D1 Time.
4 . Rename the D1 Time Quarter Grain logical table source to LTS2 Time Quarter Grain.
5 . Double-click LTS2 Time Quarter Grain to open the Logical Table Source dialog box.
6 . On the Column Mapping tab make sure show mapped columns is selected and note the column mappings. The logical columns now map to columns in two physical tables: D1 Time and D1 Time Quarter Grain.
7 . Click OK to close the Logical Table Source dialog box.
8 . In the Physical layer expand F2 Revenue Aggregate.
9 . In the BMM layer expand F1 Revenue.
10 . Drag the following physical columns from F2 Revenue Aggregate to their corresponding logical columns in F1 Revenue: Note: Do not add them as new columns.
|F2 Revenue Aggregate||F1 Revenue|
This action creates a new logical table source named F2 Revenue Aggregate for F1 Revenue.
11 . Rename the F2 Revenue Aggregate logical table source to LTS2 Revenue Aggregate.
These core tutorials will help you to learn the fundamentals of OBIEE 11g. For an in-depth understanding and practical experience, explore OBIEE 11g Training.
12 . Double-click LTS2 Revenue Aggregate to open the Logical Table Source dialog box.
13 . On the Column Mappings tab make sure show mapped columns is selected and note the column mappings. The Revenue and Units logical columns now map to columns in two physical tables:
F1 Revenue and F2 Revenue Aggregate.
14 . Leave the Logical Table Source – LTS2 Revenue Aggregate dialog box open.
Set Aggregate Content
1 . Click the Content tab.
2 . Set the following logical levels for the logical dimensions:
|Logical Dimension||Logical Level|
|H2 Product||Product Total|
|H20 Product||Product Total|
|H3 Customer||Customer Total|
|H5 Sales Rep||Total|
Explanation: You are setting aggregation content for the fact table to the corresponding levels in the dimension hierarchies. In a subsequent step, you set similar levels for the aggregate logical table source for the Time dimension. Note that all levels are set to the total level except for the H1 Time logical dimension, which is set to Quarter. The result is, when a user queries against a particular level, Oracle BI Server will “know” to access the aggregate tables instead of the detail tables.
For example, if a user queries for total sales by product by quarter, the server will access the F2 Revenue Aggregate fact table and the corresponding aggregate dimension table, D1 Time Quarter Grain. If a user queries for a level lower than the level specified here, for example Month instead of Quarter, then the server will access the detail tables (F1 Revenue and D1 Time). If a user queries for higher level (year instead of quarter) the aggregate tables will be used, because whenever a query is run against a logical level or above, the aggregate tables are used.
3 . Click OK to close the Logical Table Source dialog box.
4 . Double-click the LTS2 Time Quarter Grain logical table source to open the Logical Table Source dialog box.
5 . On the Content tab, set the logical level to Quarter.
6 . Click OK to close the Logical Table Source dialog box.
7 . Save the repository and check global consistency. Fix any errors or warnings before proceeding.
8 . Close the repository. Leave the Administration Tool open. Note that you did not need to change the Presentation layer. You made changes in the business model that impact how queries are processed and which sources are accessed. However, the user interface remains the same, so there is no need to change the Presentation layer. Oracle BI Server will automatically use the appropriate sources based on the user query.
For indepth understanding of OBIEE click on