BAPI_BUS2054_CREATE_MULTI and Too Many Lock Objects

[Former Member]

I have been asked to review an issue with too many Lock Objects being generated by a Projects System program.

The program is custom; however,it uses the core BAPIs associated with creating it's Project - specifically:

BAPI_PS_INITIALIZATION

BAPI_BUS2001_CREATE

BAPI_BUS2054_CREATE_MULTI

BAPI_PS_PRECOMMIT

BAPI_TRANSACTION_COMMIT

In this situation, the custom program is trying to build a Project with about 2000 Outlets and a template that has 4 or 5 WBS elements.

B/c of this, the system is creating and HOLDING 8000-10,000 Lock Objects while processing through the BAPI_BUS2054_CREATE_MULTI logic. The Locks are released following the COMMITs in BAPI_TRANSACTION_COMMIT.

But our issue is that 8000+ Locks are producing a "Table Lock Overflow" error for other users that are performing different t-codes / processes throughout the enterprise.

Has anyone seen and has anyone overcome this issue?

In reviewing Projects, it appears that Project Systems is creating and holding the Locks to guarantee data consistency.

Our Basis Team has the Lock Table Max set at 80 KB currently - and they are reluctant to increase beyond that - especially for one, unique program.

Thoughts? Ideas?

<b><REMOVED BY MODERATOR></b>

Message was edited by:

Alvaro Tejada Galindo

[Former Member]

Any Projects Pro's?

[Former Member]

Hi,

Run Enqueue Trace while your program is executing and study it. Check the attributes of Enqueues which are not getting cleared at the end of each transaction. Call a Dequeue FM passing attributes similar to Enqueue lock.

Hope it helps.

Regards,

Amit

[vamsixk]

the Lock table can only handle a certain number of lock entries at any given point of time.

try using parallel processing to create ur WBSE, we are updating the WBSE in this way and are not facing any issues.

Regards,

Vamsi