Bex query designer - SAP variable customer user exit: value of a restricted characteristic

[Former Member]

SAP BW 7.0

I am writing a SAP variable via a customer user exit for the characteristic 0FISCPER (Fiscal Year Period). I would like to generalize the code for these user exit and that is why I need the value of the restriction of the characteristic 0FISCVARNT (Fiscal Year Variant) in the concerning query. In my query definition the characteristic 0FISCVARNT is restricted to the value "[K4] Calendar Year, 4 spec . periods", but I would like to read this value in my user exit in stead of hardcoding it.

Does anybody know i can read in my user exit the values of the characteristic restrictions (filter values) of the concerning query.

Does anybody knows if this is possible and how this can be implemented? I have already checked all the posts in sdn on de the subject "SAP variable user exit".

Kr, Guy Verschueren

[sander_vanwilligen · Accepted solution]

Hi Guy,

The business requirement behind it is not completely clear to me, these are typical variables to be entered on the variable pop-up screen.

The first important thing to know is at what point in time you are going to program the logic, e.g. I_STEP = 2. Please refer to SAP Note 492504 - Dependent customer exit-type variables for more information.

If the programming is called after the variable pop-up, then I would expect that the fiscal year variant is available in import parameter I_T_VAR_RANGE.

Please check out SAP Note 381709 - Tips and tricks for variables part iV for the restrictions with dynamically changeable variables.

Last but not least I would like to refer to a cool blog from Hendrik Brandes . It describes a framework on how to encapsulate your BEx variables.

If you have further questions, it would be helpful if you describe in further detail what is your business requirement, the context of the other variables and your programming approach.

Best regards,

Sander

[Former Member · Accepted solution]

Hi,

I have checked the mentioned links, and I have found the solution for this specific problem.

Though I still have a general question on this issue. I will try to explain it on the hand of an example:

In the query designer Filter tab > Characteristic restrictions, I am defining a variable (type customer exit) for the characteristic 0FISCPER. In the query designer Filter tab > Characteristic restrictions, I have also set the filter value for another characterisctic for example 0FM_AREA =  "FM01". My question is: can I read in the programming of the user exit the filter value for the other characterisctic 0FM_AREA of the query. So this is not another variable, but an independant filter value defined in the bex query designer.

Anybody any idea if this is possible at all.

Kind regards,

Guy Verschueren

[sander_vanwilligen · Accepted solution]

Hi Guy,

I would expect that only variable values, regardless of the variable type, are available in import parameter I_T_VAR_RANGE. I don't expect that you are able to access the other filter values such as 0FM_AREA in your example.

Unfortunately, I'm not able to verify it right now. I advise you to create a test query, put a break-point in the user exit and execute the query in the BW backend using t/code RSRT. In debugging mode you can examine internal tables such as I_T_VAR_RANGE. I guess this the only way to find the answer on your question.

Best regards,

Sander

[Former Member · Accepted solution]

Hi,

I had already checked this table I_T_VAR_RANGE, and there are indeed only the input parameters available. So I assume that the filter values of the concerned query are not available to be used in the user exit code of the input parameters.

Kr, Guy