System Locking error

[Former Member]

Hi All,

I am running an inbound interface with volume of 50,000 records. The interface works as follows.

1. This is a flat file interface, XI will pick the file and send to R/3 via Proxy. In R/3 Existing records in SAP will be compared with flatfile records. If a record present in both flat file and SAP, that particular record will be changed if there's a difference.

2. If a record is present only in Flat file, that record will be created in SAP.

3. if a record is present in only SAP, that record will be deleted.

I am using 3 BAPIs to create, change and delete the records in SAP. they are BAPI_PLANNEDORDER_CREATE, BAPI_PLANNEDORDER_CHANGE, BAPI_PLANNEEDORDER_DELETE.

My interface is working fine when i run with smaller flat files but when i run with big files (Around 50000 records) my interface is failing due to "Time out". So i changed my program and making use of parallel processing. Now my interface is working fine but i am getting "system locking error" or " Lock table overflow error" i.e upto some 10000 records its giving correct result in BAPI but afterwards its giving me system locking error. I am calling BAPIs inside loop statement.

Also other users in my project are also getting " Lock table overflow error" when my interface is running.

My problem is the table(PLAF in my case) is getting locked for create, change and delete for each record but not getting released when that record is processed.

Urgent help required on this issue. Any help would be appreciated and promise to awrd points for helpful answers.

Thanks,

Rajesh.

[Former Member]

Hi,

release lock using Fm

db_commit to realese lock explicitly

after your BAPI is executed inside

loop.

loop at itab.

BAPI_PLANNEDORDER_CHANGE.

<b>call function db_commit.</b>

or

commit work.

endloop.

Regards

amole

[Former Member]

Hi,

are use FM dequeue_all inside loop.

REgards

Amole

[Former Member]

Hi Amole,

Thanks for u r quck reply, DO i need to call Deque_all after BAPI_TRANSACTION_COMMIT?

[Former Member]

Hi Rajesh,

Did you find a solution for your problem?

I'm also getting the same error. But the difference is we are getting the error when we are sending material characteristics thru IDOCs to external system.

Please let me know if you have any solution for this.

Thanks,

Kishore

[Former Member]

Hi,

BAPI_TRANSACTION_COMMIt will release lock explicitly

but try dequeue_all after BAPI_TRANSACTION_COMMIT.

Regards

amole