SEM-BPS 6.0 error message requested data cannot be locked but at 999 row?

Question

Hi all,
We are using SEM-BPS with WIB and EP 7.0 and I encountered issues for the first time.  I normally avoid configuring layouts with large hierarchies but at this one the client insisted.  They are in testing right now and selection of relatively small node (approx. 10-20 cost centers) still gave us an error message. 
I know layouts has a limit of 9,999 rows and we should have been okay since it is about 200-300 lines per cost center but we are getting the error message below and it mentioned a limit of 999 rows in the selection table..  Any way we can change that?
Thanks,
mary
Requested data cannot be locked (-> see long text)
Notification Number RSPLS092
Diagnosis
In order to edit data from InfoProvider 'ZYEE_C02', the requested data has to be locked exclusively for user 'YEESU01'. The data that is currently being requested is specified by a very large selection table. In order to lock the data exclusively, the system has to store a compressed version of this selection table on the SAP standard lock server. However, the compressed selection table still has more than 999 rows. So that a reasonable number of users are able to change data at the same time, the system limits the number of records allowed in a selection table to 999 records.
Information on Context of Lock Request:
Lock requests can come from BI-Planning or from BW-BPS. The context specifies the following information:
BI-Planning: for a lock request from a query, {Planning Function} for a lock request from a planning function.
BW-BPS: {Planning Area}{Planning Level}{Planning Package}{Planning Function}{Parameter Group}. For lock requests from manual planning the following is true: Planning function = '0-MP' and the parameter group is the technical name of the planning layout.
InfoProvider 'ZYEE_C02' is always a Basis InfoProvider. The current context information is:
'{0-ADHOC}{0-MP}'
System Response
The requested data cannot be locked.
Procedure
You can normally only avoid this by simplifying your selections. For more information, see the documentation on this.
Procedure for System Administration

Answer 1

Hi Mary,
in RSPLSE you use the option that the BI lock table is maintained in the SAP enqueue server. Here there is a limit - as explained in the long text of the message - that the compressed selection table for one enqueue request should not have more than 999 rows. This limit can not be changed.
The selection table seems to be very big, since the compression factor is at least 5. So please check your selection table:
1 check whether you can make the characteristic causing the problem not lock relevant
2 or use the second option that the BI lock table is maintained in a shared memory area of the central instance of the system.
But it is better to keep the selection tables small, e.g. by making some characteristics not lock relevant.
Check sizing note 928044, e.g. in case you want to use 2. The default setting is very small.
Regards,
Gregor