Text Body:
Here is another concern that we all face in BPS but not many folks
understand it completely. Here is the documentation from the Horse's mouth! (SAP Help):
Data is
locked against access from other planning sessions within a planning session from the moment where it was accessed with write
access. A lock generated once by the system lasts until the planning session is terminated.
The background for this
behavior is that only in this way can an improvement in the response times be reached: Only when accessing the data for a
certain characteristic combination for the first time, is the database is accessed. The data read from there is saved
provisionally in the SEM-BPS buffer and stays there until the end of the planning session. Further access to this data is
then directly served from the buffer without having to access the database. However, since the data in the buffer is saved
with reference to a planning session, the same data cannot be changed simultaneously in other planning sessions because
otherwise consistency problems would arise.
Saving data also does not normally remove the existing lock, since the
planning session continues, and further accesses to the buffered data could take place. However, if you wish that the system
releases locked data without you having to exit the planning session, you can do this in the following ways:
•
You add the user parameter SEM_BPS_SAVE_UNLOCK to the user master records of the employees who use SEM-BPS, and set the
parameter to the value X. This has the effect that the system always releases the data which you are editing with SEM-BPS,
when you save the data in the data basis with the Save function.
• You call up the API_SEMBPS_REFRESH function
using the SEM-BPS Application Programming Interface.
(courtesy: SAP Help)
Book Link:
SEM-BPS Learning: Hidden and Useful
stuff