Skip to Content

Variant transactions for SM30

Hi folks,

I have build a couple of custom tables in SAP and I wanted to give the users some easy way in maintaining the tables without bothering them about SM30 details ...

A couple of years ago I did this already by defining a variant transaction for the transaction SM30 wherein I skipped the first screen completely.

In 4.6C it seems that the variant transactions have been extended more (screen variants,e tc ....) so I was surprised to find out that I ran into the following problem (which I didn't have in a previous relaese):

I can define a screen variant for the first screen of SM30 and I successfully bypass the first screen ... BUT once within the maintenance screen of my custom table, the standard BACK,EXIT arrows do not work anymore ... the only way to leave the screen is killing it!

I tried to generate a screen variant for the 2nd screen and grouping the 2 screen variants in 1 transaction variant but that does not seem to work ...

What am I missing ?

Thx,

Steven

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Former Member
    Jun 24, 2004 at 08:41 PM

    Hi Steven;

    Here is our setup for performing the same steps in 4.6C which works fine, including all of the buttons.

    -- Transaction: SM31 (and check "skip initial screen")

    -- Inherit GUI attributes checked

    -- Professional User Transaction selected

    -- No options selected under GUI support

    Default values are specified as followed:

    Name of screen field Value

    VIEWNAME <insert custom table name here>

    UPDATE 'X'

    That should work for you...

    Add comment
    10|10000 characters needed characters exceeded

    • Hi John,

      Thanks for your quick reply ...

      Unfortunately it does not work ...

      I thought that the attribute "Inherit GUI attributes" would do the trick but it does not make a difference whether I change it or not ...

      I played a little bit and the behaviour is really strange:

      whatever tablename I put into the VIEWNAME field, the variant transaction does not pick it up and uses the latest used table via SM31 (so the parameter ID I guess)

      and puts that table into maintenance view ...

      Whatever I try I always end up 'locked' in SM30 or SM31 and cannot leave the screen anymore ...

      Any ideas?

      Thx,

      Steven

  • author's profile photo
    Former Member
    Jun 25, 2004 at 06:44 PM

    Steven;

    Just to be sure, are you putting the 'X' in the update field (below VIEWNAME)? It seems odd that it would work fine here but not in your system...

    -John

    Add comment
    10|10000 characters needed characters exceeded

    • Hi John,

      I remember that in previous projects where I used it you needed to put an 'X' at the update field ... (but that is already some years ago ... )

      However in this system the interace for generating the variants is more advanced meaning that it does not allow (or requires) you to enter a 'X' value for push buttons ... it visually displays the buttons and marks them with a checkbox that it is selected ... There are no options here for changing any value (like tablename) ... everything is 'recorded' and seems to be okay ...

      Still is does not work ...

      SM31 works fine without any issues ...

      This really is puzzling ...

      Steven

  • author's profile photo
    Former Member
    Jul 07, 2004 at 03:39 PM

    We run 4.6C and use a customer-defined transaction code to achieve the same result:

    From SE93, create new transaction

    - select Transaction with Parameters radiobutton

    - enter the transaction you want to use (SM30)

    - tick the Inherit GUI Attributes box (this causes all of the GUI support boxes to become checked)

    - add two entries to the default values subscreen:

    Name of Screenfield = VIEWNAME, value = Table name

    UPDATE, value = 'X'

    Save and then use the transaction as any other.

    This works for us, although Authorization capabilities are somewhat limited.

    Add comment
    10|10000 characters needed characters exceeded