Skip to Content

How to debug a call transaction where mode = 'N'

Is there a way to debug a call transaction that is executing in the background? I have a process that works in mode 'A' but isn't working in background. In my debug settings, I tried checking the "Always process requests synchronously" checkbox but that doesn't seem to work.

Mike

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 08, 2004 at 03:28 AM

    When you say "Debug a Call Transaction", what are you exactly looking for ?

    a) Do you want to debug that transaction ?

    b) Do you want to check whether each value of the field in that transaction is getting populated properly ?

    Let us know, perhaps we can help better.

    Regards,

    Subramanian V.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 08, 2004 at 08:17 AM

    I'm afraid you cannot really debug in mode 'N', but you can try CALL TRANSACTION with addition OPTIONS FROM ctuparams, where ctuparams must be a variable of DDIC type CTUPARAMS. In ctuparams you can set display mode, update mode, and also the flag NOBINPT = 'X'. With this flag set the transaction will think it runs in online mode, that is variable sy-binpt will be cleared for this transaction. The matter is that some transactions change their screen sequence depending of the flag sy-binpt.

    Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 08, 2004 at 08:32 AM

    Hi mike,

    What you can do, (not the nicest way but it works nevertheless). If you can edit the transaction insert the following statement:

    data: x(1) type c.

    while sy-uname = 'your userid here' and x is initial.

    endwhile.

    using transaction sm50 You can now debug it because it's in an endless loop.

    Not the prettiest way, but workable as a last resort. Then again I didn't mention this 😊

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 08, 2004 at 02:41 PM

    Thanks all. I was hoping with 4.7 I might have some new debugging options. This is one of those really tricky Call Transactions with message pop-ups (where we really should be using a bapi anyway). The CTUPARAMS method still doesn't show me why I'm failing in background. I suppose I'll have to try the sm50 method.

    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.