"
Supported by

Unparameterisable parameters

Every now and then you get a client who asks a programmer to create a write-protected parameter on the program selection screen. It’s a bit dumb given that the whole idea of parameters is that they are parameterisable.

But there you go, it takes all sorts.

Clients have so much imagination that SAP should create a cinema module, SAP CI, especially so they can screen all the films they carry around in their heads. I am sure some real sci-fi blockbusters would come out of it. And a few comedies too.

Well, if anyone asks you for this, do as follows:


REPORT ZTEST1.
PARAMETERS: nao_mexe LIKE mara-matnr DEFAULT '220705' MODIF ID ro.

AT SELECTION-SCREEN OUTPUT.
  LOOP AT SCREEN.
    IF SCREEN-GROUP1 = 'RO' .
      SCREEN-INPUT = '0'.
      MODIFY SCREEN.
    ENDIF.
  ENDLOOP.

START-OF-SELECTION.
  WRITE: / nao_mexe.

Seriously though, the idea of write-protecting parameters is interesting if it depends on the values of other parameters. For example, if ‘save file’ is checked, you can add the file name, if not, it is write-protected. Here’s my suggestion: just add the conditions you want to the code.

Greetings from Abapinho.

Um comentário a “Unparameterisable parameters”

  1. Felipe Fontes Diz:

    Cara bem legal sua Página de explicações, continue, precisamos dela abraços!!

Deixe um comentário


About Abapinho
Abapinho runs on WordPress
Articles (RSS) e Comments (RSS).