MDX statement error: System error in program CL_RSR_MDX_PERIODSTODATE and form FILL_MEMBER_TAB-03-

[former_member593565]

Hi Experts,

I have encountered very weird error while displaying data in BPC Virtual Provider, it returns error like below:

Look at the description, this error might related to Measures formula, but I never changed the formula, still SAP Standard. Also I do not have any new Measures, so no additional Formula.

In case formula Measure are needed, can be checked at below screenshot:

HR_Account is Account Dimension.

And I only have 1 hierarchy of Time Dimension, which can be checked at below screenshot

Hope I gave enough information and many thanks for any help.

[former_member186338]

Can you you explain step by step to reproduce your error?

[former_member186338]

I recommend upgrade to BW750 SP12 (there are some issues with SP11). I am currently on SP12

Also test TIME hierarchy on a fresh copy of ENVIRONMENTSHELL. In my case everything is working fine.

[former_member593565]

I will inform here the output once I have upgraded the SP.

Even the virtual provider of standard planning model in ENVIRONMENTSHELL is not working. I believe I never changed any dimension in ENVIRONMENTSHELL, always copy into new environment for development or testing purposes, so could be error from SAP, let see !

Many thanks for your help Vadim, really appreciate it !

[former_member186338]

TIMEID is still incorrect - has to be outside of sequence!

use something like: 10180100, 10190100,10200100...

Something like:

2018.GLOBAL BasePeriod: 001 Level: MONTH MonthNumber: 1 Period: JAN TimeID: 10180100 Year: 2018 Calendar: 2018.INQ

2018.INQ BasePeriod: 003 Level: QUARTER MonthNumber: 3 Period: Q1 TimeID: <empty> Year: 2018 Calendar: 2018.INY

2018.INY BasePeriod: 012 Level: YEAR MonthNumber: 12 Period: TOTAL TimeID: <empty> Year: 2018 Calendar: <empty>

Has to be done for ALL YYYY.GLOBAL members!

P.S. Still my question about version/SP is not answered

[former_member593565]

I have updated as per your suggestion, still get same error, and I can confirm to you that all YYYY.GLOBAL now have hierarchy already with 2 level as per your suggestion.

I think I have answered this question: Still my question about version/SP is not answered

BPC 10.1 BW 750 SP 11

[former_member186338]

Incorrect!

You have to create extra members for each YYYY.GLOBAL members with correct properties like in my sample:

YEAR property!

TIMEID property - use numbers outside of normal sequence

[former_member593565]

Hi Vadim,

I have updated as you suggested, but still have no luck, get same error. Below what I have done

[former_member593565]

Hi Vadim,

This is the view in hierarchy mode.

[former_member186338]

"Yes, I do have, this special members is used to stored driver value that being used for each month, is there any restriction? If I should put it under hierarchy what kind of member should I used as a hierarchy? or can be anything?" - this is the reason of your issue!

All members have to be part of 3 level time hierarchy.

Create extra parent members: For Year, For Quarter. Like here:

I have explained it already many times, please use search!

[former_member186338]

List view:

[former_member593565]

Hi Vadim,

I have updated Time as your suggested but still get same error while accessing data through Virtual Provider "MDX Statement error, ..", do you have any idea ?

[former_member186338]

BPC/BW version/SP?

Do you have time members outside of hierarchy - like special members for input?

[former_member593565]

Hi Vadim,

BPC 10.1, BW version/SP can check below

Yes, I do have, this special members is used to stored driver value that being used for each month, is there any restriction? If I should put it under hierarchy what kind of member should I used as a hierarchy? or can be anything?

Many Thanks and Kind Regards.

[former_member186338]

Yoki Winata

P.S. Please look on your post results - no images attached!