what is a derived table in data warehousing?

A derived table is one that is created on-the-fly using the SELECT statement, and referenced just like a regular
table or view. Derived tables exist in memory and can only be referenced by the outer SELECT in which they are
created. A simple use of a derived table is shown here.
SELECT * FROM (SELECT * FROM Sales) AS a

The inner SELECT produces a derived table and replaces a regular table or view. The key thing to remember
when using derived tables is that you must always use an alias (e.g., AS a). The following shows the error
produced when the alias is omitted.
SELECT * FROM (SELECT * FROM Sales) -- Results -- Server: Msg 170, Level 15, State 1, Line 3 Line 3: Incorrect
syntax near ')'.

It is similar to views,it is mainly used to restrict the data. Derived tables are not real tables at the
Database level , but are the selection of few columns in the Table with some aggregations, specific to
the report.This feature is available in BO 6.5 and later versions.

[Universe - by going into Insert >> Derived Tables.Type the Query - parse it and the new table
inserted can be used to any type of join / Contexts etc in the Universe.

For Derived table, i am having one scenario.

My Database table is having following Column
-Empno
-Empname
-Managerno

my Report Requirement is like:

report should display Emp name and its corressponding manager name.

Based on this reqquirement, i need to design Universe.

My steps would be like this:

1.Looking at the requiement, i would go for Derived table, having name Manger.

Derived Table(Manager) would be having following syntax.

select distinct a.EmpNo,b.EmpName from Emp a,Emp b

where a.ManagerNo=b.EmpNo

2. Joining

2. Create class Manager and Object Manager Name, Source for this object would be
Derived_table.EmpName that is manager. EmpNo. Here EmpNo is coming from Derived table syntax.

Now my universe is ready.

As per the repoer requirement i can create report.

So Bottom line is Derived table plays a major role in this scenario.]

what is the difference between derived tables and a view? Which one gives better
performance ?
When a view is referenced the SELECT of the view is merged into the SELECT that refereces it, so it is
really the same thing. Of course views save a lot ofcoding , once written are less subject to errors, and can
have permissions assigned.but,when considering logical data independence, security and reusability as
important aspects, using views may be preferred over writing derived tables over and over again.
Views play all their rollups at database level. Derived Tables will fetch values into BO's microcube & then will
perform the rollup calculations, resulting more process time.
We can use The @Function (@variable,@Prompt) in the derived Table ,but we can't do the Same thing in the
Views.
I personally favor views over derived tables because they are faster than derived tables. hence improve query
performance, compared to derived tables.

[As earlier answer suggests, views follow vital security in complience with data design, managed by core
database-guys. So it makes sure, the view design is much better & compatible, which may not be if it is a
derived table, obviously not in all cases but still in certain scenarios.]
what is difference between custom hierarchy and report based hierarchy?

Report Based Hierarchy is a by default Hierarchy which Designer created in Designer by making a
Classes and Objects.

Custom Hierarchy is your choice just like you have Dimension year, Quarter, Month, week, Day and
you dont want to use that Sequence so you create Custom Hierarchy where you choose like Year and
Month and that will be your Custom Hierarchy for your report.Custom hierarchy is used in Scope of
Analysis.

By defining a scope of analysis during drilling you are specifying up to what level in the hirerachy do
you want to drill. if you set scope of analysis as 2, the data will be drilled to Year, quarter. 3 will
include month as well as so on.
Ex. Years, Quarter, Months : level as 1 - will get only year details.
: level as 2 - only year and quarter details.
[Hierarchy nothing but level comparing or Level of Analysis reports e.g Suppose you can Analysis
Product sales Top Level to Low level ( Year->Hal->Qtr-> Mon). Like this analysis we create own
Hierarchy in report level.
Custom hierarchy we can create in designer according our req.
By default one class having one hierarchy is called report hierarchy. Default hierarchies are based on
class and objects defin ed at database pane. A default hierarchy is created with a dimension in the
order in which they are presented in the class. ]

What is the chasm and fan traps in Business Objects

Chasm trap The Chasm trap occurs when two many to one joins converge on a single table. For
example a customer can place many orders/and or place many loans. Fan trap The Fan trap occurs
when a one to many join links a table which is in turn linked by another one to many join. For
example when you run a query that asks for the total orders by each order line, for a particular
customer, an incorrect result is returned as you are performing an aggregate function on the table at
the one end of the join, while still joining to the many end.

QAAWs and Live office

The main difference is Qaaws is convert the reports in to URLs and also improve the performance but
in case of Live Office it will degrades the performance.

I mean Qaaws is doesn't show the data it will come to run time itself only. but in Live Office we can
see the data and as we want we can do reports based on requirement.
Qaaws is nothing but a query as web service,when you are generating report in Qaaws at that time
one URL can generated that URL can send to the end user.Live office is nothing one of the connector
in Xcelsius by using live office u can connect different sources, or import from the different data
sources.
Qaaws : As you know Query As a Web Service. It is generate the URL for using in Dashboard to
access report data as a Data Source.
Live Office : Bessically is a technique how to connect Dashboard with your different data source

throughExcel . It can be Webi, Crystal, Excel etc... file.

How to create predefined filters in BO

Pre defined filters are created at the Universe level.In the Universe window,select the object,right
click ,select condition then enter the condition name and filter conditions.
when you have a restriction and you dont want to bound the variable or Object then you need to
make Predefine filter in Universe. For example. you have city Object and there is couple of people
using the same objects and they belong to different branch and manager wants to restrict the
data(city) where Manager belong too. Then you need to make a predefine filter and restrict the data
like managerCityID = CityID. 
In Universe Design you need to click on yellow funnel.
Dialogue window will appear define filter name and write the condition in Where Clause. 
Parse it 
Apply it.
Ok.

Explain about scorecards & dash boards in Business Objects

Dashboard is basically a Plate form where all the component represent the Progress. Dashboard is
contain summarized data and its can view good quality of presentation.

ScoreCard is a component which shows KPIs of the Company and give them better look in order to
have good decision. like Simple Example
I have built ScoreCard in Dashboard where I am using KPIs , Measure(Profit, Discount, Sale)
Associates with Year and Department. I am Using AERO with combination of Colors(red, Green,
Yellow), If Aeros is showing toward UP with Green Color then Department Performance is
Satisfactory, If Aeros
Insert Code: 
Add this to my Subscribed Questions (?) Email me when new answer is posted (?)
Send Reset.Is going Parallel with Yellow Color then department progress is so so and same like Aeros
is showing down word with Red color then Department is showing loss.

How do I synchronise Microcubes generated by different queries?

You can access the micro cube in the BO (reporter) -> Data -> view data.In order to synchronize
microcube from two data provider, just join the common dimensions from two microcubes .

micro cube is not a report or tool.it is structure located internally.when u run a query in DI or WI fiirst
time,retrive the data from the database.when u run the same query once again the data can be
attach with microcube.data retrival is fast.beacause every time retrive data from the database is a
long process. finaaly data retrival is very fast.u can fine when u run the big quiries

[Microcubes store data which is fetched from the Database as it is. This data can be exported to your
local file, by clicking the Export option.

When Query fired very first time it hits directly against the Database and then its fetch all data and
store into one MICROCUBE. MicroCube basically a temp place holder where all the Possible dimension
combinations is stored. So, whenever you drag and drop any dimension to report then it will fetch
data through the Microcube unless you add any new dimension in the query.]