Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A



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


- 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.

Former Member
Not what you were looking for? View more on this topic or Ask a question