variable hierarchy display not changed (BEx analyzer)

[Former Member]

Hi

We have a BEx query, in which a drilldown characteristic is displayed as an hierarchy

Hierarchy display is active

Selected hierarchy:

Name - constant

Version - customer exit variable

Customer exit calculates version from manual input variable.

We need to view the report in BEx Analyzer.

When the query is opened, we select manual input variables and the hierarcy's version is set correctly.

The issue is that when we change manual input variables at runtime, the data is refreshed,

but hierarchy display is not changed. The selected hierarchy's version remains unchanged.

In order to change hierarchy display, we need to open characteristic properties and change the selected hierarchy manually

or we need to reopen the query and provide another manual input variables.

Our system version is 7.01 patch level 9

Is there any way to fix this problem

Or some workaroud?

Any help will be appreciated.

Thanks

[Former Member]

I think I found the answer

If I set property Refresh Variables - "refresh as designed" (on the "advanced" tab of drilldown characteristic properties), the problem is gone.

Related article:

OT-OLAP-VARIABLE-REFRESH - SAP NetWeaver Business Warehouse - SCN Wiki

[michael_devine]

Hi,

These Notes are missing in your system:

1753959

1745472

1751321

1717433

Regards,

Michael Devine

[Former Member]

Michael, thank you for reply.

But I don't see how these notes may help me with my problem.

1753959 - I don't get a short dump

1745472, 1751321 - system displays all queried nodes, the problem is that if I input another variable, hierarchy version variable is calculated via user-exit properly (I see it in ABAP debugger), but displayed hierarchy has version, which was set when I opened query initially.

1717433 - nodes are returned with non-empty result. I can see that data is refreshed, hierarchy version is requested correctly, but is displayed incorrectly. We can see, for example, new hierarchy leaves, but in "n/a" node.

I tried to run the same report on system with version 7.01, patch level 12 and get the same behaviour.

My problem is similar to that described in notes 993151, 957219, but our system patch level is already higher.