Issue with Local Member

Question

Hi BPC Experts,
We have migrated our environment from BPC 7.5 to BPC 10. We have also migrated our reports from EVDRE to EPM.
Now we have few reports where local members are used.
The report is buil up like this -
Entity in columns and account in rows.
We have created blocks in the report to show the grouping which is general while creating balance sheet or P&L report.
Local members are created to show the total at the bottom under each group. For ex.,
Cash account is a node we have in report.
Structure in account dimension -
Cash
     A_100
          A_123
          A_124
     B_100
          B_123
          B_124
     C_100
          C_123
          C_124
In report, we have -
CASH
Current Assets
Investments
Fixed Assets
Total Assets - =round(sum(all four above),-3)
Now the total asset is local member here.
When we drill down on CASH, it generates additional members in the report (as shown above). The local member does not go down on drill down.
When we drill down on any parent node, we expect that local member should also get drilled down and show the correct value. However, this is not happening.
Could you please share some light on how to make local members dynamic with drill down on parent node?
We are on SP14 patch with .Net4.
Best Regards,
Ashwin.

Answer 1

Hi Vadim,
We managed to get the local member in our report, however, when we drill down on the last member, the local member stays at its current position and does not follow the drill down sequence.
The members in the row axis of the report are hardcoded and column axis is dynamic. We also have few blank lines in the report.
Let me explain you that with screenshots.
We have 3 dimensions in rows and 1 dimension in column.
This is how the report looks like with ABC being a local member.
This is how our local member is set up.
When we drill down on member A_110, the local member does get drill down, but the CASH and R_All members get attached to this local member. This is how report looks like after drill down.
We need to have atleast 5-6 local members in the report.
How do we overcome this problem?
We tried inserting blank member, however, the results are the same after drill down.
Please help.
Best Regards,
Ashwin.