Regarding Function Module

[Former Member]

Hi,

Can you please tell me a function module is asyncronous update ? if so why?

thnkx

venkat

[former_member404244]

Hi,

Check the below links

http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4cea79e11d1950f0000e82de14a/content.htm

http://erpgenie.com/index.php?option=com_content&task=view&id=464&Itemid=77

Regards,

Nagaraj

[Kanagaraja_L]

Hi Venkat,

A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.

The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG. If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.

The corresponding entries in the lock table are reset by the update work process.

Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load of logging them in VBLOG. If you are running a transaction in a background work process, asynchronous update offers no advantages.

The system marks rolled-back function modules as error functions in the update task log. The error can then be corrected and the function restarted later.

Kanagaraja L