Calling a function module without actually committing the changes

[Former Member]

Hi there,

Is there any way to call a function module without actually committing the update it makes (kind of like how SE37 doesn't commit updates)?

Some functions offer this functionality via testrun parameters which is great, but then some don't and it's nice to be able to simulate the outcome before actually running it for real.

Any input appreciated.

Thanks,

L

[Former Member]

try.

IF test_flag = 'X'.

ROLLBACK WORK.

else.

COMMIT WORK AND WAIT.

ENDIF.

[Former Member]

I was thinking about that actually. Now I wonder if I could do the following:

call function n
importing stuff

do some internal program work using stuff

call function x
exporting stuff
importing morestuff

do some internal program work

rollback work

Basically could I call a bunch of update functions in my program, get all the results and outputs from these updates for my own use, and then roll back all the updates in one shot so nothing is actually changed? Basically updates that build on each other, but I don't want to commit anything.

Sounds kind of dangerous to me, but if the rollback would work then this would be very useful.

[Former Member]

A rollback won't work if a commit has been done. So if any of your FMs has a commit, you'd be out of luck.

Rob

[Former Member]

Hello,

Just define the function module like Remote-Enabled Module in the attributes tab. Read this for reference .

Regards.