on 2015 Aug 26 10:00 AM
Hi SCN,
i am currently facing the problem of margins not being shown/calculated properly in crosstabs when embedded in a hierarchy. Thus, i would be really glad if anyone of you would be able to help me.
Framework:
Screenshot:
Problem description:
As can be seen in the screenshot above, the last column shows a calculated margin in percent. This margin is only calculated properly for the lowest dimension of the hierarchy (which is POS 02 - POS 03 - POS 04). The column second to the last is showing absolute values of the margin which are calculated correctly throughout the hierarchy.
At the last column i only get valid values for the margin of the lowest dimension within the hierarchy (called POS 04 in this case), values for higher dimensions in the hierarchy (e.g. POS 03 or POS 02) only return NOT_EXIST instead of the accumulated value. I think this problem occurs because Design Studio must be able to calculate the margin for a higher hierarchy based on the accumulated values of the underlying hierarchy. Hence, values for the margin calclation of a higher dimension have to be based on values which have to be calculated via Design Studio or the Universe in the background.
One thing that makes me curious about this issue is that we do not face this problem with BO Web Intelligence Reports. We already use this calculated margin measure at some reports which did not raise this hierarchy percentage issue. Moreover, the mentioned reports are using the same BO universe and query as a data source!
Does anyone know how to solve this issue or does anybody face the same problem?
Thanks a lot in advance for your help!!!
BR,
Markus
Request clarification before answering.
Hello Markus,
could you check in the Universe if these are "database delegated" measures ?
thanks
Ingo Hilgefort
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ingo,
> what you mean with "not the solution for the issue" ?
>>What i meant is that i thought that "delegation" should be the right configuration as there is only "min", "max", "sum", "average", "none" and "quantity" left. We already tried to set the aggregation/projection to "sum" and we were able to see some margin values instead of the NOT_EXIST. These values were calculated via a sum aggregation as expected. However, using sum, min, max etc. at margins leads to invalid values. For example, margins of 5% and 10% at the lowest level can't be summarized to 15% at the level above.
Anyway, thanks for the hint that Design Studio doesn't support delegation yet! I will have a look at "none" and "quantity" at the aggregation/projection because other remaining configurations (min, max, sum, avg) seem to be not suitable for my need (as already explained above).
BR,
Markus
Hello James,
we don't have an answer to this problem yet. In the meantime i discovered that there is already an idea under review concerning the total calculation of margins in crosstabs - see total of calculated measures : View Idea
Unfortunately, it seems like there is no proper solution for this problem available. Hopefully we will find a workaround soon. Without the correct calculation of total margins in percent our whole dashboard would become useless!
I don't get it why this is not supported in Design Studio yet as this must be a basic need for nearly everyone in a dashboard.
BR,
Markus
Hello markus,
Did you fin any solution to the above issue? We are also facing the same issue and it is a big blocker for our delivery.
Can you suggest any workaround that worked for you?
Thanks,
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
49 | |
6 | |
5 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.