Locking problem in BPS solution not getting solved using RSPLSE. SEM_BPS_S

Question

Can anyone tell me exactly what "rsplse" offers to solve locking in BPS?
We have made correct selection of characteristics (in our case "costcentre" infoobject) in tab "Lock characteristics" , but still when two people are trying to access (write) data in the same transactional cube against the different cost centres, the system is throwing an error message Cube “zIC_ccp” is locked by username.  (Or if a single person is using the two packages simultaneously using  two web sessions , he is getting the same error. )
Our assessment is that he should not be facing this locking problem because cost centres here are acting as a “key” to different selection as configured in “rsplse”. 
Can anyone tell me how to use parameter SEM_BPS_SAVE_UNLOCK. I want to know t. code and other t . code and other details to execute SEM_BPS_SAVE_UNLOCK.

Answer 1

Hi,
Please check the OSS note 635244.
  From the OSS note :
<b> Notes on SET/GET parameters SEM_BPS_NO_LOCK, SEM_BPS_SAVE_UNLOCK :</b>
These two parameters have nothing to do with the problem described above. They are only designed to facilitate the Customizing process, if users carry out Customizing in t ransaction BPS0 within a project.
<b>SEM_BPS_NO_LOCK:</b> This parameter has the effect that transaction data is not locked at all. Never use this parameter in a production system. As of Support Package 14 for Release 3.1B, parameter SEM_BPS_NO_LOCK is released by an additional switch in table upc_dark2: For this purpose you have to maintain a record with param = ENABLE_NO_LOCK and value = X in table upc_dark2. Only then the system includes parameter SEM_BPS_NO_LOCK. The parameter can then be useful if you want to test functions or the manual planning with 'test data' in Customizing.
<b>SEM_BPS_SAVE_UNLOCK</b>: This parameter only works in transaction BPS0; it has the effect that the system unlocks data (if possible) after it has been saved. Therefore, the system only simulates an exit and reentry in transaction BPS0 with the last active detail application. Therefore, the above parameter can be helpful if many people work on Customizing in transaction BPS0, because objects can be unlocked earlier.
Regards,
Siva.