BEx QD error: Hierarchy does not exist for InfoObject

BEx Query Designer may show a below error related to in consistent data in SAP BW hierarchy tables.

037(BRAIN) "The hierarchy &2 &3 &4 does not exist for InfoObject &1"

Issue typically lies within table RSRHIEDIR_OLAP. There might be an inconsistent entries in the table exit. Those entries can be fixed with a help of ABAP program RRHI_CORRECT_OSID_KTAB. 

In addition, depending on particular BW version root cause can be completely different. In case there is a hierarchy node variable that is used in the BEx Query and which is bound into hierarchy that does exist in development BW system but it doesn’t exit in target BW system (Q or P) the error may appear. Tricky part here is that simple re-assignment of the variable definition from non existing to existing hierarchy doesn’t help. Only way that solves the issue is to deletion of such hierarchy node variable and its recreation again from the scratch.

More information:

1900360 - BRAIN037 during query execution using a hierarchy with THJ

2177061 - Runtime Error RAISE_EXCEPTION in CL_RRHI_VIRT_HIER_SINGLETON - exception HIERARCHY_NOT_FOUND

2754938 - Enhancement of hierarchy correction report (rsrhiedir_olap)

2433852 - How to repair inconsistent Hierarchies

DLG_VARIABLE error while running BEx report in SAP Portal

While running BEx BE report in SAP portal environment I came across below error:

          Error in rendering root for dialog “DLG_VARIABLE”

The report runs fine while running it outside the portal in BEx Analyzer, Analysis for MS Office or via t-code RSRT. There are below SAP Notes available that fix this issue. However these SAP Notes are only relevant for SAP BW 7.5 SP06 version.

2465736 - Error: Error in rendering root for dialog “DLG_VARIABLE”

2357717 - Cannot convert field VALUE_NUMBER of type DECF34 to double

As in my case BW version was 7.4 so the Notes are not applicable. Root cause within one of BEx variables type of user exit used in the query which populated wrong value. 

Debugging of BEx’s text variables

I was recently dealing a lot with text variables in BEx’s queries. I found very useful an SDN’s how to paper written by SMP’s support consultant Ricardo de Azeredo Rosa. Ricardo is mentioning how to debug BEx text variables in particular the one based on replacement path. The gist of debugging is to catch ABAP code in FM called: RRSV_CHAVL_TO_VALUE_CONVERT. By this you can easily realize what is happening with your text variable. Why it is getting strange content (e.g. very famous # sign). It is very useful while dealing with variable offsets and other not very known features of BEx.

Enjoy reading of this how to paper.

As this is my first blog post in New Year 2013 I wish you all of my readers happy and prosperous new year MMXIII.

Something about BEx’s variables

Someone may say that everything was already said about BEx’s variables. In my opinion; truth is that there is always something new on this topic. Recently I came across useful SAP Notes discussing this topic. And guess what? I learned a lot from those notes. Therefore I’m sharing it here.

121291 - Tips and tricks for the use of variables; Discuss hints related to “shifted variables (offset based)”. Useful for year to year data, comparison of cumulative values (e.g. CO-PA data). Efficient Business Content variables: 0CYEAR - refers automatically to the current year; 0CYTCM - Current year to current month;

199014 - Tips & tricks with variables II; Describes behavior of following Business Content variables: 0FYTCFP - Current year to current fiscal month; 0FYTLFP - Current year to previous fiscal month

339476 - Tips & tricks for variables part III; Depicts a function to override input of variables (given on variable screen). This can be achieved by activating setting 'Can be changed in query navigation' in variable maintenance for characteristic variables.

381709 - Tips and tricks for variables part iV; Describes cases when variable values cannot be changed even it is dynamically changeable variable based on a compounded characteristic.

629697 - Variable exit: Fields SIGN and OPT; Discuss combinations of SIGN and OPT as components of internal table E_T_RANGE that are allowed for the different variable types.

492504 - Dependent customer exit-type variables; Discuss various values of I_STEP parameter which controls when BW: Enhancements for global variables in reporting (RSR00001) is called:

1 - Call directly before the variable is entered

2 - Call directly after the variable is entered. Only if same variable could not be filled for I_STEP = 1 and it is not ready for input.

3 - To check values of variables.

0 - Enhancement is not called from variable screen. Call can come from the authorization check or from the monitor.

PS: If you want to make sure that your variable is executed in particular I_STEP, put code similar to following:

IF I_STEP = 1.

        RAISE no_processing.

ENDIF.

Other posts on BE’x variable topic:

Checking BW’s BEx variables

Where to see code for Business Content SAP exit variable?

Checking BW’s BEx variables

While your SAP BW system is evolving over the years number of BEx’s variables is growing.  With new version of there are coming even new types of those variables or existing types are being enhanced.  Table (RSZGLOBV) which stores all the variables became huge. Even some entries in there become not up-to-date as rules for certain variables have changed. To keep this table consistent SAP introduced ABAP report. It is called SAP_GLOBV_CHECK. Basically it scans RSZGLOBV table; finds inconsistencies with variable rules and even corrects such entries. The report is available as of SP 26 for BW 7.0 and respective versions.

For detailed info on the report see following SAP Note:

1563856 - Check of the variable table RSZGLOBV