cancel
Showing results for 
Search instead for 
Did you mean: 

BPC 11.1 Locking Concept

0 Kudos
330

Hello experts,

We have implemented BPC 11.1 Embedded Version to our client. The end users access the system to enter budget data by using 2 main dimension: GL Account and Cost Center. This combination is not the same for 2 users simultaneously.

But the change mode in the input form seem to be locked only by the Cost Center dimension. Two different users are not allowed to enter data regardless the fact that they are using different GL Accounts. This seems not to be right.

Does somebody know how to force the system to apply the locking concept using 2 dimensions instead of the Cost Center only?

Best Regards

Accepted Solutions (0)

Answers (3)

Answers (3)

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vasileios,

to remove lock relevant characteristics make locking less fine granular, so nothing has to be changed here. What about the information about the 'Locking Conflict'?

Regards,

Gregor

0 Kudos

Hello Gregor,

As you can see in the below picture everything is relevant for locking as you mentioned.

So, do you propose me to remove GL Account from Lock-Relevant? Our basic dimensions are the Cost Center and the GL Account. We want both of them to participate in the locking concept.

The system now seems to take into account only the Cost Center Dimension.

Best Regards,

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vasileios,

you can use transaction RSPLSE to check lock conflicts, there you can see the last recorded locking conflict on tab 'Locking Conflict'; this recording is application server specific. If you don't find a characteristic selection in the locking conflict tab this means that no restriction was used.

By default all characteristics are relevant for locking, maybe somebody 'GL Account' as a lock characteristic; you can find the lock characteristics in RSPLSE on the second tab, the setting is per planning base InfoProvider.

Regards,

Gregor