Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BATCH INPUT update mode LOCAL vs Sync

queue
Participant
0 Likes
2,128

Hello all,

Many programs created by customer use update mode 'S' to execute standard transaction, such as FB01, VA01 and so on.

From performance point of view, I think that 'LOCAL' is much better than 'Sync', since VBHDR/VBDATA are not necessary.

Is there any advantage to use 'S' instead of 'L'?

Thank you

Yuko

1 REPLY 1
Read only

Former Member
0 Likes
962

Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.

But in local updating

Switches on the local update task. This means the update data is not stored in the database, but in ABAP/4 Memory. The update works as before. The only difference is that it is not performed in a separate process, but in the same process as the calling program, i.e. when a COMMIT WORK occurs, processing does not continue until all the update requests have been performed. In the standard setting, the normal update task is always active.

so if any error occurs in local mode all the data will be rolled back and no update will occur.

regards

shiba dutta