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.
Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the function library.
Call function in background task
Flags the function module func to be run asynchronously. It is not executed at once, but the data passed with EXPORTING bzw. TABLES is placed in a database table and the next COMMIT WORK then executes the function module in another work process.
Hope this will help you to understand the difference in two options. Please close the thread if this answers your question.
Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the function library.
Call function in background task
Flags the function module func to be run asynchronously. It is not executed at once, but the data passed with EXPORTING bzw. TABLES is placed in a database table and the next COMMIT WORK then executes the function module in another work process.
Hope this will help you to understand the difference in two options. Please close the thread if this answers your question.
For Background task, If the specified destination is not available for COMMIT WORK, an executable called RSARFCSE is started in the background. This attempts to start the functional modules registered for an SAP LUW in their destination, every 15 minutes up to a total of 30 times. You can make changes to these parameters using transaction SM59. If the destination does not become available within the given time, this is noted in the database table ARFCSDATA as a CPICERR entry. By default, this entry in database table ARFCSSTATE is deleted after 8 days.
This is one of the major difference but if you need all details, SAP help explains the same in a detail way. Please check this link.
Bluesky
