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.
Calling the FM in Backgroung marks a flags for that function module func to be run asynchronously. That is, it is not executed at once. Instead, the data passed using EXPORTING or TABLES is placed in a database table and the next COMMIT WORK executes it in another work process.
Function modules that you call using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION are registered for background execution in another SAP System when the program reaches the next COMMIT WORK statement (using Remote Function Call). After the COMMIT WORK, the dialog process does not wait for these function modules to be executed (asynchronous update). All of the function modules that you register in this way are executed together in a single database LUW
if you want to run in normal background i mean the same system, then there is no need to write any thing, you can use call FUNCTION MODULE statment. but make sure that GUI_* and WS_* function modules do not work in background
I placed the break-point at Commit work and checked for the processes in sm50. When the execution atopped at the break-point I pressed F6 and then refreshed the work processes in sm50 but I was not able to find my backgroud process. I could only see the dialog process. Is it possible for me to debug this from process overview?
Bluesky
