Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Input field enabled codes

Former Member
0 Likes
1,091

May I know what is the codes to enable an input field with the name "IO_NAME"?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,056

In the screen painter, when you define a field, in the screen attributes for that field, you can specify the Screen group. There will be four Groups.

Specifying three-character identifiers for modification groups 1 to 4 allows you to group fields together. You can process them all at the same time in the program using SCREEN modification statements.

If, for example, you want to make all fields that of the modification group 2 with the ID 222 invisible, you can define the following code in the PBO module:

LOOP AT SCREEN.

IF SCREEN-GROUP2 = '222'.

SCREEN-INVISIBLE = '1'.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

Hope this helps

Vinodh Balakrishnan

8 REPLIES 8
Read only

former_member194669
Active Contributor
0 Likes
1,056

loop at screen.
   if screen-name = 'IO_NAME'.
      screen-input = '1'.
      modify screen.
    endif
endloop.
Read only

0 Likes
1,056

What is the word 'screen' , 'name and 'input' for? I should reply these words with what or no need?

Read only

0 Likes
1,056

screen is a system structure which will be filled only during runtime.

you can have a look at SE11>table name (SCREEN)

use the code given, it will work..

Read only

Former Member
0 Likes
1,056

From the link provided, I saw that the name attribute of this line

if screen-name = 'IO_NAME'.

It is suppose to write as group1 or group2. Can anyone explain what is these group 1 or group2?

Read only

Former Member
0 Likes
1,057

In the screen painter, when you define a field, in the screen attributes for that field, you can specify the Screen group. There will be four Groups.

Specifying three-character identifiers for modification groups 1 to 4 allows you to group fields together. You can process them all at the same time in the program using SCREEN modification statements.

If, for example, you want to make all fields that of the modification group 2 with the ID 222 invisible, you can define the following code in the PBO module:

LOOP AT SCREEN.

IF SCREEN-GROUP2 = '222'.

SCREEN-INVISIBLE = '1'.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

Hope this helps

Vinodh Balakrishnan

Read only

0 Likes
1,056

means I must write the loop codes at the screen itself and not in the report?

Read only

0 Likes
1,056

Hi,

You can modify the screen attributes like, input, display, hide etc... using the modify screen statement. It is placed in loops.

See the documentation for this:

Syntax

MODIFY SCREEN .

Effect

This statement can be used in the statement block after LOOP AT SCREEN only and makes sense only during PBO processing. If FROM is not specified, MODIFY SCREEN modifies the attributes of the current screen element with the values from the predefined screen work area. If a wa work area is specified, its contents are used for the modification.

The wa work area must have the same data type as screen. The name component must contain the name of the current screen element, otherwise the statement is not executed. nweisung nicht ausgeführt. Up to the group1 to group4 and length components, all remaining components of screen and wa must contain either the value 0 or 1. The value 0 deactivates the corresponding field attribute, and 1 activates it.

If MODIFY SCREEN is executed during PBO processing, the modified attributes for the display of the screen affect the current dynpro after PBO processing. The attributes of the screen element of the dynpro are reset to their static attributes at the start of each PBO processing, so that the execution of MODIFY SCREEN during PAI processing does not effect the display of the following screen.

The active component

The active component is used to set the input, output and invisible components at once. At the start of PBO processing, the active component always has the value 1. If active is set to 0 with MODIFY SCREEN, input and output are automatically set to 0 and invisible is set to 1. Other values in input, output and invisible are ignored. Conversely, setting input and output to 0 and invisible to 1 automatically sets active to 0 and a different value in active is ignored.

Modifications in Table Controls and Step Loops

During processing of a table control or a step loop, the changes affect the current line of the table control or the current step loop group. Before the processing of a table control, the change to the attributes of a screen element that is part of a line in the table control does not effect the table control, since the values are transferred from the structure created using CONTROLS. Before a step loop is processed, the change to the attributes of a screen elements that is part of a step loop group affects all groups in the step loop.

Modifications to Tabstrip Controls

If the active component for a tab title of a tabstrip control is set to 0, the whole tabstrip page is hidden.

Example

In the following PBO module, an input field called val is made mandatory and converted to display in the foreground.

MODULE modify_0100 OUTPUT.

LOOP AT SCREEN.

IF screen-name = 'VAL'.

screen-required = '1'.

screen-intensified = '1'.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

ENDMODULE.

Regards,

Renjith Michael.