Discuss OBIEE ”; Previous Next Oracle Business Intelligence Enterprise Edition (OBIEE) is a Business Intelligence (BI) tool by Oracle Corporation. Its proven architecture and common infrastructure producing and delivering enterprise reports, scorecards, dashboards, ad-hoc analysis, and OLAP analysis provides a rich end-user experience. This tutorial explains all the fundamental aspects of OBIEE. Print Page Previous Next Advertisements ”;
OBIEE Questions and Answers ”; Previous Next OBIEE Questions and Answers has been designed with a special intention of helping students and professionals preparing for various Certification Exams and Job Interviews. This section provides a useful collection of sample Interview Questions and Multiple Choice Questions (MCQs) and their answers with appropriate explanations. SN Question/Answers Type 1 OBIEE Interview Questions This section provides a huge collection of OBIEE Interview Questions with their answers hidden in a box to challenge you to have a go at them before discovering the correct answer. 2 OBIEE Online Quiz This section provides a great collection of OBIEE Multiple Choice Questions (MCQs) on a single page along with their correct answers and explanation. If you select the right option, it turns green; else red. 3 OBIEE Online Test If you are preparing to appear for a Java and OBIEE related certification exam, then this section is a must for you. This section simulates a real online test along with a given timer which challenges you to complete the test within a given time-frame. Finally you can check your overall test score and how you fared among millions of other candidates who attended this online test. 4 OBIEE Mock Test This section provides various mock tests that you can download at your local machine and solve offline. Every mock test is supplied with a mock test key to let you verify the final score and grade yourself. Print Page Previous Next Advertisements ”;
OBIEE – Useful Resources ”; Previous Next The following resources contain additional information on OBIEE. Please use them to get more in-depth knowledge on this. Useful Links on OBIEE Oracle Business Intelligence Enterprise Edition − Oracle Business Intelligence Enterprise Edition. OBIEE Wiki − Wikipedia Reference for OBIEE. Useful Books on OBIEE To enlist your site on this page, please drop an email to [email protected] Print Page Previous Next Advertisements ”;
OBIEE â Security ”; Previous Next OBIEE security is defined by the use of a role-based access control model. It is defined in terms of roles that are aligned to different directory server groups and users. In this chapter, we will be discussing the components defined to compose a security policy. One can define a Security structure with the following components The directory Server User and Group managed by the Authentication provider. The application roles managed by the Policy store provide Security policy with the following components: Presentation catalog, repository, policy store. Security Providers Security provider is called in order to get the security information. Following types of security providers are used by OBIEE − Authentication provider to authenticate users. Policy store provider is used to give privileges on all applications except for BI Presentation Services. Credential store provider is used to store credentials used internally by the BI application. Security Policy Security policy in OBIEE is divided into the following components − Presentation Catalog Repository Policy Store Presentation Catalog It defines the catalog objects and Oracle BI Presentation Services functionality. Oracle BI Presentation Services Administration It enables you to set privileges for users to access features and functions such as editing views and creating agents and prompts. Presentation Catalog privileges access to presentation catalog objects defined in the Permission dialog. Presentation Services administration does not have its own authentication system and it relies on the authentication system that it inherits from the Oracle BI Server. All users who sign in to Presentation Services are granted the Authenticated User role and any other roles that they were assigned in Fusion Middleware Control. You can assign permissions in one of the following ways − To application roles − Most recommended way of assigning permissions and privileges. To individual users − This is difficult to manage where you can assign permissions and privileges to specific users. To Catalog groups − It was used in previous releases for backward compatibility maintenance. Repository This defines which application roles and users have access to which items of metadata within the repository. The Oracle BI Administration Tool through the security manager is used and enables you to perform the following tasks − Set permissions for business models, tables, columns, and subject areas. Specify database access for each user. Specify filters to limit the data accessible by users. Set authentication options. Policy Store It defines BI Server, BI Publisher, and Real Time Decisions functionality that can be accessed by given users or users with given Application Roles. Authentication and Authorization Authentication Authenticator Provider in Oracle WebLogic Server domain is used for user authentication. This authentication provider accesses users and group information stored in the LDAP server in the Oracle Business Intelligence”s Oracle WebLogic Server domain. To create and manage users and groups in an LDAP server, Oracle WebLogic Server Administration Console is used. You can also choose to configure an authentication provider for an alternative directory. In this case, Oracle WebLogic Server Administration Console enables you to view the users and groups in your directory; however, you need to continue to use the appropriate tools to make any modifications to the directory. Example − If you reconfigure Oracle Business Intelligence to use OID, you can view users and groups in Oracle WebLogic Server Administration Console but you must manage them in OID Console. Authorization Once authentication is done, the next step in security is to ensure that the user can do and see what they are authorized to do. Authorization for Oracle Business Intelligence 11g is managed by a security policy in terms of Applications Roles. Application Roles Security is normally defined in terms of Application roles that are assigned to directory server users and groups. Example: the default Application roles are BIAdministrator, BIConsumer, and BIAuthor. Application roles are defined as functional role assigned to a user, which gives that user the privileges required to perform that role. Example: Marketing Analyst Application role might grant a user access to view, edit and create reports on a company”s marketing pipeline. This communication between Application roles and directory server users and groups allows the administrator to define the Application roles and policies without creating additional users or groups in LDAP server. Application roles allows business intelligence system to be easily moved between development, test and production environments. This doesnât require any change in security policy and all that is required is to assign the Application roles to the users and groups available in the target environment. The group named ”BIConsumers” contains user1, user2, and user3. Users in the group ”BIConsumers” are assigned the Application role ”BIConsumer”, which enables the users to view reports. The group named ”BIAuthors” contains user4 and user5. Users in the group ”BIAuthors” are assigned the Application role ”BIAuthor”, which enables the users to create reports. The group named ”BIAdministrators” contains user6 and user7, user 8. Users in the group ”BIAdministrators” are assigned the Application role ”BIAdministrator”, which enables the users to manage repositories. Print Page Previous Next Advertisements ”;
OBIEE â Prompts ”; Previous Next A Prompt is a special type of filter that is used to filter analyses embedded in a dashboard. The main reason to use a dashboard prompt is that it allows the user to customize analysis output and also allows flexibility to change parameters of a report. There are three types of prompts that can be used − Named Prompts The prompt created at the dashboard level is called a Named prompt. This Prompt is created outside of a specific dashboard and stored in the catalog as a prompt. You can apply a named prompt to any dashboard or dashboard page that contains the columns, mentioned in the prompt. It can filter one or any number of analyses embedded on the same dashboard page. You can create and save these named prompts to a private folder or a shared folder. A named prompt always appears on the dashboard page and the user can prompt for different values without having to rerun the dashboard. A named prompt can also interact with selection steps. You can specify a dashboard prompt to override a specific selection step. The step will be processed against the dashboard column with the user-specified data values collected by the dashboard column prompt, whereas all other steps will be processed as originally specified. Inline Prompts Inline prompts are embedded in an analysis and are not stored in the catalog for reuse. Inline prompt provides general filtering of a column within the analysis, depending on how it is configured. Inline prompt works independently from a dashboard filter, which determines values for all matching columns on the dashboard. An inline prompt is an initial prompt. When the user selects the prompt value, the prompt field disappears from the analysis. To select different prompt values, you need to rerun the analysis. Your input determines the content of the analyses embedded in the dashboard. Named Prompt can be applied to any dashboard or dashboard page which contains the column specified in the Prompt. Column Prompts A column prompt is the most common and flexible prompt type. A column prompt enables you to build very specific value prompts to either stand alone on the dashboard or analysis or to expand or refine existing dashboard and analysis filters. Column prompts can be created for hierarchical, measure, or attribute columns at the analysis or dashboard level. Go to New → Dashboard Prompt → Select subject area. Dashboard prompt dialog box appears. Go to â+â sign, select the prompt type. Click on the column prompt → Select column → Click OK. New Prompt dialog box appears (this appears only for column prompts). Enter the label name that will appear on dashboard next to Prompt → Select the Operator → User Input. The User Input field”s drop-down list appears for column and variable prompts, and provides you with the option to determine the User Input method for the user interface. You can select any of the following − checkboxes, radio buttons, a choice list, or a list box. Example − If you select the User Input method of Choice List and Choice List Values item of all Column Values, the user will select the prompt”s data value from a list that contains all of the data values contained in the data source. You can also further make a selection by expanding the Options tab. These series of checkboxes allow you to restrict the amount of data returned in output. Once selection is made, click OK. The Prompt is added to Definition → Save the prompt using the save option at the top right corner → Enter the name → Click OK. To test the Prompt, go to My Dashboard → Catalog and drag the prompt to column 1. This prompt can be applied to full dashboard or on a single page by clicking on Properties → Scope. Save and run the Dashboard, select the value for a Prompt. Apply and Output value will change as per prompt value. Other Prompts Currency Prompt A currency prompt enables the user to change the currency type that is displayed in the currency columns on an analysis or dashboard. Example − Suppose that an analysis contains the sales totals for a certain region of US in US dollars. However, because the users viewing the analysis reside in Canada, they can use the currency prompt to change the sales totals from USD to Canada dollars. The prompt”s currency selection list is populated with the currency preferences from the userâs → My Account dialog → Preferences tab. Currency prompt option is available only if the administrator has configured the userpref_currencies.xml file. Image Prompt An image prompt provides an image that users click to select values for an analysis or dashboard. Example − In a sales organization, users can click their territories from an image of a map to see sales information, or click a product image to see sales information about that product. If you know how to use the HTML <map> tag, then you can create an image map definition. Variable Prompt A variable prompt enables the user to select a value that is specified in the variable prompt to display on dashboard. A variable prompt is not dependent upon a column, but can still use a column. Add Reports to BI Dashboard Pages You can add one or more existing reports to a dashboard page. The advantage is that you can share reports with other users and schedule the dashboard pages using agents. An agent sends the entire dashboard to the user, including all data pages that the report references. When configuring an agent for a dashboard page that contains a BI Publisher report, ensure that the following criteria are met − The output format of the BI Publisher report must be PDF. The agent must be set to deliver PDF. You can add reports to a dashboard page as embedded content and as a link. Embedded means that the report is displayed
OBIEE â Variables ”; Previous Next In OBIEE, there are two types of variables that are commonly used − Repository variables Session variables Apart from this you can also define Presentation and Request variables. Repository Variables A Repository variable has a single value at any point of time. Repository variables are defined using Oracle BI Administration tool. Repository variables can be used in place of constants in Expression Builder Wizard. There are two types of Repository variables − Static repository variables Dynamic repository variables Static repository variables are defined in variable dialog box and their value exists until they are changed by the administrator. Static repository variables contain default initializers that are numeric or character values. In addition, you can use Expression Builder to insert a constant as the default initializer, such as date, time, etc. You cannot use any other value or expression as the default initializer for a static repository variable. In older BI versions, the Administrator tool did not limit value of static repository variables. You may get warning in consistency check if your repository has been upgraded from older versions. In such case, update the static repository variables so that default initializers have a constant value. Dynamic repository variables are same as static variables but the values are refreshed by data returned from queries. When defining a dynamic repository variable, you create an initialization block or use a preexisting one that contains a SQL query. You can also set up a schedule that the Oracle BI Server will follow to execute the query and refresh the value of the variable periodically. When the value of a dynamic repository variable changes, all cache entries associated with a business model are deleted automatically. Each query can refresh several variables: one variable for each column in the query. You schedule these queries to be executed by the Oracle BI server. Dynamic repository variables are useful for defining the content of logical table sources. For example, suppose you have two sources for information about orders. One source contains current orders and the other contains historical data. Create Repository Variables In the Administration Tool → Go to Manage → Select Variables → Variable Manager → Go to Action → New → Repository > Variable. In the Variable dialog, type a name for the variable (Names for all variables should be unique) → Select the type of variable – Static or Dynamic. If you select dynamic variable, use the initialization block list to select an existing initialization block that will be used to refresh the value on a continuing basis. To create a new initialization block → Click New. To add a default initializer value, type the value in the default initializer box, or click the Expression Builder button to use Expression Builder. For static repository variables, the value you specify in the default initializer window persists. It will not change unless you change it. If you initialize a variable using a character string, enclose the string in single quotes. Static repository variables must have default initializers that are constant values → Click OK to close the dialog box. Session Variables Session variables are similar to dynamic repository variables and they obtain their values from initialization blocks. When a user begins a session, the Oracle BI server creates new instances of session variables and initializes them. There are as many instances of a session variable as there are active sessions on the Oracle BI server. Each instance of a session variable could be initialized to a different value. There are two types of Session variables − System session variables Non-system session variables System session variables are used by Oracle BI and Presentation server for specific purposes. They have predefined reserved names which canât be used by other variables. USER This variable holds the value the user enters with login name. This variable is typically populated from the LDAP profile of the user. USERGUID This variable contains the Global Unique Identifier (GUID) of the user and it is populated from the LDAP profile of the user. GROUP It contains the groups to which the user belongs. When a user belongs to multiple groups, include the group names in the same column, separated by semicolons (Example – GroupA;GroupB;GroupC). If a semicolon must be included as part of a group name, precede the semicolon with a backslash character (). ROLES This variable contains the application roles to which the user belongs. When a user belongs to multiple roles, include the role names in the same column, separated by semicolons (Example – RoleA;RoleB;RoleC). If a semicolon must be included as part of a role name, precede the semicolon with a backslash character (). ROLEGUIDS It contains the GUIDs for the application roles to which the user belongs. GUIDs for application roles are the same as the application role names. PERMISSIONS It contains the permissions held by the user. Example – oracle.bi.server.manageRepositories. Non-system session variables are used for setting the user filters. Example, you could define a non-system variable called Sale_Region that would be initialized to the name of the sale_region of the user. Create Session Variables In the Administration Tool → Go to Manage → Select Variables. In the Variable Manager dialog, click Action → New → Session → Variable. In the Session Variable dialog, enter variable name (Names for all variables should be unique and names of system session variables are reserved and cannot be used for other types of variables). For session variables, you can select the following options − Enable any user to set the value − This option is used to set session variables after the initialization block has populated the value. Example – this option lets non-administrators set this variable for sampling. Security sensitive − This is used to identify the variable as sensitive to security when using a row-level database security strategy, such as a Virtual Private Database (VPD). You can use the initialization block list option to choose an initialization block that will be used
OBIEE â Administration ”; Previous Next In OBIEE 10g, most of OBIEE administration tasks were mostly performed either through the Administration tool, the web-based Presentation Server administration screen, or through editing files in the filesystem. There were around 700 or so configuration options spread over multiple tools and configuration files, with some options like users and groups were embedded in unrelated repositories (the RPD). In OBIEE 11g, all administration and configuration tasks are moved into Fusion Middleware Control also called as Enterprise Manager. Administration tool that was present in OBIEE 10g is also present in 11g and is used to maintain the semantic model used by the BI Server. It has few enhancements in terms of dimension handling and new data sources. A major change is around security – when you open the Security Manager dialog − Go to Manage → Identity → Security Manager Dialog box appears. Users and Application Roles are now defined in the WebLogic Server admin console. You use the Security Manager to define additional links through to other LDAP servers, register custom authenticators and set up filters, etc. In the above screenshot, the users shown in the users list are those that are held in WebLogic Serverâs JPS (Java Platform Security) service, and there are no longer any users and groups in the RPD itself. There is no administrator user in above snapshot. It has standard administrator user that you set up as the WebLogic Server administrator when you install OBIEE, which typically has the username weblogic. There are also two additional default users: OracleSystemUser – this user is used by the various OBIEE web services to communicate with the BI Server and BISystemUser is used by BI Publisher to connect to the BI Server as a data source. In Application Roles tab, you can see a list default application roles – BISystem, BIAdministrator, BIAuthor and BIConsumer – which are used to grant access to Presentation Server functionality. Create a User in OBIEE To create a new user, log on to the WebLogic Server admin console → Go to Security Realms from the Fusion Middleware Control menu → Select myrealm → Select Users and Groups. Click on Users tab, it will show you a list of existing users. Click the New. → New user dialog box opens up → enter the userâs details. You can also use the Groups tab to define a group for the user, or assign the user to an existing group. Configuration and Metadata Files Following are the key file locations In OBIEE 11g − RPD Directory C:Middlewareinstancesinstance1bifoundationOracleBIServerComponent coreapplication_obis1repository NQSConfig.INI C:Middlewareinstancesinstance1configOracleBIServerComponentcoreapplication_obis1 nqsconfig.INI NQClusterConfig.INI C:Middlewareinstancesinstance1configOracleBIApplicationcoreapplication NQClusterConfig.INI nqquery.log C:Middlewareinstancesinstance1diagnosticslogsOracleBIServerComponent coreapplication_obis1nqquery.log nqserver.log C:Middlewareinstancesinstance1diagnosticslogsOracleBIServerComponent coreapplication_obis1nqserver.log nqsserver.exe C:MiddlewareOracle_BI1bifoundationserverbinnqsserver.exe WebCat Directory C:Middlewareinstancesinstance1bifoundationOracleBIPresentationServicesComponent coreapplication_obips1catalog instanceconfig.xml C:Middlewareinstancesinstance1configOracleBIPresentationServicesComponent coreapplication_obips1instanceconfig.xml xdo.cfg C:Middlewareinstancesinstance1configOracleBIPresentationServicesComponent coreapplication_obips1xdo.cfg sawlog0.log C:Middlewareinstancesinstance1diagnosticslogsOracleBIPresentationServicesComponent coreapplication_obips1sawlog0.log sawserver.exe C:MiddlewareOracle_BI1bifoundationwebbinsawserver.exe Go to Overview. You can also stop, start and restart all of the system components like BI Server, Presentation Server etc. via OPMN. You can click the Capacity Management, Diagnostics, Security or Deployment tabs to perform further maintenance. Capacity Management We have the following four options available for capacity management − Metrics gathered via DMS. Availability of all the individual system components (allowing you to stop, start and restart them individually). Scalability is used to increase the number of BI Servers, Presentation Servers, Cluster Controllers and Schedulers in the cluster in conjunction with the âscale outâ install option. Performance option allows you to turn caching on or off and modify other parameters associated with response time. Diagnostics − Log Messages show you view of all server errors and warnings. Log Configuration allows you to limit the size of logs and information gets included in them. Security − It is used for enabling SSO and selecting the SSO provider. Deployment − Presentation allows you to set dashboard defaults, section headings, etc. Scheduler is used to set the connection details for the scheduler schema. Marketing is for configuring the Siebel Marketing Content Server connection. Mail option is used for setting up the mail server to deliver for email alerts. Repository is used to upload new RPDs for use by the BI Server. Print Page Previous Next Advertisements ”;
OBIEE – Quick Guide ”; Previous Next OBIEE – Data Warehouse In today’s competitive market, most successful companies respond quickly to market changes and opportunities. The requirement to respond quickly is by effective and efficient use of data and information. “Data Warehouse” is a central repository of data that is organized by category to support the organization’s decision makers. Once data is stored in a data warehouse, it can be accessed for analysis. The term “Data Warehouse” was first invented by Bill Inmon in 1990. According to him, “Data warehouse is a subject-oriented, integrated, time-variant and non-volatile collection of data in support of management”s decision making process.” Ralph Kimball provided a definition of data warehouse based on its functionality. He said, “Data warehouse is a copy of transaction data specifically structured for query and analysis.” Data Warehouse (DW or DWH) is a system used for analysis of data and reporting purposes. They are repositories that saves data from one or more heterogeneous data sources. They store both current and historical data and are used for creating analytical reports. DW can be used to create interactive dashboards for the senior management. For example, analytic reports can contain data for quarterly comparisons or for annual comparison of sales report for a company. Data in DW comes from multiple operational systems like sales, human resource, marketing, warehouse management, etc. It contains historical data from different transaction systems but it can also include data from other sources. DW is used to separate data processing and analysis workload from transaction workload and enables to consolidate the data from several data sources. The Need for Data Warehouse For example − You have a home loan agency, where data comes from multiple SAP/non-SAP applications such as marketing, sales, ERP, HRM, etc. This data is extracted, transformed and loaded into DW. If you have to do quarterly/annual sales comparison of a product, you cannot use an operational database as this will hang the transaction system. This is where the need for using DW arises. Characteristics of a Data Warehouse Some of the key characteristics of DW are − It is used for reporting and data analysis. It provides a central repository with data integrated from one or more sources. It stores current and historical data. Data Warehouse vs. Transactional System Following are few differences between Data Warehouse and Operational Database (Transaction System) − Transactional system is designed for known workloads and transactions like updating a user record, searching a record, etc. However, DW transactions are more complex and present a general form of data. Transactional system contains the current data of an organization whereas DW normally contains historical data. Transactional system supports parallel processing of multiple transactions. Concurrency control and recovery mechanisms are required to maintain consistency of the database. Operational database query allows to read and modify operations (delete and update), while an OLAP query needs only read-only access of stored data (select statement). DW involves data cleaning, data integration, and data consolidations. DW has a three-layer architecture − Data Source Layer, Integration Layer, and Presentation Layer. The following diagram shows the common architecture of a Data Warehouse system. Types of Data Warehouse System Following are the types of DW system − Data Mart Online Analytical Processing (OLAP) Online Transaction Processing (OLTP) Predictive Analysis Data Mart Data Mart is the simplest form of DW and it normally focuses on a single functional area, such as sales, finance or marketing. Hence, data mart usually gets data only from few data sources. Sources could be an internal transaction system, a central data warehouse, or an external data source application. De-normalization is the norm for data modeling techniques in this system. Online Analytical Processing (OLAP) An OLAP system contains less number of transactions but involves complex calculations like use of Aggregations − Sum, Count, Average, etc. What is Aggregation? We save tables with aggregated data like yearly (1 row), quarterly (4 rows), monthly (12 rows) and now we want to compare data, like Yearly only 1 row will be processed. However, in an un-aggregated data, all the rows will be processed. OLAP system normally stores data in multidimensional schemas like Star Schema, Galaxy schemas (with Fact and Dimensional tables are joined in logical manner). In an OLAP system, response time to execute a query is an effectiveness measure. OLAP applications are widely used by Data Mining techniques to get data from OLAP systems. OLAP databases store aggregated historical data in multi-dimensional schemas. OLAP systems have data latency of a few hours as compared to Data Marts where latency is normally closer to few days. Online Transaction Processing (OLTP) An OLTP system is known for large number of short online transactions like insert, update, delete, etc. OLTP systems provide fast query processing and also responsible to provide data integrity in multi-access environment. For an OLTP systems, effectiveness is measured by the number of transactions processed per second. OLTP systems normally contain only current data. The schema used to store transactional databases is the entity model. Normalization is used for data modeling techniques in OLTP system. OLTP vs OLAP The following illustration shows the key differences between an OLTP and OLAP system. Indexes − In an OLTP system, there are only few indexes while in an OLAP system there are many indexes for performance optimization. Joins − In an OLTP system, large number of joins and data is normalized; however, in an OLAP system there are less joins and de-normalized. Aggregation − In an OLTP system, data is not aggregated while in an OLAP database more aggregations are used. OBIEE – Dimensional Modeling Dimensional modeling provides set of methods and concepts that are used in DW design. According to DW consultant, Ralph Kimball, dimensional modeling is a design technique for databases intended to support end-user queries in a data warehouse. It is oriented around understandability and performance. According to him, although transaction-oriented ER is very useful for the transaction capture, it should be avoided for end-user delivery. Dimensional
OBIEE â Aggregates ”; Previous Next Aggregations are used to implement query performance optimization while running the reports. This eliminates the time taken by query to run the calculations and delivers the results at fast speed. Aggregate tables has less number of rows as compared to a normal table. How Aggregation Works in OBIEE? When you execute a query in OBIEE, BI server looks for the resources which has information to answer the query. Out of all available sources, the server selects the most aggregated source to answer that query. Adding Aggregation in a Repository Open the Repository in an offline mode in the Administrator tool. Go to File → Open → Offline. Import the metadata and create logical table source in BMM layer. Expand the table name and click on source table name to open logical table source dialog box. Go to column mapping tab to see map columns in Physical table. Go to content tab → Aggregate content group by selecting the logical level. You can select different logical levels as per the columns in fact tables like Product Total, Total Revenue, and Quarter/Year for Time as per dimension hierarchies. Click OK to close dialog box → save the repository. When you define Aggregate in logical fact tables they are defined as per dimension hierarchies. Print Page Previous Next Advertisements ”;
OBIEE â Level-Based Measures ”; Previous Next Level-based measures are created to perform calculation at a specific level of aggregation. They allow to return data at multiple levels of aggregation with one single query. It also allows to create share measures. Example Let us say there is a company XYZ Electronics which sells its products in many regions, countries and cities. Now the company President wants to see the total revenue at country level – one level below region and one level above cities. So total revenue measure should be summed up to the country level. These type of measures are called level-based measures. Similarly, you can apply level-based measures on the time hierarchies. Once the dimension hierarchies are created, level-based measures can be created by double clicking on the total revenue column in the logical table and setting the level in the levels tab. Create Level-Based Measures Open the repository in offline mode. Go to File → Open → Offline. Select .rpd file and click open → Enter repository password and click Ok. In BMM layer, right-click on Total Revenue column → New Object → Logical column. It will open the logical column dialog box. Enter the name of logical column total revenue. Go to column source tab → Check derived from existing columns using an expression. Once you select this option, expression edit wizard will be highlighted. In expression builder wizard, select the logical table → Column name → Total revenue from the left side menu → Click OK. Now go to level tab in logical column dialog box → Click on logical dimension to select it as grand total under logical level. This specifies that the measure should be calculated at grand total level in the dimension hierarchy. Once you click OK → Total Revenue logical table will appear under the logical dimension and Fact tables. This column can be dragged to presentation layer in the subject area to be used by end users to generate reports. You can drag this column from fact tables or from logical dimension. Print Page Previous Next Advertisements ”;