A query uses a variable with processing type 'Customer Exit', 'SAP Exit' or 'Authorizations' and you are facing one of the following problems:
- You run this query and after some navigation steps you call the variable screen (e.g. button 'Change Variable Values' in Bex Analyzer). In such a case, the system either processes the variables again (e.g. it calls the customer exit) or uses the values of the navigation state. You don't to know how you can control this.
- The query is embedded in a workbook (or used in a Query View). When the workbook is refreshed, the system has (again) two possibilities: it either can process the variables again or use the values which are stored in the workbook. It is unclear which query and workbook properties need to be set in order to get the desired behavior.
- The query is used in Analysis Office and changing prompts does not work as expected.
- All of the above seems to work only on initial execution, subsequent refresh does not meet expectations.
SAP BW 7.x and upwards
variable popup, java runtime, web template, prompt, change prompt, variable refresh, initial, Analysis Office , KBA , BW-BEX-OT-OLAP-VAR , Using Variables , BW-BEX-ET-WJR , BEx Web Java Runtime , BW-BEX-ET-WEB , BEx Web ABAP Runtime , BI-RA-AO-XLA , Excel Addin , BW4-AE-CORE-VAR , Variable (Runtime) , BW-BEX-ET-WB-7X , 7.x Analyzer Frontend , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.