SAP Knowledge Base Article - Preview

3073231 - Concurrent lock violation when sending data


The concurrent lock violation is normally caused by multiple user trying to send data at the same time.

The dimension lock settings are typically configured by a BPC administrator after evaluation and testing of the system in a production environment. This is done in the BPC Admin client by selecting specific dimensions under the specific Model -> Concurrent Lock.

The behavior is explained on the Model Design page in the Administrator's Guide for SAP Business Planning and Consolidation, version for the Microsoft platform:

The choice of concurrent dimension is key. Business Planning and Consolidation locking is by at least one dimension: for example, a customer uses the Entity, Category, and Time for the other locking dimensions. The combination of Entity, Category, and Time is locked by Business Planning and Consolidation when data is sent. Business Planning and Consolidation locks are one of several kinds of locks in the system: SQL and Analysis Services also have locks. This section addresses Business Planning and Consolidation locks.


Budgeting and forecasting by function – Sales, Marketing, IT, Legal: A Function dimension is secured and used for this purpose. When a user chooses Send, this sends to all entities, so other users are locked out until that send ends. The sends queue fills up quickly and response time might increase from a minute to 10 or 20 minutes. The solution is to change the concurrent dimensions to the function dimension instead of the entity type dimension. Therefore the legal entity dimension is not considered in the lock (albeit still a secured dimension).



SAP Business Planning and Consolidation 10.1, version for Microsoft


KBA , EPM-BPC-MS-EXC , Excel , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.