12-18-2012 1:56 AM
Hi All,
I have a question when call transaction, after the transaction called, the result is not updated timely , but have to wait for a few seconds some times, it seems that it is not synchronous , I read the documentation about the call transaction , it is as follows:
Is the "S" mode can solve the problem?Why it can solve the problem ? And what is the "L" mode mean?
Thank you very much.
Regards,
Chris
Moderator Message - Did you check the hyperlinks in the documentation? This is quite well documented by SAP. Un-marked as question.
Message was edited by: Suhas Saha
12-18-2012 3:02 AM
Hi.
Is it the standard transaction?
In a standard transaction, there are some which are performing renewal of asynchronous in transaction processing.
As a typical motion, it is processed by upgrade tasks in a transaction.
RFC may be used in other cases.
In the case of an upgrade task, it is avoidable by update mode 'L'option.
See help of 'CALL FUNCTION - IN UPDATE TASK'
Regards.
12-18-2012 3:18 AM
Hi,
When you are doing call transaction, the results might not be available immediately as there are some updates of the data base that are triggerd in the update task.
So it better to use commit work and wait for the update to happen.
Hope this will help.
Regards,
Amit
12-18-2012 7:23 AM
Hi Chris,
This is caused by the update technique implemented in the transaction called.
The Synchronous mode will solve your problem.
The local update option as per documentation "The only difference is that it is not performed in a separate process, but in the same process as the calling program".
See SAP Help for more information.
SET UPDATE TASK LOCAL
http://help.sap.com/saphelp_45b/helpdata/en/34/8e73e86df74873e10000009b38f9b8/content.htm
SAP Help - Asynchronous Update
http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4cea79e11d1950f0000e82de14a/content.htm
SAP Help - Update techniques
http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/frameset.htm
Regards,
Christian