one master table with multiple detail-tables (lookup)

[irinag]

I just started playing with bus objects and already have BIG problem :

in my universe I included all tables that will be used for reports plus all possible joints.

I hoped that depending on tables used for particular document/report my query will be constructed optimal way.

But it does not work this way and I am getting: "Incompatible combination of objects(QP004)"

So how would I create a report that use same master (ex lookup) few times in one query? I can write my own SQL to do this, but can I do this in universe without creating additional views?

appreciate any help
irina

 

[ATP]

Incompatible combination of objects(QP004) usually means you have not got a "Context" for the objects you have selected.

I assume you've used contexts to remove any loops from the structure.

If you select objects that do not fall into one of the contexts the query will fail as Business Objects does not know which way to go.

This is going to be difficult to explain but I'll give it a go ....

You can get round this in a few ways but it depends on the data structure and what you want to report on:

1) Make a context for each path you require
e.g. One for receipt (Item, Receipts, other_attributes) and invoices (Items, Invoices Other_attributes)

Set the option in business objects to product a query per context. This will produce 2 queries of objects from receipts and invoices are selected.


2) Duplicate the master tables with Alias tables so removing the loop.

3) Create a big detail view on the database with all the required object (create a view or populate a WIDE table (not space efficient but quick for reporting ... space is cheep anyway!)

Hope this is of some help but this really depends on your circumstances on how you would do this.

ATP

p.s. watch out for Many to Manys, (fan and chasm traps!) they can take some sorting!

p.p.s. The more universes you build the easier it gets as your brain starts to think more globally on how the universe will be used and not to how you would write a specific report.