on 09-01-2009 4:14 PM
Hello,
We usually see users in SM12 who are accessing the Planning Area. I would like to know if we delete the user locks from SM12 what really happen? Does it impact liveCache consistency and anything else?
Thanks,
SAnju
Hi Sanju,
Certain problems can result in locks that cannot be released again, with the result that
uses cannot access the locked objects.
These locks, however, can be deleted manually.
In general, however, you should not directly delete locks with the delete functions
offered in the lock management system. Unreleased locks are almost always the
symptom of another underlying problem. When you correct the underlying problem,
the locks will be released automatically.
First try to identify and remove the problem.
Only delete lock entries if you are sure that they are invalid and can be deleted
without impairing an active process (user session, update, and so on). Deleting a
lock held by an active user can lead to loss of the data entered by the user or to data
inconsistencies.
When a user changes data in the system, the system must then lock this data.
This prevents other users from changing the same data simultaneously and causing
data inconsistencies. This means that you can only change data in demand planning
(DP) that is not currently locked. If, for example, interactive planning is to select data
that has already been locked, then this data is automatically shown in display mode.
The liveCache lock is the most precise locking method. Using this locking method,
the system can create an entry in the lock table for multiple single values or one interval
per characteristic. The liveCache lock does not take exclusive selections into account.
Regards
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.