Table between universes

building reports desktopintelligence
1

Hi everyone,
on BO XI R2 I have to create a single table with objects deriving from two universes (univ_A, univ_B). I’ve created a query_A from univ_A and query_B from univ_B.
The problem is incompatiblity on some query_A objects with query_B objects… so I can’t drag and drop this objects on the table.

When the query derive from same universe the solution is sincronize some objects between queries… but now with different universe source, what can i do? the sinconization isn’t possible for some objects, so I can’t use this objects on my table.

The outer join may be a solution?

gulymin (BOB member since 2009-05-18)

2

you are not able to drag objects because objects are not linked.
Check dimensions objects are linked or not?if objects are not linked then link with other DP objects.

amitrathi1234 :india: (BOB member since 2007-10-15)

3

Hi amitra,
yes I know some objects are linked and I can drag and drop them on my table.
But some object can’t be linked because there isn’t corresponding objects on other query to link…

How I can insert on my table this unlinked objects?
Is outer join a possible solution?

gulymin (BOB member since 2009-05-18)

4

not amitra it’s Amit :slight_smile: …

then make those objects as detail object of some dimension objects…

And i think it’s not a matter of outer join.you are fetching data from two queryies.so you have to link dimension objects or make some objects as detail objects of dimension objects…

amitrathi1234 :india: (BOB member since 2007-10-15)

5

Ok Amit :wink:

I can link a object with other object only if there is corrisponding between type of data.
On my query_A I’ve object that can’t linked everyone!!

I try to set this dimension object to detail object but the same problem… can’t drag and drop on my table.
If I set this dimesion object to measure… I can drag and drop, but I don’t think that mainteining correct one-to-one relation among my datas

gulymin (BOB member since 2009-05-18)

6

Hi,

Linking a dimension object is possible even if the list of values for the two queries is different.

Lets say query a retrieves clients A,B,D,F and query b retrieves clients B,C,F. Then the ‘linked’ version retrieves A,B,C,D and F.
It will be the superset, so consistent with a full outer join.

Now if you have measures from query A they can go in the table block.
The lines that have data (in this case for client A,B,D and F) will show the measure value for that dimension value.

Same applies for the measures from query B (in this case lines for clients B,C and F will show values).

Other (unlinked) dimension objects coming from query a OR from query B can go in the block.
If they result in more lines, the measure value from the ‘opposite’ query will show the ‘total’,
the calculation is only available on the linked dimension value level.

If you have other dimension objects to add you can either turn them to measure (by putting a max() around them)
or you can make them a detail of the linked dimension object.
:!: Notice that in both cases it is only valid if you have just ONE value for each dimension value.

To clarify this another example;
if query a retrieved client (dim)/product (dim)/revenue (meas) and query b retrieved client (dim)/month(dim)/payment (meas),
putting client and both product and month in one table block would not make sense.
In this case, make the common dimension object(s) a section master and put the queries a and b in two separate table blocks.
:idea: They CAN be positioned next to each other so they look like one.

Hope this helps,
Marianne

marianne :netherlands: (BOB member since 2002-08-20)