They are used to perform custom drill down on objects from same or different classes in Universe. To create a Custom hierarchy, go to Tools → Hierarchies.
An Alias table is known as reference to a standard table in Data Foundation. The data in Alias table is completely same as the original table.
Alias tables are used to break loops in Join path in Data Foundation layer. An Alias table can also be used to rename a table.
You can use query panel to create or preview queries on a Business Layer or on the top of Universe published in repository.
Query panel allows you to add objects in the query and to preview the query results.
It is also possible to move object browser, components browser, Query browser and properties panel from the default locations. To dock a component, you have to click on top of panel and drag it to docking icon. To move a component, you have to first remove auto hiding.
By using derived table function
@derived_table(Derived Table Name)
In UDT, Universe are created with file extension as .unv. In IDT, Universe file extension is changed to .unx file.
To open unv file in IDT, it can’t be directly opened but you can convert unv file to unx file to open in Information Design tool.
You can’t open an IDT .unx file in Universe Design tool nor you can convert it to unv file.
Universe Design tool is single source enabled however IDT is multi source enabled means you can extract the data from different data sources while creating a Universe.
Universe Design Tool (UDT)
Information Design Tool (IDT)
Objects in the business layer are inserted automatically based on the cube. You can add below functions to enhance features in Business Layer −
Alerts are used to set notifications for data values, if values are acceptable or require attention. To enable alerts, click the check box.
You can set Alert Thresholds, enable auto color, etc.
Using aggregate awareness, you can use pre-aggregated data in tables in the database. It is used to improve query performance by processing less number of rows.
When you add an aggregate aware object in query, query generator retrieves the data from table with highest aggregation level.
Consider a Sales Fact table where sales is aggregated by per month. If your query asks for sales per month, query generator will retrieve the data from aggregated table.
Using UMT Upgrade Management provided with BI 4 for prior releases or in IDT you can do a direct conversion.
In a Universe there can be many objects which are dependent on each other and moving, deleting a resource can impact other resources that depends on that resource.
To check the dependency between different resources, you can select show local dependency.
A derived table is a virtual table in the data foundation that combines other tables using calculations and functions.
You can use derived tables for below purpose −
To create new models, you can use template as starting point. Template also gives an idea how different component works and you can add them to canvas to build a new model.
It shows you list of template under that category.
When you add objects using a query, you have options to select −
By manually entering values in cells in Spreadsheet and then binding these cells to component label and values under Properties.
Selector component allows users to pick different options at run time. Selector can be used to configure item’s row, value, position and label into embedded spreadsheet.
You can add selectors from Component browser in Dashboard designer.
You can set color for each element of a component in data model. Colors can be defined in Appearance tab under Properties pane.
There are wide range of colors available and you can also create your own custom colors.
To define color for each element, select the element → Go to Color Selector for each element. You can select below sections in color dialog box −
Theme Color : To define color of current theme.
Standard Color: These are group of basic colors.
Recent Color: This shows recently used colors.
Single value components are used for adding interactivity to data models. You can use them to add more attention to important parameters.
Single value components can be used in different styles −
Business Layer −
This layers contain all the classes and objects, you can check dimensions and measures that are defined in a Universe.
When you publish the business layer in repository, this shows the completion of Universe creation.
You can check the summary of Business Layer to see number of attributes, dimensions, measures, classes, LOV’s etc.
Data Foundation Layer −
This layer is used to define data foundation - includes tables from data source, joins, and keys etc.
These components allow you to connect your data model to web. Apart from this, you can also use data manager to configure web connectivity.
URL button: When user clicks at run time, a button links to a relative or absolute URL.
Reporting Service Button: This allows you to connect to reporting services server and select a report to use in data model.
Slide Show: This allows you to create a slide show of URL based images and SWF files.
SWL loader: This allows you to load SWF files from a URL and you don’t have to import the files. It is similar to slide show component but it provides better memory management.
Connection Refresh Button: This allows user to refresh the connection manually when you link to it.
Dashboards designer is SAP Business Objects data visualization tool that is used to create interactive dashboards from different data sources. Dashboard designer allows BI developers to create custom dashboards and analysis that meet the business requirement in an organization.
Dashboards can include different graphs, charts and gauge that are based on the data provided by data sources. Dashboards are used by Senior Management that offers up to date information to information to company CEO’s and VP’s.
No, business layer reads the structure of the OLAP source automatically.
The idea is basically if you need to access data from a table and regular RDBMS then your connection should be a relational connection but if your source is an application and data is stored in cube (multidimensional like Info cubes, Information models) then you would use an OLAP connection.
Relational connection can only be created in IDT/UDT.
OLAP can be created in both IDT and CMC.
Another thing to note is relational connection (including HANA) will always produce a SQL statement to be fired from report while OLAP connection normally create a MDX statement.
To use aggregate awareness, first the aggregated table has to be loaded to database and then add the table to Data Foundation.
Define aggregate aware objects. These are objects in the business layer for which you want queries to use the aggregate tables when possible instead of performing aggregation using non-aggregate tables.
In the SQL expression for the object, define the SELECT statement to use the @Aggregate_Aware function −
@Aggregate_Aware(sum(aggr_table_1), …, sum(aggr_table_n))
In IDT, it doesn’t convert OLAP universes created with prior releases. It is recommended to make a connection to OLAP source to take dimensional modeling advantages.
You can’t convert universes based on stored procedures using IDT.
Using IDT, you can convert linked universes however they are not supported in BI 4.
In SAP Dashboard Designer, below data connections are supported −
When you join a dimension table with two fact tables with one to many relationship, when you drag a dimension along with measure from both the fact tables, value of measures are inflated. This is called Chasm trap.
This can be solved using Context by creating two different contexts.
Other way is to go to Universe parameters and select the check box → Multiple SQL statements for each measure
You can define various access levels of an object −
When you define an object as public, all users can access the object. If an object is defined as restricted, users that are granted access level of restricted or higher can access. To define access level of objects −
Select the object in Business layer for which you want to define the access level. You can use CTRL key to select multiple objects. Right click on object → Change Access Level.
Using themes, you can apply same layout, appearance and formatting to data models when you need all models with same look. Theme provides you with a color scheme but you can customize it as per requirement.
To apply a theme, go to Format → Theme
Container component can be nested to create multilayer models. You can use canvas container within main canvas to hold one or more components. You can add, move, delete or change components in panel container.
You can use different types of containers −
File extension remains same when you run over in UMT. You need to perform a conversion in IDT to change file extension from unv to unx.
These components can be used with queries on Universe.
Query Refresh Button: This allows user to refresh the data at runtime. You can include Universe or BEX query to allow users to request a query refresh at run time.
Query Prompt Selector: This allows user to select values from BEX or Universe query prompts at run time. As per prompt type, user can select a single value to use as filter parameter or can choose selection objects.
A Personal connection is defined as created by one user and cannot be used by other users.
A shared connection can be used by other users through a shared server. You can’t publish a Universe to repository using a shared connection.
A secured connection overcomes the above limitations and you can use this to export Universe to the central repository.
Using query browser, you can click on Add query → Universe as data source
Select the published Universe and to add objects, you can use Query panel.
When query is added, you can do mapping of objects to spreadsheet and later to Dashboard components.
You can publish Webi report block as a BI service and can be consumed directly in Dashboard.
In a context, there are three states defined for a Join −
Included joins − In a part of the schema that is ambiguous, the context solves the loop by defining a path with the included joins.
Excluded joins − In a part of the schema that is ambiguous, the excluded joins define the path that context will never take.
Neutral joins are in a part of the schema that is not ambiguous, and are always included in the query path of the context. Any join that is not explicitly included or excluded is neutral.
A Context can be defined manually or by clicking detect Context option.
There are different ways −
You can use SLT method for data replication to HANA and then create a Universe on the top of HANA database. Universe can be consumed in Dashboard using query browser.
You can directly create a Universe on the top of transaction system.
Using transient provider, you can connect ECC to load data to BW and query browser can be used to connect to BW.
.cns - secured Repository connection
.cnx - local unsecured connection. If you use this connection it will not allow you to publish anything to repository.
Select the component → right click Properties tab
On right side, you get options to define various properties of a component in dashboard model.
To see dependent resources in Repository for a particular resource under Local project, right click and click on show Repository Dependency.
Enter the session details where resources are published and click on log in. It will show you list of published Universes in repository that are based on selected resource under Local Project.
IDT is known as Business Objects design tool that extracts the data from different data sources using an OLAP and Relational connection to create Universes. There are different Universe parameters that can be passed at time of Universe creation.
It can be used in below reporting and dashboard tools −
In a Universe, when you have 3 tables in structure and first table is joined with one to many relationship with second table which is connected with one to many relationship with third table and when you drag a measure from 2nd table and dimension from 3rd table, value of measure is inflated, this condition is called Fan trap.
You can resolve this by creating an alias of the 2nd table and defining contexts so that normal table is joined only with the first table, while the alias is joined with both the 1st and the 3rd table. We would take 2nd table’s measure only from the normal table and other dimensions of the 2nd table from the alias table.
Spreadsheets are preferred when the number of rows are less in Dashboard. It is by default set to 512 rows but you can edit this setting by going to Preferences.
Index awareness in a Universe determines which values in a filter conditions of the queries built from the universe, are replaced by their corresponding indexes or surrogate keys. Values in filter comes from dimensions table and you need a join with the fact table to get this value.