Beginning with Release 3.0A, a new function is available for the lock object in FI-SL planning. The lock object is required in FI-SL planning so that two users cannot plan the same dataset at the same time.
The SAP lock management only allows you to lock key fields. This means that it was only possible to lock the 'fixed fields' (ledger, record type, version, year) when using FI-SL tables with objects. A logical lock, for example, on account intervals, was not possible since the account only occurred in the data part of the summary table. It was therefore not possible for two users to plan different account intervals within the same ledger (with the same version).
A new function has been introduced to solve this problem for Release 3.0A. The customer can create a structure in the Repository and then enter all important fields of the customer summary table in this structure for which a lock is later to be used (for example, ledger, record type, version, fiscal year, company code, account, personnel number, and so on). However, fields with type NUMC cannot be included in the structure. The fields are to be explicitly marked as a key (Extras --> Display key). You should make sure that the ledger is entered at the first position in the definition of the structure since the rollup requires this field for its locking logic (you can use the structure GLREFINT as a reference). The structure must then be activated. You then have to create a lock object. The lock object is called EGxxxxxxxE, where xxxxxxx can be up to 7 characters long and is user-defined. When defining the lock object in the Repository, the structure that has just been defined must be entered as a primary table. The lock object must also be activated. To be able to use the lock object productively, the FI-SL table directory must be changed using transaction GCI3. You have to select the summary table for which you want to extend the locking logic and enter the name of the lock object. You must enter 'xxxxxxx' (see above) as the name of the lock object.
Note: Beginning with Release 3.0A, a standard lock is used on the fields account (RACCT), business area (RBUSA) and cost center (RCNTR) for FI-SL tables in planning. If only these fields are of importance in the customer table, it is not necessary to create a separate lock object.