Business Objects Interview Questions with Answers

3/15/2010 No Comment

Collection of Business Objects Interview Questions.

Explain about Lookup and Fact Tables in Business Objects?
Answer : Lookup tables: A lookup or a dimension table contains information associated with a particular entity or subject.It is the table where the textual descriptions of the business are stored. A dimension table is one of a set of comparison tables to a fact table

Fact Tables: A fact table contains statistical information about transactions, numerical measurements of the business. As such, he fact table contains the KPI of the Business.

Define Loops. Can you tell me how to detect loops? How can you go about resolving loops? 

Answer : In a RDBMS, a loop occurs when joins form multiple paths between lookup tables.
Loops can be detected by the following.
  • Run the Check Integrity function, which indicates the existence of any loops.
  • Select the Detect Loops command from the Tools menu.
Loops can be resolved by creating aliases and contexts.

What do you mean by an Alias?
Answer : In SQL an alias is an alternative name for a table. In DESIGNER, an alias is just a pointer to another table. The purpose of aliases is to resolve structural issues in a database arising from SQL limitations. Whenever possible you should use an alias instead of a context.

What do you mean by a context in Business Object?

Answer : Context is a method by which Designer can decide which path to choose when more than one path is possible from one table to another in the universe.Generally used transactional database with multiple Fact tables.

The disadvantage of using a context is given below.
Answer : When you use a context, you expose the Business Objects end user to the database structure. They are forced to decide which context they want to use to run their query. The role of the universe is to shield end users from the database structure, so they do not have to make such decisions.

Explain what do you mean by Fan trap and Chasm Trap and how will you resolve it?
Answer : A Fan Trap occurs when a “One to Many” (1:M) join links a table which is in turn linked by another “One to Many” (1:M) join.
There are two ways to solve Fan trap as cited below.

  • By Creating an alias and applying aggregate awareness function. This is the most effective way to solve the Fan trap problem.
  • By Using Multiple SQL statements for each measure.
A Chasm Trap occurs when two “Many to one” (M:1) joins from two Fact tables converge on a single Lookup table.

There are three ways to solve a Chasm trap

  • By creating a Context.
  • By creating multiple universes (WEBINTELLIGENCE only).
  • By using Multiple SQL statements for each measure
When will you use multiple universes in Business Objects?
Answer : You can use multiple universes to solve a Chasm trap in a WEBINTELLIGENCE universe when
Multiple SQL for Measures cannot be used as there are dimension objects defined for one or both of the fact tables.

Under what circumstances you will not use multiple universes?
Answer : Please ensure that you will not use multiple universes in the following situations cited below

  • In  a Full client BUSINESSOBJECTS universes
  • When a WEBINTELLIGENCE universe does not contain dimension objects defined for any of the fact tables.
Related Posts

No comments :


Aired | The content is copyrighted and may not be reproduced on other websites. | Copyright © 2009-2016 | All Rights Reserved 2016

Contact Us | About Us | Privacy Policy and Disclaimer