Data locking due to buffer

[Former Member]

Hi,

Would anyone has a workaround for the following situation (on the Web)when 2 users access the same layout?

The layout has a variable on cost center included in its planning level.

User1 selects cost center A, the layout is opened. User1, then selects cost center B, the layout is refreshed.

User 2 selects cost center A, the system cannot open the layout as User 1 has locked it (even if he moved to cost center B).

I know this is due to the buffer but is there a command I could include somewhere to have the buffer emptied when one user switch to a new cost center to unlock the previous one ?

Thanks

[Former Member · Accepted solution]

Hello David

Have you received my mail. By the way now I can connect.

See OSS note 635244.

Regards

Mike

[Former Member · Accepted solution]

Yes thanks.

The note indicates how to remove all the locks which we do not want in our production system. It also includes a way to reset the buffer when saving in BPS0. I would very much like to find a way to reset the buffer on the web either automatically when changing a variable value or when saving data.

The reasons for the lock can be understood from a technical point of view but is hard to explain from a user point of view (the lock should be on what is really selected).

Thanks

[Former Member · Accepted solution]

Hi David,

Did you look at note 720265. It explains how to make an entry in the UPC_DARK2 (table). You need to add WEB_REFRESH_ON_CHANGE, and value X into this table.

Then go to your web interface. You will see an option in your variabe (cost centre variable?) subcomponent to "Update on Change". In this option, you can choose to update other variable etc (or use * for all).

Maybe this will sort out your problem. If not, I would recommend having 2 variables, 1 for the user to select a cost centre, and a 2nd variable - which is updated from the 1st variable - which sits in your layouts and controls what is seen in the layout.

Good luck,

Regards,

Rael

[Former Member · Accepted solution]

Hi,

I already tried that and it is not working. Even if the 2nd variable is refreshed, the original selection is still included in the lock.

Thanks

[former_member93896 · Accepted solution]

Hello David,

the locking scenario is just how BPS works. The proper way to release locks is to exit.

The buffer has been implemented for specific reasons and works quite well in most situations. It avoids multiple database reads and therefore provides good performance. The assumption is that no two people work on the same object at the same time. It is no different than two users trying to open and change the same Word document at the same time. Only one can win and for the other to make a change, the winner has to close the document. I think if you explain it that way to users, they will understand.

From a design point of view, I suggest to build in read-only layouts that users can get into even if someone else is working on the data.

Also re-examine the business process. How often does it really happen that two people need to change the same data at the same time? Is it really the same data? Maybe it is more like another round of planning. Then you should setup a version concept to separate the data properly.

Hope this helps,

Marc

SAP NetWeaver RIG