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

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

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

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. 6 . The Create New Data Source dialog box opens. Click the System DSN tab and click Add. 2. Click Start > Programs > Administrative Tools > Data Sources (ODBC) to open the ODBC Data Source Administrator. perform the following steps: 1.

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

7. Click OK to close the Oracle ODBC Driver Configuration dialog box. 11. 9. 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. You should see a "Testing Connection" message indicating the connection is successful. 8. 10. enter the password SH for the SH schema and click OK. In the Oracle ODBC Driver Connect dialog box. Click OK to close the Testing Connection message. 8 .

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

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

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

To verify connectivity. right-click the SH schema folder and select Physical Diagram > Object (s) and All Joins. 12 . perform the following steps: 1. you can select the SH database object and then click the Physical Diagram button on the toolbar. 11. In the Physical layer. Alternatively. 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. click Tools > Update All Row Counts. When update all row counts completes.10.

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

Make sure the join expression is: CHANNELS. Continue to create the following joins: 14 . Click OK to close the Physical Foreign Key dialog box.CHANNEL_ID 6. 7.It matters which table you click first. The Administration Tool makes a best "guess" and automatically determines which columns should be included in the join. The join between Channels and Sales is displayed in the Physical Diagram.CHANNEL_ID = SALES. 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.

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

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 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. Logical fact tables contain the measures by which an organization gauges its business operations and performance. Collections of logical columns form logical tables. Most of the vocabulary translates into logical columns in the business model. 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 . To build the Business Model and Mapping layer. or logical. Logical dimension tables contain the data used to qualify the facts. Each logical column (and hence each logical table) can have one or more physical objects as sources. 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. The Business Model and Mapping layer of the Administration Tool defines the business. A business model object contains the business model definitions and the mappings from logical to physical tables for the business model. The Business Model and Mapping layer of the Administration Tool can contain one or more business model objects. This is where the physical schemas are simplified to form the basis for the users’ view of the data.

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

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

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

A logical table’s Sources folder contains the logical table sources. A new AMOUNT_SOLD logical column is added to the Sales Facts logical table. Logical table sources define the mappings from a logical table to a physical table. it is possible to change names in the Business Model and Mapping layer without impacting the mapping. is the same name as the 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. However. Drag the AMOUNT_SOLD column from the Physical layer to the Sales Facts logical table in the Business Model and Mapping layer.3. SALES. Because you dragged a column from the Physical layer. the logical table source name. 20 .

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

Create Logical Joins To create logical joins in the business model. Notice that each logical table has a yellow table icon. all table icons are yellow. CUSTOMERS. Select the following tables in the Physical layer. PROMOTIONS. this indicates a fact table. PRODUCTS. Select only these tables: CHANNELS. TIMES 2. Because you have not yet created the logical joins. In the Business Model and Mapping layer. 22 . Drag the selected tables from the Physical layer onto the SH business model folder in the Business Model and Mapping layer. 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. perform the following steps: 1.

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

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

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

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

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

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

Verify that the Channels logical table now has only four logical columns.4. 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 . 5.

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

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

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

8. verify that Channel Class and Use for drilldown are selected. 10 In the Logical Level Key dialog box. Each level key can consist of one or more columns at this level. The level key defines the unique elements in each logical level. 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. 9. Right-click Channel Class and select New Logical Level Key. 37 .

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

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

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

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

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

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

It is the view of the data seen by end users in client tools and applications. Do not check global consistency. set Number of elements at this level to 1. uncheck Use for drill down for Products Detail_Key (Prod ID).21. The Presentation layer provides a means to further simplify or customize the Business Model and Mapping layer for end users. Presentation layer objects can then be renamed and reorganized. and rename data as necessary for the set of users. organize the data in a way that aligns with the way users think about the data. To build the Presentation layer. 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. you perform the following steps: 1. Check Use for drill down for all other keys in the ProductsDim hierarchy. 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. 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. For the Product Total Attribute level. You typically create Presentation layer objects by dragging objects from the Business Model and Mapping layer. For the Products Detail level. 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. 44 . set Number of elements at this level to 5. you can organize columns into catalogs and folders. For example. For the Category level. such as Oracle BI Answers. If you complete this step. save the repository. Corresponding objects are automatically created in the Presentation layer.

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

For example. a detailed message alerts you to the nature of the inconsistency. For example. but is not a requirement for a consistent repository. if there are physical tables with no keys defined. Best Practices messages provide information about conditions but do not indicate an inconsistency. Repositories and the business models within them must pass the consistency check before you can make business models available for queries. the object type. 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. You then test the repository by running queries using Oracle BI Answers. For each message the Consistency Check Manager identifies the message type. and provides a detailed description of the message. but is not a requirement for a consistent repository. if the Administrator user has an empty password this should be addressed. To test and validate a repository. depending upon the intent of the Oracle BI Server administrator. Warning messages indicate conditions that may or may not be errors. display results using 46 . You begin by checking the repository for errors using the check consistency option.Testing and Validating a Repository You have finished building the initial business model and now need to test the repository before continuing your development. the object. you examine the query log file to verify the SQL generated by Oracle BI Server. The Consistency Check Manager displays three types of messages: Error messages indicate errors that need to be fixed to make the repository consistent. a best practice message is displayed. When a repository or business model is inconsistent. Defining keys for physical tables is best practice. Finally. There are options to display only selected message types.

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

7. Click OK to close the Business Model properties dialog box. 6. If you see only Warning and Best Practices messages. 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). Double-click the SH business model object to open the Business Model properties dialog box. 48 . Click No when asked to check global consistency (you just checked it). 8. you can ignore the messages for now and click Close. In the Business Model and Mapping layer. 5. If the Consistency Check Manager displays any Error messages. Notice that Available for queries is checked.4. edit the repository to correct the inconsistencies and run the consistency check again. Save the repository.

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

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

log).3.1.. Browse to G:\biee\10. you start the Oracle BI Server service to load the SH repository into memory. 51 . An entry in the Repository section of the initialization file NQSConfig.. 1.Create an empty Webcatalog to test your RPD The end-user report objects are stored in a Web Catalog. We will create a new Web catalog to start our testing of the SH. You will find instructions for doing this in the online documentation. Modify the NQSConfig.ini instructs Oracle BI Server to load a specific repository into memory upon startup. 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.rpd. If Oracle BI Server detects a syntax error while loading the repository.ini only if you wish to change system settings like turning caching on. it logs the error to the server log file (.\\OracleBI\server\Log\NQServer.

Ensure that the previous step is completed and that the files listed under each service are correct. Oracle BI Presentation Server and Oracle BI Java Host services were not started prior to making the previous change. If the Oracle BI Server.The path to the Web Catalog is stored in another initialization file called InstanceConfig.html Select Repository: sh. The editing of this file has also been simplified on the Linux image by the Process Control page 1.xml. 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.oracle.us.rpd and Web Catalog SH_Start Click SET 2. Open the Process Control Page: http://oracle2go. you will need to explicitly start them.

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

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

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

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

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 use physical columns for calculations that require and aggregation rule to be applied after 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. Oracle BI Server has a calculation engine to perform a multitude of calculations. Users can then easily build queries using familiar terminology. you use the Expression Builder to create calculation measures that appear as columns to users in Answers. use physical columns as objects in a formula. When you create formulas based on physical columns. You use logical columns for calculation formulas that require an aggregation rule that is applied before the calculation. All three methods are covered in this OBE. you have to map for each physical source it could be derived from. To create calculation measures. 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. You can use existing logical columns as objects in a formula. or use the Calculation Wizard to automate the process. You can also build calculation measures in Answers. The advantage of defining a logical column formula based on existing logical columns is that you only have to define it once. In the examples in this lesson. There are different methods for creating calculation measures in the Administration Tool.” An Expression Builder enables you to create expressions that are similar to expressions created with SQL.Creating Calculation Measures Often.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.

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

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

2. To create a calculation measure using the Calculation Wizard.Create a Calculation Measure Using the Calculation wizard In this topic. 3. A new column named Amount Sold#1 is added to the business model. Return to the SH repository. perform the following steps: 1. Right-click the Amount Sold logical column and select Duplicate. 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.

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

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

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

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

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

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

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

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

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

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

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

System and nonsystem variables are represented by a question mark icon in the Variable Manager. Session variables are created and assigned a value when each user logs on. You use the Variable Manager to define variables and initialization blocks. session variables. Oracle BI Server substitutes the value of a variable for the variable itself in the metadata. System variables have reserved names and are used for specific purposes by Oracle BI Server. There are two types of session variables: system and nonsystem. such as authenticating users. To create initialization blocks. system session variables. A repository variable has a single value at any point in time. Initialization blocks are used to initialize dynamic repository variables. A variable has a single value at any point in time. There are two classes of variables: repository variables and session variables. 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. and nonsystem session variables. 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 . There are two types of repository variables: static and dynamic. Repository variables are represented by a question mark icon in the Variable Manager. Static repository variables have values that are constant and do not change while Oracle BI Server is running.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. Dynamic repository variables have values that are refreshed by data returned from queries in initialization blocks.

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

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

7. 96 . Click OK to close the Session Variable Initialization Block Data Source dialog box. 9. In the Default Initialization String field. Double-click Connection Pool or click the Select button to add the connection pool to the Session Variable Initialization Block Data Source dialog box. 8. 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. The initialization string is visible in the Session Variable Initialization Block dialog box. type the following initialization string: select ':USER'. 2 from Dual 10. 'CountryManagers'. Click the Browse button and select SH > Connection Pool in the Select Connection Pool dialog box.

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

17. 98 . GROUP. 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. Repeat the steps and add three more variables: UserCountry. Click Yes when promoted about the GROUP and LOGLEVEL session variables having a special purpose. and LOGLEVEL.

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

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

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

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

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

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

CALENDAR_MONTH_DESC. 9. The connection pool and initialization string are added to the Repository Variable Init Block dialog box. 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. CALENDAR_MONTH_ID from TIMES WHERE TIME_ID = (select max(TIME_ID) from SALES) 10.8. type the following SQL: select TIME_ID. CALENDAR_YEAR. 105 . In the Default Initialization String field.Click OK to close the Repository Variable Init Block Data Source dialog box.

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

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

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

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

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

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

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

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

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

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. Repeat the steps and map Products. the Time attributes must be in a separate physical layer table definition from other attributes. Click OK to close the Logical Table Source dialog box. Specifically. We need to use this approach for the imported XML file.6. Call the object TimeAlias 115 . This can be easily achieved in most instances via the use of an alias.Prod Category to Category and verify the logical table source mapping. 11. Right click on SHQuota. Select New Object > Alias. 1.

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.2. Right-click on the XML database and select Physical Diagram > Selected Objects Only 3. 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 . Create a join on ALL COLUMNS by multi-selecting all columns from both table lists.

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

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

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

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

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

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

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

CALENDAR_YEAR = 2001 ) group by T268.CALENDAR_QUARTER_DESC ASC) as c4 from TIMES T268. SAWITH0.TIME_ID = T268.CALENDAR_QUARTER_DESC as c3.c2 as c2. T268.c1 as c1.c3 as c2. T268.c1 as c3 from SAWITH0 order by c2 +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:07 -------------------. ROW_NUMBER() OVER (PARTITION BY T268.CALENDAR_QUARTER_DESC. SALES T245 where ( T245.c4 = 1 ) ) select SAWITH0.c2 as c1.Sending query to database named SH (id: <<46098>>): WITH SAWITH0 AS (select D1. SAWITH0.c3 as c3 from (select sum(T245.CALENDAR_YEAR as c2.AMOUNT_SOLD) as c1.-------------------.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. D1. T268.CALENDAR_QUARTER_DESC ORDER BY T268.TIME_ID and T268.Sending query to external gateway database named G:\SHQuota.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 ) D1 where ( D1.xml (id: <<46004>>): <NQSQueryInput><NQSDatabaseName>G:\SHQuota. D1.

13. and subsequently incorporated into Oracle BI Interactive Dashboards and Oracle BI Delivers.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. Executing Direct Database Requests Users with the appropriate permissions can create and issue a direct database request directly to a physical back-end database. 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. 15. 14. 125 . this privilege is set only for users defined as Presentation Server Administrators. Click Close Window to close the Oracle BI Presentation Services screen. Leave Answers open.Rows 4. Click Finished to close the Session Management screen.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.<NQSTableFullName>/ora/SHQuota.Rows 201. you can create direct database requests. Close the query log. By default. bytes 9648 retrieved from database query id: <<46004>> +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:08 -------------------. bytes 224 retrieved from database query id: <<46098>> 12.xml</NQSTableFullName> </NQSColumn> </NQSQuery></NQSQueryInput> +++Administrator:b5ed0000:b5ed000b:----2007/05/22 01:16:08 -------------------.

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

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

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

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

g.Insert a path for the aggregate DDL file. E. 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 . Click Next Select the whole fact table SalesFacts Select the levels of aggregation for each dimension.sql. G:\AggregateDDL. Since we are including SHQuota fields.

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

"Subregion") using connection pool "orcl SH"."Connection Pool" in "orcl SH"."Category Sales". "SH"."CountDays"."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"."Quota (000)") at levels ("SH". "SH"."TimesDim"."Unit Cost"."Salesfacts"("Amount Sold"."Gross Profit Physical".exe utility on-demand or.Execute the Aggregate Build Scripts These scripts can be executed either using the NQCmd."# Customers MAgo"."Unit Cost MAgo"."Connection Pool" in "orcl SH"."CustomersDim"."Unit Cost MAgo"."Gross Profit Physical". 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."Unit Cost".sql -u Administrator -p Administrator Notice the executed command and output results: create aggregates "ag_Salesfacts" for "SH"."CountDays".sql_DDL -u Administrator -p Administrator Notice the executed command and output results: prepare aggregates "ag_Salesfacts" for "SH". 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."ProductsDim"."Amount Sold MAgo"."Subregion") using connection pool "orcl SH"."Quota (000)") at levels ("SH"."Category"."Quarter"."Category".."TimesDim"."Salesfacts"("Amount Sold"."# of Customers". "SH"."SH" Statement execute succeeded Processed: 1 queries 132 . "SH". we will use the NQCmd utility. As we have not configured the scheduler yet."Amount Sold MAgo"."Category Sales".."ProductsDim"."Quarter"."# of Customers"."# Customers MAgo".

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. 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 .

This further speeds up query times and ensures that tables are joined at the same level so as not to double count any records. for the Time Dimension) that aggregate dimension tables are included and set to the correct level for that dimension.g. 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.

the server uses the aggregate definitions for the base measures to calculate the derived figures in the most optimal way. 9.Test the aggregates by logging into Answers and creating the same query as before: Run the query and check the results 8."Variance from Quota" saw_3. 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. Notice also that even though the physical aggregate tables do not include any calculated measures like Variance from Quota or % Quota. Presentation: SH +++Administrator:b5fc0000:b5fc001b:----2007/05/22 05:42:10 135 .SELECT Calendar.General Query Info: Repository: BIEE. "Sales Facts". "Sales Facts". Subject Area: SH."Calendar Year" saw_0. "Sales Facts".SQL Request: SET VARIABLE QUERY_SRC_CD='Report'. -------------------."Amount Sold" saw_1. "Sales Facts". 10. Click Manage Sessions."% of Quota" saw_4 FROM SH ORDER BY saw_0 +++Administrator:b5fc0000:b5fc001b:----2007/05/22 05:42:10 -------------------. Click Settings > Administration. Locate the last query run under Cursor Cache and click View Log.Quota saw_2.

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

This allows users to make one request for the desired result. For example. Oracle BI Server provides Ago and ToDate functions for time series comparisons. SQL was not designed with business reports in mind. 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. Time comparisons allow businesses to analyze data that spans multiple time periods. To create time series measures. 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 . as Ralph Kimball states. Oracle BI Server runs multiple queries in parallel to get the results. the ToDate function can calculate Month to Date sales for a given year.Creating Time Series Measures The ability to compare business performance with previous time periods is fundamental to understanding a business. 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. and to enable researchers and early developers to proceed with building the first relational systems in the mid1970s. 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. providing a context for the data. For example. Both of these functions operate on measures. The ToDate function is used to aggregate a measure attribute from the beginning of a specified time period to the currently displaying time. along with the corresponding quarter ago sales. Yet. The queries that run in the background to support the time measure are transparent to the user. the Ago function can produce sales for every month of the current quarter. You use the Expression Builder to apply the functions.

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

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

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

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

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

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

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

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

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

Summary In this lesson. 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. Business Model and Mapping. you should have learned how to: Build the Physical. 147 . you can refer to: Additional OBEs on the OTN Web site.

Sign up to vote on this title
UsefulNot useful