Ansicht
Dokumentation

SIMG_CFMENUCX01_RU01 - Set Lock Mode for Rollups

SIMG_CFMENUCX01_RU01 - Set Lock Mode for Rollups

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

When you execute a rollup to the consolidation system, the system locks the rollup itself and the consolidation processing ledger being updated. This is why it is initially not possible to simultaneously execute multiple rollups to the same ledger.

However, during the data collection phase of consolidation it may be absolutely necessary to record data for different consolidation units in the same consolidation processing ledger using rollups because of organizational reasons.

You can use different lock modes to accomplish this. You can adjust the level of detail used for locking a rollup to meet your organizational requirements. You can set lock modes for each integrated consolidation type and dimension. And you can change, delete or display the lock mode entries that already exist in this customizing step.

The different lock modes only apply to consolidation systems - that is, systems that contain the master data of the integrated consolidation units (except for lock mode 3 - see below).

The level of detail and, thus, the number of lock entries to be managed increases with each lock mode:

  • Lock mode 0: Locks at the level of integrated consolidation type / dimension / consolidation processing ledger
  • Lock mode 1: Locks at the level of integrated consolidation type / dimension / consolidation processing ledger / company of the consolidation unit
  • Lock mode 2: Locks at the level of integrated consolidation type / dimension / consolidation processing ledger / consolidation unit
  • Lock mode 3 (expert mode): The system does not set any locks. Instead, the user is responsible for avoiding conflicts if rollups are executed simultaneously.
    This lock mode applies to pure sender systems that do not contain any master data for integrated consolidation units and, therefore, cannot be used for lock modes 1 and 2.

The following alternatives are available for systems from which only data of a transactional application is exported to the consolidation system (rollup file):

  • You set lock mode 0 (global lock) or lock mode 3 (no lock).
  • In all other cases, the system automatically sets a global lock (lock mode 0). The same is true if the system does not find a lock mode entry when executing a rollup for the integrated consolidation type and dimension of the updated data stream.

Which lock mode you choose depends on your organizational requirements:

  • You do not need to make any settings in this step if any of the following applies: (a) You transfer and write to the consolidation system data for all consolidation units in a single file; (b) You read data from a sender table in a single process step; (c) You can do without the simultaneous execution of rollups. In this case, the system uses lock mode 0.
  • Choose lock mode 1 for this integrated consolidation type and dimension if you want to simultaneously record data for the consolidation units of one or more companies, for example, in a hierarchy of consolidation groups which is broken down by companies (of the consolidation units).
  • You will require lock mode 2 for this integrated consolidation type and dimension if you want to simultaneously roll up data for a single consolidation unit or a group of consolidation units for different companies.

Recommendation

Try to use the smallest lock mode number possible and, thus, the number locks to be set. Increase the locking capacity if you encounter locking management problems when executing a rollup.

  1. Specify the integrated consolidation type, the dimension, and the lock mode for the rollup.
  2. Choose one of the following options:
  • Set lock mode

  • Display all entries

  • Reconcile entries

  • Delete all entries






Fill RESBD Structure from EBP Component Structure   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4495 Date: 20240523 Time: 161323     sap01-206 ( 86 ms )