Monday, May 25, 2009

Desktop Intelligence Related Questions

1) What is Desktop Intelligence?
Desktop Intelligence is an integrated query, reporting and analysis solution for business professionals that allows you to access the data in your corporate databases directly from your desktop and present and analyze this information in a Desktop Intelligence document.
When you run the query, Desktop Intelligence connects to the database and retrieves the data mapped to the objects you selected. A query is a type of data provider. The data provider contains the data you have chosen to retrieve from the data source. Using this data set, you can build interactive reports. Desktop Intelligence lets you access data from a wide range of sources: from relational and multidimensional databases, from packaged applications, from personal data documents, and, using Microsoft Visual Basic for Applications procedures, from virtually any source.

2) How is information shared in business objects?
You can quickly and easily share the documents you have created with other users in your company, either by sending them directly to selected individuals or groups, or by Exporting them to the repository as Folders or Categories. The repository stores the documents you send so that other users can retrieve and view them. It also stores information about the documents it stores, such as name of sender, date, and also which users in the company have the right to retrieve and view a document. You can Import documents that other users have sent, using Web Intelligence documents which you can open and view in Desktop Intelligence. You can also use InfoView to send documents for scheduled processing.

3) How are documents organised in repository?
The Repository organizes documents into Folders and Categories in an orderly system that permits easy access for you and others working with documents. You select the documents you want to import from or export to Desktop Intelligence.

Folders: Folders are the physical place where documents are stored. Only one document with a given name may be placed in a folder or category. It is possible to place documents in several categories. If necessary change the name of the document or give it a number to place it in the same folder or category. It is possible to create or delete sub-folders.
There are 2 types of folders:
My Folders with 2 sub-folders
• Favorites (Generally reserved for often used documents)
• Inbox (Generally reserved for documents received from other users
Public Folders (For shared documents.)

Categories: Categories are used for classifying information regardless of its storage location.
There are two types of Categories:
• Corporate Categories
• Personal Categories

4) What are different data sources available for Desktop Intelligence?
Desktop Intelligence lets you access data from a wide range of sources. You can access data from:
• Universes
• Personal Data Files
•Stored Procedures: You can only use stored procedures if your supervisor or IS department has provided them, and if the RDBMS at your site supports them. A stored procedure is an SQL (Structured Query Language) script, saved and executable on your database.
• Freehand SQL Server: You can use free-hand SQL if you are familiar with SQL, which is the language used to interact with relational databases. In free-hand SQL, you open or write a SQL script, which you then run against the database.
• XML Data Provider
• VBA Data Provider

5) Can all Desktop Intelligence users build queries using all data providers?
Your Desktop Intelligence supervisor can restrict access to certain types of data providers, or even certain objects within a universe. As a result, you might be able to build queries on universes but no other type of data provider, and then be able to use only certain objects in the universe. The way the supervisor sets up access to data providers and other Desktop Intelligence features depends entirely upon the query and reporting needs of your organization.

6) Who sets up connection to data providers in desktop intelligence?
Universe: The Universe designer sets up connection to the database.
Stored Procedures: The supervisor creates the connection to access a stored procedure.
Free- hand SQL: In free-hand SQL, you can create your own connection to the database. Once you have created the connection, you can make it available to other users.
Personal data files and XML files: When you access data in a personal data file or XML file, you select the file and in doing so, you “connect” to it. This is not a technical task, it’s just a question of selecting the right file.
VBA procedures: A VBA procedure runs a VBA macro that retrieves data for your Desktop Intelligence report. The person who creates the macro defines the connection to the data source in the macro code.

7) What are restrictive connections to database in desktop intelligence mean?
If you are working with a universe that is set up with a restrictive connection, you need to supply the database username and password to run a query. This username/password is not the one that you use to log onto Desktop Intelligence; it is the username/password of the underlying database (for example an SQL Server database) that the universe accesses. This database normally remains hidden, but the universe designer can set up a restrictive connection to add an extra layer of security. Depending on the type of restrictive connection, you need to supply the database username and password in some or all of the following situations:
• When you first run a query
• When you refresh a query
• When you parse a query to test its validity

8) How Universe queries are generated using Desktop Intelligence?
When you build a query, you select objects from a universe, then run the query. Desktop Intelligence connects to the database, and retrieves the data mapped by the objects you selected. Desktop Intelligence retrieves this data by executing an SQL query against the database. Desktop Intelligence generates this SQL according to the objects you select.
9) What is meant by building powerful queries in Desktop Intelligence?
You build a simple query by adding objects to the Query Panel. The procedures described in the following sections enable you to build a more powerful query by controlling the data that your queries retrieve. You can:
• Define scope of analysis
• Conditions
• Sort data
• Retrieve a specified number of rows of data
• Eliminate duplicate rows of data from the query result

10) What is meant by Scope of Analysis?
Analysis means looking at data from different viewpoints and on different levels of detail. “Scope of analysis” means a subset of data, returned by a query, that you will use for analysis in your report. The data for your scope of analysis does not appear in the report until you decide that you want to use it in analysis.

The scope of analysis you can define depends on hierarchies in the universe. A hierarchy, which the designer sets up when creating the universe, consists of dimension objects ranked from “less detailed” to “more detailed”. The objects that belong to hierarchies are the ones you can use to define scope of analysis.

11) How do you limit the query using conditions and what are they?
A condition is a way of limiting the data that a query returns. In Desktop Intelligence, you can set three types of conditions on a query:
Predefined conditions: When universe designers build universes, they can create predefined conditions for you to use.
Simple conditions: Enable you to limit data returned by a result object. For example, you can find out about certain customers by applying a simple condition on the Customer object, then selecting the customer names that appear in a dialog box.
Complex conditions: Enable you to limit the query results by any object in the universe.

12) What are options that can be setup before running a query?
Before running a query, you can set options that enable you to:
• Specify the number of rows of data that you want the query to return. The Default Value option corresponds to the maximum number of rows that the universe designer specified for queries on the current universe.
• Eliminate duplicate rows of data.
• Retrieve no data when you run the query. In this case, Desktop Intelligence generates the query SQL but does not connect to the database. The names of the objects included in the query appear as column headings in the report. This option is useful if you want to save the query you have built, but refresh it at an off-peak time.

13) What are the restrictions on Free-hand SQL?

The types of SQL script that you are allowed to run as free-hand SQL are determined by your Desktop Intelligence administrator. If you attempt to run a script for which you do not have permission, you will receive an error message. Typically, you are able to run scripts that contain only one SELECT statement.

Note: BusinessObjects does not execute COMPUTE and ORDER BY clauses in free-hand SQL statements.

14) What are restrictions on Stored Procedures?
• The Desktop Intelligence supervisor grants access to the database or account where stored procedures are located.
• Not all RDBMSs support stored procedures.
• COMPUTE, PRINT, OUTPUT or STATUS statements contained in stored procedures are not executed.

15) What are the benefits on using Personal Data files?
The main benefits of using personal data files are as follows:
• You can display corporate data next to personal data in the same report which can be used for comparison.
• If you have no connection to a remote database or if there is no RDBMS at your site, you can use personal data files as your only data source.
• You can use Desktop Intelligence reporting and analysis features to work on data that comes from other applications.

16) How do you use Visual Basic for Applications procedures?
A VBA data provider is a powerful and flexible tool for accessing external data. Very often you will want to access automation servers through VBA to retrieve their proprietary data. VBA allows you to retrieve data from various sources: ADO, DAO, RDO, Application Object Models, EDK and low-level APIs.

To create a VBA data provider, you write a VBA procedure that takes the interface DpVBA Interface as a parameter. You can write this procedure from within the VBA environment of Desktop Intelligence. The DpVBAInterface is the interface to the VBA data provider Automation object. The procedure for writing a VBA data provider is:

1. Create a connection to the data source.
2. Create a data cube.
3. Set the data cube dimensions.
4. Populate the cube with data from the data source.

Once the data cube is populated, you can generate a report based on this data in Desktop Intelligence.

17) What is an XML?
XML is a text-based data format that structures data in elements or tags. XML files are similar to the HTML files used to build pages on the World Wide Web. The principal difference is that, the set of HTML elements is limited to those used to describe the structure of a Web page, an XML file can contain any elements, depending on its application.

Creating an XML-based report involves two steps:
• building an XML filter
• building the report
18) What are common dimensions?
Common dimensions are dimensions with the same name occurring in the same universe.
Dimensions called Year that occur in a universe and an Excel spreadsheet are not common. Desktop Intelligence will prompt you to link them.
19) What situations require you link data providers?
Desktop Intelligence automatically links data providers with a common dimension. Two dimensions in separate data providers are common when they belong to the same universe and have the same name. Desktop Intelligence prompts you to link data providers if there is no common dimension between the data providers. If you simply want to add columns of data to a report, use the Edit Data Provider command on the Data menu instead of building a new query. This method lets you add result objects to the initial query; Desktop Intelligence automatically inserts the new columns of data in the report or creates a new report.

20) Which dimension should act as a link between data providers?
It is necessary that the dimension you use to link data providers be the same type (numeric or alphanumeric) in both data providers. If not, two rows of data will appear for the linked object when you create a table that uses the object.
Additionally you should use only dimensions that return the same type of values. It doesn’t make sense to create a link between dimensions with totally different lists of values (Year and Region, for example).

21) What is difference between purging and deleting of data providers?
Purging means emptying a data provider of its results, deleting means getting rid of the data provider for good —an action that cannot be undone.
Why purge or delete a data provider? Purging reduces the size of a document, so is useful when you want to send the document to other users, or save it on a diskette, for example. You should only delete a data provider, however, if you are certain that you and other users no longer need it.


22) What are different ways in which data can be analyzed using desktop intelligence?
• Desktop Intelligence on-report analysis allows you to work directly on your data in your report using drag and drop and or with simple mouse clicks.
• Desktop Intelligence enables you to carry out multidimensional analysis in Drill mode.
• Desktop Intelligence Slice and Dice mode allows you to organize data for analysis in the slice and dice panel.
23) What is On-report analysis?
You can drag and drop data on your report to get a different viewpoint for your analysis. You can add data from the Report Manager to create tables and sections. You can replace, swap and re-organize data on the report. Desktop Intelligence redoes the calculations in your report immediately so that you can see at once how different combinations of factors affect your performance. Dynamic on-report grouping allows you to create groups for comparative analysis and you can quickly insert common business calculations or easily create your own formulas and variables for analysis. You can sort, filter and rank your data using a simple mouse click to focus your analysis on a slice of data.

24) What is Drill – mode?
Drill mode is a Desktop Intelligence analysis mode that allows you to break down data and view it from different angles and on different levels of detail to discover what the driving factor is behind a good or bad result. Drill mode allows you to include data for analysis behind the scenes of your report and display the top level data only. If necessary, you can drill down to the more detailed data to understand the higher-level data. This allows you to see how different aspects of your business affect your revenue step by step.


25) How does drill mode work?
The person who creates the Desktop Intelligence universe organizes objects in hierarchies, with the most general object in the class at the top and the most detailed at the bottom. Objects are grouped in this way to make it easy for you to find what you are looking for. They are classified inside the groups so that if you want to make a high level report you know you need to include objects at the top of the list in your query and if you want a more detailed report then you choose objects from further down the list.

26) How are hierarchies used in drill mode?
When you analyze data in drill mode, you use hierarchies. The universe classes are the default hierarchies you use for drilling but the universe designer can also set up custom hierarchies. You can also create and edit hierarchies in your reports. Drill hierarchies contain dimension objects only. In drill mode, you drill down on dimensions, for example from Year to Quarter to Month. At each level Desktop Intelligence recalculates measures such as Revenue or Profit Margin.


27) What is the difference between drill-up, drill-down, drill across and drill through?
Drilling down: When you drill down, you display the next level of detail in a hierarchy
Drilling up: Drilling up is the opposite of drilling down. When you drill up, you go back up through the hierarchy to display data on less detailed levels.
Drilling across: When you drill down and up, you move through the levels of the same hierarchy. However, if you cannot find the answer to a question by analyzing data in its current hierarchy, you can move to another hierarchy to analyze other data.
Drilling through to the database to bring in new data If the lowest level of detail you need is not currently available in the report, you can drill through to the database directly from drill mode and get the data you need. You do not have to edit the query in the Query Panel.

28) What is Slice Dice mode?
Slice-and-dice mode enables you to switch the position of data in a report, for example by moving columns to rows to create a crosstab. You can also use slice-and-dice mode to:
• work with master/detail reports
• display and remove data
• rename, reset and delete blocks
• turn tables and crosstabs into charts, and vice versa
• apply, edit and delete breaks, filters, sorts, rankings and calculations

You access slice-and-dice mode through the Slice and Dice Panel, a pop-up window that provides a graphical representation of the report you are working on. You carry out slice-and-dice tasks by dragging and dropping icons that represent your data.

29) What are master/detail reports?
Master/detail reports display data in sections. Each section contains a “master” or parent piece of data, for example a resort, or a year. The rest of the data in the section relates to the master.
30) How are filters used to manage filters?
A filter enables you to hide data you do not want to view behind the scenes and display only the data you need. There are two types of filter. A global filter affects the whole report. A block specific filter filters data for the specified chart, table or crosstab only.

31) How can the filter be ignored using formulas?
You can force Desktop Intelligence to ignore any filters you have inserted on a report so that it calculates on all data, not just the filtered values. To do this, you use the NoFilter function. The syntax is: =NoFilter(formula)

In the first table, the sum includes New York and Washington revenues only.
The formula to calculate this sum is: =Sum()

In the second table, formula for calculating the sum includes the NoFilter function. As a result, the sum includes revenues for all cities. The formula is as follows:
=NoFilter (Sum())

32) What is the use of ranking?
You might want to show just the extreme ranges of your data, for example your top ten customers. Ranking enables you to look at the largest and smallest numbers in a report. Like filtering, it hides the data you do not want to display. Desktop Intelligence does not delete the data from the report; you can view it again whenever you like by removing the ranking. Ranking also sorts the data in descending order. Thus, the largest value of the ranking is always at the top of the ranked column and the smallest value at the bottom. You can rank data in tables, crosstabs or master cells in master/detail reports.

33) How is ranking performed if they are breaks inserted inside the data?
In a table or crosstab in which breaks have been inserted, data is ranked separately for each break level.
Note: If you have created a local variable using values from different data providers, you will not be able to rank data based on this variable. The variable will not be displayed in the list in the Ranking dialog box.

34) How do you manage ranking with filters and sorts?
To rank data in a report, you must remove any sorts or filters currently applied to that data. If any sorts or filters exist when you try to apply a ranking, Desktop Intelligence displays the following message: A sort and/or a filter has already been applied to the selection. Do you want to overwrite it?

35) What is the function of alerts?
You can highlight data in a Desktop Intelligence report using alerters. Alerters use special formatting to make data that fits certain conditions stand out from the rest of the data. This helps draw attention to trends and exceptions in report data.

36) Can we use alerters on charts?
No

37) What are user objects and what does it contain?
A universe consists primarily of classes and objects created by the universe designer. If the objects in a universe do not meet your needs, you can create your own additional user objects. User objects appear in the User Objects class in the universe. You include them in queries in the same way that you include regular objects. You do not need to define a connection to a database to define a user object.

A user object has a name, a type (character, date or numeric), a qualification (dimension, measure or detail) and a formula. The formula contains a combination of functions, objects, user objects, operators, and text. User objects are end-user personal objects that are not shared with other end-users. User objects are defined for each universe and stored on a local file inside the “\Universe” folder. For example, if you create a user object in the BEACH.UNV universe, Desktop Intelligence stores it locally in the file BEACH.UDO in the Universe folder.

38) What are the restrictions on user objects?
· Cannot be moved from User class: You can work only with the user objects that you create yourself, and you cannot move user objects from the User Objects class.
· Also, user objects are available only in the universe in which they were created.
· User objects are not shared.
· Reports that include user objects can only be viewed by other end-users. This is because user objects are stored locally in a user object definition file. Other end-users, who do not have the same user object definition file, are not able to access the user object definitions.
· If an end-user tries to refresh or edit a query that contains another user’s user objects, Desktop Intelligence removes the objects from the query and report. Despite these restrictions, the universe designer can convert user objects into regular objects that can be made available in other universes and for other users.
Note: You cannot schedule reports that contain user objects and keep the user objects; they are removed when the report is refreshed.

39) How can the user objects be shared among the end users?
If you want to share user objects with other users, you should ask the universe designer to include these user objects in the related universe in order to make them available to all Desktop Intelligence end-users.

40) What are wildcard characters?
Conditions with the Match pattern and Different from pattern operators are great for finding lists of similar values, such as customer names beginning with S.

Wildcards are special characters that can denote any single character, or any number of characters. Desktop Intelligence supports the standard wildcard characters, which are:
% : Replaces several characters, or in the response to a prompt. For example, N% returns all values beginning with an N (New York, Nevada)
- : Replaces a single character in a constant. For example, GR_VE returns Grave, Grove, Greve.
41) How does the operator in list work?
The In list operator lets you select multiple values for a document. These multiple values can be a condition on a query that you want to build or can be the basis for an interactive document in which Desktop Intelligence prompts other users to select values from the list you created to view data limited to their needs.

42) Explain the difference between Different from and except operator?
Different from, Not in list and Except are all operators that exclude certain data from your query results. Does this mean that you could use this condition to obtain a list of customers who have not stayed at Bahamas Beach?
Resort Different from ‘Bahamas Beach’
The result of this query includes those customers who have stayed at Bahamas Beach and elsewhere. Why? Because reservations exist for these customers for resorts other than Bahamas Beach. These reservations alone are enough to satisfy the condition ‘Resort differs from Bahamas Beach’. Furthermore, this condition excludes customers who have made no reservations. Desktop Intelligence checks these customers’ records against reservations and determines that no reservations satisfy the condition ‘Resort differs from Bahamas Beach’ - because there are no reservations! Nevertheless, it is clear that a report showing customers who have not stayed at Bahamas Beach should include customers who have not stayed anywhere.

You solve this problem by using the Except operator instead of Different from. When you use Except, Desktop Intelligence builds two queries:
• All customers.
• Customers who have reservations for Bahamas Beach.
Desktop Intelligence then subtracts the customers given by the second query from those given by the first. This returns the result you want.

Note also that:
• You can only specify one value with Different from, but multiple values with Not in list.
• You can only specify one value with Except. However, you can build combined queries using MINUS to exclude, for example, Bahamas Beach customers and 1996 customers.

43) Define level of calculation?
· If you want to obtain a single result row: click Globally, then click Next.
· If you want to obtain several result rows: click By one or more objects, select the objects from the list.

44) What is meant by synchronization of calculation?
While making a condition in the query panel and adding a calculation to a condition after choosing the level of calculation it prompts for synchronizing the calculation.
This is can be done in two ways:
· If you want to make a calculation independently of your objects: click Independently of your objects, then click Next.
· If you want to make a calculation for each value of one or more of your objects, which allows you to limit the calculation to particular objects: click For each value of one or more objects, select the objects from the list, then click Next.

45) What is meant by applying calculation to a query?
When you use a calculation, Desktop Intelligence builds SQL that contains a subquery. A subquery is an inner query. The database that receives the SQL generated by Desktop Intelligence evaluates the result of the inner query against each row of the outer query to determine if the row should appear in the result.

In the process as you move through the wizard, you specify:
Ø The object to use in the calculation: This is the object in the outer query whose value is compared against the result of the inner query. In the example, the object is Invoice Date.
Ø The aggregate function to apply to the object: In the example you applied the Maximum function because you were interested in the most recent invoice date.
Ø The level of calculation: This determines the grouping in the subquery. In the example you chose Globally because you were interested simply in the customer’s latest invoice date, not a latest invoice date by some other criteria.
Ø Synchronization: This determines the subquery links to the main query In the example you chose the Customer object because you were interested in each customer’s latest invoice date.
Ø The number of values to compare: This determines how many values in the subquery the database compares against the values in the outer query. In the example you can choose either option because the subquery returns one row only for each customer.

46) What is list of values?
A list of values contains the values returned by an object. You use lists of values to select the value(s) you need when defining conditions on a query or when selecting the value(s) in a prompt. When you use or view a list of values for the first time, Desktop Intelligence creates a .lov file that contains the query definition and the values it returns. By default, .lov files are located in sub-folders inside the UserDocs folder.

47) How are list of values created?
In Designer, the universe designer decides whether to associate a list of values with an object. Once associated, the list of values can be viewed or edited in Designer or Desktop Intelligence. The first time you view an object’s list of values, Desktop Intelligence runs a query and retrieves the values from the database; the object’s default list of values is generated by the object query.

48) Where does the function Variance doesnot work?
Variance syntax containing the Where operator will work in all cases except when you have two cascading Wheres (a variance using a Where operator that contains a formula that also uses a Where operator) or in certain contexts, for example the variance of the variable "" in Report.

49) What is a crosstab?
A crosstab displays data in rows and columns, as opposed to a table which displays data in columns only. Measures are typically placed in the body of a crosstab at the intersection of rows and columns.

50) What are input context and output contexts?
Desktop Intelligence defines an input context and an output context to determine the result of an aggregate calculation. A context is made up of one or more dimensions.
-The input context consists of one or more dimensions that go into the calculation.
-The output context consists of one or more dimensions that Determine the result of the calculation.
The syntax for input and output contexts is as follows:
=AggregateFunction( In ) In
The following example explains this in more detail.
Example: The following formula returns the minimum revenue per city per region:
=Min( In (,)) In
The input context consists of Region and City, while the output context is Region.

51) What are reset contexts?
You use a reset context in a cumulative aggregation, such as running total revenue per quarter. The reset context consists of one or more dimensions which reset the value of the calculation to zero each time a dimension value changes.

Example: Calculating running total revenue per country
You want to calculate running total revenue per country per year, and naturally you want the calculation to be reset for each country. When the value of Country changes, you want the calculation to begin at 0. To obtain this result, you display Country, Year and Revenue in a table, and apply a break on Country. You then add the cumulative aggregation =RunningSum(;)
in which you specify Country as the reset context.

The syntax is
=RunningAggregateFunction(;)
giving, for example =Sum(;;)
52) What are local variables?
A local variable is a named formula. Local variables appear in the list of variables in the Report Manager Data tab; you can use them to build tables, charts and crosstabs in the same way as you use variables returned by a data provider.

Why use local variables?
Variables have a number of advantages over formulas because there are some things you cannot do using formulas alone:
• You cannot apply alerters, filters, sorts and breaks on columns or rows containing formulas, but you can on those containing variables.
• You can include variables qualified as dimensions in drill hierarchies. Local variables are also useful because:
• You can re-use them easily in the same document.
• Formulas can be complex. You can use (and reuse) variables in formulas to simplify them. Because you can re-use variables, you don’t need to type the same formulas over and over again. Variables make complex formulas easier to decipher because they break the formulas up into manageable components.

53) What are functions?
Desktop Intelligence contains many built-in functions which greatly extend its capabilities. Functions are pre-defined formulas. A function consists of the function name followed by a pair of parentheses. The parentheses can contain arguments and arguments supply functions with values on which to operate. Arguments can be objects, constants or other functions.

54) Concatenation:

Combining data in a single cell:

Concatenation(character string, character string)

=Concatenation(,)

=Concatenation( ,(Concatenation(" " ,))) Name>)))

The syntax to achieve the same result as shown above using the & operator is:

=&" "&

The Concatenation() function and & operator allow you to combine charactertype data only. If you want to combine text or character-type data with numbers you must first convert the number into a character string. Otherwise, Desktop Intelligence displays the error message 'Incompatible data type'. You can convert a number to a character string using the FormatNumber() function.

In the same way, if you want to combine text with dates using the & operator or the Concatenation() function, you must first convert the date into a character string. Otherwise, Desktop Intelligence displays the error message 'Incompatible data type'. You can convert a date into a character string using the FormatDate() function.

Joins

Equi Join: An equi-join links two tables on common values in a column in table 1 with a column in table 2. The restriction conforms to the following syntax:
Table1.column_a = Table2.column_a
In a normalized database the columns used in an equi-join are usually the primary key from one table and the foreign key in the other
Theta Join: A theta join is a join that links tables based on a relationship other than equality between two columns. A theta join could use any operator other than the “equal” operator.
Outer Join: An outer join is a join that links two tables, one of which has rows that do not match those in the common column of the other table. You define an outer join by specifying which table is the outer table in the original equi-join. The outer table contains the column for which you want to return all values, even if they are unmatched.
Shortcut join:A shortcut join is a join that provides an alternative path between two tables.
Shortcut joins improve the performance of a query by not taking into account intermediate tables, and so shortening a normally longer join path.
Self restricting joins: A self restricting join is not really a join at all, but a self restriction on a single table. You can use a self restricting join to restrict the results returned by a table values using a fixed value.

Universe Related Questions

1) What is a Universe?
Universe is a semantic layer that isolates you from the complexities of the database. A universe maps to data in the database in everyday terms that describe your business situation. Universes are made up of classes and objects. For example, the objects in a human resources universe would be Names, Addresses, Salaries. Classes are logical groupings of objects. Each class has a meaningful name, such as Vacation (for objects pertaining to employee vacations). Each object maps to data in the database and enables you to retrieve data for your reports.

2) How do u export universe to repository?
You make a universe available to Web Intelligence users and other designers by exporting a universe to the repository. When you export a universe the universe is: Moved to the selected universe folder on the repository file system and Created in the Central Management System (CMS). Each time the universe is exported to the repository, the universe version in the CMS is updated. Exporting a universe to the repository involves following steps:
1. Select File > Export. The Export Universe dialog box appears.
2. Select a universe folder from the folder drop down list box. (or) Click the Browse button and select a universe folder in the folder browser.
3. If you want to lock the universe, double-click the universe name.
4. Click a group in the Groups list box. This is the user group that uses the exported universe.
5. Click a universe in the Universes list box. The Universes list box shows the names of the active universes.
6. If you want to export other universes that are not open, click the Add Universe button, and then use the browser to select the other universes.
7. Click

3) What is Strategies?
A strategy is a script that automatically extracts structural information from a database or flat file. Strategies have two principle roles:
• Automatic join and cardinality detection (Join strategies)
• Automatic class, object, and join creation (Objects and Joins strategies)
Strategies can be useful if you want to automate the detection and creation of structures in your universe based on the SQL structures in the database. There exits two types of strategies:
-Built in strategy is the Default strategy shipped with Designer. Built in strategies cannot be customized.
-External strategy: User defined script that contains the same type of information as a Built in strategy, but customized to optimize information retrieval from a database.

4) What is a derived table?
Derived tables are tables that you define in the universe schema. You create objects on them as you do with any other table. A derived table is defined by an SQL query at the universe level that can be used as a logical table in Designer. Derived tables have the following advantages:
• Reduced amount of data returned to the document for analysis.
• Reduced maintenance of database summary tables. Derived tables can, in some cases, replace statistical tables that hold results for complex calculations that are incorporated into the universe using aggregate awareness.
Derived tables are similar to database views, with the advantage that the SQL for a derived table can include prompts.
5) What is Join Path Problems?
A join path is a series of joins that a query can use to access data in the tables linked by the joins. Join path problems can arise from the limited way that lookup and fact tables are related in a relational database. The three major join path problems that you encounter when designing a schema are the following:
• Loops: Returns too few rows. Joins form multiple paths between lookup tables.
• Chasm traps: Returns too many rows. Many to one joins from two fact tables converge on a single lookup table. This type of join convergence can lead to a join path problem called a chasm trap.
• Fan traps: Returns too many rows. A one to many join links a table which is in turn linked by a one to many join. This type of fanning out of one to many joins can lead to a join path problem called a fan trap.

6) What is a Lookup Table?
A lookup (or dimension) table contains information associated with a particular entity or subject. For example, a lookup table can hold geographical information on customers such as their names, telephone numbers as well as the cities and countries in which they reside. In Designer, dimension and detail objects are typically derived from lookup tables.

7) What is a Fact Table?
A fact table contains statistical information about transactions. For example, it may contain figures such as Sales Revenue or Profit. In a universe, most but not all, measures are defined from fact tables.


8) What are Contexts?
Contexts are a collection of joins which provide a valid query path for Web Intelligence to generate SQL. Contexts are used in:
• Solving loops:
• Solving chasm traps.
• Assisting in some solutions for fan traps.
• Assisting in detecting incompatibility for objects using aggregate awareness.

9) How can we detect chasm trap?
Detect Contexts examines the many to one joins in the schema. It picks up the table that receives converging many to one joins and proposes contexts to separate the queries run on the table. This is the most effective way to ensure that your schema does not have a chasm trap.

10) How Do You Detect a Fan Trap?
You cannot automatically detect fan traps. You need to visually examine the direction of the cardinalities displayed in the table schema. If you have two tables that are referenced by measure objects and are joined in a series of many to one joins, then you may have a potential fan trap.
11) How does a context resolve a loop?
A context resolves a loop by defining a set of joins that specify one specific path through tables in a loop. It ensures that joins are not included from different paths within the same SQL query.

12) How Do You Resolve a chasm Trap?
To resolve a chasm trap you need to make two separate queries and then combine the results. Depending on the type of objects defined for the fact tables, and the type of end user environment, you can use the following methods to resolve a chasm trap:
• Create a context for each fact table. This solution works in all cases.
• Modify the SQL parameters for the universe so you can generate separate SQL queries for each measure. This solution only works for measure objects. It does not generate separate queries for dimension or detail objects.

13) How Do You Resolve a Fan Trap?
There are two ways to solve a fan trap problem.
• Create an alias for the table containing the initial aggregation, then use Detect Contexts (Tools > Detect Contexts) to detect and propose a context for the alias table and a context for the original table. This is the most effective way to solve the fan trap problem.
• Altering the SQL parameters for the universe. This only works for measure objects.

14) What is a microcube?
When you create a measure you must specify the way the aggregate function will be projected onto a report. Returned values for a measure object are aggregated at two levels of the query process:
• Query level. Data is aggregated using the inferred Select statement.
•Microcube Level: A microcube is a conceptual way to present the data returned by a query before it is projected onto a report. It represents the returned values held in memory by a Business Objects reporting product. The block level is the 2 dimensional report that a user creates with the returned data. A user can choose to use all, or only some of the data held in the microcube to create a report. A user can also do aggregate functions on the returned values in the microcube (local aggregation) to create new values on a report.

15) What are @Functions?
@Functions are special functions that provide more flexible methods for specifying the SQL for an object. @Functions are available in the Functions pane of the Edit Select box for an object. @Functions are very flexible. Depending on what you want to achieve, you can use any @function in either a Select statement, or a Where clause.

@Aggregate_Aware: The @Aggregate_Aware function allows an object to take advantage of tables containing summary data in the database. If your database contains summary tables and you are running queries that return aggregate data, it is quicker to run a Select statement on the columns that contain summary data rather than on the columns that contain fact or event data.

@Aggregate_Aware(sum(agg_table_1), ... sum(agg_table_n))


@Prompt: You can use the @Prompt function to create an interactive object. You use a @Prompt function in the Where clause for an object. It forces a user to enter a value for a restriction when that object is used in a query. When the user runs the query, a prompt box appears asking for a value to be entered. @Prompts are useful when you want to force a restriction in the inferred SQL but do not want to preset the value of the condition.

@Prompt(‘message’,‘type’,[lov],[MONOMULTI],[FREECONSTRAINED])

@Select: You can use the @Select function to re-use the Select statement of another object. When the @Select function is used in the Select statement of an object, it specifies the path of another object in the universe as a parameter of the @Select function, in the form Class_Name\Object_Name. This then acts as a pointer to the Select statement of the referenced object.

@Select(Classname\Objectname)

Note:
When you use @Select and @Where functions, one object now depends on another in the universe. You have created a new object dependency. When one object is deleted, the other object using the @Select or @Where function needs to be manually updated.

@Where: You can use the @Where function to re-use the Where clause of another object. When the @Where function is used in the Where clause of an object, it specifies the path of another object in the universe as a parameter of the @Where function, in the form Class_Name\Object_Name. This then acts as a pointer to the Where clause of the referenced object. Using the Where clause creates a dynamic link between two objects. When the Where clause of the original object is modified, the Where clause of the referencing object is automatically updated.

16) What is multidimensional analysis?
Multidimensional analysis is the analysis of dimension objects organized in meaningful hierarchies. Multidimensional analysis allows users to observe data from various viewpoints. This enables them to spot trends or exceptions in the data. A hierarchy is an ordered series of related dimensions. An example of a hierarchy is Geography, which may group dimensions such as Country, Region, and City.
In Web Intelligence you can use drill up or down to perform multi dimensional analysis.

17) What are external strategies?
An external strategy is an SQL script stored externally to the .UNV file, and structured so that it can be used by Designer to automate object or join creation, and table detection tasks in a universe. External strategies are stored in an external strategy file with the extension STG. External strategy files are in XML format. There is one for each supported RDBMS.

18) What is Aggregate Awareness?
Aggregate awareness is a term that describes the ability of a universe to make use of aggregate tables in a database. These are tables that contain pre-calculated data. You can use a function called @Aggregate_Aware in the Select statement for an object that directs a query to be run against aggregate tables rather than a table containing non aggregated data. Using aggregate tables speeds up the execution of queries, improving the performance of SQL transactions.

The reliability and usefulness of aggregate awareness in a universe depends on the accuracy of the aggregate tables. They must be refreshed at the same time as all fact tables. A universe that has one or more objects with alternative definitions based on aggregate tables is said to be “aggregate aware”. These definitions correspond to levels of aggregation. For example, an object called Profit can be aggregated by month, by quarter, or by year. These objects are called aggregate objects. Queries built from a universe using aggregate objects return information aggregated to the appropriate level at optimal speed.

@Aggregate_Aware(sum(agg_table_1), ... sum(agg_table_n))

19) What are incompatible objects?
You must now specify the incompatible objects for each aggregate table in the universe. The set of incompatible objects you specify determines which aggregate tables are disregarded during the generation of SQL. With respect to an aggregate table, an object is either compatible or incompatible. The rules for compatibility are as follows:
• When an object is at the same or higher level of aggregation as the table, it is compatible with the table.
• When an object is at a lower level of aggregation than the table (or if it is not at all related to the table), it is incompatible with the table.

20) What is a restriction set?
A restriction set is a named group of restrictions that apply to a universe. You can apply a restriction set to a selected group or user account for a universe. When users connect to a universe, the objects, rows, query types, and connection that they use in the universe are determined by their applied restriction set. You can create, edit, and delete a restriction set at any time once the universe has been exported to the CMS. You can create multiple restriction sets depending on the query needs of a target user group.

21) What are linked universes?
Linked universes are universes that share common components such as parameters, classes, objects, or joins. When you link two universes, one universe has the role of a core universe, the other a derived universe. When changes are made in the core universe, they are automatically propagated to the derived universes.

22) What is a core universe?
The core universe is a universe to which other universes are linked. It contains components that are common to the other universes linking to it. These universes are called derived universes. The core universe represents a re-usable library of components. A core universe can be a kernel or master universe depending on the way the core universe components are used in the derived universes.

23) What are derived universes?
A derived universe is a universe that contains a link to a core universe. The link allows the derived universe to share common components of the core universe:
• If the linked core universe is a kernel universe, then components can be added to the derived universe.
• If the linked core universe is a master universe, then the derived universe contains all the core universe components. Classes and objects are not added to the derived universe. They can be hidden in the derived universe depending on the user needs of the target audience.

24) How are universes optimized?
Query time can often be shortened by optimizing a universe. There are several ways you can optimize a universe:
• Optimizing the Array Fetch parameter in the Universe Parameters.
• Allocating a weight to each table.
• Using shortcut joins.
• Creating and using aggregate tables in your database.

Table weight is a measure of how many rows there are in a table. Lighter tables have less rows than heavier tables. By default BusinessObjects sorts the tables from the lighter to the heavier tables. The order in which tables are sorted at the database level depends on your database. For example, Sybase uses the same order as BusinessObjects, but Oracle uses the opposite order. The SQL will be optimized for most databases, but not for Oracle where the smallest table is put first in the sort order. So, if you are using an Oracle database, you can optimize the SQL by reversing the order that BusinessObjects sorts the tables. To do this you must change a parameter in the relevant PRM file of the database.

25) Different ways to link universes?
The following approaches when linking universes:
• Kernel approach
• Master approach
• Component approach

Kernel approach: With the kernel approach, one universe contains the core components. These are the components common in all universes. The derived universes that you create from this kernel universe contain these core components as well as their own specific components.

Master approach: The master approach is another way of organizing the common components of linked universes. The master universe holds all possible components. In the universes derived from the master, certain components are hidden depending on their relevance to the target users of the derived universe. The components visible in the derived universes are always a subset of the master universe. There are no new components added specific to the derived universe.

Component approach: The component approach involves merging two or more universes into one universe. The Sales universe below was created by merging two universes: Part 1 and Part

26) Explain about detail objects?
Dimensions are focus of analysis in a query. A dimension maps to one or more columns, functions in the database that are key to a query. Detail Objects provides descriptive data about a dimension. A detail is always attached to a dimension. It maps to one or more columns or functions in the database that provide detailed information related to a dimension. One cannot drill on details nor link on details when linking multiple data providers. While Customer ID would be a dimension, customer name, address, phone and soon should be details.

27) What is business objects repository?
Business Objects Repository:
Ø It is a semantic layer which stores the BO Users and their privileges.
Ø Repository means set of database tables, Business object store security information e.g user, group, access permission, user type etc. , universe information e.g. objects, classes, table name, column name, relationship etc and document information.
Ø Repository contains data accounts with three domains in each one type. You can create the repository anywhere. The security domain has the user security info and other domains address.


28) What are domains?
Domain is nothing but logical grouping of system tables. There are three domains usually in a basic setup they are Secure, Universe, Document. In 6.5 Universe are situated in one domain, Reports in one domain and Supervisor.


29) When is the Repository created?
In 5i/6i versions repository is created after installing the software, whereas in XI version a repository is created at the time of installation.

Specification for Universe Design document

The TRS document contains
-> Introduction ( overview, assumptions, acronyms, stakeholders)
-> Business Requirements (report requirements)
-> Data Sources
-> Universe Design (tables names and column names, classes, Naming conventions of objects, joins & relations, conditions to create at universe level)
->Security Design (security levels)