topic commit after batch input call transaction in Application Development and Automation Discussions

commit after batch input call transaction

mark_fryu — Fri, 01 Apr 2022 07:34:36 GMT

when i call a batch input with call transaction CO02 without commit i see that works, but is it necessary to commit after the call transaction?

Re: commit after batch input call transaction

Jeansy — Fri, 01 Apr 2022 07:43:23 GMT

Hi Mark,

it depends on which update mode you use for BatchInput.

A: Asynchronous
S: Synchronous
L: Local Update (explicit COMMIT needed)

Normally a COMMIT is needed to save the changes.

KR
Jens

Re: commit after batch input call transaction

Luca_Cavarretta — Fri, 01 Apr 2022 08:01:59 GMT

La ringrazio per la risposta

I have 'S' but what's the difference with 'A' ?

I need it to finish all the updates, and then continue with the abap code, what should I use?

Re: commit after batch input call transaction

Sandra_Rossi — Fri, 01 Apr 2022 08:29:34 GMT

No it's not needed. Transactions which need to update database should handle the commit themselves (save + commit work).

Re: commit after batch input call transaction

Jeansy — Fri, 01 Apr 2022 08:39:51 GMT

The simple difference in Synchronous and Asynchronous is that:

In synchronous mode, the posting is done once and the system waits for its result before commiting for the next posting (assuming that the call transaction is done in a loop.) This would consume more time. But this is considered the safe option in most cases.

--> A synchronous Workflow task must be executed before control is passed to the next step. It is used for tasks that do not involve required updates, because once the workitem is executed, control is passed on to the next step without checking the success or failure of any update that might or might not have taken place.

-->An asynchronous Workflow task should be used when a successful update is required prior to control being passed to the next step. The task does not end when it is executed. The task ends when a terminating event is received. The terminating event requires a COMMIT WORK before it is triggered.

Unless otherwise you have a strong reason, please avoid the Asynchronous mode.

Reward points if you wish.

Re: commit after batch input call transaction

Luca_Cavarretta — Fri, 01 Apr 2022 09:42:24 GMT

ok thank you, so if i'm using "synchronous" can i not put a commit after the batch input?

I take this opportunity to ask another question:

what is the difference between:

-commit

-commit and wait

I need the commit which "saves" everything before moving forward