Skip to Content

Call transaction

I have created a custom screen with verios buttons. Each button triggers a call transaction. The first button triggers CT04 and works the way I would like it to. The user creates a characteristic, saves and clicks the back arrow to go back to the custom screen where they have the option of clicking on another button. However, none of the other transactions - CU01, CL02 etc allows the user to go back to the custom screen after saving and clicking the back arrow. Rather they are taken back to the application menu (and totally out of my program). I found for example if I went to CU03 (display) then backing out also takes the user to the custom screen. Create and change is the problem. Any suggestions would be greatly appreciated.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2004 at 03:48 AM

    Hi Jill,

    The problem that you are facing is because of code in this manner.

    If you just debug you will see that we have the following.

    If its batch input, then leave.

    else leave to transaction CU01.

    So to make it appear like a batch input session what you might do is.

    Do call transaction give empty bdcdata table, and specify the options as follows.

    DATA: options TYPE ctu_params.

    DATA: bdcdata TYPE STANDARD TABLE OF bdcdata.

    options-racommit = 'X'.

    options-dismode = 'E'.

    sy-binpt = 'X'.


    OPTIONS FROM options.

    If you remove the parameter racommit = 'X' then it will automatically come back to ur previous session on pressing save, but if u want to press back to come back to the previous session then racommit must be 'X'. You should be able find similar work arounds in other cases as well.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 20, 2004 at 02:41 PM

    Thanks Pavan (especially for your timely response) - it worked like a dream


    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.