what is concurrent lock

[Former Member]

Can anyone educate me on the topic of concurrent lock.

Each Application seems to have a node for concurrent lock settings which can be seen in outlooksoft admin.

My guess. It determines the dimensions relevant for locking for an App.

Regards

[Former Member]

Thanks Alwin. Big help. That was my initial guess to but can't see how exactly the performance is compromised. Thanks again.

[Former Member]

Performance is the main problem when you set the concurrent lock setting for all dimension. Mostly when you send data, you will sent data for several accounts at the same time. This must all be checked, stored en cleared by the sendgoverner service of BPC. And in fact this is not necessary, when a user is entering data for a specific entity, in most cases this is the only user entering the data for this entity.

Alwin

[Former Member]

Hi,

I've read in the BPC Admin Guide that "data submission is based on a first come first serve basis". So the concurrent lock settings actually prevents concurrent data submission conflicts between users working on the same data intersection.

The Entity, Time, and Category dimensions are locked by default.

Here's my question: What is the disadvantage of locking ALL the dimensions on the concurrent lock settings of a certain application?

[JHattendorf]

Concurrent locks prevent multiple users from sending data to the same intersection at the same time. For example, defining concurrent lock to include Entity, Category and Time would prevent two users from modifying data for the same entity (Local Office 1) for the same category of data (e.g. Budget) in the same period of time (e.g. 2009.JAN).

It's a database setting that can be managed in the Admin tool -- added in v5. One of the notes in this forum regarding v7 indicates that it will be managed behind the scenes in v7.

J

--- Oops... didn't see Alwin's response when I started the reply.

Edited by: Jeff Hattendorf (Akili) on Jul 15, 2008 4:59 PM

[Former Member]

Make sense.

In SAP world we can specify infoObjects that are relevant for locking meaning one person can only modify the intersection of its value. This can be done thru rsplse.This was my thought process when I asked the question.

Workstatus looks like Data slices in SAP world.

[Former Member]

wrong guess

the locking for applications is done via workstatus.

The concurrent locking setting is to prevent the possibilitie that two (or more) users are changing the data for the same intersections.

For example: if the concurrent lock settings are set to entity,time,category (which is the default and in almost all cases the right setting), if you change the data for a certain intersection, the used intersection will be locked when records are processed and written back to the database. normally all of this will be done within a second.

If for example you have an extra costcenter dimension in your application and several different users are entering data for different costcenters but for only 1 entity, it may be usefull to add the costcenter dimension to the concurrent lock settings, in this case you want users to be able to sent data for 1 entity at the same time.

Hope this helps,

Alwin