Member Selector - Dimension Property Options

[Former Member]

Hi All

We are seeking a method to manipulate the row definition, inner dimension member based on two scenarios: Please see the example and scenarios below:

What we have tried:

*By default, we have the fund member selector linked to the first dimension (account) property (FUND). This produces the correct results for scenario 2 above.

*We have a EPMDIMENSIONOVERRIDE for the fund. This produces the correct results for scenario 1 above.

*We have used EPMOLAPMEMBERO to reference the local member value. However this results in multiple funds being displayed for each account. 

What we need:

We need a method to be able to toggle between scenarios 1 & 2, with the row defintion being dynamically updated (after refresh).

Is there any API or EPM formula that allows the member selector, dimension property to be overriden/manipulated?

Any other ideas?

Any assistance much appreciated

Glen

[former_member186338 · Accepted solution]

For scenario 1 use EPMDIMENSIONOVERRIDE for the ACCOUNT with condition FUND=6100. Scenario 2 is not clear...

In general if you have FUND linked to the account property - don't override fund, use criteria for ACCOUNT!

Vadim

[Former Member · Accepted solution]

Hi Vadim,

Thanks for the response.

Based on a certain condition we want to apply Scenario 1 or Scenario 2 accordingly.

Let's say the condition is Program vs. Non-Program (comes from WBS Dimension).

If the selected WBS is Program then Scenario 1 should be applied. i.e. apply the EPMDimensionOverride

If the selected WBS is Non-Program then Scenario 2 should be applied. i.e. Use the Dimension Property Link from the ACCOUNT dimension. (i.e. ACCOUNT.FUND) and de-activate the EPMDimensionOverride.

We couldn't figure if there is a EPM Formula or an API for apply the Scenario 2, i.e. Linking the FUND display to the FUND Property on the ACCOUNT dimension, so that we can only apply it conditionally and not always.

Thanks,

[former_member186338 · Accepted solution]

Still not clear!

How do you want to select required ACCOUNT members in scenario 2?

First scenario will work fine with dimension override on ACCOUNT to select only accounts with specific FUND in property.

In both scenarios the property link will be in place!

[Former Member · Accepted solution]

Dear Vadim,

Agree that first scenario works fine with Dimension Override but the Second Scenario (which is the Property Link) will be erased by the first Scenario (which is Dimension Override) after it takes place.

For any given report try using a Property Link for a given dimension (from the Report Editor) and then use Dimension Override on the same dimension, you will see from the Report Editor that the Property link settings will be wiped out by what ever you are doing from the Dimension Override formula.

Cheers!

[former_member186338 · Accepted solution]

"Override on the same dimension" - Dear Sreekar, I have written in 2 posts that IT'S NOT THE SAME DIMENSION!!! Override has to be used on the dimension WITH property! Is it clear?

[Former Member · Accepted solution]

Dear Vadim,

Sorry for not being clear. I've prepared an example in the below screen shot.

Hope it's clear now.

Thanks,

[former_member186338 · Accepted solution]

And the ACCOUNT member list is the same for both scenarios? Still no answer for this question!

If yes - then it's impossible to switch between scenarios! No way!

[Former Member · Accepted solution]

Yes, the ACCOUNT member list remains the same for both scenarios.

The FUND values should change according to a certain (ex. WBS) selection.

Thanks for confirming that it's impossible so we can explore other resorts.

But is there any way that we can configure the 'Dim Property Link' through EPM formulas or APIs (instead of doing it from Report Editor) ??

[former_member186338 · Accepted solution]

There is no EPM formula that will restore property link... For VBA - look on 42.4.5.3 AddMemberToRowAxis with relation parameter Property = 12 or Member Property = 15 but the syntax is not documented...

Vadim

[Former Member · Accepted solution]

Hi Vadim,

Tried AddMemberToRowAxis API with "Property = 12" and "MemberProperty = 15" with various combination of syntaxes but with no luck.

Also raised it with SAP and they came back saying "Property = 12" and "MemberProperty = 15" are not supported yet. Said that they will be contacting their document team and get it removed from the EPM User guide document .. which is a shame.

Thanks for your help anyway!