I have a unique scenario in BO hierarchy. I have table A, table B and table C which are in parent child relationships like A B C. Now the relationships are stored in table D.
In most of the scenarios, we have one to one parent child relation in tables A,B and C with table D, while in same scenario : 1 value from table A can have more than 1 values in table B and these leads to incorrect results. The data in database is like that.
Is there any possible way to avoid these double count in business objects. I am using BO XI 3.1
A) Use a COUNT DISTANICT with Database Delegated
B) Review your hierarchy: if you are storing parent nodes and child nodes with separate foreign keys in your fact table you will get an incorrect inflation of your facts. In other words your data structure SHOULD look like this:
Parent node --< Child nodes Level 1 --< child nodes level 2 --< … --< Leaf nodes --< FACT table
No key from the parent node should be found in your fact table, only the keys of leaves should be found in your fact table.