Answer Posted / rahul tandon

Loop is a situation in the BO universe design process. A
circular path of joins is formed between the tables. The
SQL queries are not able to interpret the joins; this
results in the wrong results from the queries; often less
records are retrieved than the actual number of records.

A loop situation can be resolved by Aliases and Contexts.
Make sure to break the joins(circular path) by aliasing the
table(dimension table) which has 1n's coming out of it from
both the end. The path then gets broken and ends as two
different path, one ending at the original dimension table
and the other at the aliased table(of that dimension). Both
of the paths now convey a differnt business case scenario
and depending upon the scenario a particlar path(query has
to be fired).

Explain the difference between union and group?

1094

---

Is there any tool that can compare two unvs / two rpts , built using bo 5.1 / bo 6.5?

976

---

explain in detail about type 3?

1009

---

What is a fantrap in business objects?

1162

---

What is the profile and package?

2283

---

Which versions are used in the bo dashboard work?

1043

---

What are the steps to do to use alerts in bo?

1390

---

What we need to discuss with designer before starting the universe designing.

2243

---

How much data hold in one universe 336 can any one explain about core dimension, balanced dimension, and dirty dimension?

1127

---

Differences between business objects and web intelligence reports?

1206

---

i want my connection to be dynamic. How can I make it. I mean the username and password should be dynamic. How?

2096

---

Can we configure two instances of CMS pointing to two different CMS system databases?

2021

---

Explain what are the measure objects?

978

---

Explain and tell me about a situation where your analysis of a problem was deemed to be incorrect? What would you have done differently?

1257

---

What is the difference between business requirement document and use case document.

1003

---