Skip to Content
author's profile photo Former Member
0
Former Member

Ansynchronous when using "Call transaction"

Posted on Dec 18, 2012 at 01:56 AM 12 Views

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

aaaa.png (13.7 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 18, 2012 at 03:02 AM
    0

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 18, 2012 at 03:18 AM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Christian Jianelli
    Christian Jianelli
    Posted on Dec 18, 2012 at 07:23 AM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.