Creating a Repository 11.1.1.7

8/10/2019 Creating a Repository 11.1.1.7

1/222

Purpose

This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool (11.1.1.7) to build, modify, enhance, and manage an Oracle

BI repository. You learned how to import metadata from a data source, 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. You

learn to create calculated measures, hierarchies, aggregates, and time series measures.

Time to Complete

Approximately 4 hours.

Introduction

This tutorial shows you how to build an Oracle BI metadata repository using the Oracle BI Administration Tool. You learn how to import metadata

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

Hardware and Software Requirements

The following is a list of hardware and software requirements:

Have access to or have Installed Oracle Business Intelligence Enterprise Edition 11g.

Please note: This tutorial is built using Oracle Business Intelligence Enterprise Edition 11.1.1.7.0.

When setting up query logging, you must select Action > Set Online User Filter in Identity Manager to view users in the repository.

1.

To complete this tutorial you must have access to the BISAMPLE schema that is included with the Sample Application for Oracle

Business Intelligence Suite Enterprise Edition Plus. There are two options for accessing the BISAMPLE schema:

You can download the Sample Application virtual box image from here.1.

Click here to access the ForOBE.7z file, which has the BISAMPLE schema. Save ForOBE.7z, unzip, and begin with README.txt.2.

2.

Prerequisites

Before starting this tutorial, you should:

Have some familiarity with the Oracle BI 11g Administration Tool

Have the proper permissions to upload 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, flat files, XML documents, and

so forth. In this example, you import and configure tables from the BISAMPLE schema.

To build the Physical layer of a repository, you perform the following steps:

Creating a New Repository1.

Importing Metadata2.

Verifying Connection3.

Creating Aliases4.

Creating Physical Keys and Joins5.

Creating a New Repository

Select Start > Programs > Oracle Business Intelligence > BI Administrationto open the Administration Tool.1.

Creating a Repository Using the Oracle BI Administration Tool (11.1.1.7)

ating a Repository Using the Oracle BI Administration Tool http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi...

222 19-09-2014 10:25


2/222

Select File > New Repository.2.

Select the Binarymethod.3.


222 19-09-2014 10:25


3/222

Enter a name for the repository. In this tutorial the repository name is BISAMPLE.4.


222 19-09-2014 10:25


4/222

Leave the default location as is. It points to the default repository directory.5.

Leave Import Metadata set toYes.6.

Enter and retype a password for the repository. In this tutorial BISAMPLE1is the repository password.7.


222 19-09-2014 10:25


5/222

Click Next.8.

Importing Metadata

Change the Connection Type to OCI 10g/11g. The screen displays connection fields based on the connection type you selected.1.


222 19-09-2014 10:25


6/222

Enter a data source name. In this example the data source name is orcl. This name is the same as the tnsnames.ora entry for this Oracle

database instance.

2.

Enter user name and password for the data source. In this example the username and password are both BISAMPLE. Recall that

BISAMPLE is the name of the user/schema you created in the prerequisite section.

3.


222 19-09-2014 10:25


7/222

Click Next.4.

Accept the default metadata types and click Next.5.

In the Data source view, expand the BISAMPLEschema.6.


222 19-09-2014 10:25


8/222

Use Ctrl+Clickto select the following tables from BISAMPLEschema:

SAMP_ADDRESSES_D

SAMP_CUSTOMERS_D

SAMP_PRODUCTS_D

SAMP_REVENUE_F

SAMP_TIME_DAY_D

7.


222 19-09-2014 10:25


9/222

Click the Import Selected button to add the tables to the Repository View.8.


222 19-09-2014 10:25


10/222

The Connection Pooldialog box appears. Accept the defaults and click OK.9.


f 222 19-09-2014 10:25


11/222

The Importingmessage appears.10.


f 222 19-09-2014 10:25


12/222

When import is complete, expand BISAMPLEin the Repository Viewand verify that the five tables are visible.11.


f 222 19-09-2014 10:25


13/222

Click Finishto open the repository.12.

Expand orcl > BISAMPLEand confirm that the five tables are imported into the Physicallayer of the repository.13.


f 222 19-09-2014 10:25


14/222

Verifying Connection

Select Tools > Update All Row Counts.1.

When update row counts completes, move the cursor over the tables and observe that row count information is now visible, including

when the row count was last updated.

2.

Expand tables and observe that row count information is also visible for individual columns.3.


f 222 19-09-2014 10:25


15/222

Right-click a table and selectView Datato view the data for the table.4.

Close the View Data dialog box when you are done. It is a good idea to update row counts or view data after an import to verify

connectivity. Viewing data or updating row count, if successful, tells you that your connection is configured correctly.

5.


f 222 19-09-2014 10:25


16/222

Creating Aliases

It is recommended that you use table aliases frequently in the Physicallayer to eliminate extraneous joins and to include best practicenaming conventions for physical table names. Right-click SAMP_TIME_DAY_Dand select New Object > Aliasto open the Physical

Tabledialog box.

1.

EnterD1 Timein the Name field.2.


f 222 19-09-2014 10:25


17/222

In the Descriptionfield, enterTime Dimension Alias at day grain. Stores one record for each day.3.

Click the Columnstab. Note that alias tables inherit all column definitions from the source table.4.


f 222 19-09-2014 10:25


18/222

Click OKto close the Physical Tabledialog box.5.

Repeat the steps and create the following aliases for the remaining physical tables.

SAMP_ADDRESSES_D = D4 Address

SAMP_CUSTOMERS_D = D3 Customer

SAMP_PRODUCTS_D = D2 Product

SAMP_REVENUE_F = F1 Revenue

6.

Creating Keys and Joins

Select the five alias tables in the Physicallayer.1.


f 222 19-09-2014 10:25


19/222

Right-click one of the highlighted alias tables and select Physical Diagram > Selected Object(s) Onlyto open the Physical Diagram.

Alternatively, you can click the Physical Diagram button on the toolbar.

2.

Rearrange the alias table objects so they are all visible.3.


f 222 19-09-2014 10:25


20/222

You may want to adjust the objects in the Physical Diagram. If so, use the toolbar buttons to zoom in, zoom out, fit the diagram, collapse

or expand objects, select objects, and so forth:

4.

Click the New Joinbutton on the toolbar.5.

Click the F1 Revenuetable and then the D1 Timetable. The Physical Foreign Keydialog box opens. It matters which table you click

first. The join creates 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.

6.


f 222 19-09-2014 10:25


21/222

Select the D1 Time. CALENDAR_DATEcolumn, and then select F1 Revenue.BILL_DAY_DTto join the tables. Ensure that the

Expression edit box (at the bottom) contains the following expression:

"orcl".""."BISAMPLE"."D1 Time"."CALENDAR_DATE" = "orcl".""."BISAMPLE"."F1 Revenue"."BILL_DAY_DT"

7.

Click OKto close the Physical Foreign Key dialog box. The join is visible in the Physical Diagram.8.


f 222 19-09-2014 10:25


22/222

Please be aware of the following upgrade considerations for Oracle BI EE 11g Release 1 (11.1.1.5): Joins in the Physical and

Business Model diagrams are now represented by a line with an arrow at the "one" end of the join, rather than the line with crows

feet at the "many" end of the join that was used in previous releases. When creating joins in the Physical and Business Model

Diagrams, you now select the "many" end of the join first, and then select the "one" end of the join. In previous releases, joins in

the diagrams were created by selecting the "one" end of the join first.

Repeat the steps to create joins for the remaining tables. Use the following expressions as a guide. Please notice that D4 Addressjoins

to D3 Customer.

"orcl".""."BISAMPLE"."D2 Product"."PROD_KEY" = "orcl".""."BISAMPLE"."F1 Revenue"."PROD_KEY"

"orcl".""."BISAMPLE"."D3 Customer"."CUST_KEY" = "orcl".""."BISAMPLE"."F1 Revenue"."CUST_KEY"

"orcl".""."BISAMPLE"."D4 Address"."ADDRESS_KEY" = "orcl".""."BISAMPLE"."D3 Customer"."ADDRESS_KEY"

9.

Click the Auto Layoutbutton on the toolbar.10.

Your diagram should look similar to the screenshot:11.


f 222 19-09-2014 10:25


23/222

Click the Xin the upper right corner to close the Physical Diagram.12.

Select File > Saveor click the Savebutton on the toolbar to save the repository.13.

Click Nowhen prompted to check global consistency. Some of the more common checks are done in the Business Model and Mappinglayer and Presentationlayer. Since these layers are not defined yet, bypass this check until the other layers in the repository are built.

You learn more about consistency check later in this tutorial.

14.

Leave the Administration Tooland the repository open for the next topic.

Congratulations! You have successfully created a new repository, imported a table schema from an external data source into the Physical

layer, created aliases, and defined keys and joins.

In the next topic you learn how to build the Business Model and Mappinglayer of a repository.

15.


f 222 19-09-2014 10:25


24/222

In this topic you use the Oracle BI Administration Tool to build the Business Model and Mapping layer of a repository.

The Business Model and Mapping layer of the Administration Tool defines the business, or logical model of the data and specifies the mappings

between the business model and the Physical layer schemas. This layer is where the physical schemas are simplified to form the basis for the

users view of the data. The Business Model and Mapping layer of the Administration Tool can contain one or more business model objects. A

business model object contains the business model definitions and the mappings from logical to physical tables for the business model.

The main purpose of the business model is to capture how users think about their business using their own vocabulary. The business model

simplifies the physical schema and maps the users business vocabulary to physical sources. Most of the vocabulary translates into logical

columns in the business model. Collections of logical columns form logical tables. Each logical column (and hence each logical table) can have

one or more physical objects as sources.

There are two main categories of logical tables: fact and dimension. Logical fact tables contain the measures by which an organization gauges

its business operations and performance. Logical dimension tables contain the data used to qualify the facts.

To build the Business Model and Mapping layer of a repository, you perform the following steps:

Creating a Business Model

Examining Logical Joins

Examining Logical Columns

Examining Logical Table Sources

Renaming Logical Objects Manually

Renaming Logical Objects Using the Rename Wizard

Deleting Unnecessary Logical Objects

Creating Simple Measures

Creating a Business Model

Right-click the white space in the Business Model and Mappinglayer and select New Business Modelto open the Business Model

dialog box.

1.

EnterSample Salesin the Namefield. Leave Disabledchecked.2.


f 222 19-09-2014 10:25


25/222

Click OK. The Sample Sales business model is added to the Business Model and Mappinglayer.3.

In the Physicallayer, select the following four alias tables:

D1 Time

D2 Product

D3 Customer

F1 Revenue

Do not select D4 Addressat this time.

4.


f 222 19-09-2014 10:25


26/222


27/222

Because you dragged all tables simultaneously from the Physical layer onto the business model, the logical keys and joins are

created automatically in the business model. This is because the keys and join relationships were already created in the Physical

layer. However, you typically do not drag all physical tables simultaneously, except in very simple models. Later in this tutorial, you

learn how to manually build logical keys and joins in the Business Model and Mapping layer. The process is very similar to

building joins in the Physical layer.

Double-click any one of the joins in the diagram to open theLogical Joindialog box. In this example the join between D1 Timeand F1

Revenueis selected.

Notice that there is no join expression. Joins in the BMM layer are logical joins. Logical joins express the cardinality relationships

between logical tables and are a requirement for a valid business model. Specifying the logical table joins is required so that

Oracle BI Server has necessary metadata to translate logical requests against the business model into SQL queries against the

physical data sources. Logical joins help Oracle BI Server understand the relationships between the various pieces of the

business model. When a query is sent to Oracle BI Server, the server determines how to construct physical queries by examining

how the logical model is structured. Examining logical joins is an integral part of this process. The Administration Tool considers a

table to be a logical fact table if it is at the many end of all logical joins that connect it to other logical tables.

3.

Click OKto close the Logical Join dialog box.4.

Click the Xto close the Business Model Diagram.5.

Examining Logical Columns

Expand the D1 Timelogical table. Notice that logical columns were created automatically for each table when you dragged the alias1.


f 222 19-09-2014 10:25


28/222

tables from the Physicallayer to the BMMlayer.

Examining Logical Table Sources

Expand the Sourcesfolder for the D1 Timelogical table. Notice there is a logical table source, D1 Time. This logical table source maps

to the D1 Timealias table in the Physicallayer.

1.

Double-click the D1 Timelogical table source (not the logical table) to open the Logical Table Sourcedialog box.2.


f 222 19-09-2014 10:25


29/222

On the Generaltab, rename the D1 Timelogical table source to LTS1 Time. Notice that the logical table to physical table mapping is

defined in the "Map to these tables"section.

3.

On the Column Mappingtab, notice that logical column to physical column mappings are defined. If mappings are not visible, select

Show mapped columns.

4.


f 222 19-09-2014 10:25


30/222


31/222

Click on the first logical column, BEG_OF_MONTH_WID, to highlight it.2.

Click on BEG_OF_MONTH_WIDagain to make it editable.3.


f 222 19-09-2014 10:25


32/222

Rename BEG_OF_MONTH_WIDto Beg of Mth Wid. This is the manual method for renaming objects. You can also rename an object

and select Renameto manually rename an object.

4.

Renaming Objects Using the Rename Wizard

Select Tools > Utilities > Rename Wizard > Executeto open the Rename Wizard.1.

In the Select Objectsscreen, click Business Model and Mappingin the middle pane.2.


f 222 19-09-2014 10:25


33/222

Expand the Sample Salesbusiness model.3.

Expand the D1 Timelogical table.4.

UseShift+Click to select all of the logical columns except for the column you already renamed, Beg of Mth Wid.5.


f 222 19-09-2014 10:25


34/222

Click Addto add the columns to the right pane.6.

Repeat the steps for the three remaining logical tables so that all logical columns from the Sample Salesbusiness model are added to

the right pane. Only the columns from F1 Revenueare shown in the screenshot.

7.


f 222 19-09-2014 10:25


35/222

Click Nextto move to the Select Typesscreen.

Notice that Logical Column is selected. If you had selected other object types, such as logical tables, the type would have

appeared here.

8.

Click Nextto open the Select Rulesscreen.9.


f 222 19-09-2014 10:25


36/222

In the Select Rulesscreen, select All text lowercaseand click Addto add the rule to the lower pane.10.

Add the rule Change each occurrence of _ into a space.11.

Add the rule First letter of each word capital.12.


f 222 19-09-2014 10:25


37/222

Click Nextto open the Finish screen. Verify that all logical columns will be named according to the rename rules you selected.13.

Click Finish.14.

In the Business Model and Mappinglayer, expand the logical tables and confirm that all logical columns have been renamed as

expected. The screenshot shows only the columns in D1 Time.

15.


f 222 19-09-2014 10:25


38/222

In the Physicallayer, expand the alias tables and confirm that all physical columns have notbeen renamed. The point here is you can

change object names in the BMMlayer without impacting object names in the Physicallayer. When logical objects are renamed, the

relationships between logical objects and physical objects are maintained by the logical column to physical column mappings.

16.

Deletin Unnecessar Lo ical Ob ects


f 222 19-09-2014 10:25


39/222

In the BMMlayer, expand Sample Sales > F1 Revenue.1.

Use Ctrl+Click to select all F1 Revenuelogical columns except forRevenueand Units.2.

Right-clickany one of the highlighted logical columns and select Delete. Alternatively you can select Edit > Deleteor press the Delete

key on your keyboard.

3.


f 222 19-09-2014 10:25


40/222

ClickYesto confirm the delete.4.

Confirm that F1 Revenuecontains only the Revenueand Unitscolumns.5.

Creating Simple Measures

Double-clickthe Revenuelogical column to open the Logical Columndialog box.

alt description here

1.

Click the Aggregationtab.2.


f 222 19-09-2014 10:25


41/222

Change the default aggregation rule to Sum.3.

Click OKto close the Logical Columndialog box. Notice that the icon has changed for the Revenuelogical column indicating that an

aggregation rule has been applied.

4.


f 222 19-09-2014 10:25


42/222

Repeat the steps to define the SUMaggregation rule for the Unitslogical column.

Measures are typically data that is additive, such as total dollars or total quantities. The F1 Revenue logical fact table contains the

measures in your business model. You aggregated two logical columns by summing the column data.

5.

Savethe repository without checking global consistency.

Congratulations! You have successfully built a business model in the Business Model and Mapping layer of a repository and created

business measures.

6.

You have created the initial Sample Sales business model in the repository. You now create the Presentation layer of the repository. The

Presentation layer exposes the business model objects in Oracle BI user interfaces so that users can build analyses and dashboards to analyzetheir data.

To build the Presentation layer you perform the following steps:

Creating a Subject Area

Creating Presentation Tables

Creating Presentation Columns

Renaming Presentation Columns

Reordering Presentation Columns

Creating a Subject Area

Right-click the white spacein the Presentation layer and select New Subject Areato open the Subject Area dialog box.1.

On the General tab, enterSample Salesas the name of the subject area.2.


f 222 19-09-2014 10:25


43/222

Click OKto close the Subject Areadialog box. The Sample Salessubject area is added to the Presentationlayer.3.

Creating Presentation Tables

Right-click the Sample Salessubject area and select New Presentation Tableto open the Presentation Table dialog box.1.

On the Generaltab, enterTimeas the name of the presentation table.2.


f 222 19-09-2014 10:25


44/222

Click OKto close the Presentation Table dialog box. The Time presentation table is added to the Sample Sales subject area.3.

Repeat the process and add three more presentation tables: Products, Customers, and Base Facts.

Please note that you are using the manual method for creating Presentation layer objects. For simple models it is also possible to

drag objects from the BMM layer to the Presentation layer to create the Presentation layer objects. When you create presentation

objects by dragging from the BMM layer, the business model becomes a subject area, the logical tables become presentation

tables, and the logical columns become presentation columns. Note that all objects within a subject area must derive from a single

business model.

4.

Creating Presentation Columns

In the BMMlayer, expand theD1 Timelogical table.1.


f 222 19-09-2014 10:25


45/222

Use Ctrl+ Clickto select the following logical columns:

Calendar Date

Per Name Half

Per Name Month

Per Name Qtr

Per Name Week

Per Name Year.

2.


f 222 19-09-2014 10:25


46/222

Dragthe selected logical columns to the Timepresentation table in the Presentationlayer.3.

Repeat the process and add the following logical columns to the remaining presentation tables:

Products: Drag Brand, Lob, Prod Dsc, Typefrom D2 Product.

Customers: Drag Cust Key, Namefrom D3 Customer.

Base Facts: Drag Revenue, Unitsfrom F1 Revenue.

4.

Renaming Presentation Columns

In the Presentationlayer, expand the Productspresentation table.1.

Double-click the Lobpresentation column to open the Presentation Column dialog box. On the General tab notice that "Use Logical

Column Name"is selected. When you drag a logical column to a presentation table, the resulting presentation column inherits the

logical column name by default. In this example the Lob presentation column inherits the name of the logical column "Sample

Sales"."D2 Product"."Lob".

2.


f 222 19-09-2014 10:25


47/222

Deselect Use Logical Column Name. The Name field is now editable.3.

EnterLine of Businessin the Name field.4.


f 222 19-09-2014 10:25


48/222

Click OKto close the Presentation Column dialog box. Notice that the presentation column name is now changed to Line of Businessin

the Presentationlayer.

5.

In the BMMlayer, expand D2 Product. Notice that the Loblogical column name is not changed. The point here is you can change object

names in the Presentationlayer without impacting object names in the BMMorPhysicallayers.

6.

In the BMMlayer, rename the Prod Dsclogical column to Product. Notice that the name change is inherited by the corresponding

presentation column.

7.

Make the following name changes to logical objects in the BMMlayer so that the names of the corresponding presentation columns are

also changed:

For the D3 Customerlogical table:

Change Cust Keyto Customer Number.

Change Nameto Customer Name.

8.


f 222 19-09-2014 10:25


49/222

Confirm that the corresponding presentation column names are changed.9.

Reordering Presentation Columns

In the Presentationlayer, double-click the Timepresentation table to open the Presentation Tabledialog box.1.


f 222 19-09-2014 10:25


50/222

Click the Columnstab.2.

Select columns and use the up and down arrows, or drag the columns. to rearrange the presentation columns into the following order

from top to bottom:

Per Name Year

Per Name Half

Per Name Qtr

Per Name Month

Per Name Week

Calendar Date

3.


f 222 19-09-2014 10:25


51/222

Click OKto close the Presentation Tabledialog box and confirm that the presentation column order is changed in the Presentation

layer.

4.

Repeat the steps to reorder the columns in the Productspresentation table:

Brand

Line of Business

Type

Product

5.

Savethe repository without checking global consistency.

Congratulations! You have successfully built the Presentation layer of a repository.

6.

You have finished building an initial business model and now need to test and validate the repository before continuing. You begin by checking

the repository for errors using the consistency checking option. Next you load the repository into Oracle BI Server memory. You then test the

repository by running an Oracle BI analysis and verifying the results. Finally, you examine the query log file to observe the SQL generated by

Oracle BI Server.

To test and validate a repository you perform the following steps:

Checking Consistency

Disabling Cache


f 222 19-09-2014 10:25


52/222

Loading the Repository

Setting Up Query Log

Creating and Running Analysis

Checking the Query Log

Checking Consistency

Select File > Check Global Consistency.1.

You should receive the message Business model "Sample Sales" is consistent. Do you want to mark it as available for queries?2.

ClickYes. You should receive the message: Consistency check fixed certain object(s); there are no errors, warnings or bestpractice violations left to report.

If you do not receive this message, you must fix any consistency check errors or warnings before proceeding.

3.

Click OK. Notice that the Sample Sales business model icon in the BMMlayer is now green, indicating it is available for queries.4.


f 222 19-09-2014 10:25


53/222

Save the repository without checking global consistency again.5.

Select File > Close to close the repository. Leave the Administration Tool open.6.

Disabling Cache

Open a browser and enter the following URL to navigate to Oracle Enterprise Manager:

http://:7001/em

In this tutorial the URL is http://localhost:7001/em

1.

Log in as an administrative user. Typically you use the administrative user name and password provided during the Oracle BI installation.

In this example the user name is weblogic.

2.

In the left navigation pane, expand Business Intelligenceand click coreapplication.3.

Click the Capacity Management tab.4.

Click the Performancesub tab.5.


f 222 19-09-2014 10:25


54/222

Locate the Enable BI Server Cachesection. Cache is enabled by default.6.

ClickLock and Edit Configuration.7.

Click Closewhen you receive the confirmation message "Lock and Edit Configuration - Completed Successfully."8.

Deselect Cache enabled. Caching is typically not used during development. Disabling cache improves query performance.9.

Click Apply.10.


f 222 19-09-2014 10:25


55/222

Click Activate Changes.11.

Click Closewhen you receive the confirmation message Activate Changes - Completed Successfully.12.


In the right pane, click the Deploymenttab.1.

Click the Repositorysubtab.2.


f 222 19-09-2014 10:25


56/222



In the "Upload BI Server Repository"section, click Browseto open the Choose file dialog box.5.

By default, the Choose file dialog box should open to the repositorydirectory. If not, navigate to the repository directory with the

BISAMPLE repository. If not, browse to D:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1

\repository.

6.

Select the BISAMPLE.rpdfile and click Open.7.


f 222 19-09-2014 10:25


57/222

EnterBISAMPLE1as the repository password and confirm the password.8.

Click Apply.9.

In the BI Server Repository section, confirm that the Default RPD is now BISAMPLE with an extension. In this example the file name isBISAMPLE_BI0079.

10.


f 222 19-09-2014 10:25


58/222


Allow Active Changes processing to complete. Click Closewhen you receive the confirmation message Activate Changes - Completed

Successfully.

12.

On the Availability > Processespage, select BI Servers, and click Restart Selected.13.


f 222 19-09-2014 10:25


59/222

ClickYeswhen you receive the message Are you sure you want to restart selected components?14.

Allow the Restart Selected In Progressprocessing to complete. This may take a few moments.15.

Click Closewhen you receive the confirmation message Restart Selected Completed Successfully".16.

Confirm that all components are running. Oracle BI cache is now disabled and the BISAMPLE repository is loaded into BI Server.17.

Leave Oracle Enterprise Manageropen.18.

Setting Up Query Log

Return to the Administration Tool, which should still be open.1.

Select File > Open > Onlineto open the repository in online mode. You use online mode to view and modify a repository while it is

loaded into the Oracle BI Server. The Oracle BI Server must be running to open a repository in online mode.

2.


f 222 19-09-2014 10:25


60/222

EnterBISAMPLE1as the repository password and enter your administrative user name and password.3.

Click Opento open the repository in online mode.4.

Select Manage > Identityto open Identity Manager.5.

In the left pane, select BI Repository.6.


f 222 19-09-2014 10:25


61/222

SelectAction > Set Online User Filter.7.

Enter an asteriskand click OKto fetch users from the identity store.8.

In the right pane, double-click your administrative user to open the User dialog box. In this example the administrative user is weblogic.9.

In the User dialog box, on the User tab, set Logging level to 2.10.


f 222 19-09-2014 10:25


62/222

Click OKto open the Check Out Objects dialog box.11.

In the Check Out Objects dialog box, click Check Out. When you are working in a repository open in online mode, you are prompted to

check out objects when you attempt to perform various operations.

12.

Select Action > Closeto close Identity Manager.13.

Select File > Check In Changes. Alternatively, you can click the Check In Changesicon on the toolbar.14.


f 222 19-09-2014 10:25


63/222

Save the repository. There is no need to check consistency.15.

Select File > Copy Asto save a copy of the online repository with the security changes.16.

In the Save Copy As dialog box, save the file as BISAMPLE.rpd , replacing the existing BISAMPLE repository.17.


f 222 19-09-2014 10:25


64/222

ClickYeswhen asked if you want to replace the existing BISAMPLE repository. This will create a new BISAMPLE repository with query

logging set for the weblogic user.

18.

Select File > Closeto close the repository.19.

Click OKwhen you receive the following message:

"In order for your online changes to take effect, you will have to manually restart each non-master Oracle BI Server instance in the

cluster."

20.


f 222 19-09-2014 10:25


65/222

Leave the Administration Tool open.21.

Creating and Running Analysis

Open a browser or a new browser tab and enter the following URL to navigate to Oracle Business Intelligence:

http://:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics

1.

Sign in as an administrative user. Typically you use the administrative user name and password provided during the Oracle BI

installation. In this example the user name is weblogic. If you need help identifying a user name and password, contact your companys

Oracle BI Administrator.

2.

In the left navigation pane, underCreate... >Analysis and Interactive Reporting, select Analysis.3.


f 222 19-09-2014 10:25


66/222

Select the Sample Salessubject area.4.

Select Reload Server Metadata.5.

In the left navigation pane, expand the folders in the Sample Sales subject area and confirm that the user interface matches the

Presentationlayer of the repository.

6.

Double-click the following column names in the Subject Areas pane to add them to the analysis:

Time.Per Name Year

7.


f 222 19-09-2014 10:25


67/222

Base Facts.Revenue

Click Results.8.

The analysis results are displayed in a compound layout, which includes a Title view and a Table view.9.

Use scrollbar slider of the compound layout to view additional rows.10.


f 222 19-09-2014 10:25


68/222


Click Administration.1.

Click Leave Page when prompted with the message: Are you sure?2.

On the Administration page, under Session Management, select Manage Sessions.3.

In the Cursor Cache section, locate your query and select View Log.4.


f 222 19-09-2014 10:25


69/222

Your log entry should look similar to the screenshot.5.

Locate the SQL Request section. This section contains the logical SQL issued by the query.6.

Just below the SQL Request section is the General Query Info section. This section identifies the repository, subject area, and

presentation catalog from which the query was run. You will need to scroll right to see the General Query Info text.

7.

Click the browser back button to return to the Manage Session page.8.

Click the browser back button to return to the Administration screen.9.

Click Home to return to the Home page.10.

Sign out of Oracle BI. ClickLeave Page when prompted about navigating away from this page. Leave the Oracle BI browser page open.11.

In this set of steps you create multiple logical table sources for the D3 Customer logical table. To create multiple logical table sources you

perform the following steps:

Opening the Repository in Offline Mode

Adding a New Logical Table Source

Creating Presentation Layer Objects


f 222 19-09-2014 10:25


70/222

Creating and Running an Analysis



Return to the Administration Tool, which should still be open. If not, select Start > Programs > Oracle Business Intelligence > BI

Administration.

1.

Open the BISAMPLErepository in offline mode with repository password as BISAMPLE1. Recall that earlier in this tutorial you created a

copy of the online repository and saved it as BISAMPLE.rpd.

2.

Select Manage > Identity to open Identity Manager.3.

Select BI Repository in the left pane.4.

Recall that earlier in this tutorial you created a copy of the online repository with logging level defined for the administrative user. Confirm

that your administrative user is visible in the right pane. In this example the administrative user is weblogic.

5.

Double-click the administrative user to open the User dialog box. On the Usertab, confirm that logging level is set to 2.6.


f 222 19-09-2014 10:25


71/222

Click Cancel to close the User dialog box.7.

Select Action > Closeto close Identity Manager. The offline BISAMPLE repository now has a user with a logging level set to 2. This will

allow you to check the query log as you complete the remaining exercises in this tutorial. You will not have to repeat the steps of copying

an online repository.

8.

Adding a New Logical Table Source

In the BMMlayer, expand Sample Sales > D3 Customer > Sources. Notice that the D3 Customer logical table has one logical table

source named D3 Customer.

1.

Rename the D3 Customer logical table source (not the logical table) to LTS1 Customer.2.


f 222 19-09-2014 10:25


72/222

Double-click LTS1 Customerto open the Logical Table Source dialog box.3.

Click the Column Mapping tab and notice that all logical columns map to physical columns in the same physical table: D3 Customer. It

may be necessary to scroll to the right to see the Physical Table column. Make sure "Show mapped columns"is selected.

4.


f 222 19-09-2014 10:25


73/222

Click OK to close the Logical Table Source dialog box.5.

In the Physicallayer, expand orcl > BISAMPLE.6.

Drag D4 Addressfrom the Physical layer to the D3 Customerlogical table in the BMMlayer. Notice this creates a new logical table

source named D4 Address for the D3 Customer logical table. It also creates new logical columns that map to the D4 Address physical

table.

7.


f 222 19-09-2014 10:25


74/222

In the BMMlayer, double-click the new D4 Address logical table source to open the Logical Table Source dialog box.8.

On the General tab, enterLTS2 Customer Addressin the Name field.9.


f 222 19-09-2014 10:25


75/222

Click the Column Mappingtab and notice that all logical columns map to physical columns in the same physical table: D4 Address. If

necessary, select Show mapped columnsand deselect Show unmapped columns.

10.

Click OKto close the Logical Table Source dialog box.11.


f 222 19-09-2014 10:25


76/222

Confirm that the D3 Customerlogical table now has two logical table sources: LTS1 Customerand LTS2 Customer Address. A single

logical table now maps to two physical sources.

12.

Right-click the new ADDRESS_KEYcolumn and select Delete. This is a duplicate column and is not needed.13.


f 222 19-09-2014 10:25


77/222

ClickYesto confirm the delete.14.

Use the Rename Wizard or a manual renaming technique to rename the new address logical columns (with uppercase letters) in D3

Customer. Your results should look similar to the screenshot. Hint: To use the Rename Wizard, select all of the new logical columns, then

right-click any one of the highlighted columns and select Rename Wizard to launch the wizard. If you need help using the Rename

Wizard, refer to Renaming Objects Using the Rename Wizardsection from earlier in this tutorial.

15.

Rename the remaining logical table sources according to the following table. Recall that logical table sources are located in the Sources

folder for a logical table. For example: D2 Product > Sources.

16.


f 222 19-09-2014 10:25


78/222


79/222

Click OK to close the Presentation Tabledialog box. Confirm that the Customer Regionspresentation table is added to the Sample

Sales subject area in the Presentationlayer.

3.

In the BMMlayer, expand Sample Sales > D3 Customer.4.


f 222 19-09-2014 10:25


80/222

Drag the following logical columns fromD3 Customerto Customer Regionsin the Presentationlayer:

Address 1

Address 2

Area

City

Country Name

Estab Name

Postal Code

Region

State Province

State Province Abbrv

Your column names may be slightly different depending on how you renamed them.

5.

Reorder the Customer Regions presentation columns in the following order, from top to bottom:

Region

Area

Country Name

State Province

State Province Abbrv

City

Postal Code

Address 1

Address 2

Estab Name

6.


f 222 19-09-2014 10:25


81/222

Double-click the Sample Sales subject area in the Presentationlayer to open the Subject Area dialog box.7.

Click the Presentation Tablestab.8.

Reorder the presentation tables so that Customer Regionsappears afterCustomers.9.


f 222 19-09-2014 10:25


82/222

Click OK to close the Subject Area dialog box. Confirm that the presentation tables appear in the expected order.

You now have two presentation tables, Customers and Customer Regions, mapped to the same logical table, D3 Customer. The

D3 Customer logical table is mapped to two physical sources: D3 Customer and D4 Address.

10.

Save the repository and check global consistency when prompted. You should receive a message that there are no errors, warnings, or

best practice violations to report.

If you do receive any consistency check errors or warnings, fix them before proceeding.

11.

Click OK to close the consistency check message.12.

Close the repository. Leave the Administration Tool open.13.


Return to Oracle Enterprise Manager, which should still be open. If not, open a browser and enter the following URL to navigate to

Oracle Enterprise Manager:

http:///:7001/em

In this tutorial the URL is http://localhost:7001/em

1.

If necessary, log in as an administrative user. Typically you use the administrative user name and password provided during the Oracle

BI installation. In this example the user name is weblogic.

2.


f 222 19-09-2014 10:25


83/222

In the left navigation pane, expand Business Intelligenceand click on coreapplication.3.

Click the Deploymenttab.4.

Click the Repositorysub tab.5.



In the "Upload BI Server Repository"section, click Browseto open the Choose file dialog box.8.

By default, the Choose file dialog box should open to the repositorydirectory. If not, navigate to the repository directory with the

BISAMPLE repository. If not, browse to D:\bi\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1

\re ositor .

9.


f 222 19-09-2014 10:25


84/222


85/222

In the BI Server Repository section, confirm that the Default RPD is now BISAMPLE with an extension. In this example the file name is

BISAMPLE_BI0080.

13.



f 222 19-09-2014 10:25


86/222


Successfully.

15.

On the Availability > Processespage, select BI Servers, and click Restart Selected.16.

ClickYeswhen you receive the message Are you sure you want to restart selected components?17.




f 222 19-09-2014 10:25


87/222




Return to Oracle BI, which should still be open. If not, open a browser or browser tab and enter the following URL to navigate to Oracle

Business Intelligence:

http:///:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics.

1.

If your previous session has timed out, sign in as an administrative user. Typically you use the administrative user name and password

provided during the Oracle BI installation. In this example the user name is weblogic.

2.

In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.3.


f 222 19-09-2014 10:25


88/222


89/222

Products.Type

Base Facts.Revenue

Click Resultsto view the analysis results. Use the Get more rowsbutton at the bottom of the results screen to see more rows.8.


Click Administration.1.




f 222 19-09-2014 10:25


90/222


Your log entry should look similar to the screenshot.5.




7.





f 222 19-09-2014 10:25


91/222


In this set of steps you use existing measures to created a derived calculation measure. To create a derived calculation measure you perform

the following steps:


Creating a Calculation Measure Derived from Existing Columns

Creating a Calculation Measure Using a Function





Return to the Administration Tool, which should still be open. If not, select Start > Programs > Oracle Business Intelligence > BI

Administration.

1.

Select File > Open > Offline.2.

Select BISAMPLE.rpdand click Open. Do not select any BISAMPLE repository with an extension, for example, BISAMPLE_BI0079.rpd.

Recall that these are the repositories that have been loaded into Oracle BI Server memory.

3.

EnterBISAMPLE1as the repository password and click OKto open the repository.4.


f 222 19-09-2014 10:25


92/222


93/222


94/222

Click the Edit Expressionbutton to open Expression Builder.6.

In the left pane select Logical Tables > F1 Revenue > Revenue.7.


f 222 19-09-2014 10:25


95/222

Click the Insert selected itembutton to move the Revenue column to the right pane.8.

Click the division operatorto add it to the expression.9.


f 222 19-09-2014 10:25


96/222

In the left pane select Logical Tables > F1 Revenueand then double-click Unitsto add it to the expression.10.

Click OKto close Expression Builder. Notice that the formula is added to the Logical Column dialog box.11.


f 222 19-09-2014 10:25


97/222

Click OKto close the Logical Column dialog box. The Actual Unit Pricecalculated measure is added to the business model.12.

Drag Actual Unit Pricefrom the BMMlayer to the Base Facts presentation table in the Presentationlayer.13.

Save the repository and check consistency. Fix any errors or warnings before proceeding.14.

Creating a Calculation Measure Using a Function

In the BMMlayer, right-click F1 Revenue and select New Object > Logical Columnto open the Logical Column dialog box.1.


f 222 19-09-2014 10:25


98/222

On the General tab, enterRevenue Rank in the Name field.2.

Click the Column Sourcetab.3.


f 222 19-09-2014 10:25


99/222


100/222

In the left pane selectFunctions > Display functions > Rank.6.

Click the Insert selected itembutton to move the Rank function to the right pane.7.


of 222 19-09-2014 10:25


101/222

Click in the expression.8.

In the left pane select Logical Tables > F1 Revenueand then double-click Revenueto add it to the expression.9.


of 222 19-09-2014 10:25


102/222

Click OKto close Expression Builder. Notice that the formula is added to the Logical Column dialog box.10.

Click OKto close the Logical Column dialog box. The Revenue Rank calculated measure is added to the business model.11.

Drag Revenue Rank from the BMMlayer to the Base Factspresentation table in the Presentationlayer.12.


of 222 19-09-2014 10:25


103/222


104/222


Click Closewhen you receive the confirmation message Lock and Edit Configuration - Completed Successfully.7.

Click Browseand navigate to the directory with the BISAMPLErepository.8.

By default, the Choose file dialog box should open to the repositorydirectory. If not, browse to D:\bi\instances\instance1\bifoundation

\OracleBIServerComponent\coreapplication_obis1\repository

9.

Select the BISAMPLE.rpdfile and click Open.10.


of 222 19-09-2014 10:25


105/222

EnterBISAMPLE1as the repository password and confirm the password.11.

Click Apply.12.

Confirm that the default RPD is now BISAMPLE with an extension. In this example the file name is BISAMPLE_BI0081.13.


of 222 19-09-2014 10:25


106/222



Successfully.

15.

On the Availability > Processespage, select BI Servers, and click Restart Selected16.


of 222 19-09-2014 10:25


107/222

ClickYeswhen you receive the message Are you sure you want to restart selected components?.17.






Return to Oracle BI, which should still be open. If not, open a browser or browser tab and enter the following URL to navigate to Oracle

Business Intelligence:

http:///:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics.

1.

If necessary, log in as an administrative user. Typically you use the administrative user name and password provided during the Oracle

2.


of 222 19-09-2014 10:25


108/222

In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis. Hint: If your session has not timed out,

you can create a new analysis by selecting New > Analysis.

3.

Select the Sample Salessubject area.4.

In the left navigation pane, expand theBase Factsfolder and confirm that the Actual Unit Priceand Revenue Rankcolumns are

visible.

5.

Create the following analysis by double-clicking column names in the Subject Areas pane:

Products.Product

Base Facts.Revenue

Base Facts.Revenue RankBase Facts.Units

Base Facts.Actual Unit Price

6.

Sort Revenue Rankin ascending order.7.

Click Resultsto view the analysis results.8.


of 222 19-09-2014 10:25


109/222

Please note that the Actual Unit Price calculation is correct, although it does not make sense from a business perspective. For

example, the unit price for an LCD HD Television would not be 9 dollars. This is a result of the underlying sample data.


Click the Administrationlink in the upper right.1.

ClickLeave Page when you are asked "Are you sure?"2.




of 222 19-09-2014 10:25


110/222

Your log entry should look similar to the screenshot.

Note that the division of Revenue by Units is calculated in the outer query block (D1.c2 / nullif ( D1.c1, 0) as c3 in this example).

Because you defined the Actual Unit Price calculation using logical columns, the SUM aggregation rule is applied to the Revenue

and Units columns first and then the division is calculated.

5.




7.





In this set of steps you add logical dimension hierarchies to the business model. A logical dimension represents a hierarchical organization of

logical columns belonging to a single logical dimension table. Logical dimensions can exist in the Business Model and Mapping layer and in the


of 222 19-09-2014 10:25


111/222


112/222

In the BMMlayer, right-click the Sample Salesbusiness model and select New Object > Logical Dimension > Dimension with

Level-Based Hierarchyto open the Logical Dimension dialog box.

1.

Name the logical dimension H2 Product.2.

Click OK. The logical dimension is added to the Sample Sales business model.3.

Creating Logical Levels

Right-click H2 Product and select New Object > Logical Level.1.

Name the logical level as Product Total.2.


of 222 19-09-2014 10:25


113/222

Because this level represents the grand total for products, select the Grand total levelcheck box. Note that when you do this, the

Supports rollup to higher level of aggregationfield is grayed out and protected.

3.

Click OKto close the Logical Level dialog box. The Product Totallevel is added to the H2 Product logical dimension.4.


of 222 19-09-2014 10:25


114/222

Right-click Product Totaland select New Object > Child Levelto open the Logical Level dialog box.5.

Name the logical level Product Brand.6.

Click OKto close the Logical Level dialog box. The Product Brandlevel is added to the logical dimension.7.


of 222 19-09-2014 10:25


115/222

Repeat the steps to add the following child levels:

Product LOBas a child of Product Brand

Product Typeas a child of Product LOB

Product Detailas a child of Product Type

Use the screenshot as a guide:

8.

Associating Logical Columns with Logical Levels

Expand the D2 Product logical table.1.

Drag the Brandcolumn from D2 Product to the Product Brand level in H2 Product.2.


of 222 19-09-2014 10:25


116/222

Continue dragging logical columns from the D2 Productlogical table to their corresponding levels in the H2 Productlogical dimension:

Logical Column Logical Level

Lob Product LOB

Type Product Type

Product Product Detail

Prod Key Product Detail

Your results should look similar to the screenshot:

3.

Setting Logical Level Keys

Double-click the Product Brand logical level to open the Logical Leveldialog box. On the Generaltab, notice that the Product LOB

child level is displayed.

1.


of 222 19-09-2014 10:25


117/222

Click the Keystab.2.

EnterBrandfor Key Name.3.


of 222 19-09-2014 10:25


118/222

In the Columns field, use the drop down list to select D2 Product.Brand.4.

Check Use for Display. When this is selected, users can drill down to this column from a higher level.5.


of 222 19-09-2014 10:25


119/222

Set Brandas the Primary key.6.

Click OKto close the Logical Level dialog box. The icon changes for Brand to show that it is the key for the Product Brand level.7.


of 222 19-09-2014 10:25


120/222

Use a different technique to create a logical level key: Right-clickLob for the Product LOB level and select New Logical Level Keyto

open the Logical Level Key dialog box.

8.

In the Logical Level Key dialog box, accept the defaults and click OK.9.

The icon changes forLobto show that it is the key for the Product LOBlevel.10.


of 222 19-09-2014 10:25


121/222

Use either method to set the remaining keys for the H2 Product logical dimension:

Logical Level Logical Level Key Use for Display

Product Type Type Yes

Product Detail Product Yes

Product Detail Prod Key No


Please note that the Detail level (lowest level of the hierarchy) must have the column that is the logical key of the dimension table

associated with it and it must be the key for that level: Prod Key in this example.

11.

Set Prod Keyas the primary key for the Product Detail level. Hint: Double-click the level and select the Keystab.12.


of 222 19-09-2014 10:25


122/222

Creating a Logical Dimension for Time

Use a different technique to create a logical dimension for Time. Right-click the D1 Time logical table and select Create Logical

Dimension > Dimension with Level-Based Hierarchy.

1.

A new logical dimension,D1 TimeDimin this example, is automatically added to the business model.2.

Rename D1 TimeDimto H1 Time.3.

Expand H1 Time . Notice that two levels were created automatically: D1 Time Total and D1 Time Detail. D1 Time Detail is populated

with all of the columns from the D1 Time logical table.

4.


of 222 19-09-2014 10:25


123/222

Rename D1 Time Total to Time Total, and rename D1 Time Detail to Time Detail.5.

Right-click Time Detailand select New Object > Parent Levelto open the Logical Level dialog box.6.


of 222 19-09-2014 10:25


124/222

On the General tab, name the logical level Week, and check Supports rollup to higher level of aggregation.7.

Click OKto close the Logical Level dialog box. The Week level is added to the H1 Time logical dimension.8.

Repeat the steps to add the remaining logical levels:

Monthas a parent of Week

Quarteras a parent of Month

Halfas a parent of Quarter

Yearas a parent of Half

9.


of 222 19-09-2014 10:25


125/222

Your final results should look similar to the screenshot:

Associating Time Logical Columns with Logical Levels

Use a different technique to associate logical columns with logical levels. Drag the logical columns from the Time Detail logical level (not

from the D1 Time logical table) to their corresponding levels in the H1 Time logical dimension. This is a convenient technique when

logical columns are buried deep in the business model.

Logical Column Logical Level

Per Name Year Year

Per Name Half Half

Per Name Qtr Quarter

Per Name Month MonthPer Name Week Week


1.

Delete all remaining columns from the Time Detail level except forCalendar Dateso that only Calendar Dateis associated with the

Time Detail level. Notice that deleting objects from the hierarchy does not delete them from the logical table in the business model.

2.


of 222 19-09-2014 10:25


126/222

Set the logical keys for the H1 Time logical dimension according to the following table:

Logical Level Level Key Use for Display

Year Per Name Year Yes

Half Per Name Half Yes

Quarter Per Name Qtr Yes

Month Per Name Month Yes

Week Per Name Week Yes

Time Detail Calendar Date Yes

3.

Creating a Logical Dimension for Customer

Use either technique to create a logical dimension with a level-based hierarchy named H3 Customerfor the D3 Customer logical table

with the following levels, columns, and keys. Hint: Create the levels first, then double-click a logical column to open the Logical Column

dialog box and use the Levels tab to associate the logical column with a logical level.

Level Column KeyUse for

Display

Customer Total

Customer Region Region Region Yes

Customer Area Area Area Yes

Customer Country Country Name Country Name Yes

Customer State State Province State Province Yes

Customer City City City Yes

Customer Postal

CodePostal Code Postal Code Yes

Customer Detail

Customer Name

Customer

Number

Customer Name

Customer

Number

Yes

No

1.


of 222 19-09-2014 10:25


127/222

Set Customer Totalas the grand total level.

Set Customer Numberas the primary key for the Customer Detail level.


Setting Aggregation Content for Logical Table Sources

Expand D1 Time > Sources.1.

Double-click the LTS1 Timelogical table source to open the Logical Table Source dialog box.2.


of 222 19-09-2014 10:25


128/222

Confirm that Aggregation content, group byis set to Logical Level and the logical level is set to Time Detail for the H1 Timelogical

dimension.

4.

Click OKto close the Logical Table Source dialog box.5.

Repeat to verify or set content settings for the remaining logical table sources using the table and screenshots as a guide:

Logical Table Source Logical Dimension Logical Level

LTS1 Product H2 Product Product Detail

LTS1 Customer H3 Customer Customer Detail

LTS2 Customer Address H3 Customer Customer Detail

LTS1 Revenue

H1 Time

H2 Product

H3 Customer

Time Detail

Product Detail

Customer Detail

6.


of 222 19-09-2014 10:25


129/222


130/222

Save the repository and check global consistency. Fix any errors or warnings before proceeding. Notice that you did not have to make

any changes to the Presentationlayer.

7.

Close the repository. Leave the Administration Tool open.8.

Testing Your Work

Return to Oracle Enterprise Managerand load the BISAMPLE repository.1.

Return to Oracle BI, which should still be open, and sign in if necessary.2.


of 222 19-09-2014 10:25


131/222

Products.Brand

Base Facts.Revenue

Click Results.4.

Click on the BizTechbrand and verify that you can drill down through the hierarchy to see revenue data at each level.5.

Select New > Analysis > Sample Sales.6.


Create the following analysis:

Time.Per Name Year

Base Facts.Revenue

8.


of 222 19-09-2014

Date post:	02-Jun-2018
Category:	Documents
Upload:	veereshhsm
View:	219 times
Download:	0 times

Creating a Repository 11.1.1.7

Documents