Get Example source ABAP code based on a different SAP table
• SCREEN ABAP_STRUCTURE
ABAP_DYNPRO - The Structure SCREEN> Most components of the structure SCREEN >> from the ABAP Dictionary correspond to the properties of a screen element on a dynpro. Data objects with the data type SCREEN> can be used as a work area in the following ABAP statements:
in LOOP AT SCREEN>>, to read the screen element properties of a dynpro,
in MODIFY SCREEN>>, to modify the screen element properties of a dynpro. The following table shows the components of SCREEN>, their assignment to the field properties in the dynpro, and the possible values. Component>Length>Type>Property> Value>Meaning> name>132c>Name>name>Name group1>3c>Group1>id1>Modification group group2>3c>Group2>id2>Modification group group3>3c>Group3>id3>Modification group group4>3c>Group4>id4>Modification group required>1c>Mandatory field>0>, 1> , 2>Mandatory or recommended field input>1c>Input>0>, 1>Input-ready field output>1c>Output>0>, 1>Display field intensified>1c>Light>0>, 1> Highlighted field invisible>1c>Invisible>0>, 1> Invisible element length>1x><(>VisLg<)>>...>Field length active>1c>-0>, 1>Active field display_3d>1c>Two-dimensional>0>, 1 >Frame value_help>1c>Input help>0>, 1>, 2>Input help button request>1c>-0>, 1>Input exists values_in_combo>1c>Dropdown list box>0>, 1>Input help exists The component name> contains the name name> of the current dynpro field in the loop. The components group1> to group4> can contain three figure identifiers id1> to id4>, which were assigned to the current screen element when it was defined. These identifiers allow the screen elements to be grouped together in up to four different modification groups> . These can be queried in logical expressions in the statement block after LOOP AT SCREEN>> to process multiple screen elements in the same way. The remaining components of the structure SCREEN> (apart from request>) show the display properties of the current screen element. Apart from length>, they can have the value 0 or 1, where content 1 means active> and content 0 means inactive>. In addition, required> and value_help> can also have the value 2:
With required>, value 2 means a recommended field which is displayed on the screen in the same way as a mandatory field (value 1) but no check is performed.
With value_help>, value 2 means that the input help button is always displayed, whereas value 1 means that the button is only displayed if the cursor is positioned on the dynpro field. Except for active> and request>, all components of the structure SCREEN> correspond directly to a property of the current screen element.
The component active> does not have a corresponding property. A change of its content using MODIFY SCREEN> > affects the properties input>, output> and invisible>, and correspondingly the components input>, output> and invisible> of the structure SCREEN>.
The component request> has the following meaning:
It is set to the value 1 by the runtime framework if the event PAI occurs, if user input exists in the dynpro field.
Using MODIFY SCREEN>>, its content can be set to the value 1 at PBO time to simulate user input. If the component request> has the value 1 for a dynpro field at PAI time, those dialog modules are executed that are called for this field using the additions ON REQUEST> and ON CHAIN-REQUEST> after the dynpro statement FIELD>>. BEGIN_SECTION SAP_INTERNAL_HINT The component COLOR> of structure SCREEN> is not evaluated. Besides INTENSIFIED> there is no other way to affect the color of a screen field. END_SECTION SAP_INTERNAL_HINT