Error in posting data to buffer: CL_RSPLS_DELTA_BUFFER_B unf Form READ-06-

Question

Hello,
I have a problem in executing functions in my planning folders which contain hierarchy variables in the filter of the function. 
Whenever I run a SAP standard function which has a hierarchy variable in the function filter, I get an error meesage.  The function copies the values, and when it tries to post them to the buffer I get an error message and the planning workbook gets logged off from SAP.
The message:
u2022Programm Fehler in Klasse     SAPMSSY1 Methode: UNCAUHGT_EXCEPTION
u2022Systemfehler in Programm      CL_RSPLS_DELTA_BUFFER_B unf Form READ-06-.
It seems to me that there is an error in SAP which involves reading the hierarchy in my filter, this leads to the above mentioned error when the system tries to post the data to the buffer.
System info:
SAP NetWeaver BI 7.0
We have patch level 20.
Help regarding this problem would be appreciated.
Regards,
Julian

Answer 1

Hello Gregor,
thanks for your response.  The error is in the planning workbook, the transfer button doesnt work, but Save does work.
The problem seems to be that I have a help query which runs before the plan query.  The help query has a Hierarchy user exit variable which the user cannot input values, this reads certain master data.  This is in the Static filter.  In the dynamic filter is an input hierarchy variable (same characteristic as the exit variable).  This receives the values from the user exit variable.  The input hierarchy variable is also in the Plan Query where I have the buffer error message.
If I take the Hierarchy variables out of the help query and put them in the plan query, then it works, no error message.
Conclusion:  it seems that the system has trouble posting data in the buffer if you have a hierarchy variable in the help query. (it works fine for non Hierarchy variables)  We debugged it, and the SAP program does not recoginize -06- assigend element in the program.
Is there a SAP note to correct this?  I found one that was very similar to my problem but it is old, for level 10.  We are on patch level 20.
Thanks for your help,
Julian