Lock table overflow: MC 603

[Former Member]

Hi,

I hav the lock error MC603 in my program.

The program makes phone number inserts using

BAPI_BUPA_CENTRAL_CHANGE

running in parallel.

The migration files have unique BP numbers. No duplicate BP numbers.

Actually I assume the BAPI locks only the BP that it is updating.

Since no BPs are duplicate in migration files...how can we have lock errors?

WHo knows?

Thanks in advance!

Thomas

[Former Member]

Hi,

I hav the lock error MC603 in my program.

The program makes phone number inserts using

BAPI_BUPA_CENTRAL_CHANGE

running in parallel.

The migration files have unique BP numbers. No duplicate BP numbers.

Actually I assume the BAPI locks only the BP that it is updating.

Since no BPs are duplicate in migration files...how can we have lock errors?

WHo knows?

Thanks in advance!

Thomas

[Former Member]

I don't have much knowledge of this BAPI or BP but a simple question would be that what error message you are getting ?

&(^%%^^(*&)&) is locked ?? So that you could know that what field is getting locked by SAP and then can go into its details.

Also, do use rollback and commit BAPI's after your BAPI call depending on the state, to release the locks in time if not already doing so.

BR

Diwakar

[Former Member]

You can see in SE91 that the error message MC 603 does not indicate any further info on lock object.