Avoiding locks in BPS workbench

Question

Hi all,
we are in the middle of a tough implementation, short before deadline. This means that 5-6 persons are developing in parallel, in different Multi-Areas, but refering back to the same basic areas and reference areas for variables.
Currently we tend to lock each other in the workbench regularly. I remember there is a setting somewhere in a control table (UPC_DARK2?) which limits those locking problems in the workbench, but I cannot remember details and also did not find anything in SDN. Can someone help?
Many thanks in advance,
Andreas

Answer 1

Notes on SET/GET parameters SEM_BPS_NO_LOCK, SEM_BPS_SAVE_UNLOCK
These two parameters have nothing to do with the problem described above. They are only designed as a help for the Customizing process, if users carry out Customizing in Transaction BPS0 within a project.
SEM_BPS_NO_LOCK: 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 the table upc_dark2: For this purpose you have to maintain a record with param = ENABLE_NO_LOCK and value = X in the 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 the Customizing.
SEM_BPS_SAVE_UNLOCK: This parameter only works in Transaction BPS0; it has the effect that the system unlocks data (if possible) after it has been saved. Thus, the system only simulates an exit and reaccess in Transaction BPS0 with the detail application last active. Therefore, the above parameter can be helpful if many people work on Customizing in Transaction BPS0, because objects may be unlocked earlier.