on 06-25-2009 11:03 AM
Hi specialists,
I've got the following problem:
We've got a mixed BEx-client-environment with user using BEx 3.5 as well as BEx 7.x.
So I create workbooks with BEx-Analyzer 3.5 and transport them from the developement-system to the production-system.
The problem: Obviously the variable-selection that I used at last in the developement-system is saved in the workbook. So let's say I tested the query in the dev-system with "DE01" as value for the company_code on the variable screen, then this value is saved in the workbook and transported to the prod-system.
In the production-system the value is not replaced anymore by the users permitted company-code values (the variable is based on the users permissions), but the user has to remove this "DE01" manually and has to enter all his personal company-codes manually - which makes the permission-bases-variable senseless.
Even if I clear all variable-values in the developement system (which is not possible for mandatory variables) prior to saving the workbook, the issue is the same: This time empty fields are presented in the prod-system, but the permission-based-variable isn't set correctly - the field stays empty (=exactly as it was when I saved the workbook in the dev-system).
So, how can I clear the variable-screen-values before I save and transport the workbook to the prod-system? The only way (and it is certainly not the recommended one) i found: If I cancel the query at once after having confirmed the variable-screen and save/transport that query, then the variables seem to be really empty and the permission-based variables in the prod-system work.
Hi there,
Did you tried workbook settings under the tab Variables unmarked the tick for "Process Variables on Resfresh"?
I did not tried myself, but might be a good try out.
Diogo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have mandatory field? If yes, it is hard to run the workbook without putting any valid value.
I usually put # in the mandatory field and keeping optional varaible open and run the report. Ideally I should not get any result and even if I do, i delete the result from the workbook and save the workbook.
So, when user run the report in production, they will have to remove # for mandatory variables and put thier value.
But there is no way by which you set the value of all the mandatory selection fields BLANK..
- Danny
So, when user run the report in production, they will have to remove # for mandatory variables and put thier value.
Mh - most of our reports have variables for "company_code","sales_org" (for example).
Normaly this fields are not mandatory but optional.
But: Normaly if the user opens such a variable-screen (for the first time) the company_code and sales_org are preset according to the users permissions for this chars.
If I follow your description, then the variable-screen would open with "#" or "" - but wouldn't be replaced by the user's permitted values anymore 😕 - hence the phone rings because the users didn't manage to restrict the variables to their permitted values.
Maybe this is a case for an oss-message for the area BW-BEX-ET-USAB Userability Frontend....
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.