CUSTOM MEASURE Not Working After Migration to SAP BPC 10.1 on HANA

[N1kh1l]

Hello Experts,

We had a Custom Mesure to calculate Inception to date and it was working fine on BPC 10 on Oracle. Recently we migrated to BPC 10.1 Standard on BW 7.5 SP 6 on HANA. We have enabled the SPRO Parameters required for HANA as well as ENABLE_HANA_MDX successfully.The Custom Measure now fails with error MDX Statement Error:"Internal Error: no result set"

The MEASURE Formula is as below.

SUM([%TIME%].[2017_DUMM]:[%TIME%].CURRENTMEMBER,[MEASURES].[/CPMB/SDATA])

Surprisingly If I just change the formula to below, it works

SUM([%TIME%].[2017_DUMM]:[%TIME%].[2060_DUMM],[MEASURES].[/CPMB/SDATA])

2017_DUMM and 2060_DUMM are both base members. The problem is with CURRENTMEMBERS.

Kindly Help if you have faced something similar.

Regards

Nikhil

[former_member186338 · Accepted solution]

Please show the screenshot of your TIME dimension administration. I suspect that it's configured incorrectly!

All base members have to be in 3 level structure

[N1kh1l · Accepted solution]

Hi Vadim,

Yes you are correct, I find a lot of time dimension dummy members which are orphan. I dont know how was it working in BPC 10 also which I just tested and it does. The customer has around 35 dummy base members for storing Yearly values and they dont want them to be included in Year.Total Nodes. Can I create one DUMMY.Total, DUMMY.QTR and bring all Year_DUMM under DUMMY.QTR like below

DUMMY.TOTAL

DUMMY.QTR

2017_DUMM

2018_DUMM

-

-

-2060_DUMM

Regards

Nikhil

[former_member186338 · Accepted solution]

Yes, create something like this and fill other properties correctly!

May be it's better to have:

2017.DTOTAL

2017.DQTR

2017_DUMM

2018.DTOTAL

2018.DQTR

2018_DUMM

[N1kh1l · Accepted solution]

Thanks Vadim,

I created the DUMMY.TOTAL, DUMMY.QTR and brought all dummy members under DUMMY.QTR. I see the properties for the Dummy members as below.

BASE_PERIOD - 012 for all dummy members.

MONTHNUM - 12 for all dummy members

TIMEID - 9999.2017, 9999.2018 for 2017_DUMM and 2018_DUMM and so on

YEAR - 2017, 2018 and so on for 2017_DUMM, 2018_DUMM

I am facing one problem now which is the dummy members (just 4 of them) are not appearing in correct sequence. I tried moving them up and down manually but that creates duplicate members (which looks like a bug). I fixed them by moving the wrong sequence members out of hierarchy and then including them again. Although this has fixed everything now but Just wanted to know if the properties are correctly maintained.

Nikhil

[former_member186338 · Accepted solution]

May be some issues with different YEAR property for DUMMY.TOTAL, DUMMY.QTR and for 2017_DUMM, 2018_DUMM, etc...

But may be it's OK 🙂