User Tools

Site Tools


abap:screens

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
abap:screens [2017/02/13 17:10]
ginko [Statuts GUI]
abap:screens [2018/06/25 16:33] (current)
ginko [Manipulation dynamique des champs]
Line 49: Line 49:
  
 [[http://​help.sap.com/​saphelp_banking60/​helpdata/​en/​9f/​dbab6f35c111d1829f0000e829fbfe/​content.htm|Help SAP]] : Setting Attributes Dynamically. Avec notamment la table de vérité pour les champs ACTIVE, INPUT, OUTPUT, and INVISIBLE. [[http://​help.sap.com/​saphelp_banking60/​helpdata/​en/​9f/​dbab6f35c111d1829f0000e829fbfe/​content.htm|Help SAP]] : Setting Attributes Dynamically. Avec notamment la table de vérité pour les champs ACTIVE, INPUT, OUTPUT, and INVISIBLE.
 +
 +<code abap> ​  LOOP AT SCREEN.
 +       IF screen-name = wgv_cur.
 +         IF cur = line.
 +           break user.
 +           ​screen-input = 1.
 +           ​MODIFY SCREEN.
 +         ​ENDIF.
 +       ​ENDIF.
 +     ​ENDLOOP.</​code>​
 +
 +There are certain hierarchy rules between the components ACTIVE, INPUT, OUTPUT, and INVISIBLE. They also have different effects depending on their respective static settings.
 +
 +The ACTIVE component has no equivalent in the element attributes. Instead, it changes the components INPUT, OUTPUT, and INVISIBLE.
 +
 +At the beginning of the PBO, ACTIVE is always set to 1, regardless of the static attribute settings. Setting ACTIVE to 0 automatically sets INPUT = 0, OUTPUT = 0, and INVISIBLE = 1. Any other changes to the settings of INPUT; OUTPUT, and INVISIBLE to the current screen element are ignored. Conversely, setting INPUT = 0, OUTPUT = 0, and INVISIBLE = 1 automatically sets ACTIVE to 0, and any further assignment to ACTIVE for the current screen element will be ignored. The setting ACTIVE = 1 has no other effect on the attributes. The only purpose of the ACTIVE component is to allow you to make a screen field inactive through a single assignment. You should particularly note that a module call linked to a FIELD statement in the screen flow logic is always executed, even when SCREEN-ACTIVE = 0 for the field in question. If you want to prevent a module from being processed for an inactive field, you must specify the FIELD- and MODULE statements separately.
 +
 +There are eight possible combinations of ACTIVE, INPUT, OUTPUT, and INVISIBLE, that have the following effect on screen fields:
 +
 +^ACTIVE^INPUT^OUTPUT^INVISIBLE^Effect^
 +|1|1|1|0|Screen field is displayed, even if Invisible is set statically. Field contents are displayed.Ready for input, even if Input is not set statically. However, not ready for input if the Output only is set statically.|
 +|1|1|0|0|Screen field is displayed, even if Invisible is set statically, except when Output only is set statically. Field contents are not displayed. Ready for input, even if Input is not set statically.|
 +|1|0|1|0|Screen field is displayed, even if Invisible is set statically. Field contents are displayed. Not ready for input, even if Input is set statically.|
 +|1|0|0|0|Screen field is displayed, even if Invisible is set statically, except when Output only is set statically. Field contents are not displayed. Not ready for input, even if Input is set statically.|
 +|1|1|1|1|Screen field is displayed, even if Invisible is set statically, except when Output only is set statically. Field contents are not displayed. Ready for input, even if Input is not set statically. User input is masked by asterisks ( *).|
 +|1|1|0|1|Screen field is displayed, even if Invisible is set statically, except when Output only is set statically. Output is masked by asterisks ( *). Ready for input, even if Input is not set statically. User input is masked by asterisks ( *).|
 +|1|0|1|1|Screen field inactive. Screen field is not displayed, regardless of the static attributes.|
 +|0|0|0|1|Screen field inactive. Screen field is not displayed, regardless of the static attributes.|
 +
 +If a field is statically-defined as Output only, setting INPUT = 1 has no effect. INPUT is always 0 for these fields. Masking user input by asterisks ( *) can be used for entering user passwords.
 +
 +If a whole line becomes invisible when you make fields invisible, the screen is automatically made smaller. You can, however, switch off this attribute in the static screen attributes by selecting Switch off runtime compression.
 +
 +**REQUIRED**
 +
 +When you set REQUIRED = 1, a field that is ready for input is made mandatory. Users can only leave the screen when all mandatory fields contain an entry. Exception: Function codes of type E and modules with the AT EXIT-COMMAND addition.
 +
 +**DISPLAY_3D**
 +
 +When you set DISPLAY_3D = 0, the three-dimensional frame for input/​output fields is removed. You cannot use DISPLAY_3D = 1 to create a three-dimensional effect for text fields or screen fields with the Output only attribute.
 +
 +**VALUE_HELP**
 +
 +Setting VALUE_HELP to 0 or 1 switches the input help button off and on respectively.
 +
 +**INTENSIFIED**
 +
 +If you set INTENSIFIED = 1, the field contents of input fields are changed from black to red. The contents of output fields are changed from black to blue.
 +
 +**LENGTH**
 +
 +You can set the LENGTH component to a value shorter than the statically-defined output length ( vislength) for input/​output fields and Output only fields. This allows you to shorten their output length. You cannot shorten other screen elements, or lengthen any screen elements.
 +
 +**REQUEST**
 +
 +Setting REQUEST = 1 for a field that is ready for input has the same effect in the PAI event as if the user had changed the field contents. This means that a conditional module call using ON REQUEST or ON CHAIN-REQUEST would be executed regardless of whether the user really changed the field. REQUEST is automatically reset to 0.
  
 ===== Affichage dynamique des icônes ===== ===== Affichage dynamique des icônes =====
abap/screens.txt · Last modified: 2018/06/25 16:33 by ginko