Different behaviour of F4 searchhelp BADI in Java Web and ABAP Web

Question

I implemented the Badi RSR_VARIABLE_F4_RESTRICT_BADI to restrict the values in the F4 search help of variables in a query.
When executing the query in ABAP Web or in the BEx Analyzer in Excel everything works fine.
The variable popup shows up and when I hit F4 on a characteristic it jumps in the code once and determines the values I want to see
BUT: When I execute the same query in Java Web runtime, the Badi is executed 6 (SIX) times before even displaying the variable screen Anyone has got an idea?
As I am determining the results in the search help depending on transactional data in a cube it's a big mess when executing this piece of code 6 times even if I do not need it at that stage.....
As a small workaround i created a constructor for the implemented class, as this is only called once at runtime, but this cannot be the solution.

Answer 1

Hi Stefan,
Have a read of this article:
http://sapdiary.com/index.php?option=com_content&view=article&id=12787:restricting-the-value-help-in-the-variables-screen-of-a-query&catid=81:data-services&Itemid=81
Also double check you are honouring the spirit of all the input parameters.
The symptom you describe occurred in the older solution using a customer exit (function module) when the "Variable Name" parameter was used incorrectly in the code, hence it did not behave as the API expected.
When you have it in debug mode and are looking at all the available variables in memory (global and local) do any of them change between the six calls?
Hope this helps,
John.