on 02-06-2018 3:47 PM
I have time depending hierarchies set up for the entity dimension. I have a EPM report where the time periods are listed in the columns and account in the rows. The entity is selected based on the context. I have 3 ranges of time periods, with each their own key date.
So I split the report in three, each of them now sharing the row and page axis and each with their periods in the columns and their own key date.
This does not work. The differences in the entity time dimension are not reflected over time.
When I now move the entity to the row axis besides the account dimension, it is still not working.
If I now expand on the entity member, showing the children (and the parent), the 3 reports show the correct data for all periods.
If I now bring the organization to the page axis, containing the children (as a string of members) of the originally selected parent it still works.
And (of course) now removing the children and getting back the original parent, the data is not correct again.
My question, is this expected behavior? Does TDH only make sense when the dimension is positioned in rows/columns? We are on SAP BPC NW 10.1
Hi Vadim, Its now investigated by SAP.
In your opinion, should it work (as being logical) or have you seen it work?
kind regards
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It does not make any difference if
I put the Parent entity in the rows (shared) as shown in my cases or
in the columns along the time periods or
in one (shared) Page sheet or
with separate Page sheets or .
even without shared rows (so 2 separate reports on one sheet).
I tried them all.
kind regards
Tim
Separate worksheet or workbook does not make a difference.
I tested a bit further.
Three situations: WB1 with Keydate 1, WB2 with Keydate 2 and WB3 with both (totally not shared)
I tried to change the keydate manually for each report. Nothing happens.
Then I changed the context keydate, even if non of the reports referenced to it!
At first nothing happens, but then after a few minutes I refreshed again and in all 3 workbooks the refresh gave me the data belonging to the context key date (whatever the used key date of the report itself)!! So still useless 🙂
I retried this a couple of times and every time the same. With a delay of 2-3 minutes the data changed!
(The development database is not really big, and there is almost no data on this entity in the two time periods).
So my preliminary 'conclusions'.
1. In case a single parent entity is used in one of the three axis, the report does not seem to 'recognize' the TDH-mechanism and uses the EPM-keydate. Ofcourse this could be as developed, but without liking it.
2. The delay could be something in our BW- set up
For example increase the LimitTDHCountInCache value. I am not sure if that would help, as
although we have in fact 6 TD-hierarchies in the entity dimension, during the above process I switched only between 2 keydates all the time. But any suggestions are welcome
It's better to illustrate your question with screenshots - to be sure that I understand you correctly.
For sure the axis with TDH dimension can't be shared!
You can use 3 individual page axis with Excel formula relations...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.