topic Call Transaction in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2078234#M430919 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P> What Is Exact meaning of CALL TRANSACTION 'LOCAL' update mode?</P></BODY></HTML> Tue, 17 Apr 2007 09:46:22 GMT Former Member 2007-04-17T09:46:22Z Call Transaction https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2078234#M430919 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P> What Is Exact meaning of CALL TRANSACTION 'LOCAL' update mode?</P></BODY></HTML> Tue, 17 Apr 2007 09:46:22 GMT https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2078234#M430919 Former Member 2007-04-17T09:46:22Z Re: Call Transaction https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2078235#M430920 <HTML><HEAD></HEAD><BODY><P>This statement switches on the local update. In the local update, priority update function modules - registered during the current SAP LUW using CALL FUNCTION ... IN UPDATE TASK - are registered in the ABAP memory instead of the VBLOG database table. In addition, it specifies that the current work process and not the update work process run these modules during the current database LUW, when the COMMIT WORK statement is executed. This statement has no effect on low-priority update function modules. </P><P></P><P>At the beginning of every SAP LUW, the local update function is deactivated. If you wish to use it, you must reactivate it again before the first update function module is registered. </P><P></P><P>Regards</P></BODY></HTML> Tue, 17 Apr 2007 09:51:30 GMT https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2078235#M430920 Faaiez 2007-04-17T09:51:30Z