Skip to Content

SWIA transaction variant creation issue

Hi All,

I need to create a custom transaction for SWIA transaction by hiding some parameters in initial screen and hiding some function keys in result screen.

1. In went to shd0 transaction and gave required information and clicked on create

2. It navigated to original SWIA transaction when I gave some parameter and click enter it is not poping up configuration screen (menu config screen) -> it happens correctly for someother transactions like va01 etc but for SWIA transaction on initial screen I am not getting config / setting / menu pop up.

3. After giving input and execute, screen navigates to result screen -> here if I click anything config screen is appearing allowing me to hide function keys and menu items. So I could able to change the second screen - not first screen.

Question: Why I am not able to see config (settings) popup on SWIA initial screen????

Note: I have an alternative but it wont solve my issue totally. i.e. create a program variant by going into SWIA transaction -> click save -> do required modifications -> save as variant -> create a custom transaction (se93) using this variant. But issue with this is using this way I cannot modify the second (result) screen.

If I follow both (program variant for modifying first screen, transaction variant shd0 for second (result screen) -> I can not create custom transaction (se93) using this both as I can create custom transaction for either program variant or transaction variant - not both at a time for single custom tcode.

I already did lot of research in SDN but no use...

Please help.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Nov 08, 2012 at 12:27 AM

    Is this because initial screen is not created using module pool (it is created by program RSWIWILS i.e. program parameter ).

    I tried the same to customize my own alv report's transaction (using shd0 transaction) -> as it happened with SWIA transaction I am not able to make changes to initial screen but I could able to change second screen.

    So, Can't I make changes (hide fields) in a program screen (not module pool) using shd0 transaction variant?

    **************** Update *************

    I almost confirmed that we cannot use transaction variant (shd0 transaction) for program/report parameters - it is only for module pool program screens.

    Now what I can do is...

    1. Create a program variant for hiding fields in first screen (RSWIWILS) ---- this is working fine

    2. Create transaction variant for hiding function keys in 2nd screen (result screen) ----- this is working fine

    Now the issue is ---- how to create a custom t-code (se93) using both of above variants (program variant and transaction variant)???????????????

    I could see that we can create a custom t-code either by using report variant (program variant) or transaction variant - not using both.

    Any solution????

    In Simple words: How to create custom t-code using both program variant and transaction variant???? or

    If I have a t-code created using transaction variant then how to assign program variant to this?



    Note: I tried to create a program and execute transaction with variant but this wont show parameter at all.....

    submit ZSWIA using selection-set 'ZVSWIA'.

    I tried using a custom program and calling

    submit RSWIWILS using selection-set 'ZVSWIA' via selection-screen.

    it shows the selection but in the result screen function keys are not visible.

    1. 1. If we create a ztcode with option report program then function keys are not visible – either it is creating ztcode directly using rswiwils program & variant or creating ztode using cutom program which submits rswiwils program.
    2. 2. If we create transaction variant then we must create ztcode of type transaction variant – in this case we cannot customize initial screen (as its report program parameter).


    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.