When end users will maintain a z-table with 100+ rows, it helps to be able to restrict the selection by any number of selection criteria.  This document attempts to define a “best practice” method for calling a table maintenance dialog from a selection screen.

Current Table Maintenance

The standard way to show a table maintenance dialog is via SM30, Call View Maintenance

/wp-content/uploads/2013/08/sm30_265731.png

or a custom parameter transaction that calls SM30 for a specific table, with parameters VIEWNAME and UPDATE = ‘X’.

Neither of these provide an initial selection screen.  Entries can be restricted by checking the “Enter conditions” radiobutton, but users are more familiar with selection screens than with the dialog box that pops up.  Therefore it is good UI to use a selection screen instead of the “Enter conditions” radiobutton.

Example Selection Screen Definition

In this example, an executable report has been created with selection screen.

REPORT  z_maintain_mytable.

DATA mytable    TYPE z_mytable.

DATA selections TYPE TABLE OF vimsellist.

DATA selection  TYPE vimsellist.

SELECT-OPTIONS: so_selop1 FOR mytablemyfield1,

                 so_selop2 FOR mytablemyfield2.

PARAMETERS: p_param1 TYPE z_mytablemyfield3,

             p_param2 TYPE z_mytablemyfield4.

sel_screen.PNG

Calling Function Modules

When the user clicks execute, the program needs to read their selections and call the table maintenance dialog.  The following code shows how this is easily done by using function modules ‘VIEW_RANGETAB_TO_SELLIST’ and ‘VIEW_MAINTENANCE_CALL’.

START-OF-SELECTION.

  DEFINE addsel.

    CALL FUNCTION ‘VIEW_RANGETAB_TO_SELLIST’

      EXPORTING

        fieldname          = &1

        append_conjunction = ‘AND’

      TABLES

        sellist            = selections

        rangetab           = &2[].

  END-OF-DEFINITION.

  DEFINE addparam.

    IF &2 IS NOT INITIAL.

      CLEAR selection.

      selectionviewfield = &1.

      selectionvalue = &2.

      selectionand_or = ‘AND’.

      selectionoperator = ‘EQ’.

      APPEND selection TO selections.

    ENDIF.

  END-OF-DEFINITION.

  add_sel ‘MYFIELD1’ so_selop1.

  add_sel ‘MYFIELD2’ so_selop2.

  add_par MYFIELD3′ p_param1.

  add_par MYFIELD4′ p_param2.

  CALL FUNCTION ‘VIEW_MAINTENANCE_CALL’

    EXPORTING

      action                = ‘U’ “for Update

      view_name             = ‘Z_MYTABLE’

      complex_selconds_used = ‘X’

    TABLES

      dba_sellist           = selections

    EXCEPTIONS

      OTHERS                = 1.

  IF sysubrc = 1.

    MESSAGE ID symsgid TYPE symsgty NUMBER symsgno

               WITH symsgv1 symsgv2 symsgv3 symsgv4.

  ENDIF.

Horray!  That is all. In only 46 lines (plus two for every select-option or parameter), this will bring the user to from the selection-screen to the table maintenance screen.

tab_maint.PNG

This is a collaborative document.  If there are better ways of achieving this functionality don’t hesitate to chime in and contribute!

To report this post you need to login first.

18 Comments

You must be Logged on to comment or reply to a post.

  1. Michael Fallenb├╝chel

    Great work! But not perfect.

    Let’s say you have a table with a field type QUAN 13,3.

    Now you do your selection in the dynamic selection screen for this field from 1 to 5.

    ABAP will dump, saying “ASSIGN_OFFSET_NOTALLOWED”.

    “Part of the source field “<VALUE>” was assigned to a field symbol,

    but this is not allowed for fields of type “P”.”

    Any one has a solution for this?

    (0) 
    1. Frank Stiefeling

      Hi Michael,

      I’m dealing with the same problem. For me it seems to be a bug in form TRANSLATE_SELLIST_TO_WHERETAB of program SAPLSVIX.

      I tried many things but have no solution yet how to fill DBA_SELLIST.

      I’m still working…

      (0) 
      1. Michael Fallenb├╝chel

        Correct, the mistake is in TRANSLATE_SELLIST_TO_WHERETAB.

        I already made a call at SAP, first they told me VIEW_MAINTENANCE_CALL is not released, I told them it is (see help “The function moduel has been released”), nothing more since last contact yesterday.

        If there are any updates I will let you know…

        (0) 
    2. Ramu R

      Dear Michael,

      i am also getting same error.Please tell me how you solve this.Please do needful.

      Thanks & Regards,

      Avinash

      (0) 
      1. Michael Fallenb├╝chel

        Hi Ramu,

        you need to implement note 2007905

        Then I have added some coding (function  RS_DS_CONV_IN_2_EX) “in between” to convert my selection values to internal format (decimal point, …)

        Hope this helps

        Michael

        (0) 
        1. Ramu R

          HI michael

          Thank You for reply.and how to edit the values of selection screen like key fields.for example i enter the value in selection screen in output if i am trying to edit the values getting following error.

                 Specify the key within the work area

          Regards,

          Ramu

          (0) 
  2. Frank Stiefeling

    Hello Suhas,

    I use function FREE_SELECTIONS_DIALOG to create dynamic selections for a pool of different tables of our application.

    Then I convert export parameter EX_FIELD_RANGES to DBA_SELLIST to call VIEW_MAINTENACE_CALL.

    For the conversion I use VIEW_RANGETAB_TO_SELLIST and some code of my own, depending on field type.

    But that doesn’t work for fields of type P.

    BR

    Frank

    (0) 
      1. Suhas Saha

        Hello Gentlemen,

        I don’t use the VIEW_MAINTENANCE_CALL function. I use the TMG event AA and call the selection-screen in there.

        I already made a call at SAP, first they told me VIEW_MAINTENANCE_CALL is not released

        Interesting, i thought that the FM is “released”. But if you see the date it is blank ­čś»

        /wp-content/uploads/2014/02/2014_02_18_151605_390788.jpg

        Something fishy is going on there ­čśŤ

        BR,

        Suhas

        (0) 
          1. Suhas Saha

            Hello All,

            Just to clarify, when i said –

            I don’t use the VIEW_MAINTENANCE_CALL function

            i meant for this scenario. I have used this FM many times & it has always worked like a charm ­čÖé

            BR,

            Suhas

            (0) 
      2. Eric Peterson Post author

        Thanks for the feedback everyone!  I’m learning a ton.

        I like how Suhas’ method uses the standard events instead of slapping an executable report on the front end.  Perhaps we can combine our document and wiki and determine a best practice.

        My only concern with his method is the filtering on the application server and not the database – is that the right choice in this scenario?  And does VIEW_MAINTENANCE_CALL do the same thing?

        (0) 

Leave a Reply