Business objects universe design tool

They have discovered that one of their departments are using a Microsoft Access database to record sales data. The Department Heads have indicated that they would like the information provided in a user-friendly format.

This will facilitate them to gain greater insight to their sales data to understand the trends and sales performance. To provide the connection between the data source Microsoft Access and the reporting tool a universe needs to be created. A semantic layer is a business representation of corporate data that helps end-users access data using common business terms.

Often when database developers build databases their main objectives involve the efficient creation, updating, and deletion of data. They are not usually concerned about whether nondatabase people understand the complexities of the underlying structures. While business users want to create reports based on the data contained in the database to facilitate decision making. The semantic layer insulates the business users from the underlying data complexity while ensuring the business is accessing the correct data sources and using consistent terminology.

The semantic layer enables users to use common business terms rather than the technical database language to access, manipulate, and organize information, it simplifies the complexity of the business data. The following diagram displays the various components of the semantic layer. A Universe is a semantic layer tool used in Business Objects to map the data in your data source using everyday terms.

The Universe enables the user to create a query to extract the data from a data source, describe it using common business terms, and then analyze the data using different reporting tools. The Universe is used to run queries against the data source to extract data. On the right of the screen is the schema of the database. While on the left are Universe objects that are required for reporting. However, before you create a universe you need to create a database connection. A data access driver is the software that connects the Universe to your middleware.

Watch here to learn how. To view the full IDT 4. To submit and vote on ideas for enhancements to this product, click here. Business Intelligence BusinessObjects. Browse pages. A t tachments 0 Page History.

Jira links. SAP BusinessObjects information design tool 4. What's New. How To Tutorials - see how to accomplish specific workflows:. No labels. Powered by Atlassian Confluence 7. Connection to an OALP data source can be created using connection wizard. You can use standard and transactional info cubes to create OLAP Universe or you can also use virtual info cubes.

You can see Bex queries supported more Universe features as compared to InfoCube and InfoCube requires more effort to customize Universe. Click Add in the "Wizard Connection" dialog box. In the next window, you need to select Connection Type. Select Personal to restrict access to the universe creator. You can use personal connections to access personal data on a local machine only. You can also launch connection wizard from Quick Design wizard.

Click on Begin button as shown below and it will take you to Define Universe parameter window. You can also check connection properties of an existing connection. In UDT, you have an option to run query against the aggregated tables in database. A condition can be set, and that query will run against aggregated tables for query optimization. This method of using aggregated tables is known as aggregate awareness. To build aggregated aware objects, you need to first identify the objects: measure or dimension objects.

You need to find out all possible combinations of aggregate objects in all tables and then arrange them in aggregate level order. Pass the names of all aggregated tables as arguments. When a universe is deployed, you make it available to Web intelligence users for reporting. Universe are deployed when they are exported to CMS repository. To make Universe available to all designers, you have to check if the Universe is not built on a secured connection.

Secured connections are used to export Universe to CMS repository. You need to select the target Universe domain and a group. If someone else is using Universe, it will be showed as greyed locked. For Universe in CMS, you can define users who can edit and delete based on access rights assigned to their user group.

At the Universe level, you can define users who are allowed to use a particular Universe. Access to Universe are managed using restrictions and you can apply multiple restrictions to single dashboard. You can also edit and delete restrictions as per access requirement. The dialog box appears. The current restrictions which are applied to Universe are available under available restrictions column.

You can find users and user groups that are defined for each restriction under Available Groups and Users pane. To add a user or group, click on add user or group button. You can also define groups with highest priority of restrictions. Click on Priority button and restriction on group name with highest priority will take precedence. To create new restrictions, click on New button on left side. This will open Edit restriction dialog box.

You have to enter the restriction name and you can see all restriction control tabs below. From each tab, you can select different restriction types as mentioned above. For example, control settings allow you to limit the size of result set and the execution time of the query.

Once you create new restrictions, you can apply to selected user and group. Once restriction is applied, it will show restriction name in the right pane. In the Universe design tool, the access to users and groups are managed using restrictions. In BO 4. Linked Universes are used to share common components such as parameters, classes, objects, or joins from different data sources. From BO 4. In UDT, Universe are created with file extension as. In IDT, Universe file extension is changed to.

To open unv file in IDT, it cannot be directly opened, however, you can convert unv file to unx file to open in Information Design tool. You cannot open an IDT. Universe Design tool is single source enabled. IDT is multi source enabled which means the data can be extracted from different data sources while creating a Universe. You can select unv file saved in repository or on local folder. Once you connect to BO repository, you can find all Universe published to repository in the left pane.

In the next window, you have an option to select conversion parameters. You can also change the destination folder to save. Sanjo Thomas. Neha Gupta. Sumit Agarwal. Neha Malik. Previous Page. Next Page. Useful Video Courses. More Detail. Previous Page Print Page. Save Close. Revision Revision number which indicates the number of times the universe has been exported to the CMS.

Comments Information about universe for yourself or another designer. Statistics List of the number of classes, objects, tables, aliases, joins, contexts, and hierarchies contained in the universe. Cancel last modification that has not been validated. If you make several changes to a join expression without validating the changes, clicking Cancel returns the expression to its original state.

Validate expression. This applies any changes to the join expression. Can contain special characters. Must be unique in universe.