ORACLE BUSINESS INTELLIGENCE WORKSHOP

Creating a Repository Using the Oracle Business Intelligence Administration Tool

Purpose This tutorial shows you how to use the Oracle BI EE Administration Tool to build, modify, enhance, and manage an Oracle BI repository on the BIC2G:EE 10.1.3.2 VMWare image (Linux Edition v1.0). Time to Complete: Approximately 3 hours Topics This tutorial covers the following topics: Page Prerequisites .....................................................................................................2 Building the Physical Layer of a Repository ......................................................3 Building the Business Model and Mapping Layer of a Repository...................16 Building the Presentation Layer of a Repository..............................................44 Testing and Validating a Repository................................................................46 Creating Calculation Measures .......................................................................57 Organizing the Presentation Layer ..................................................................87 Using Initialization Blocks and Variables .........................................................93 Adding Multiple Sources................................................................................110 Executing Direct Database Requests............................................................125 Using Aggregates..........................................................................................129 Creating Time Series Measures ....................................................................137 Summary .......................................................................................................147

1

OVERVIEW This tutorial shows you how to build an Oracle BI metadata repository. You learn how to import metadata from databases and other data sources, simplify and reorganize the imported metadata into a business model, and then structure the business model for presentation to users who request business intelligence information via Oracle BI user interfaces, such as Oracle BI Answers and Oracle BI Interactive Dashboards.

Prerequisites
This tutorial is for a Windows client environment connecting to the Linux BIC2G image as a server. Instructions for installing VMWare software and client BI tools and data source drivers are found in the file “Prerequisites for Oracle BI Workshop” After installing VMWare and opening the BIC2G Linux image, follow these instructions to map a network drive on local client to the Linux Server: ¾ Go to http://192.168.209.134/go/setup.html and click on the Map button.

¾ Execute the downloaded file to map the chosen drive letter (G:) to the Linux Server. Open up the mapped drive and rename the existing SH.rpd repository: ¾ Open up G:\biee\10.1.3.2\OracleBI\server\Repository in windows explorer ¾ Rename the existing SH.rpd to SH_backup.rpd

2

Building the Physical Layer of a Repository
In this topic you use the Oracle BI Administration Tool to build the Physical layer of a repository. The Physical layer defines the data sources to which Oracle BI Server submits queries and the relationships between physical databases and other data sources that are used to process multiple data source queries. The recommended way to populate the Physical layer is by importing metadata from databases and other data sources. The data sources can be of the same or different varieties. You can import schemas or portions of schemas from existing data sources. Additionally, you can create objects in the Physical layer manually. When you import metadata, many of the properties of the data sources are configured automatically based on the information gathered during the import process. After import, you can also define other attributes of the physical data sources, such as join relationships, that might not exist in the data source metadata. There can be one or more data sources in the Physical layer, including databases, spreadsheets, and XML documents. In this example, you import and configure tables from the sample SH schema included with the Oracle 10g database. To build the Physical layer, you perform the following steps: Create a New Repository Create an ODBC Data Source Import SH Schema Create Physical Joins

3

2\OracleBI\server\Repository Name the file SH. 3. 4. perform the following steps: 1.3. http://oracle2go. the local Repository folder is selected by default.rpd. 5. Browse to the Linux server repository folder in the drive mapped during the pre-requisite steps to this section: Browse to G:\biee\10.Create a New Repository To create a new repository. Click Start > Programs > Oracle Business Intelligence > Administration to open the Oracle BI Administration Tool.oracle.us. In the New Repository dialog box. 4 . Wait for the flag to turn RED.html Select the checkbox next to BI Server. Click File > New to open the New Repository dialog box. click on STOP. 2.com/go/process_control/pc. Open the BIC2G Process Control for Services.1.

then the Business Model and Mapping layer. You can work on each layer at any stage in creating a repository. 5 . and Physical.6. The Presentation layer is where the business model is customized for presentation to the user. Leave the Administration Tool open. and then the Presentation layer. Business Model and Mapping. but the typical order is to create the Physical layer first. The Physical layer is where information on physical data sources is stored. If necessary. Click Save. select Tools > Options > Show toolbar to display the toolbar. The new repository opens in the Administration Tool and displays three empty layers: Presentation. The Business Model and Mapping layer is where measurements and terms used in business are mapped to the physical data sources.

6 . Click Start > Programs > Administrative Tools > Data Sources (ODBC) to open the ODBC Data Source Administrator. Click the System DSN tab and click Add. 2. To create an ODBC data source for importing the SH schema information.Create an ODBC Data Source An ODBC data source is needed to import schema information about a data source into an Oracle BI Server repository. perform the following steps: 1. The Create New Data Source dialog box opens.

In the Oracle ODBC Driver Configuration dialog box. 6. select the appropriate TNS Service Name from the drop down list (ORCL in this example). Click Finish to open the Oracle ODBC Driver Configuration dialog box. and enter SH as the User ID for the SH schema. select the Oracle driver. In the Create New Data Source dialog box.3. Click Test Connection to open the Oracle ODBC Driver Connect dialog box. 4. 5. enter a Data Source Name (this can be any name). 7 .

10. 9. 8 . 11. In the Oracle ODBC Driver Connect dialog box. enter the password SH for the SH schema and click OK. Click OK to close the Testing Connection message. You should see a "Testing Connection" message indicating the connection is successful. Verify that the SH system data source is added in the ODBC Data Source Administrator and click OK to close the ODBC Data Source Administrator. 8. Click OK to close the Oracle ODBC Driver Configuration dialog box.7.

.Import SH Schema To import the SH schema information into the repository. 3. . 2. select the SH ODBC DSN you created in a previous step. click File > Import > from Database . locate the SH schema folder. 9 . and click OK to open the Import dialog box. perform the following steps: 1. In the Import dialog box. enter SH as the user name and password. In the Oracle BI Administration Tool. In the Select Data Source dialog box.

PRODUCTS. TIMES 5. COSTS. The Connection Pool dialog box opens. Expand the SH schema folder and use Ctrl + Click to select the following tables: CHANNELS. Verify that only the Tables and Keys checkboxes are selected.4. CUSTOMERS. SALES. and click the Import button. COUNTRIES. It is best practice to only import objects needed to support your business 10 . PROMOTIONS. which is the default.

11 . Please note that this is the TNS service name. click Close to close the Import dialog box. on the General tab. verify that the call interface is set to Default (OCI 10g) and change the data source name to the appropriate tnsnames. 9. In the Physical layer of the repository. 7. The import process starts.ora entry ( ORCL in this example). You can always delete objects later if they do not support your business model. 6. However. expand the SH schema folder and verify that the correct tables are imported. 8. Leave the rest of the settings as they are and click OK to close the Connection Pool dialog box.model. In the Connection Pool dialog box. not the ODBC DSN. When the Import process completes. don’t worry if you import extra objects at this point.

10. click Tools > Update All Row Counts. right-click the SH schema folder and select Physical Diagram > Object (s) and All Joins. perform the following steps: 1. Alternatively. To verify connectivity. 11. When update all row counts completes. In the Physical layer. you can select the SH database object and then click the Physical Diagram button on the toolbar. 12 . verify that the row counts are displayed in the Physical layer of the Administration Tool: Create Physical Joins To create physical joins in the Physical layer of the repository.

right-click in the white space. select Zoom. and adjust the size. In the Physical Diagram. Rearrange the tables so they are all visible in the Physical Diagram. 5. 4. 3. Click the Channels table and then the Sales table.2. Click the New Foreign Key button on the toolbar. The Physical Foreign Key dialog box opens. if the tables are too big. 13 .

Make sure the join expression is: CHANNELS.CHANNEL_ID = SALES.CHANNEL_ID 6. The join is creating a one-to-many (1:N) relationship that joins the key column in the first table to a foreign key column in the second table.It matters which table you click first. Continue to create the following joins: 14 . The Administration Tool makes a best "guess" and automatically determines which columns should be included in the join. 7. Click OK to close the Physical Foreign Key dialog box. The join between Channels and Sales is displayed in the Physical Diagram.

TIME_ID PRODUCTS. Click No when prompted to check global consistency.COUNTRY_ID = CUSTOMERS. click the X in the upper right corner to close the Physical Diagram.COUNTRY_ID Note that Countries joins to Customers and Costs in not joined for now. Select File > Save or click the Save button on the toolbar to save the repository. bypass this check until the other layers in the repository are built. When you are finished. Checking Global Consistency checks for errors in the entire repository. set up an ODBC data source. Congratulations! You have successfully created a new repository. All other tables join directly to Sales.CUST_ID = SALES. Some of the more common checks are done in the Business Model and Mapping layer and Presentation layer.PROMOTIONS. 10. 8.PROMO_ID TIMES. In the next topic you learn how to build the Business Model and Mapping layer of a repository. 15 .PROMO_ID = SALES.PROD_ID = SALES. You learn more about consistency check later in this tutorial. Leave the Administration Tool and the SH repository open for the next topic. imported a table schema from an external data source into the Physical layer. Since these layers are not defined yet. 9.PROD_ID CUSTOMERS. and defined keys and joins.CUST_ID COUNTRIES.TIME_ID = SALES.

model of the data and specifies the mappings between the business model and the Physical layer schemas. There are two main categories of logical tables: fact and dimension. Most of the vocabulary translates into logical columns in the business model.Building the Business Model and Mapping Layer of a Repository In this topic you use the Oracle BI Administration Tool to build the Business Model and Mapping layer of a repository. The Business Model and Mapping layer of the Administration Tool defines the business. Collections of logical columns form logical tables. The business model simplifies the physical schema and maps the users’ business vocabulary to physical sources. The main purpose of the business model is to capture how users think about their business using their own vocabulary. A business model object contains the business model definitions and the mappings from logical to physical tables for the business model. This is where the physical schemas are simplified to form the basis for the users’ view of the data. or logical. To build the Business Model and Mapping layer. Each logical column (and hence each logical table) can have one or more physical objects as sources. Logical fact tables contain the measures by which an organization gauges its business operations and performance. The Business Model and Mapping layer of the Administration Tool can contain one or more business model objects. you perform the following steps: Create a Business Model Create Logical Tables Create Logical Columns Create Logical Joins Rename Business Model Objects Delete Unnecessary Business Model Objects Build Dimension Hierarchies 16 . Logical dimension tables contain the data used to qualify the facts.

In the Business Model dialog box. Leave it empty. 2. 3. You enable the business model for querying later after the Presentation layer is defined and the repository passes a global consistency check. The Description edit box is used to add a comment for yourself or another developer.Create a Business Model To create a new business model. 17 . right-click the white space and select New Business Model. name the business model SH and leave the Available for queries box unchecked. Click OK to close the Business Model dialog. The red symbol on the business model indicates it is not yet enabled for querying. The new SH business model appears in the Business Model and Mapping layer. In the Business Model and Mapping layer. perform the following steps: 1.

perform the following steps: 1. Click OK to close the Logical Table dialog.Create Logical Tables To create a new logical table. In the Logical Table dialog box. The Sales Facts logical table appears in the SH business model in the Business Model and Mapping layer. 18 . right-click the SH business model and select New Object > Logical Table. The Sources folder is populated in the next step when you create a logical column. name the table Sales Facts. 2. 3. In the Business Model and Mapping layer.

expand the Sales physical table.Create Logical Columns To create a logical column. 19 . In the Physical layer. perform the following steps: 1. Select the column AMOUNT_SOLD. 2.

3. the logical table source name. 20 . Because you dragged a column from the Physical layer. Logical table sources define the mappings from a logical table to a physical table. Expand the Sources to see the logical table source that was created automatically when you dragged the AMOUNT_SOLD column from the Physical layer. 4. is the same name as the physical table. A new AMOUNT_SOLD logical column is added to the Sales Facts logical table. SALES. However. A logical table’s Sources folder contains the logical table sources. Drag the AMOUNT_SOLD column from the Physical layer to the Sales Facts logical table in the Business Model and Mapping layer. it is possible to change names in the Business Model and Mapping layer without impacting the mapping.

Notice that the logical column icon is changed to indicate an aggregation rule is applied. 7. 21 . double-click the AMOUNT_SOLD logical column to open the Logical Column dialog box. In the Business Model and Mapping layer. Click the Aggregation tab. 6. select SUM. In the Default aggregation rule drop down list. 8.5. Click OK to close the Logical Column dialog box.

Drag the selected tables from the Physical layer onto the SH business model folder in the Business Model and Mapping layer. Select the following tables in the Physical layer. CUSTOMERS. 22 . this indicates a fact table.Create Logical Joins To create logical joins in the business model. In the Business Model and Mapping layer. perform the following steps: 1. Because you have not yet created the logical joins. PROMOTIONS. Notice that each logical table has a yellow table icon. TIMES 2. PRODUCTS. Select only these tables: CHANNELS. This automatically creates logical tables in the Business Model and Mapping layer. The icon color for dimension tables changes to white in a later step when you create logical joins. all table icons are yellow.

Adjust the zoom factor.3. Rearrange the table icons so they are all visible. tables. Also note 23 . Place the Sales Facts table in the middle. Click the New Complex Join button in the toolbar. Leave the default values as they are. business model. Right-click the SH business model and select Business Model Diagram > Whole Diagram. The order is important. and cardinality. 5. join type. if desired. Click the Channels table icon first and then click the Sales Facts table icon in the Logical Table Diagram window. but note which properties you can set: name. The Logical Join dialog box opens. 4. driving table. 6. The second table clicked is the many side of the relationship.

Repeat the steps for the remaining tables. Do not change the default values. 7. Your final result should look similar to the picture. is at the many end of the join: 8. when defining logical joins. Notice that the fact table. Sales Facts. you leave the defaults as they are. 24 .which properties you cannot set: the join expression and the join columns. click OK. Typically. and verify your work in the Logical Table Diagram.

Sales Facts. Products. Customers. a yellow icon indicates a fact table and a white icon indicates a dimension table. Notice that the color of the table icons for the dimension tables has changed to white in the business model. Save the SH repository. and Times. Click the X in the upper right corner to close the Logical Table Diagram. Defining the join relationships determined which tables are the logical dimension tables and which is the logical fact table. Do not check global consistency. Click Tools > Utilities. Rename Business Model Objects To use the Rename Wizard to rename the objects in the business model. perform the following steps: 1. A fact table is always on the many side of a logical join. You now have a logical star schema consisting of one logical fact table. 10.9. and five logical dimension tables: Channels. In a business model. 25 . Promotions.

Click the Add Hierarchy button. 3. Click Select None. Check Logical Table and Logical Column. 5. 7. click Rename Wizard and then Execute. 26 . In the Rename Wizard. 6. click the Business Model and Mapping tab and select the SH business model. In the Utilities dialog box. 4. Click Next.2.

8. Click Next. 9. Select All text lowercase.

10. Click Add 11. Click Change specified text. In the Find box, type an underscore. In the Replace box, type a space.

12. Click Add.

27

13. Click First letter of each word capital and click Add. 14. Click Change specified text. In the Find box, type a space and the letters Id. In the Replace With box, type a space and the letters ID. Check Case sensitive.

15. Click Add. 16. Click Next and review changes.

17. Click Finish and verify that logical tables and logical columns in the Business Model and Mapping layer are changed as expected.

28

18. Save the repository. Do not check global consistency.

29

2.Delete Unnecessary Business Model Objects To delete logical columns that are not needed in the business model. 30 . you can use the Delete key on your keyboard. 3. Alternatively. perform the following steps: 1. use Ctrl + click to select the Channel Class ID and the Channel Total ID logical columns. Right-click either of the highlighted columns and select Delete to delete the columns. For the Channels logical table in the Business Model and Mapping layer. Click Yes to confirm the delete.

Repeat the steps to delete the following logical columns in the Customers table: ¾ Cust City ID ¾ Cust State Province ID ¾ Country ID ¾ Cust Main Phone Number ¾ Cust Total ID ¾ Cust Src ID ¾ Cust Eff From ¾ Cust Eff To ¾ Cust Valid 31 . Verify that the Channels logical table now has only four logical columns.4. 5.

32 . Place the cursor over the icon to display the screenshot and repeat the steps to delete the highlighted logical columns in the Products table. Place the cursor over the icon to display the screenshot and verify that the Customers logical table has only the following logical columns: 7.6.

Place the cursor over the icon to display the screenshot and repeat the steps to delete the highlighted logical columns in the Promotions table. Place the cursor over the icon to display the screenshot and verify that the Promotions logical table has only the following logical columns: 11.8. Place the cursor over the icon to display the screenshot and verify that the Products logical table has only the following logical columns: 9. 12. Do not delete any columns in the Times table. Save the repository. Do not check global consistency. 10. 33 .

Build Dimension Hierarchies Dimension hierarchies introduce formal hierarchies into a business model, allowing Oracle BI Server to calculate useful measures and allowing users to drill down to more detail. In a business model, a dimension hierarchy represents a hierarchical organization of logical columns belonging to a single logical dimension table. Common dimension hierarchies used in a business model are time periods, products, customers, suppliers, and so forth. Dimension hierarchies are created in the Business Model and Mapping layer and end users do not see them in end user tools such as Oracle BI Answers or Interactive Dashboards. In each dimension hierarchy, you organize dimension attributes into hierarchical levels. These levels represent the organizational rules and reporting needs required by your business. They provide the structure that Oracle BI Server uses to drill into and across dimensions to get more detailed views of the data. Dimension hierarchy levels are used to perform aggregate navigation, configure level-based measure calculations, and determine what attributes appear when Oracle BI users drill down in their data requests. To build the Channels dimension hierarchy in the SH business model, perform the following steps: 1. Right-click the Channels logical table and select Create Dimension.

34

2. Right-click the ChannelsDim object, which was created by the action in the previous step, and select Expand All.

3. Place the cursor over the icon to display the screenshot and verify that the ChannelsDim dimension hierarchy matches the picture.

4. Right-click the Channels Detail level and select New Object > Parent Level.

5. In the Logical Level dialog box, name the logical level Class and set the

35

Number of elements at this level to 3. This number does not have to be exact. The ratio from one level to the next is more important than the absolute number. These numbers only affect which aggregate source is used (optimization, not correctness of queries).

6. Click OK to close the Logical Level dialog box. The new Class level is added to the hierarchy.

7. Right-click the Class level and select Expand All.

36

Drag the Channel Class column from the Channel Detail level to the Class level to associate the logical column with this level of the hierarchy. Each level key can consist of one or more columns at this level. 10 In the Logical Level Key dialog box. The level key defines the unique elements in each logical level. Right-click Channel Class and select New Logical Level Key. 9. 37 .8. verify that Channel Class and Use for drilldown are selected.

13.11. The Channel Total Attribute level is added to the hierarchy. Right-click the Class level and select New Object > Parent Level. name the logical level Channel Total Attribute and set the Number of elements at this level to 1. 38 . In the Logical Level dialog box. The Channel Class column now displays with a key icon. Click OK to close the Logical Level Key dialog box. 12. 14. Click OK to close the Logical Level dialog box.

18. Drag the Channel Total column from the Channel Detail level to the Channel Total Attribute level.. 16. Right-click the Channel Total Attribute level and select Expand All. verify that Channel Total and Use for 39 . Right-click Channel Total and select New Logical Level Key. In the Logical Level Key dialog box.15. 17.

notice that Use for drilldown is selected. 40 . Click OK to close the Logical Level Key dialog box. Right-click the Channel Desc column and select New Logical Level Key.drilldown are selected. 21. 20. In the Logical Level Key dialog box. The Channel Total column now displays with a key icon. 19.

Both Channel Desc and Channel ID display with key icons. 41 . 24. 23. Click the Keys tab. Double-click the Channels Detail level to open the Logical Level dialog box. Click OK to close the Logical Level Key dialog.22.

uncheck Use for drilldown. 26. Notice that the key icons are different. In the Logical Level Key dialog box. Channel Desc is used for drill down Channels Detail_Key is 42 . 28. 27. Click OK to close the Logical Level Key dialog box.25. Click the Edit button. Click Channels Detail_Key.

Use the preceding steps. Save the repository. when a user drills down in Answers or a dashboard. Click OK to close the Logical Level dialog box. Place the cursor over the icon to display the screenshot and verify that the finished ChannelsDim hierarchy looks like the picture. 31. Optional: Build a dimension hierarchy for the Products logical table. when a user drills down from the Channel Class column (the next highest level). Later. the default is to drill down to the Channel Desc column. Based on this example. 30. the screenshot. set Number of elements at this level to 43 . and the characteristics below as a guide. The ProductsDim dimension hierarchy should have the following characteristics: ¾ For the Subcategory level. you use a different repository that already has the dimension hierarchies prebuilt. 29. Don't worry if you cannot complete this step. not the Channels Detail_Key column. 32. Do not check global consistency. the default drill is to the level key that has Use for drilldown checked in the next lowest level. In Part Two of this OBE.not.

¾ For the Category level. If you complete this step. Presentation layer objects can then be renamed and reorganized. Do not check global consistency. and rename data as necessary for the set of users. The Presentation layer provides a means to further simplify or customize the Business Model and Mapping layer for end users. Corresponding objects are automatically created in the Presentation layer. uncheck Use for drill down for Products Detail_Key (Prod ID). To build the Presentation layer. ¾ Check Use for drill down for all other keys in the ProductsDim hierarchy. Simplifying the view of the data for users makes it easier to craft queries based on users’ business needs because you can expose only the data that is meaningful to the users. such as Oracle BI Answers. 44 . save the repository. you perform the following steps: 1. set Number of elements at this level to 1. For example. organize the data in a way that aligns with the way users think about the data. It is the view of the data seen by end users in client tools and applications. Building the Presentation Layer of a Repository In this topic you use the Oracle BI Administration Tool to build the Presentation layer of a repository. set Number of elements at this level to 5. The Presentation layer is built after the Physical layer and Business Model and Mapping layer and adds a level of abstraction over the Business Model and Mapping layer. you can organize columns into catalogs and folders. ¾ For the Product Total Attribute level.21. Drag the SH business model from the Business Model and Mapping layer to the Presentation layer to create the SH catalog in the Presentation layer. ¾ For the Products Detail level. You typically create Presentation layer objects by dragging objects from the Business Model and Mapping layer.

Expand the SH catalog in the Presentation layer. 3. Save the repository. 45 . Notice that the tables and columns in the Presentation layer exactly match the tables and columns in the Business Model and Mapping layer.2. Do not check global consistency. Notice also that dimension hierarchies are not displayed.

Defining keys for physical tables is best practice. display results using 46 . you perform the following steps: Run a Consistency Check Enable Query Logging Create an empty Webcatalog to test your RPD Change the metadata files file and Start Oracle BI Services Use Oracle BI Answers to Execute Queries Use Query Log to Verify Queries Run a Consistency Check Consistency check is a utility in the Administration Tool that checks if a repository has met certain requirements. For example. You then test the repository by running queries using Oracle BI Answers. if there are physical tables with no keys defined. a detailed message alerts you to the nature of the inconsistency. There are options to display only selected message types. To test and validate a repository. You begin by checking the repository for errors using the check consistency option. the object type. if the Administrator user has an empty password this should be addressed. For each message the Consistency Check Manager identifies the message type. the object. For example. a best practice message is displayed. Best Practices messages provide information about conditions but do not indicate an inconsistency. The Consistency Check Manager displays three types of messages: Error messages indicate errors that need to be fixed to make the repository consistent. Finally. and provides a detailed description of the message. When a repository or business model is inconsistent.Testing and Validating a Repository You have finished building the initial business model and now need to test the repository before continuing your development. Repositories and the business models within them must pass the consistency check before you can make business models available for queries. you examine the query log file to verify the SQL generated by Oracle BI Server. depending upon the intent of the Oracle BI Server administrator. but is not a requirement for a consistent repository. Warning messages indicate conditions that may or may not be errors. but is not a requirement for a consistent repository.

3. You should receive a message indicating that the repository is consistent and asking if you want to make it available for queries. Click Yes to make the SH business model available for queries. you perform the following steps: 1. The Consistency Check Manager displays. check all objects in the repository. 2.qualified names. and copy the results to another file. 47 . Select File > Check Global Consistency. To check consistency.

5. Save the repository. you can ignore the messages for now and click Close. Notice that Available for queries is checked. Click OK to close the Business Model properties dialog box. Click No when asked to check global consistency (you just checked it). If you see only Warning and Best Practices messages. edit the repository to correct the inconsistencies and run the consistency check again.4. 8. 7. notice that the SH business model icon has changed to indicate the business model is now available for queries (the red circle with a line is gone). In the Business Model and Mapping layer. Double-click the SH business model object to open the Business Model properties dialog box. If the Consistency Check Manager displays any Error messages. 48 . 6.

The Administrator user appears in the right pane. Select Manage > Security. In the Password field. 4. 49 . select Users in the left pane. In the Security Manager. type Administrator and then confirm in the Confirm Password field. In the Logging level field. In the right pane. Verify that the User tab is selected. double-click Administrator.Enable Query Logging To enable query logging for the Administrator user. The User dialog box opens. 3. perform the following steps: 1. set the value to 2. 2.

retrieve the results. 50 . and examine the query log. 6. Do not check global consistency. Click Action > Close to close the Security Manager. 7. you need to generate some queries. Select File > Exit to close the Administration Tool. and technical support. 5. Save the repository. Click OK to close the User dialog box.To test the repository. You log query activity at the individual user level. Logging is intended for testing. In production mode. 8. logging is normally disabled because query logging can impact performance by producing very large log files. 9. debugging. Select File > Close to close the repository.

log). If Oracle BI Server detects a syntax error while loading the repository. You will find instructions for doing this in the online documentation. it logs the error to the server log file (. 51 .3.\\OracleBI\server\Log\NQServer.1..ini only if you wish to change system settings like turning caching on. Modify the NQSConfig. The Linux image includes a special Process Control page that allows us to easily perform this change to the server’s main metadata files through a web GUI.2\OracleBIData\web\catalog Create a new folder in this location called SH_Start Change the metadata files file and Start Oracle BI Services In this step. Browse to G:\biee\10. you start the Oracle BI Server service to load the SH repository into memory. An entry in the Repository section of the initialization file NQSConfig. 1. We will create a new Web catalog to start our testing of the SH.ini instructs Oracle BI Server to load a specific repository into memory upon startup.Create an empty Webcatalog to test your RPD The end-user report objects are stored in a Web Catalog.rpd..

xml. Ensure that the previous step is completed and that the files listed under each service are correct. you will need to explicitly start them. Oracle BI Presentation Server and Oracle BI Java Host services were not started prior to making the previous change. Check the BI Server and BI Presentation Server boxes and click Start Wait until all the relevant flags go green 52 .com/go/process_control/pc. Open the Process Control Page: http://oracle2go.oracle.html Select Repository: sh.The path to the Web Catalog is stored in another initialization file called InstanceConfig.rpd and Web Catalog SH_Start Click SET 2.us. If the Oracle BI Server. The editing of this file has also been simplified on the Linux image by the Process Control page 1.

Log in to Oracle Business Intelligence as Administrator with password Administrator 3. Click the Cust State Province column in the left pane to add it to the request criteria on the right. Click the Answers link. click the Customers folder to expand it. 4. Click the SH subject area. 2.Use Oracle BI Answers to Execute Queries To start Oracle BI Answers and execute a query. Select Start > Programs > Oracle Business Intelligence > Presentation Services. Click the Sales Facts folder in the left pane to expand it. 53 . In the left pane. 5. perform the following steps: 1. Notice that the folders and columns in Answers match the folders and column in the Presentation layer of the repository. 7. 6.

results are displayed in a compound layout. By default. Click the Amount Sold column to add it to the request criteria. Click the Results tab. 10.8. consisting of a title and a table view. 54 . 9.

In the Session Management window. Click the Manage Sessions link to open the Session Management window. Click Settings > Administration to open the Oracle BI Presentation Services Administration Window. The log file should look similar to the picture. click the View Log link for the last entry.Use Query Log to Verify Queries 1. The log displays the last query executed by Administrator. 3. 4. 2. under Cursor Cache. 55 .

Congratulations! Up to this point you have successfully built the Physical. Leave Answers open. just below the SQL Request section. This section contains the logical SQL issued from Answers. number of rows returned. Locate the General Query Info section. just below the General Query Info section. Locate the Sending query to database named SH section. This section identifies the repository. 6. run a consistency check. and so forth. Click Finished to close the Session Management window. and presentation catalog from which the query was run. adding multiple logical table sources. building variables and initialization blocks. mapping to aggregate tables. subject area. Click Close Window to close the Oracle Bi Presentation Services Administration window. For the remainder of this OBE you enhance the repository by performing tasks such as building calculation measures.Locate the SQL Request section. 7. Business Model and Mapping. Close the query log. This section identifies the physical data source to which Oracle BI Server is connecting and the physical SQL that was generated. 5. and tested the repository using Oracle BI Answers. and Presentation layers of a repository. and so forth. 56 . 8. The rest of the file contains information such as query status.

You use logical columns for calculation formulas that require an aggregation rule that is applied before the calculation. The advantages to building calculation measures in the repository is the measures are built once and can be made available to all users. You can also build calculation measures in Answers. In the examples in this lesson. To create calculation measures. You use physical columns for calculations that require and aggregation rule to be applied after the calculation. All three methods are covered in this OBE. use physical columns as objects in a formula. you have to map for each physical source it could be derived from. or use the Calculation Wizard to automate the process. Users can then easily build queries using familiar terminology.Creating Calculation Measures Often. Oracle BI Server has a calculation engine to perform a multitude of calculations. Calculation measures allow end users to ask business questions like “Show me the accounts receivable balance as of Q3” or “Show me the difference between units ordered and units shipped. When you create formulas based on physical columns. The advantage of defining a logical column formula based on existing logical columns is that you only have to define it once.” An Expression Builder enables you to create expressions that are similar to expressions created with SQL. you use the Expression Builder to create calculation measures that appear as columns to users in Answers. There are different methods for creating calculation measures in the Administration Tool. a business wants to compare values of a measure and needs a calculation to express the comparison. you perform the following steps: Create a BI Server ODBC Connection Load a Prebuilt Repository Create a New Measure Create a Calculation Measure Using Answers Create a Calculation Measure Using Logical Columns Create a Calculation Measure Using Physical Columns Create a Calculation Measure Using the Calculation wizard 57 . You can use existing logical columns as objects in a formula.

requests being sent to the server as Logical SQL queries. we need to first create the necessary ODBC DSN: 1. Enter a suitable name for the DSN e.Create a BI Server ODBC Connection To edit the RPD while the server is running it is necessary to create a direct connection to the server rather than opening up the . ¾ Login ID: Administrator ¾ Password: Administrator ¾ Port: 9703 Check the box “Connect to the Oracle BI Server to obtain default settings…” 58 . LinuxPEServer-SalesHistory Enter oracle2go for the Server Click Next > 4. Open Start > Control Panel > Administrative Tools > Data Sources (ODBC) 2. The Oracle BI Server provides an ODBC API just for this purpose.g. This is also the way that Presentation Services connects to the mid-tier BI Server.rpd “Online”. Click on the System DSN tab and select Add… 3.rpd file on it’s own. To connect to this layer to modify the .

Hit OK to close the ODBC Administrator 59 . Change the default Catalog to SH Click Finish 6.Click Next > 5.

Using Windows Explorer. To load the prebuilt repository.oracle.com/go/process_control/pc.rpd to SH. Start the Oracle BI Server service from the process control page: http://oracle2go. Using Windows Explorer.ini file.html 2. navigate to the SetupFiles folder and copy the SH_PartTwo.3. Type Administrator in the Password field and click Open. 6. 8. you modified the entry in the Repository section of the initialization file to instruct Oracle BI Server to load the SH repository into memory upon startup. but with the following relevant differences: Physical joins are built for the the COSTS physical table in the Physical layer. The provided repository is similar to the repository you built in the first part of this OBE.html 7. and TimesDim.us. There are four additional dimension hierarchies: CustomersDim.rpd file to G:\biee\10. 3. select the LinuxPEServer-Sales History DSN you created earlier. in an earlier step. 5. navigate to G:\biee\10. There is no need to update the NQSConfig. 4. Rename SH_PartTwo.1. PromotionsDim. perform the following steps: 1.rpd. Change the name of the SH.2\OracleBI\server\Repository.oracle. ProductsDim. 9. 10 The SH repository opens in online mode.Load a Prebuilt Repository A prebuilt repository is provided to expedite your completion of the remaining exercises in this OBE.rpd. Stop the Oracle BI Server service using the Process control page: http://oracle2go. Click File > Open > Online.com/go/process_control/pc. because.2\OracleBI\server\Repository. 60 . In the Open Online dialog box.3.us. Click Start > Programs > Oracle Business Intelligence > Administration to open the Administration Tool.1.rpd file to SH_PartOne.

Up to this point .. Oracle BI Server has already opened the repository file and the operating system has put a write-lock on the file. you pick an Oracle BI ODBC DSN that points to the repository you want to edit (i. PromotionsDim. The Administration Tool then communicates changes to Oracle BI Server and Oracle BI Server makes the corresponding changes to its in-memory copy. tells the OS to save the changed file. makes those changes to its in-memory copy. In offline mode the relationship between the Administration Tool and the repository is like the relationship between any Windows application and a file. 12 When Update Row Counts completes. If desired. you develop a repository in offline mode and use online mode for minor updates and changes. the relationship is different. This may take a . An application. the Administration Tool in this case. opens a file for editing.. Typically. and. few minutes. When the Administration Tool tells it to. expand the Physical layer and verify that . click Tools > Update All Row Counts. examine the structure of the provided repository before proceeding with the remaining steps in this OBE. examine the relevant differences: the physical joins for the COSTS physical table.e. Now that you have a consistent repository and Oracle BI Server is running and using the repository. when told by the Administration Tool. makes changes to its in-memory copy. you can make changes to the metadata in online mode. Oracle BI Server sends the Administration Tool a copy of its in-memory repository. Oracle BI Server can act as an agent of the Administration Tool. In particular. row counts appear for all tables and columns. and tells the OS to save the changed file. ProductsDim. the repository that is the default repository in the DSN). Then it listens for messages from the Administration Tool about changes. all the changes you have made to the repository have been in offline mode. In online mode. 61 . and TimesDim. In this mode. 11 To verify connectivity. When you start the Administration Tool in online mode. and the four additional dimension hierarchies: CustomersDim.

If you do not see the red check marks. At that point the changes you made become active. 62 . Thus. When you are finished editing. you must check out objects before editing them. Once the objects have been edited. objects were checked out automatically when you ran Update Row Counts. the Administration Tool is configured to check out objects automatically. select Tools > Options > General Tab > Check out objects automatically. you can save the changes to the repository. you check them in again.Notice that the objects have a red check mark. Since Oracle BI Server may be processing queries while you are editing the repository in online mode. In this example.

In the Physical layer. and rename the column to Unit Cost. 63 . Alternatively. navigate to COSTS > UNIT_COST. Drag UNIT_COST from the Physical layer to the SALES logical table source for the Sales Facts logical table. UNIT_COST appears as a logical column in the Sales Facts logical table. Right-click the UNIT_COST logical column.Create a New Measure To add a new measure to the Sales Facts table. perform the following steps: 1. 3. 2. select Rename. slowly double-click the column to make it editable.

64 . Click File > Check In Changes or click the Check In Changes button on the toolbar to check in changes.. 5. 6. Review the messages. Hint: doubleclick the column to open the Logical Column properties dialog box and click the Aggregation tab.4. The Consistency Check Manager opens and displays Warnings and Best Practices messages. Drag the Unit Cost logical column to the Sales Facts presentation folder. 7. Click Yes when prompted to check global consistency. Set the aggregation rule for the Unit Cost logical column to SUM.

65 . . If you desire. and then click the Disable button.8. Click the Options tab. 11 Click the Messages tab. review the other Best Practices items that are checked. review the other Warnings items that are checked. select Check Features Match Default. For the purposes of this tutorial. 10 Select Best Practices > Physical Table > Search for Tables With No Keys. . If you desire. you disable the Warnings and Best Practices messages. 9. and then click the Disable button. Expand Warnings folder.

15 Return to Answers to test the new column in Answers. Times. Sales Facts. Sales Facts. . indicating a consistent repository.12 Click Check All Objects. . 16 Click Reload Server Metadata. log in as Administrator with password Administrator. 18 Click Results. click the Answers link. 13 Click Close to close the Consistency Check Manager. If Answers is not open. 14 Save the repository. and click the SH subject area. The Consistency Check Manager displays with no . 19 Click Settings > Administration > Manage Sessions > View Log to view the . select Start > Programs > Oracle Business Intelligence > Presentation Server. 17 Build the following request: . . query log and examine the SQL generated by the request.Calendar Year. 66 .Amount Sold. messages. .Unit Cost. .

Click the Criteria tab.Create a Calculation Measure Using Answers Before you create calculation measures in the metadata using the Administration Tool. you create a calculation measure using Answers. click to the right of "Sales Facts". 4. 2. 5. The Edit Column Formula dialog box displays with "Sales Facts". Add another Amount Sold column to the request. 3. The request from the previous set of steps should still be open. perform the following steps: 1. Click the Edit Formula button for the Amount Sold column that you just added. In the Edit Column Formula dialog box. To create a calculation measure using Answers."Amount Sold" in the Column formula field."Amount Sold" in the Column Formula field. 67 . You do this so you can compare your results later when you create similar calculations measures in the repository. 6. Click the Minus operator to add it to the formula.

68 . click Sales Facts > Unit Cost to add it to the formula. 10.7. In the Custom Heading field. type Gross Profit. 9. 8. In the left panel. Click the Custom Headings check box.Click OK to close the Edit Column Formula dialog box and verify the change to the request.

11. 13. 69 .Leave Answers open for the next topic. 12.Click Settings > Administration > Manage Sessions > View Log to view the query log.Click Results.

Return to the SH repository. In the Logical Column dialog box. 4. perform the following steps. Select Sales Facts in the middle pane. and click Insert. using existing logical columns to define the calculation formula. 3. 2. 6. In the left pane. Right-click the Sales Facts logical table and select New Object > Logical Column. click Logical Tables. Amount Sold in the right pane. you define a new calculation measure named Gross Profit in the Sales Facts logical table. 70 . Click the Expression Builder button (three dots) to open the Expression builder. The Amount Sold column is added to the formula. To create a calculation measure using logical columns. name the logical column Gross Profit and check Use existing logical columns as the source.Create a Calculation Measure Using Logical Columns In this topic. 5. 1. which should still be open in online mode in the Administration Tool.

Notice that the formula appears in the Logical Column dialog box. Click the minus sign operator to add it to the formula.7. Double-click Unit Cost in the right pane to add it to the formula. 71 . 9. Click OK to close the Expression Builder. 8.

The Gross Profit logical column appears in the business model. you must correct the errors before continuing. Drag the Gross Profit logical column to the Sales Facts table in the Presentation layer. 16. close the Consistency Check Manager. If there are Error messages. which should still be open from the previous topic. 13.10. Return to Answers. If the repository is consistent (no Error messages). Click Reload Server Metadata. Check in changes. 15. Save the repository. 11. 14. Click OK to close the Logical Column dialog box. Click Yes when prompted to check global consistency. 72 . 12.

Sales Facts.17. (If the request from the previous topic is still open. Sales Facts.Unit Cost. 18. Create the following request.Gross Profit 73 .Calendar Year ¾ Sales Facts. Expand Sales Facts and verify that the Gross Profit column is now visible in Answers. delete the Gross Profit column you created in Answers and then add the Gross Profit column you created in the repository to the query.) ¾ Times.Amount Sold.

c1 as c4 in the example pictured here). Leave Answers open for the next topic.19. 24. 20. Note that the difference between AMOUNT_SOLD and UNIT_COST is being calculated in the outer query block (SAWITH0. Because you defined the Gross Profit calculation using logical columns. Click Settings > Administration > Manage Sessions > View Log to view the query log. the columns are summed first and then the difference is calculated.SAWITH0. Close the query log. Click Results. You compare these results to the query results in the next practice. Click Finished to close the Session Management window. Verify that the results are the same as for the query you built using the Gross Profit column created in Answers.c2 . Click Close Window to close Oracle BI Presentation Services Administration. Your results should look similar to the picture. 22. 21. 23. 74 .

Click OK to close the Logical Column dialog box. 5. 4. using physical columns to define the calculation formula. In the Logical Column dialog box.Create a Calculation Measure Using Physical Columns In this topic. 2. Click the Aggregation tab. 6. Return to the SH repository. Right-click the Sales Facts logical table and select New Object > Logical Column. 1. you define a new calculation measure named Gross Profit Physical in the Sales Facts logical table. Gross Profit Physical is 75 . which should still be open in online mode in the Administration Tool. 3. To create a calculation measure using physical columns. Set the default aggregation rule to SUM. perform the following steps. name the logical column Gross Profit Physical.

select Physical Tables > SALES > 76 . 9. 10 In the Expression Builder. 7.added to the business model. The Logical Table Source dialog box opens. Click the Column Mapping tab. Click the Expression Builder button for the Gross Profit Physical logical column. 8. Expand Sales Facts > Sources and double-click the SALES logical table source.

.

AMOUNT_SOLD and then click the Insert button to add the column to the formula.

11 Click the minus sign operator to add it to the formula. . 12 Select Physical Tables > COSTS > UNIT_COST and then click the Insert . button to add the column to the formula.

13 Click OK to close the Expression Builder. Notice that the expression is added . in the Logical Table Source dialog box.

77

14 Click OK to close the Logical Table Source dialog box. The icon for Gross . Profit Physical changes to indicate an aggregation rule is applied.

15 Drag Gross Profit Physical to Sales Facts in the Presentation layer. .

16 Check in changes. . 17 Click Yes when prompted to check global consistency. If the repository is . consistent (no Error messages), close the Consistency Check Manager. If there are Error messages, you must correct the errors before continuing. 18 Save the repository. . 19 Return to Answers, which should still be open from the previous topic. . 20 Click Reload Server Metadata.

78

.

21 Expand Sales Facts and verify that the Gross Profit Physical column is now . visible in Answers.

22 Create the following request. . ¾ Times.Calendar Year, Sales ¾ Facts.Amount Sold, Sales Facts.Unit Cost, Sales Facts.Gross Profit Physical

23 Click Results. Verify that the results are the same for the Gross Profit . Physical (built using physical columns) as they were for the Gross Profit column (built using logical columns).

79

Your results should look similar to the picture. the results are the same for the logical column and the physical column calculations. Note that the difference between amount sold and unit cost is calculated first and then summed: sum(T245. . 26 Click Finished to close the Session Management window.AMOUNT_SOLD . 24 Click Settings > Administration > Manage Sessions > View Log to view . whereas the calculation formula for the physical columns looks like this: sum(AMOUNT_SOLD – UNIT_COST). 27 Click Close Window to close Oracle BI Presentation Services Administration.The calculation formula for the logical columns looks like this: sum(Amount Sold) – sum(Unit Cost). Because of arithmetic laws. So in this example. .T168. 80 . the query log. you know that you can sum ColumnA and sum ColumnB and then take the differences of those sums. . 25 Close the query log. 28 Leave Answers open for the next topic.UNIT_COST)in the example pictured here. and have exactly the same results if you calculate the difference first (the value in ColumnA – the value in ColumnB for each row) and then sum the difference. .

perform the following steps: 1. which should still be open in online mode in the Administration Tool. 81 . you use the Calculation Wizard to define a new calculation measure named Share of Category in the Sales Facts logical table. 3. Return to the SH repository. 2. Right-click the Amount Sold logical column and select Duplicate. A new column named Amount Sold#1 is added to the business model.Create a Calculation Measure Using the Calculation wizard In this topic. To create a calculation measure using the Calculation Wizard.

Click the Levels tab and select Category as the logical level for ProductsDim. Rename Amount Sold#1 to Category Sales. 8. 6. 5. Category Sales is now a level-based measure that will calculate total sales at the category level when used in a query. You use the Calculation Wizard to create a share measure in the steps that follow. Click OK to close the Logical Column dialog box. Level-based measures are useful for creating share measures. 7.4. 82 . Right-click Amount Sold and select Calculation Wizard. Double-click Category Sales to open the Logical Column dialog box.

Check Category Sales as the column to compare with Amount Sold.Click Next.Uncheck Change and Percent Change and check Percent. 11. 83 . Click Next. 12. 10.9.

Click Next.13.Click Finish.Change Calculation Name to Share of Category. 15. 14. Share of Category is added to the business model.Drag Category Sales and Share of Category to Sales Facts in the 84 . 16.

Click Reload Server Metadata. If there are Error messages.Click Yes when prompted to check global consistency. If the repository is consistent (no Error messages). Notice the sort settings for the Prod Category and Amount Sold columns. 22. 85 .Presentation layer.Place the cursor over the icon to display the screenshot and use it as a reference to create a query. 24. 18. close the Consistency Check Manager. which should still be open from the previous topic. 21. 20.Return to Answers. 17. you must correct the errors before continuing.Expand the Times folder.Expand Sales Facts and verify that Category Sales and Share of Category are now visible in Answers.Save the repository. 23.Check in changes. 19.

Click the All Choices link.Hold down the Ctrl key and click the Calendar Year column to open the Create/Edit Filter dialog box.Click Results. 27. 29.Click 2001 to add it to the Value field. 28.25. The filter is added to the request.Click OK to close the Create/Edit Filter dialog box. Only partial results are shown in the picture. 26. 86 .

30. where you can create and edit tables. and rename data as necessary for the set of users. For example. Organizing the Presentation Layer The Presentation layer is built after the Physical layer and Business Model and Mapping layer and adds a level of abstraction over the Business Model and Mapping layer. Presentation catalogs allow you to show different views of a business model to different sets of users. Changes to 87 .Leave Answers open. However. or delete Presentation layer tables. such as Oracle BI Answers. Corresponding objects are automatically created in the Presentation layer. Presentation catalogs contain presentation tables. They cannot span business models. multiple presentation catalogs can refer to the same business model. You can use the Presentation Tables tab in the Presentation Catalog properties dialog box to reorder. Simplifying the view of the data for users makes it easier to craft queries based on users’ business needs because you can expose only the data that is meaningful to the users. organize the data in a way that aligns with the way users think about the data. You typically create Presentation layer objects by dragging objects from the Business Model and Mapping layer. You can also use this tab to access the Presentation Table dialog box. You also can manually create catalogs and folders based on the needs of your users. The Presentation layer provides a means to further simplify or customize the Business Model and Mapping layer for end users. It is the view of the data seen by end users in client tools and applications. you can organize columns into catalogs and folders. sort. Presentation catalogs have to be populated with content from a single business model.

you can drag a column from a single logical table in the Business Model and Mapping layer onto multiple presentation tables. Use presentation tables to organize columns into categories that make sense to the user community. 3. Presentation columns define the columns used to build queries in the Oracle BI user interface. Return to the SH repository. To provide a convenient organization for your end users. Presentation tables contain presentation columns. You can also use this tab to access the Presentation Column dialog box. In the Presentation layer. perform the following steps: 1. 88 .the Presentation layer do not impact corresponding objects in the Business Model and Mapping layer. or delete Presentation layer columns. A presentation table can contain columns from one or more logical tables. where you can create and edit columns. 2. which should still be open in online mode in the Administration Tool. by default. Use the Columns tab in the Presentation Table properties dialog box to reorder. The names and object properties of the presentation tables are independent of the logical table properties. Presentation tables appear as folders in the Oracle BI user interface. The presentation column names are. Presentation tables contain presentation columns. double-click the SH presentation catalog to open the Presentation Catalog dialog box. Click the Presentation Tables tab. sort. To organize the Presentation layer. such as Oracle BI Answers. identical to the logical column names in the Business Model layer.

The description displays as a tool tip in Answers. Adding -> in the description nests the table under the table above it. In the Description field. type -> Calendar time attributes. Click OK to close the Presentation Table dialog box. Click the General tab and name the presentation table Calendar. 5. Repeat the steps and create another presentation table named Fiscal with >Fiscal time attributes in the Description field. Drag the tables or use the Up and Down buttons to rearrange the tables in the following order: ¾ Times 89 . 9. To create a new presentation Table. 6. 7. click the Add button to open the Presentation Table dialog box.4. 8.

14. 12.Drag the columns or use the Up and Down arrows to reorder the columns. A suggested approach is to order the columns hierarchically from top to bottom.¾ ¾ ¾ ¾ ¾ ¾ ¾ Fiscal Calendar Products Customers Channels Promotions Sales Facts 10. The column order is changed in the Presentation layer. 90 . 11. The new tables are added to the Presentation layer and the presentation tables are reordered.Click the Columns tab.Double-click the Channels presentation table to open the Presentation Table dialog box.Click OK to close the Presentation Table dialog box. 13.Click OK to close the Presentation Catalog dialog box.

If the repository is consistent (no Error messages). Use Shift+click and Ctrl+click to select multiple columns. 20. 16.Click Reload Server Metadata.Click Yes when prompted to check global consistency. If there are Error messages. close the Consistency Check Manager.Save the repository. 21. 19. 91 . 17. which should still be open from the previous topic.Expand the Times presentation table. 18.Return to Answers. you must correct the errors before continuing.15.Check in changes.Use cut and paste to move all the fiscal columns from the Times presentation table to the Fiscal presentation table and all the remaining columns from the Times presentation table to the Calendar presentation table.

Leave Answers open.Verify that the Fiscal and Calendar folders are nested under the Times folder.Verify that the columns in the Fiscal and Calendar folders appear as expected. 24. 92 .22.Verify that the Channels columns appear as expected. 23. 25.

Oracle BI Server substitutes the value of a variable for the variable itself in the metadata. A repository variable has a single value at any point in time. you perform the following steps: Create an Initialization Block for Session Variables Test the Initialization Block and Session Variables Create a Dynamic Repository Variable 93 . You use the Variable Manager to define variables and initialization blocks. Session variables are created and assigned a value when each user logs on. A variable has a single value at any point in time. Static repository variables have values that are constant and do not change while Oracle BI Server is running. There are two types of session variables: system and nonsystem. and nonsystem session variables. session variables. Dynamic repository variables have values that are refreshed by data returned from queries in initialization blocks. System variables have reserved names and are used for specific purposes by Oracle BI Server. Repository variables are represented by a question mark icon in the Variable Manager. system session variables. Initialization blocks are used to initialize dynamic repository variables. There are two classes of variables: repository variables and session variables. There are two types of repository variables: static and dynamic. System and nonsystem variables are represented by a question mark icon in the Variable Manager. Variables can be used instead of literals or constants in the Expression Builder in the Administration Tool. and dynamic repository variables. Non-system variables are applicationspecific variables created by an Administrator. To create initialization blocks.Using Initialization Blocks and Variables You can use variables in a repository to streamline administrative tasks and modify metadata content dynamically to adjust to a changing data environment. such as authenticating users.

A session is an instance of a user running the client application. the initialization of session variables is not scheduled. however. 94 . there are as many instances of a session variable as there are active sessions on Oracle BI Server. Unlike a repository variable. 3. To create an initialization block for session variables.Create an Initialization Block for Session Variables Session variables are like dynamic repository variables in that they obtain their values from initialization blocks. Click Manage > Variables to open the Variable Manager. Oracle BI Server creates new instances of session variables and initializes them. Return to the SH repository. 2. Unlike dynamic repository variables. Each instance of a session variable could be initialized to a different value. When a user begins a session. perform the following steps: 1. The session starts when the application is started and ends when the application is exited. Click Session > Initialization Blocks. which should still be open in online mode in the Administration Tool.

Right-click in the white space on the right and select New Initialization Block. 95 . type setUser in the Name field. 6. Click the Edit Data Source button to open the Session Variable Initialization Block Data Source dialog box. In the Session Variable Initialization Block dialog box. 5.4.

In the Default Initialization String field. 'CountryManagers'. The initialization string is visible in the Session Variable Initialization Block dialog box. Click the Browse button and select SH > Connection Pool in the Select Connection Pool dialog box. Click OK to close the Session Variable Initialization Block Data Source dialog box. 8. type the following initialization string: select ':USER'. 2 from Dual 10. 96 . 9.7. Double-click Connection Pool or click the Select button to add the connection pool to the Session Variable Initialization Block Data Source dialog box. case when upper(':USER') = 'KURT' then 'Germany' when upper(':USER') = 'KEIKO' then 'Japan' when upper(':USER')= 'CHARLES' then 'United Kingdom' when upper(':USER') = 'KAREN' then 'United States of America' end.

Click Yes when prompted about the USER session variable having a special purpose. 16. Click New to open the Session Variable dialog box. 13. The USER variable is added to the Session Variable Initialization Block Variable Target dialog box. 12.11. type USER. 97 . 15. Click OK to close the Session Variable dialog box. In the Name field. Click Edit Data Target to open the Session Variable Initialization Block Variable Target dialog box. 14.

Repeat the steps and add three more variables: UserCountry.17. The order is important. The order of the variables must match the order of the values for the variables in the initialization string in the initialization block. Click Yes when promoted about the GROUP and LOGLEVEL session variables having a special purpose. and LOGLEVEL. GROUP. 98 .

Click OK to close the Session Variable Initialization Block Variable Target dialog box. Save the repository. 99 .18. 21. 20. Check in changes. 22. The setUser initialization block is visible in the Security Manager. Click Action > Close to close the Variable Manager. The variables are displayed in the Variable Target section of the Session Variable Initialization Block dialog box. 19. Click OK to close the Session Variable Initialization Block dialog box.

Test the Initialization Block and Session Variables 1. Name the group CountryManagers. 5. 2. Click Manage > Security to open the Security Manager. 100 . Right-click the white space in the right pane and select New Security Group. Click Groups in the left pane. Click the Permissions button to open the User / Group Permissions dialog box. 3. 4.

Click the Expression Builder button (three dots) on the right to open the 101 .6. 7. 9. Click the Add button. Click Select to add Customers to the User / Group Permissions dialog box. Click the Filters tab. Click the Customers presentation table. 8. 10.

12. The filter is added in the User / Group Permissions dialog box. Click OK to close the Expression Builder. Select Session Variables > UserCountry and click the Insert button to add UserCountry to the formula as an argument in the VALUEOF() function. Click the = operator to add it to the formula. 13. 11. 14. Select Logical Tables > Customers > Country and then click the Insert button to add Country to the formula. 102 .Expression Builder (you may need to scroll to see the button).

18. Click OK to close the Group dialog box.Calendar Year. Sales Facts. Keiko. Karen = United States of America). 16. 21. 23. Times. Click Results. 20. The results of the query should correspond to the the user's country (Kurt = Germany. 22. Check in changes.Calendar. CountryManagers is added as a group in the Security Manager. The picture shows the results when the user = Kurt. 24.Country. Create the following query: Customers. Return to Answers. 17. Log out of Answers. Charles = United Kingdom. or Karen. Click OK to close the User / Group Permissions dialog box.Amount Sold. Keiko = Japan.15. Charles. Test the initialization block by logging in to Answers as one of the users in the initialization block: Kurt. Click Action > Close to close the Security Manager. Save the repository. 19. 103 .

Leave Answers open. Name the initialization block getMaxSalesDate. 5. 2. 6.25. Click the Browse button to open the Select Connection Pool dialog box. Click Edit Data Source to open the Repository Variable Init Block Data Source dialog box. 7. Return to the SH repository open in online mode. Click Repository > Initialization Blocks. Click Manage > Variables to open the Variable Manager. 4. 3. Right-click the white space and select New Initialization Block to open the Repository Variable Init Block dialog box. 104 . Create a Dynamic Repository Variable 1.

CALENDAR_MONTH_ID from TIMES WHERE TIME_ID = (select max(TIME_ID) from SALES) 10. Double-click the SH > Connection Pool object to add it to the Connection Pool field in the Repository Variable Init Block Data Source dialog box. 105 . CALENDAR_YEAR.8. 9. In the Default Initialization String field. CALENDAR_MONTH_DESC.Click OK to close the Repository Variable Init Block Data Source dialog box. The connection pool and initialization string are added to the Repository Variable Init Block dialog box. type the following SQL: select TIME_ID.

11.Use the New button to create four variables: maxSalesDate. maxYear. 12. 106 .Click Edit Data Target to open the Repository Variable Init Block Variable Target dialog box.

13. 16. 17.Click Test and verify you get the results in the picture. 107 .maxMonthDesc.Click OK to close the Repository Variable Init Block Data Source dialog box. and maxMonthID. The order is important. 14. The variables appear in the Variable Target field in the Repository Variable Init Block dialog box.Click Edit Data Source to open the Repository Variable Init Block Data Source dialog box.Click OK to close the Repository Variable Init Block Variable Target dialog box.Close Results. The order of the variables must match the column order in the initialization string. 15.

Build the following query: Calendar. 19. 24.Select File > Check Global Consistency. The getMaxSalesDate initialization block is displayed in the Variable Manager. close the Consistency Check Manager. 20.18. 108 . If the Consistency Check Manager displays any errors.Click OK to close the Repository Variable Init Block dialog box.Click Action > Close to close the Variable Manager.Amount Sold. Sales Facts.Return to Answers.Save the repository.Select Repository > Initialization Blocks > Variables > Dynamic to see the variables displayed in the Variable Manager. edit the repository to correct the errors before continuing. 23.Click the Add Filter button for the Calendar Year column.Check in changes. If there are no error messages. 26. 22. 25. 21.Calendar Year.

Click Results and verify that Calendar Year returns the expected result. 109 .Click OK to close the Create/Edit Filter dialog box. 28. click Add > Variable > Repository.27. 29.In the Server Variable field. The filter is added to the request. 30. type maxYear.In the Create/Edit Filter dialog box.

SHQuota.rpd that you backed-up as SH_backup. This equates to the folder /ora/ in the Linux file system. When a logical table source does not contain the entire set of data at a given level. you need to specify the portion of the set that it does contain. Select File > Import > from Database. Import the XML data source into the repository 1. When there are multiple sources. go to the Process Control page and change the BI Server to use the original SH. 110 . The goal is to provide seamless and efficient access from the users' perspective. First. To add quota information to the business model. Return to the SH repository open in online mode. copy the file SHQuota. you perform the following steps.xml. In this example. Import the XML data source into the repository Map the Logical Dimension Columns Setup Time Alias on imported XML source Create the quota measures Test the Quota Measures. 2.Adding Multiple Sources Data is often partitioned into multiple physical sources for a single logical table in a business model. the metadata is built so that Oracle BI Server handles the navigation to the appropriate source. Oracle BI Server can seamlessly access and process data from multiple sources in an efficient manner to satisfy users’ requests. sales quota numbers are stored in an XML file. Oracle BI Server needs to know the content of the sources in order to pick the appropriate source for the query. You incorporate the quota numbers into the business model and create business measures to report variance from quota and percent of quota. When individual sources at a given level contain information for a portion or fragment of the domain.rpd at the beginning of this entire tutorial. Also.xml to the network drive G:\.

Verify that Tables are checked and click Import. Insert the URL: G:\SHQuota. 4.xml Leave the XSLT and other parameters blank. In the Import dialog box. Click OK. select the top level SHQuota.3. 5. Change the Connection Type to XML in the dropdown. 6. Click OK to accept the default configuration for the XML Connection Pool 111 . The Import dialog box opens.xml object.

Double-click the Table database object in the Physical layer (SHQuota) to open the Table dialog box. Since this file needs to be accessed by the Linux server we need to change the path to the file.7. 9. Change the URL from G:\SHQuota. 8.xml 112 . close the Import dialog box and verify that the SHQuota table has been imported into the Physical layer. When import completes.xml to /ora/SHQuota. Click the XML tab.

11.Check in changes. 113 .Save the repository.Click OK to close the Table dialog box.Likewise. change the following other column types: ¾ Quota: DOUBLE ¾ Year: INT ¾ QtrNumber:INT 12. Click on the Columns tab. 14.10. Double-click on Amt column and change Type to DOUBLE. 13.Since XML is all text by default. Click OK. this time we need to manually tell the server what format the column data is expected in.

Notice the logical to physical column mappings. 114 . Double-click the SHQuota logical table source in the Customers > Sources folder to open the Logical Table Source dialog box. In the Business Model and Mapping layer. Drag the physical column Country from SHQuota in the Physical layer to the logical column Customers.Map the Logical Dimension Columns 1. Click the Column Mapping tab. 2. Drag the physical columns SubRegion and Region from SHQuota in the Physical layer to the corresponding logical columns in the Customers table in Business Model and Mapping Layer. Notice that a new logical table source. expand Customers > Sources and note that there are two logical table sources: CUSTOMERS and COUNTRIES. is created automatically.Country in the Business Model and Mapping layer. 5. SHQuota. 4. 3.

Prod Category to Category and verify the logical table source mapping. the Time attributes must be in a separate physical layer table definition from other attributes. Select New Object > Alias. Setup Time Alias on imported XML source The Time Comparison measure functions Ago() and ToDate() used elsewhere in this tutorial enforce requirements on the physical tables. 1. Specifically. We need to use this approach for the imported XML file. Repeat the steps and map Products. Right click on SHQuota. 11. Call the object TimeAlias 115 .6. Click OK to close the Logical Table Source dialog box. This can be easily achieved in most instances via the use of an alias.

Create a join on ALL COLUMNS by multi-selecting all columns from both table lists. Create a foreign key join from the TimeAlias table to the SHQuota table: ¾ Click on the foreign key button: ¾ The icon should remain pushed in ¾ Now click first on the TimeAlias table and then click on the SHQuota table (The join path should appear as a line from the source to target as you drag the mouse between the first and second click) 4. The expression for the join should correctly map each column from parent to child but can be edited if it is not as shown below: 116 . Right-click on the XML database and select Physical Diagram > Selected Objects Only 3.2.

Fix any errors before proceeding. 8. 6. this join on all columns ensures we can model the XML file as an aggregate time dimension without worrying about double-counting quotas. Accept the table key creation by clicking Yes. Check in changes. Save the repository.Since we don’t have a dedicated dimension table at the quarter level. 9. 117 . 5. Check global consistency. The joined Tables should appear in the Physical layer as follows: 7.

and a new logical column. Quota. Double-click Sales Facts. The Quota logical column states quota in thousands. Drag the column SHQuota. 4. Notice that a new logical table source. Close the Logical Table dialog box. so rename Quota to Quota (000). 12.Quota from the Physical layer onto the Sales Facts logical table.Create the quota measures 1. 5. are created.Set the Level of the Quota (000) Measure according to the granularity of the XML file: 118 . SHQuota. Click the Aggregation tab and set the aggregation rule to Sum.Quota to open the Logical Table dialog box. 3. 2.

Check Use existing logical columns as the source."Sales Facts". 7. Right-click Sales Facts and select New Object > Logical Column to open the Logical Column dialog box.Create the following formula: 1000*"SH". Click the Expression Builder button (three dots) to open the Expression Builder. 10.6."Quota (000)" 119 . 8. 9. Click the General tab and name the logical column Quota.

120 .Click Next.Amount Sold and select Calculation Wizard.Click Next. 13. The Quota column is added to the business model.Close the Expression Builder. The formula displays in the Logical Column dialog box. 12. 15. 14.Close the Logical Column dialog box.11.Right-click Sales Facts.Select the Quota column. 16.

In the Calculation Name field.Click Next.Uncheck Percent Change. 19.In the Finish window. verify the calculations that will be created by the Calculation Wizard. name the calculation Variance from Quota. 21.Check Percent and make sure it is selected. leave the name as is: % of Quota. 20. In the Calculation Name field.17.Make sure Change is selected. 121 . 18.

The calculation measures are added to the business model. and % of Quota measures to the Sales Facts presentation table. 23. edit the repository to correct the errors before proceeding.Add the Quota (000). Variance From Quota. 122 .Save the repository.22. If you receive any Error messages.Check global consistency.Check in changes. 24. Quota. 25. Test the Quota Measures. 26.Click Finish.

Locate the last query run under Cursor Cache and click View Log. 2000. Notice that two separate queries are executed to collect the data from the ORCL database and the SHQuota. 8. 9. Return to Answers. Click Results.% of Quota. Reload Server Metadata. 3. Click Manage Sessions. Sales Facts. 7. 4. Sales Facts.Amount Sold. 11. 5. Examine the query log Click Settings > Administration.xml file: 123 . 2001.Quota.Variance From Quota. Log out and then log back in as Administrator with password Administrator. Sales Facts.1. 6. 2. (Please note that SHQuota contains data only for 2001). Create the following request: Calendar. Sales Facts. Drill down on 2001. Create the following filter: ¾ Calendar Year is equal to / is in 1999. 10.Calendar Year.

CALENDAR_QUARTER_DESC as c3.c3 as c2.CALENDAR_QUARTER_DESC ORDER BY T268.CALENDAR_QUARTER_DESC.Sending query to database named SH (id: <<46098>>): WITH SAWITH0 AS (select D1. T268.c1 as c1.c4 = 1 ) ) select SAWITH0.xml (id: <<46004>>): <NQSQueryInput><NQSDatabaseName>G:\SHQuota. T268.xml</NQSDatabaseName><NQSUser></NQSUser>< NQSPassword></NQSPassword><NQSQuery><NQSColumn> <NQSColumnType>int</NQSColumnType> <NQSColumnAlias>c2</NQSColumnAlias> <NQSColumnName>Year</NQSColumnName> <NQSColumnFullName>//Table/QUOTA/Year</NQSColumnFullName> <NQSTableName>SHQuota</NQSTableName> <NQSTableAlias>4194</NQSTableAlias> <NQSTableAliasName>SHQuota</NQSTableAliasName> <NQSTableFullName>/ora/SHQuota.AMOUNT_SOLD) as c1.CALENDAR_YEAR = 2001 ) group by T268.c2 as c1.CALENDAR_QUARTER_DESC ASC) as c4 from TIMES T268. D1.xml</NQSTableFullName> </NQSColumn> <NQSColumn> <NQSColumnType>string</NQSColumnType> <NQSColumnAlias>c3</NQSColumnAlias> <NQSColumnName>QtrDesc</NQSColumnName> <NQSColumnFullName>//Table/QUOTA/QtrDesc</NQSColumnFullName> <NQSTableName>SHQuota</NQSTableName> <NQSTableAlias>4194</NQSTableAlias> <NQSTableAliasName>SHQuota</NQSTableAliasName> 124 .CALENDAR_YEAR as c2.TIME_ID = T268.Sending query to external gateway database named G:\SHQuota. T268.TIME_ID and T268. ROW_NUMBER() OVER (PARTITION BY T268.c3 as c3 from (select sum(T245.CALENDAR_YEAR ) D1 where ( D1. SALES T245 where ( T245.-------------------. SAWITH0.c1 as c3 from SAWITH0 order by c2 +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:07 -------------------. SAWITH0. D1.c2 as c2.

xml</NQSTableFullName> </NQSColumn> </NQSQuery></NQSQueryInput> +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:08 -------------------.Query Status: Successful Completion +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:08 -------------------. The results of the request can be displayed and manipulated within Oracle BI Answers. 125 .Rows 201.<NQSTableFullName>/ora/SHQuota. 15. bytes 224 retrieved from database query id: <<46098>> 12. 13. Executing Direct Database Requests Users with the appropriate permissions can create and issue a direct database request directly to a physical back-end database. and subsequently incorporated into Oracle BI Interactive Dashboards and Oracle BI Delivers. you can create direct database requests.Rows 4. By default. Close the query log. bytes 9648 retrieved from database query id: <<46004>> +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:08 -------------------. Click Close Window to close the Oracle BI Presentation Services screen. Click Finished to close the Session Management screen. Leave Answers open. 14. this privilege is set only for users defined as Presentation Server Administrators. The following privilege settings in Oracle BI Presentation Services Administration control whether you can create and issue physical requests: Edit Direct Database Requests: If this privilege is set for you.xml</NQSTableFullName> </NQSColumn> <NQSColumn> <NQSColumnType>double</NQSColumnType> <NQSColumnAlias>c5</NQSColumnAlias> <NQSColumnName>Quota</NQSColumnName> <NQSColumnFullName>//Table/QUOTA/Quota</NQSColumnFullName> <NQSTableName>SHQuota</NQSTableName> <NQSTableAlias>4194</NQSTableAlias> <NQSTableAliasName>SHQuota</NQSTableAliasName> <NQSTableFullName>/ora/SHQuota.

click Manage Privileges to open the the Privilege Administration screen. Note that the Execute Direct Database Requests privilege is not granted to anyone. In Answers. In the Privilege Administration screen. you can issue physical requests. 126 . 3. Note that the Edit Direct Database Requests privilege is granted to Presentation Server Administrators. scroll down to Answers. By default. Click (not permitted) to open the Change Privilege Permissions screen. click Settings > Administration. this privilege is not enabled for anyone. 5. perform the following steps: 1.Execute Direct Database Requests: If this privilege is set for you. To execute a direct database request. 2. In the Oracle BI Presentation Service Administration screen. the Administrator user is a member of this group. 4. By default. It can be changed by a Presentation Server Administrator.

. 10 Click the Answers link to return to the Answers start page.6. Click Finished to close the Change Privilege Permissions screen. 9. Click Finished to close the Privilege Administration screen. Click Close Window to close the Oracle BI Presentation Services Administration screen. 8. Click the Add button next to Presentation Server Administrators to give this group explicit access to this privilege. 7. 127 . Notice the change to the privilege permissions for Execute Direct Database Requests.

. . Your results should look similar to the screenshot. . 13 In the SQL Statement field. 12 In the Connection Pool field. type SELECT * FROM Channels.11 Click the Create Direct Request link. 128 . 15 Click Results. source enclosed in double quotes ("SH". type the connection pool name for the SH data ."Connection Pool" in this example). 14 Click Validate SQL and Retrieve Columns to display the columns from the . Channels table. 16 Leave Answers open .

Using Aggregates Aggregate tables store pre-computed results. This eliminates the need for run-time calculations and delivers faster results to users. processing should be quicker. therefore. For Oracle BI Server to have enough information to navigate to aggregate tables. In the Administration Tool. The following steps are included for Managing Aggregates: Run the Aggregate Persistence Wizard Execute the Aggregate Build Scripts Study the Aggregate Metadata and Test in Answers Run the Aggregate Persistence Wizard 1. Hence from the business model we have already created. The calculations are done ahead of time and the results are stored in the tables. Oracle BI Server allows users to concentrate on asking the right business questions. which are measures that have been aggregated (typically summed) over a set of dimensional attributes. you need to configure certain metadata in the repository. Using aggregate tables is a very popular technique for speeding up query response times in decision support systems. because the server decides which tables provide the fastest answers. it is possible to quickly generate aggregate tables to improve system performance and have these tables automatically mapped into the central business model without the need to maintain these mappings manually. without query authors or tools having to specify aggregate tables in the queries. There is a utility in Oracle BI EE called the Aggregate Persistence Wizard that enables model-first DWH development and maintenance. The aggregate navigation capability of Oracle BI Server allows queries to use the information stored in aggregate tables automatically. Aggregate tables should have many fewer rows than the non-aggregate tables and. go to Tools > Utilities Select Aggregate Persistence Wizard and click Execute… 129 .

Click Next Select the whole fact table SalesFacts Select the levels of aggregation for each dimension.g. G:\AggregateDDL. E.sql. these should only include the dimensions for which quotas are stored and to the following maximum depth: ¾ ProductDim: Category ¾ TimeDim: Quarter ¾ CustomerDim: Subregion Click Next 130 .Insert a path for the aggregate DDL file. Since we are including SHQuota fields.

Click Next Notice the logical SQL generated by the wizard "ag_Salesfacts" for "SH"."Connection Pool" in "orcl SH"."Quarter"."Gross Profit Physical".."# Customers MAgo"."SH" Check I am done and click Next Click Finish Save and Check-in Changes."Category Sales"."Subregion") using connection pool "orcl SH"."Quota (000)") at levels ("SH"."CountDays"."Category"."# of Customers"."CustomersDim"."Salesfacts"("Amount Sold".Select the location for the aggregate within the existing SH schema."ProductsDim"."Unit Cost". Close the Administration Tool 131 ."TimesDim". "SH"."Amount Sold MAgo"."Unit Cost MAgo". "SH".

"Salesfacts"("Amount Sold"."# Customers MAgo".sql_DDL -u Administrator -p Administrator Notice the executed command and output results: prepare aggregates "ag_Salesfacts" for "SH"..sql -u Administrator -p Administrator Notice the executed command and output results: create aggregates "ag_Salesfacts" for "SH".exe utility on-demand or."# Customers MAgo"."Unit Cost"."Unit Cost"."Category"."Amount Sold MAgo"."SH" Statement execute succeeded Processed: 1 queries 132 ."Subregion") using connection pool "orcl SH"."Category Sales"."Gross Profit Physical"."Connection Pool" in "orcl SH"."Quota (000)") at levels ("SH"."Category"."CustomersDim"."Amount Sold MAgo"."Subregion") using connection pool "orcl SH"."Category Sales"."Quarter"."TimesDim". "SH"."Gross Profit Physical". "SH"."Unit Cost MAgo"."# of Customers"."ProductsDim". "SH"."SH" Statement execute succeeded Processed: 1 queries Next run the following command to create the Aggregate tables in the database nqcmd -d LinuxPEServer-SalesHistory -s g:\AggregateDDL."CustomersDim".. To execute the aggregate build scripts follow these steps: Open a command prompt: Start > Run > cmd Browse to G:\ and run the following command to create the Aggregate metadata nqcmd -d LinuxPEServer-SalesHistory -s g:\AggregateDDL."CountDays". we will use the NQCmd utility. if the BI Server is to be responsible for rebuilding aggregates on a regular basis these jobs can be set up in the BI Scheduler."CountDays". As we have not configured the scheduler yet.Execute the Aggregate Build Scripts These scripts can be executed either using the NQCmd."TimesDim"."Unit Cost MAgo"."ProductsDim"."Quarter". "SH"."Salesfacts"("Amount Sold"."Connection Pool" in "orcl SH"."Quota (000)") at levels ("SH"."# of Customers".

defining the appropriate expression to map each Logical column to the aggregate table: Then the aggregation level of the logical table source is configured for each dimension under the Content tab to tell the server when it should be used vs the detail tables or other aggregates: 133 .Study the Aggregate Metadata and Test in Answers Open Admin Tool and connect to Oracle BI Server Online Notice the new Physical tables with a red icon have been created in the SH schema and new Logical table sources in the Business Model Studying the new SalesFacts table source. you can understand how preexisting aggregates are manually mapped into the business model by creating a new logical table source.

for the Time Dimension) that aggregate dimension tables are included and set to the correct level for that dimension. This further speeds up query times and ensures that tables are joined at the same level so as not to double count any records. Join on Category: 134 .g.Also you can see from the new Logical Dimension Table sources (e. The tables we created with the Aggregate Persistence Wizard have the following physical relationships: E.g.

Test the aggregates by logging into Answers and creating the same query as before: Run the query and check the results 8. "Sales Facts"."Calendar Year" saw_0. "Sales Facts". Click Settings > Administration."Amount Sold" saw_1.SQL Request: SET VARIABLE QUERY_SRC_CD='Report'. 10. "Sales Facts"."Variance from Quota" saw_3.Quota saw_2.General Query Info: Repository: BIEE. Locate the last query run under Cursor Cache and click View Log. Click Manage Sessions. Presentation: SH +++Administrator:b5fc0000:b5fc001b:----2007/05/22 05:42:10 135 . "Sales Facts". Subject Area: SH. -------------------."% of Quota" saw_4 FROM SH ORDER BY saw_0 +++Administrator:b5fc0000:b5fc001b:----2007/05/22 05:42:10 -------------------. Notice also that even though the physical aggregate tables do not include any calculated measures like Variance from Quota or % Quota.SELECT Calendar. the server uses the aggregate definitions for the base measures to calculate the derived figures in the most optimal way. You can see from the SQL that the BI Server “aggregate awareness” ensured the new table was used without any guidance from the user and as a result all previously created queries will now run faster if they are at a sufficiently high level of granularity. 9.

T4315.-------------------.Calendar_Q000007F5 = T4383. nvl(SAWITH0.Sending query to database named orcl SH (id: <<213522>>): WITH SAWITH0 AS (select sum(T4383.Calendar_Y00000809 as c3 from SA_Quarter0000097D T4315. SAWITH0.Calendar_Q000007F5 ) group by T4315.Query Status: Successful Completion 136 . 0) end as c5 from SAWITH0 order by c1 +++Administrator:b5fc0000:b5fc001b:----2007/05/22 05:42:10 -------------------. ag_Salesfacts T4383 where ( T4315. sum(T4383.0 / nullif( SAWITH0.c1 * 1000 = 0 then NULL else SAWITH0. 0) . SAWITH0.nvl(SAWITH0.c3 as c1. 0) as c4.c2 * 100.c1 * 1000 .c1 * 1000 as c3.c2 .c2 as c2. case when SAWITH0.Calendar_Y00000809) select distinct SAWITH0.Quota_0008059661B) as c1.Amount_Sol00000140) as c2.c1 * 1000.

Yet. You use the Expression Builder to apply the functions. the Ago function can produce sales for every month of the current quarter. SQL was not designed with business reports in mind. as Ralph Kimball states. Oracle BI Server provides Ago and ToDate functions for time series comparisons. along with the corresponding quarter ago sales. The queries that run in the background to support the time measure are transparent to the user. providing a context for the data.Creating Time Series Measures The ability to compare business performance with previous time periods is fundamental to understanding a business. perform the following steps: Identify a Dimension as a Time Dimension Create a Month Ago Measure Create a Change Month Ago Measure Create a ToDate Measure Ensure Correct Month Sort-Order for To-Date Calculation Test the Time Series Measures 137 . How else can you explain the fact that there is no direct way in SQL to compare this year to last year?” – Ralph Kimball The solution is to model time series data in the Oracle BI repository. The ToDate function is used to aggregate a measure attribute from the beginning of a specified time period to the currently displaying time. Both of these functions operate on measures. SQL was really an interim language designed to allow relational table semantics to be expressed in a convenient and accessible form. The Ago function calculates the aggregated value as of some time period shifted from the current time. This allows users to make one request for the desired result. and to enable researchers and early developers to proceed with building the first relational systems in the mid1970s. Time comparisons allow businesses to analyze data that spans multiple time periods. Oracle BI Server runs multiple queries in parallel to get the results. For example. To create time series measures. SQL was not designed to make comparisons over time straightforward: ”The most difficult area of data warehousing is the translation of simple business analyses into SQL. the ToDate function can calculate Month to Date sales for a given year. For example.

5. Click OK to close the Dimension dialog box. 3. Expand TimesDim to the Times Detail level and double-click the Times Detail level to open the Logical Level dialog box. In the Dimension dialog box. 2. 7. check Time Dimension. Click the Keys tab. double-click the TimesDim dimension hierarchy to open the Dimension dialog box. 138 . In the Business Model and Mapping layer.Identify a Dimension as a Time Dimension: 1. Check the Chronological Key checkbox for Times Detail_Key. Click OK to close the Logical Level dialog box. 6. 4.

Click Insert to add the Ago function to the Expression Builder. 4. 3. Select Functions > Time Series Functions > Ago. Check Use existing logical columns as the source. Click the Expression Builder button (three dots) to open the Expression Builder. 2. Right-click Sales Facts and select New Object > Logical Column to open the Logical Column dialog box. 5. 6. Name the logical column Month Ago Sales.Create a Month Ago Measure 1. 139 .

Select Logical Tables > Sales Facts and then double-click Amount Sold to add it to the expression.7.Click <<integer>> in the expression and type 1. 10. Click the first <<expr>> in the expression.Select Time Dimensions > TimesDim and then double-click Month to add it to the expression. 8. 9. 140 . The Ago function calculates the Amount Sold value one month prior to the current month. Click the second <<expr>> in the expression. 11.

13.Click OK to close the Expression Builder.Click OK to close the Logical Column dialog box. The formula is displayed in the Logical Column dialog box. 141 .12.

7. 8. 5. 142 . Check Use existing logical columns as the source. 3.Create a Change Month Ago measure 1. Insert a minus sign in the expression. The formula is displayed in the Logical Column dialog box. Right-click Sales Facts and select New Object > Logical Column to open the Logical Column dialog box. Select Logical Tables > Sales Facts and then double-click Amount Sold to add it to the expression. Select Logical Tables > Sales Facts and then double-click Month Ago Dollars to add it to the expression. Click OK to close the Logical Column dialog box. 4. 9. 6. 2. Click OK to close the Expression Builder. Name the logical column Change Month Ago Dollars. Click the Expression Builder button to open the Expression Builder.

Right-click Sales Facts and select New Object > Logical Column. Select Logical Tables > Sales Facts and then double-click Amount Sold. 143 . Name the new logical column Year To Date Sales. Select Functions > Time Series Functions and double-click ToDate to insert the expression. 5. 7. Open the Expression Builder. 6.Create a To-Date Measure 1. Select Use existing logical columns as the source. 4. 3. 2. Click the first <<expr>>.

10. The formula is displayed in the Logical Column dialog box. 144 . Click OK to close the Logical Column dialog box.8. 11. Select Time Dimensions > TimesDim and the double-click Year to add it to the expression. Click the second <<expr>>. 9. Click OK to close the Expression Builder.

expand the Times logical table. 145 . In the Business Model and Mapping layer. 5. Select Calendar Month Desc and click OK.Ensure Correct Month Sort-Order for To-Date Calculation 1. The sort order column displays in the Logical Column dialog box. Click OK to close the logical column dialog box. 2. 7. Double-click Calendar Month Name to open the logical column dialog box. Check in changes. 6. 4. 3. Click the Set button. 8. Drag the three time series measures from the Business Model and Mapping layer to the Sales Facts presentation table. The Calendar Month Name column is now automatically sorted by Calendar Month Desc whenever it is used in an Answers query.

Year To Date Sales ¾ Calendar Year is equal to / is in 2001 3. Check global consistency. Fix any errors before proceeding. 146 . 10.Save the repository.Change Month Ago Sales ¾ Sales Facts. Return to Answers and reload server metadata. 2. See here for how to resolve any Time dimension errors related to imported XML data source.Month Ago Sales ¾ Sales Facts.Amount Sold ¾ Sales Facts.Calendar Month Name ¾ Sales Facts. Create the following query and filter in Answers: ¾ Times. Test the Time Calculations 1.9. Click Results.

Summary In this lesson. Business Model and Mapping. and Presentation layers of a repository Test and validate a repository Create calculation measures Use initialization blocks and variables Add multiple sources to logical tables in a business model Execute direct database requests Use aggregate tables to speed processing Create time series measures Related Information To learn more about Oracle Business Intelligence. 147 . you should have learned how to: Build the Physical. you can refer to: Additional OBEs on the OTN Web site.

Sign up to vote on this title
UsefulNot useful