Lock problem in IP Web Model

[Former Member]

Hello, Experts;

I need some help with IP Web Models.

We've built a planning application with Integrated Planning, and we have troubles with autorization variable. We restrict access depending on 0PROFIT_CTR values, with a profit center node authorization variable. This variable is inside all our filters, and works fine in queries. We only see what we must see.

And this variable is ready for input, so users can restrict profit centers before entering web models. If a users is authorizated to a profit centers node (all profit centers below that node), he/she can restrict access to only one profit center (one among authorizated ones) so this way he/she only locks just that profit center.

This way, users can work simultaneously having the same authorizations.

Problem is with planning secuences. These planning secuences work with the same IP filters, including profit center autorization, but it seems that planning sequences are missing that previous restriction that users can do selecting only one profit center in previous selection screen. If 2 users with same autorization enter the same planning web model, first one locks the other.

But if they choose 2 different individual profit center before, they don't lock each other when they run planning web model. There's no lock message in web model, BUT IT APPEARS WHEN THEY REFRESH DATA OR SAVE.

Any one knows how can we get it? We need IP sequences to use that previous profit center selection that users do before entering IP application.

We're in serious trouble, please help

Best regards.

[Former Member]

Hi Luisma,

I would get that there is something wrong with the varialbe binding.

See [http://help.sap.com/saphelp_nw70/helpdata/EN/43/1c3da031b70701e10000000a422035/frameset.htm].

Could you please check the variable binding in the WAD?

Regards Matthias

[Former Member]

Hi Matthias;

First of all, thanks for your answer.

We've placed one SET_SELECTION_STATE_BY_BINDING command in web model properties, in "Action before rendering".

This is the way we try to fix that variable value before calling our planning sequences, but i'm not sure any more.

Could you tell me what sould we do to get variable binding???

Thanks a lot.

Luisma

[Former Member]

Hi Luisma,

the variables in the filter of the query and the variable for the planning function live in different "containter". This is the reason why variable binding is necessary. As far as I understood you correctly you are using a variable which gets some values (based on the authorizations) in the filter. Let this variable be VAR_QRY. Then you have another variable in the filter of the planning sequence. Let this variable be VAR_SEQ.

Now you need to bind variable VAR_QRY and VAR_SEQ. Using SET_SELECTION_STATE_BY_BINDING looks good, if your bind variable VAR_QRY to variable VAR_SEQ. Is your variable VAR_SEQ based on authorizations as well? I would try a normal variable (with multiple values) here and check if this works.

Hope this helps.

Matthias

[Former Member]

Hi, Matthias;

In fact, the variable is the same, ZPROF_AUTH. We have the same variable inside both filters: filters in queries and filters in planning sequences. Users can only execute planning functions regarding authorizated profit centers. Our planning sequences create a previous version for budget, but only for those authorizated profit centers, just that ones that each user see in the model.

In fact, that statement for binding shouldn't be necessary, because there's no diferent authorization variables. It's always the same, all the time.

Even that, we decided to set that statement for all data providers inside web model, but it doesn't work.

Could it be a matter of selecting variables properties in web model??? We mark "Display variable screen" and "Display same variables only once" in behaviour properties, but dismark the others.

I'm affraid i'm in a big mess...

[Former Member]

Hi,

you are using the same variable ZPROF_AUTH in both filters.

You wrote:

 In fact, that statement for binding shouldn't be necessary, because there's no diferent authorization variables. It's always the same, all the time.

.

But as I mentioned before the variables for the query and the variables for the sequence live in different container. They need to be connected using the variable binding. So you need to do the variable binding always; even if the variables are the same. The binding should be defined by the user always. Variable binding is not based on the name of the variable!!!

Could it be a matter of selecting variables properties in web model??? We mark "Display variable screen" and "Display same variables only once" in behaviour properties, but dismark the others. 

I do not think, that the above is the reason. I would focus on the variable binding.

What I would do in your case:

- create a new variable (not based on authorization) and include it in the filter for the planning sequence

- delete the variable ZPROF_AUTH from the filter of the planning sequence

- model the variable binding in the template to hand over the value of ZPROF_AUTH (query filter) to your new variable in the filter of the planning sequence

- unmark display screen ( because the user should not be able to change the contents of the new variable) (you may not want to do this right now, it can be done later as well)

- start your webtemplate and append &DEBUG=X to the url of the web template and press ENTER. This restarts the query and gives some debugging informations, e.g. the variable binding

Hope this helps

Matthias