Skip to Content
Former Member
Apr 15, 2010 at 10:19 PM

"COMMIT WORK" (in called function module) causes dump of a transformation


Hi everyone,

I am actually facing a problem with a transformation, which calls a function that uses "COMMIT WORK".

For each data package the function module insert values into a database table, that needs to be updated and commited.

The next data package needs to know about the updated values created by the previous data package.

The problem is when you use COMMIT in this situation, it closes all opened cursors and creates a dump. The transformation tries to fetch the next data package and encounters a dump situation.

There was also a solution with EXPORTING into and IMPORTING from ABAP memory, but this solution might dump because of memory overflow.

Has anyone faced a similar situation and found a solution? Thank you for answering!