BPC 10.1 Embedded Locking Issues

[former_member238775]

I'm aware of the locking mechanism for the BPC 10.1 Embedded version, but am concerned with the correct usage. Our users are used to the locking mechanism from BPC 7.5 where the last in wins. We have several BEx queries where we have a large area of information can be planned on and the embedded functionality may cause a lot of concurrency issues.

Another issue that arises is due to the need to have authority checks on two of our info objects. This makes us have to have a variable in the characteristic restrictions with an authorization type AND a variable in default values that allows the user to input a smaller set of data. Since this piece is in the default values section, it is not added to the lock object.

We have turned locking off in order to keep testing for now, but are looking for solutions or best practices for our production system.

I would be interested in learning others' usage in queries, data slices, etc that may be helpful to us.

Thanks in advance!

[former_member603961]

Did you find any answer??

[cornelia_lezoch]

Hello Rakesh,

questions for planning should be tagged as "BW Planning".

the logic of how to define lock characteristics should be:

1. what is authorization relevant - put it into filter an define it as lock relevant
2. what is used in filter and generally defineing "planning round" define as lock relevant (usually version, year, scenario)
3. whatever devides user resposibilities - where several users what to work at the same time but for different data sets - define ist as lock relevant.

regards

Cornelia