BusinessObjects Board

Hard and fast rules for resolving loops on an OLTP universe

Hi,

I know that we have some hard-n-fast rules to resolve loops universe from a data warehousing system, such as : use aliases, when using the same table over and over again, but for different purposes and use contexts for each fact table.

But are there any thumb rules for resolving loops against an OLTP system?
Any insights into this would be greatly helpful to me.

Thanks!
Lalitha


lalitha (BOB member since 2006-05-05)

The rules don’t change. Use contexts for paths and aliases for purposes. Cardinality settings on joins often indicate which situation you’re looking at.


Dave Rathbun :us: (BOB member since 2002-06-06)

Can you please elaborate?

I know, this has been discussed a number of times but this is one topic that’s been confusing, atleast to me.Sorry for all the repetition.

Thanks!
Lalitha


lalitha (BOB member since 2006-05-05)

Did you read the “sticky” topic at the top of this forum?


Dave Rathbun :us: (BOB member since 2002-06-06)

I read, Dave… It talks about the cardinalities and how they help us detect the Chasm and Fan traps. But how do they help in fixing the loops?
Please let me know if i’m missing anything here ofcourse i’m :))

Thanks!
Lalitha


lalitha (BOB member since 2006-05-05)

I’m going to suggest you post a question in that sticky topic so we keep all of the context/alias/loop discussions in one place. :slight_smile:


Dave Rathbun :us: (BOB member since 2002-06-06)