02-02-2010 10:41 PM
Hi,
We are consistantly getting the ABAP runtime dump SYSTEM_ON_COMMIT_INTERRUPTED for last few days.
The runtime error is in customized program.
But the error is on the statement
"Leave Program."
The customized code has some processing and then it calls a screen through another function module call and then if sy-subrc is zero, above statement is executed.
I really can not relate these two things.
Does screen call has anything to do with the runtime dump?
Please suggest a solution.
Would doing "Commit Work" before this sentence would be enough?
The description of the runtime dump for your reference:
Error analysis
During the COMMIT WORK statement, the following are executed:
- the routines registered with the statement PERFORM .. ON COMMIT,
- the registered methods for the events of the object services
and
- possibly the local update (SET UPDATE TASK LOCAL).
An exception was raised and caught. The normal sequence of the routines
was interrupted by this resulting in the program being continued before
the call of COMMIT WORK. As this can lead to inconsistencies, the
processing cannot be continued in the normal way.
02-02-2010 10:46 PM
I hope you are coming out of the program while system in the process of updating the database. Just add one more statement that 'Wait up to 5 seconds' before leave program and see.
09-01-2010 5:19 AM