I am not sure if I should be posting this here in WEBI or it should be under Universe design.
I have a table ‘Location’ having Location details.
Another table ‘Stock’ at the company level (aggregate), without location details. Both belong to different contexts and have no joins.
I have set Location table as incompatible with Objects from Stock Table and vice versa.
The Prevent Cartesian product is checked in the universe SQL parameters.
A report on DESKI with Location and Stock on the same Data provider gives a Cartesian product error. But the same report on WEBI does not display any error and brings back the Cartesian product result set.
Has anyone come across this issue or is there something I am doing wrong?
Import the universe. Go to File> parameters
Go to SQL Tab.
See if the “Allow selection of Multiple Context” option is checked. If not then enable it by checking it then save it then export the universe to the repository.
I have a similar issue. We have found that the warn option does not in fact warn about cartesian products. It failed to warn about this simple query, and a cartesian product was generated.
SELECT FIRST_NAME.FIRST_NAME ,
LAST_NAME.LAST_NAME
FROM
(
SELECT ‘BOB’ AS FIRST_NAME FROM DUAL
) FIRST_NAME,
(
SELECT ‘LAWSON’ AS LAST_NAME FROM DUAL
) LAST_NAME
So then I saw the post above which suggests setting the Multiple Paths option to Allow Selection of multiple contexts. This did not work either. Any other possible workarounds?
I’m not sure what you are trying to say by that query … I find the Query is not complete as I can see that it has a self join without a joining condition??
So there are chances for you to get a cartesian product.
Could you please explain your problem exactly? It’ll help me in understanding the problem better.
I was just trying to create a query that i knew for sure would generate a cartesian product, so i could test whether or not the warn option works. That query does in fact generate a cartesian product, and even though i have the warn option set, there is no warning. I am asking if anyone knows about any woarkarounds for this issue, which i believe is a known issue by SAP.
I have noticed the same issue as the OP - a report created in Deski gets a Cartesian Product warning, but the same report coded in Webi does not. Both reports use the same Universe. I am using XIr2.
I also see this issue. I tested everything using Deski and Query Panel from Designer… I assured my users they would be warned if they ever pull a cartesian. This is true in Deski, but in Webi there is no warning.
This is a big limitation to me, my specific situation does not allow for contexts or any other method of control over this.
Were you able resolve this issue? Could you please share? We are experiencing the same issue. Even though we have 50 joins, just one specific join was not recognized by BO.
Last weekend our Bo was upgraded to SP6 fix pack 1.
Its context issue, and in the context, we have 1:M and M:1 cardinality joins for the same table. after removed join from the context, cardinality issue disappeared.
This issue didn’t surface with SP6, but showed up in SP6. Some how SP6 doesn’t like both cardinality in same context.
(BOB member since 2008-04-02)
(BOB member since 2004-03-22)
(BOB member since 2005-08-11)