Creation of screens

[Former Member]

Hi,

Can u let me know as to how I create , view or edit a screen.

[abdul_hakim]

Hi

For creating views go to the SE11.

I would suggest you to check the corresponding ABAP Document in http://help.sap.com

Cheers,

Hakim

[former_member156446]

if you know the program that is calling the screen and the screen number you can see using SE51 Tr.

or se80 if you know the package name and the screen number

[Former Member]

Hi Devraj,

Please check this link

Dialog Programming

http://sap.mis.cmich.edu/sap-abap/abap09/index.htm

SCREENS

http://help.sap.com/saphelp_nw04/helpdata/en/e4/2adbef449911d1949c0000e8353423/frameset.htm

Best regards,

raam

[Former Member]

hi....

take the function group from your table maintainenence generator and got to se80...

In se80 you edit the screen for your table.

whatevr changes you want in the table maintaiannece can be done through se80 and the function group.

[Former Member]

Hello,

U can view screens from transaction SE80 where u can enter program name or function group name.

U can also see it in SE38 transaction by clicking on hierarchy button which next to activation button on appliction toolbar of the window.

In both cases hierarchy dropdown will appear on left side of screen, where u can click on screens folder and select the desiered screen.

Reward if useful.

[Former Member]

Hi,

If your question is just how to create the screen , view and edit, then

we need to go to SE51(Screen Painter) or SE80 (Object Navigator) where in we can create a screen in a program.

we need to right click on program name in SE80 then we get drop down menu having Create -- > Screen.

Once done with creation of screen we can double click to view the screen and edit it by clicking change button.

I hope this will help you.

Plz reward if useful.

Thanks,

Dhanashri.

[Former Member]

Hi Devaraj,

Open ur program in SE80.

Right Click on ur program name on the left side of ur screen (Object list).

Place cursor on Create -> click on Screen.

A prompt appears for u to enter a screen number, enter any number excepting 1000 as it is reserved for standard selection screens.

Click on continue.

Screen painter appears with the Flow Logic pseudo code.

Click on the Layout button on ur Application toolbar, to design the screen( u need to have the screen painter patch installed in ur system beforehand).

Try till this and let me know if ot was of use.

[Former Member]

Hi.

Any screen can be identified by program name and screen number

To create your own screens, go to screen painter (i.e., SE51) click on layout button which takes u to screen designing part where insert all the fields u want, u may refer directly dictonary table fields using dictonary fields icon provided on toolbar. u can place pushduttons on screen for whose function code is manditory.

In the initial screen of screen painter go to flow logic, there exists two events process before output and process after input which are automatically given along with two modules commented each. Uncomment these two modules and write the code which u need to process.

Process before output event is processed just before screen is going to display. So write the code which u want to process before the screen going to display in module under this event(i.e, giving values to field, disableing field etc,). There is a screen table which provides screen information, loop at that table and preform necessary changes to it. the only option we can perform to this table is MODIFY SCREEN.

SCREEN TABLE FIELDS

LOOP AT SCREEN .

...

ENDLOOP.

Effect

The statements LOOP AT SCREEN ... ENDLOOP define a loop around a statement block. For every screen element of the current dynpro, to which a dynpro field is assigned, one loop pass is executed. After the LOOP statement either the predefined workarea screen or the workarea wa (when using INTO) contains the properties of the respective screen element. wa must have the same data type as screen.

While processing a table control or a step loop (that is, within a LOOP loop of the dynpro flow logic), for its screen elements the current properties are determined in the current row or group. Outside of the processing of a table control or step loop, for its screen elements the statically predefined properties of all rows or groups are determined.

The table below shows the components of screen and their assignment to the field properties in the dynpro.

Component Length Type Attribute Description

name 132 c Name Name

group1 3 c Group1 Modification group

group2 3 c Group2 Modification group

group3 3 c Group3 Modification group

group4 3 c Group4 Modification group

required 1 c Required-entry field Mandatory field

input 1 c Input input-enabled field

output 1 c Output display field

intensified 1 c Intensified intensified field

invisible 1 c Invisible invisible element

length 1 x visLength Field length

active 1 c Input/Output/Invisible active field

display_3d 1 c Two-dimensional Box

value_help 1 c Input help Input help key

request 1 c - Input exists

values_in_combo 1 c Dropdown listbox Value help exists

The component name in the loop contains the name of the current dynpro field. The components group1 to group4 can contain three-character IDs, which were assigned to the current screen element in its definition. These IDs allow you to combine the screen elements in up to four different modification groups. In the statement block after LOOP AT SCREEN, these can be queried in logical expressions in order to process several elements in the same way.

The other components of table screen represent the display properties of the current screen element. With the exception of length, they can contain 0 or 1, where 1 is "active" and 0 is "inactive".

Except active, all components of structure screen directly correspond to one attribute of the current screen element. The component active has no match in the attributes. If you change its content with MODIFY SCREEN, this affects the attributes Input, Output and Invisible and thus the components input, output and invisible of structure screen.

MODIFYING SCREEN

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

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.

Where in process after input(PAI), this is the event that triggers after user had entered values on screen. Using sy-ucomm we can write our code for push buttons, and checkings all are done in pai module.

there exists two more events process on value help( used for F1 help) and process on value request(used for F4 help).