Skip to Content
0
Feb 04, 2009 at 03:16 PM

Update tasks still exist after Roll back

32 Views

Hi,

In a Z_BAPI i've doing several BAPI_EQUI_CREATE calls to create equipments.

USER1 : 1 call is incorrect and 6 are correct, the BAPI_TRANSACTION_ROLLBACK is done.

Another user USER2 is calling the bapi simultaneously with correct data and correct calls of BAPI_EQUI_CREATE. So at the end of the Z_BAP a BAPI_TRANSACTION_COMMIT is performed.

Sometimes (depending of timing) USER2 gets a shortdump and a update task error.

The shortdump indicates that INSERT is done for the same key : SAPSQL_ARRAY_INSERT_DUPREC.

In the logging of the update task error (by transaction SM13) we are seeing old data (belonging to USER1 and other old data) that does not belong to USER2.

How is it possible that USER2 during COMMIT WORK update task from other people processes.

Any clues / suggestion / help ?

regards,

Hans