Dialog Programming ("Required" Screen Field) Processing

Hey Guys,
I have a screen that contains a field that I have set as "Required". I also have 2 buttons on the Function Keys bar
BACK -> LEAVE TO SCREEN 0. and
EXIT -> LEAVE PROGRAM.
My problem is that I want to process these buttons even if the user has not entered any information in the "Required" field, since the user wants to leave the screen and not process data.
Is there a way to bypass the "Required" clause?
Regards,
Madhur

Hi Madhur,
This <a href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbaa9535c111d1829f0000e829fbfe/content.htm">link</a> gives you the exact inofrmation you need along with wonderful explanation and illustration.
Regards,
Anand Mandalika.

Similar Messages

Drop down in Dialog programming for a field on the screen

Hi Friends !
I have 2 screen fields zfield1- Indicator and zfield- answer .
The user wants a drop down for indicator as X or Blank to choose from and for answer the user wants YES or NO as the dropdown .
How do i create these dropdowns for the fields ?
Do I need to create search help or does dialog give other options to add these dropdowns.
Please advise .
Thanks!!

set zfield1 up where it's data element is using the domain YESNO.
For answer I use this routine a lot.
PERFORM get_dd07t_value USING 'ZLMCONTTYPE'
                              out_rec-ctype
                              out_rec-ctype_desc.
*&      Form get_dd07t_value
     -->P_DOMNAME text
     -->P_KEY      text
     -->P_RESULT   text
FORM get_dd07t_value USING    p_domname
                              p_key
                              p_result.
CLEAR p_result.
SELECT SINGLE ddtext INTO p_result
    FROM dd07t
    WHERE domname = p_domname
      AND ddlanguage = sy-langu
      AND domvalue_l = p_key.
IF sy-subrc NE 0.
    p_result = 'None'.
ELSE.
    p_result = dom_rec-ddtext.
ENDIF.
ENDFORM.                    " get_dd07t_value

Dialog Programming Requirement

Hello Guys!
Hope u all doing well.
Any one have done any real time scenario on dialog programs
Any Custom module pool program u ve developed.
Pls tell the requirement
4r which records, tables Used.
Pls give ur solution for the development with steps by steps in detail.
Hoping for your replies eagerly.
Thanks all.

Hi,
check below code , use delete_text after get_text_as_r3table method.
 CALL METHOD editor->get_text_as_r3table
 IMPORTING
 table = li_text_table
 EXCEPTIONS
 error_dp = 1
 error_cntl_call_method = 2
 error_dp_create = 3
 potential_data_loss = 4.
 CALL METHOD editor->delete_text
 EXCEPTIONS
 error_cntl_call_method = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
CALL METHOD editor->set_text_as_r3table
 EXPORTING
 table = li_text_table
 EXCEPTIONS
 error_dp = 1
 error_dp_create = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
I have done the coding using above methods which is exactly like your requirement , it is working fine for me.
Regards
Appana
Message was edited by: L Appana

Dialog programming - bring screen in front

I have a requirement where I am supposed to call a module pool screen in search help exit of material using call transaction. It is working when i use F4 help from MM03, but when i am using the same search help from a custom sceen, the new screen opens behind the F4 help screen. Is there a way i can bring that screen in front?
Thanks,
HD

Hi,
try the following:
In SE51 of your screen select screen attributes and change screen type to Modal dialog box Then it should come to front!
Regards,
Klaus

Transaction programming - Making screen fields 'output only'

Hi all,
I have a problem concerning a screen - it is so that the screen is used by several transactions - Create 'plan', Display 'plan' and Change 'plan'.
When it's called from the 'Display' transaction I want the screen to be output-only. So I wrote something like this:
MODULE modify_screen OUTPUT.
if sy-tcode = 'ZAF03'.
loop at screen.
if screen-name cp 'I_AFPL*'.
screen-input = '0'.
modify screen.
endif.
endloop.
endif.
ENDMODULE.
The problem is that this screen contains a tabstrip control. The subscreens on the pages of the tabstrip control contain table controls, and the table controls refer to some internal tables in the program.
All the fields which I want to make 'output only' are fields of internal tables beginning with 'I_AFPL' that's why the condition...
This works very well for the fields on the main screen, but not for the fields of the table controls on the tabstrip control... and I'm calling that module from the main screen and also from the subscreens of the 'pages' of the tabstrip control. In the debugger I see that the input is set to 0 but when the screen 'comes on screen' I can still do input in those fields...
Can anyone tell me what I'm doing wrong?
Thanks,

Hi Ashish,
for table control to disable a column we use the cols property in the screen'..the tablecontrol-cols is set to zero to inactivate a column
Now assume the name of your table control is ZTABLECONT..double click on the screen painter on the table control..these 2 names must be the same....
if you need to disable columns of table control as a part of user action..like say click of a button..it can be entered in PAI by checking the sy-ucomm
data declaration:
data : cols like line of ZTABLECONT-cols.
Case sy-ucomm.
when 'PUSH'.
loop at ZTABLECONT-cols into cols.
if cols-screen-input = '1'.
cols-screen-input = '0'.
endif.
modify ZTABLECONT-cols from cols index sy-tabix.
endloop.
endcase.
This will disable all the columns
for a particular column do the following
For this imagine you have 5 columns
in the below code
index = 1 => column 1
index = 2 => column 2
index = 3 => column 3
index = 4 => column 4
index = 5 => column 5
in the below code , only column2 will be disabled....
so whicever column you want to disable ..just give the index
for multiple disabling..just write the code accordingly
LOOP AT ZTABLECONT-cols INTO cols WHERE index = 2.
IF cols-screen-input = '1'.
cols-screen-input = '0'.
ENDIF.
MODIFY ZTABLECONT-cols FROM cols INDEX sy-tabix.
ENDLOOP.
Pls check and revert....
Regards
Byju

Dialog Programing: Output screen layout is different from actaul layout

Hi,
I have developed screen layout in SE51 and same is used in my program.Program is working fine but the problem is in column order.I designed layout in SE51 by copying structure from ABAP dictionary and same has been used in my program but output layout column order is completely different from SE51 screen layout.When i check this on Se51,everything is in order.
My program is referring the same screen number and program.there is only one screen i.e 100.
How do we fix this problem.
Regards,

Looks like, your table settings got changed for the table control on the screen.
Run your program.
Now, on the screen you can find out the "Table Settings" in the Top Right corner of the Table control as ICON.
Press the Icon and it will bring the Table Settings screen.
In the Current Settings, choose the Basic Settings ... save and close.
Regards,
Naimesh Patel

Table for Screen Field Properties

Hi Guys,
I have strange requirement.
Lets say i have designed 5 fields in the Dialog Program. 2 fields belongs to Group1,another 2 fields belongs to Group2 and 3rd field is belongs to group3.
Where can i find those values (I mean which table). I belive it should be Program,screen no and data type.
Note : Groups you can set in Attributes of the field in Dialog Program.
Thanks
Poorna

Setting Screen Field Attributes
Every screen field has attributes that you set in the Screen Painter when you define the
screen. At runtime, you may want to change these attributes, depending on what
functions the user has requested in the previous screen. At runtime, attributes for each
screen field are stored in a memory table called SCREEN. You do not need to declare
this table in your program. The system maintains the table for you internally and updates
it with every screen change.
The memory table SCREEN contains the following fields:
Name Length Description
NAME 30 Name of the screen field
GROUP1 3 Field belongs to field group 1
GROUP2 3 Field belongs to field group 2
GROUP3 3 Field belongs to field group 3
GROUP4 3 Field belongs to field group 4
ACTIVE 1 Field is visible and ready for input
REQUIRED 1 Field input is mandatory
INPUT 1 Field is ready for input
OUTPUT 1 Field is for display only
INTENSIFIED 1 Field is highlighted
INVISIBLE 1 Field is suppressed
LENGTH 1 Field output length is reduced
DISPLAY_3D 1 Field is displayed with 3D frames
VALUE_HELP 1 Field is displayed with value help
To activate a field attribute, set its value to 1. To deactivate it, set it to 0. When you set
the ACTIVE attribute to 0, the system suppresses the field and turns off the ready for
input attribute. The user can neither see the field nor enter values into it.
Note
You can define values for each of these attributes in the Attribs. for 1 field section in
the field list of the Screen Painter. If you need more information about attribute
meanings, see BC ABAP/4 Workbench Tools.
Modifying the Screen SAP AG
Setting Screen Field Attributes
32u20134 May 1997
As an example of modifying the screen dynamically, start with transaction tz50
(development class SDWA).
The transaction consists of two screens. In the first screen the user can enter flight
identifiers and either request flight details (by pressing a Display pushbutton) or press the
Change pushbutton to change the data of screen 200.
The field attributes are now set dynamically, according to whether the Display button or
the Change button was selected. In both cases the same screen is now called, but with
different field attributes.
If the same attributes need to be changed for several fields at the same time, these fields
can be grouped together. For example, in order to change the fields in screen 200
dynamically, we assign these fields in the Screen Painter to the group MOD. You can
specify up to four modification groups for each field. The contents of the Groups field
are stored in the SCREEN table.
The changes to the attributes of the fields in this group can be implemented in a PBO
module:
SAP AG Modifying the Screen
Setting Screen Field Attributes
May 1997 32u20135
MODULE MODIFY_SCREEN OUTPUT.
CHECK MODE = CON_SHOW.
L0OP AT SCREEN.
CHECK SCREEN-GROUP1 = u2019MODu2019.
SCREEN-INPUT = u20190u2019.
MODIFY SCREEN.
ENDLOOP.
ENDMODULE.
The memory table SCREEN contains each field of the current screen together with its
attributes.
The LOOP AT SCREEN statement puts this information in the header line of this system
table.
In this example taken from transaction tz50, if the user chooses Display then SCREENINPUT
is set to u20190u2019 and all fields belonging to the MOD group thus become display-only
fields.
Because attributes have been changed, the MODIFY SCREEN statement is used to write
the header line back to the table.
Modifying the Screen SAP AG
Changing Screen Field Attributes with the Function Field Selection

Difrence between module pool and dialog programming

Hi abapers,
can plz tell me difrence between module pool and dialog programming.

Hi,
Actually Dialog Programming is Module pool Programming.
Please go thru this , see if your dbout gets clear.
Basic components of dialog program?
- Screens (Dynpros)
- Each dialog in an SAP system is controlled by dynpros.A dynpros consists of a screen
And its flow logic and controls exactly one dialog step.
- ABAP/4 module Pool.
Each dynpro refers to exactly one ABAP/4 dialog program .Such a dialog program is also called a module pool ,since it consists of interactive modules.
Regards,
Priyanka.

Dialog programming and module-pool programming

Can someone tell em the difference between dialog programming and module-pool programming ?

Hi Vinod ,
Actually Dialog Programming is Module pool Programming.
Please go thru this , see if your dbout gets clear.
Basic components of dialog program?
- Screens (Dynpros)
- Each dialog in an SAP system is controlled by dynpros.A dynpros consists of a screen
And its flow logic and controls exactly one dialog step.
- ABAP/4 module Pool.
 Each dynpro refers to exactly one ABAP/4 dialog program .Such a dialog program is also called a module pool ,since it consists of interactive modules.
Regards,
AShwini

Dialog programming - How to place a select-option field in a dialog screen

Hi all,
In Dialog Programming, How to place a select-option field in a dialog screen.
Kindly give me some example code...
Thanks,
Jaffer Ali.S

hi Ali,
U can add select-options in ur module pool by using SELECTION-SCREEN BEGIN OF SCREEN <scrn> AS SUBSCREEN command.
check this link for reference.....
http://help.sap.com/saphelp_47x200/helpdata/en/e7/deb237b9a9a968e10000009b38f8cf/frameset.htm
Example Code :
DATA : ok_code TYPE sy-ucomm.
SELECTION-SCREEN BEGIN OF SCREEN 1010 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS: p_rad1 RADIOBUTTON GROUP grp1 DEFAULT 'X',
 p_rad2 RADIOBUTTON GROUP grp1,
 p_rad3 RADIOBUTTON GROUP grp1.
SELECT-OPTIONS: s_matnr FOR mara-matnr,
 s_matkl FOR mara-matkl,
 s_mtart FOR mara-mtart.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN END OF SCREEN 1010.
START-OF-SELECTION.
CALL SCREEN 100.
*& Module STATUS_0100 OUTPUT
MODULE status_0100 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
CALL SCREEN 1010 .
ENDMODULE. "status_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
 text
MODULE user_command_0100 INPUT.
CASE ok_code.
 WHEN 'EXIT'.
 LEAVE PROGRAM.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
SCREEN 100 ****************
PROCESS BEFORE OUTPUT.
MODULE status_0100.
CALL SUBSCREEN sub_1010 INCLUDING sy-repid '1010'.
***** where sub_1010 is name of sub-screen area
PROCESS AFTER INPUT.
CALL SUBSCREEN sub_1010.
MODULE user_command_0100.
<<< REMOVED BY MODERATOR >>>
Harimanjesh AN
Edited by: Marcelo Ramos on Dec 17, 2008 7:54 PM

Process on value request in Dialog screen based on value of screen field

Hello Gurus,
I have a check box on a dialog screen. If the checkbox is checked, based on that I want the other field on the same dialog screen to follow logic for F4 dropdown.
Now I know if I want to write this, I have to write this in Process on value-request. But how do I get the value of the check box checked or not on the same screen in Process on value-request.
If it had been a simple selection screen I would have defined the check box as
Parameter: v_checkbox as checkbox user-command uc1.
But how do I handle above situation in dialog screen case ?
Please help.
Regards,
Jainam.
Edited by: Jainam Shah on Sep 29, 2009 6:19 PM

Hi Shah,
You have the addition for MODULE statement as ON INPUT.
Eg : FIELD <screen field> MODULE <module> ON INPUT.
You can give the check box field name in the above statement.
If you want to find as soon as the check box is checked, you can find it here.
Or else, in the addition ON REQUEST
you can see for the check box field value whether it is checked or not.
Thanks,
Prasad

Reset Screen field in dialog program

Hi,
I have four inputs fields in my dialog program, i select based on f4 value and insert into table. Once i press save, the fourth
input field must be automatically reset to blank.So that i again input some value and save.
How to achieve this?

Hi Renjit ,
Once your save operation is successful , clear the corresponding varaible in the program ..
Regads,
Arun

Screen sequence processing when using modal dialog box

I have been struggling with a dialog program which I have written. I have a screen which has 2 radiobuttons and a check box (screen 100). If the checkbox is marked, a modal dialog screen pops up (screen 150). If I complete both input fields on screen 150, I can go through to screen 200, then back out of screen 200 to screen 100, and then I can back out 100 to screen 0.
The problem I have is the validation I have put in screen 150 if one or both input fields have no values or if I want to exit screen 150. If I exit screen 150, in order to get back to screen 100 in the main screen I need to do CALL SCREEN 100 as if I use SET SCREEN 100, 100 then appears in my modal dialog box screen.
If I try to back out of screen 100 to screen 0, the program then brings up screen 150 in the PAI part of the module and then go to screen 0 when I close screen 150 even though I have coded SET SCREEN 0. LEAVE SCREEN. in the user command module of screen 100. Here is my code:
screen 100
PROCESS BEFORE OUTPUT.
MODULE status_0100.
PROCESS AFTER INPUT.
MODULE user_command_0100.

Modules for 100
*& Module STATUS_0100 OUTPUT
* text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'ZL_PWB_GR1'.
SET TITLEBAR 'ZL_PWB_GR1'.
CLEAR: w_hse_stock, w_new_product, wa_sto, w_reverse,
 mara-matnr, mkpf-mblnr.
PERFORM release_lock.
REFRESH CONTROL 'TC_GR' FROM SCREEN 0200.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
* text
MODULE user_command_0100 INPUT .
CASE ok_code.
 WHEN 'ENTER'.
 IF w_reverse = space.
 CALL SCREEN 0200.
 ELSE.
 CALL SCREEN 0150 STARTING AT 30 2
 ENDING AT 75 5.
 ENDIF.
 WHEN 'BACK' OR 'EXIT' OR 'CANC'.
 w_pai = c_yes.
 SET SCREEN 0.
 LEAVE SCREEN.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
screen 150
PROCESS BEFORE OUTPUT.
MODULE status_0150.
PROCESS AFTER INPUT.
MODULE exit_command_0150 AT EXIT-COMMAND.
FIELD mara-matnr MODULE check_matnr.
FIELD mkpf-mblnr MODULE check_art_doc.
Modules for 150
MODULE user_command_0150.
*& Module STATUS_0150 OUTPUT
* text
MODULE status_0150 OUTPUT.
SET PF-STATUS 'GR_REV'.
SET TITLEBAR 'GR_REV'.
ENDMODULE. " STATUS_0150 OUTPUT
*& Module exit_COMMAND_0150 INPUT
* text
MODULE exit_command_0150 INPUT.
IF sy-ucomm = 'EXIT'.
 CALL SCREEN 100.
ENDIF.
ENDMODULE. " exit_COMMAND_0150 INPUT
*& Module check_matnr INPUT
* Check if issues has been filled and if issue is a valid article no.
MODULE check_matnr INPUT.
DATA: l_matnr TYPE matnr.
IF mara-matnr IS INITIAL.
 MESSAGE i010(ad) WITH 'Issue no. required'.
 EXIT.
ELSE.
 SELECT SINGLE matnr FROM mara INTO l_matnr
 WHERE matnr = mara-matnr.
 IF sy-subrc NE 0.
 CLEAR l_matnr.
 MESSAGE i010(ad) WITH 'Issue does not exist'.
 ENDIF.
ENDIF.
ENDMODULE. " check_matnr INPUT
*& Module check_art_doc INPUT
* text
MODULE check_art_doc INPUT.
IF mkpf-mblnr IS INITIAL.
 MESSAGE i010(ad) WITH 'Article document no. required'.
 EXIT.
ELSE.
 PERFORM get_art_doc USING mara-matnr
 mkpf-mblnr.
 IF sy-subrc NE 0.
 MESSAGE i010(ad) WITH 'No article document exists for this issue'.
 ENDIF.
ENDIF.
ENDMODULE. " check_art_doc INPUT
*& Module USER_COMMAND_0150 INPUT
* text
MODULE user_command_0150 INPUT.
CASE sy-ucomm.
 WHEN 'ENTE'.
 IF mara-matnr NE space AND mkpf-mblnr NE space.
 CALL SCREEN 200.
 ELSE.
* MESSAGE i010(ad) WITH 'Please fill in both fields'.
 SET SCREEN 150.
 ENDIF.
ENDCASE.
ENDMODULE. " USER_COMMAND_0150 INPUT
Any suggestions or pointers would be greatly appreciated as I am going round in circles.
Thanks
Larissa

Have got around this by removing the references to SET SCREEN 150. This way, I can get around the screen sequencing. It just means that I cannot keep my screen 150 in view if a validation message occurs but for now it will do for what I need.
Thank you for your help anyway.
Larissa

Making attributes of field dynamic in dialog program in layout editor.

hi,
to make a field required or possible or hidden, we define its attributes in attributes in layout editor.
is it possible to make attributes of fields that we define in layout editor dynamic ?
if functional people want to make some field non-mandatory or mandatory then they go in configuration, and do it. so does this mean that the attributes of the fields that we define in layout editor during dialog program can be made dynamic.
how is this possible ? because attributes are selected using dropdown, its not a code ?
please help in solving this mystery...

Screen Modifications --
demo_dynpro_modify_simple
demo_dynpro_modify_screen
Please dont forget to reward points
Sudheer

Select option in Dialog program screen

Hi friends,
do we have any way to get a select option displayed in dialog programming ?
or
create a screen field with the properties of a select option in dialog screen ?
or
any standard function module to support this scenario ?
Thanks and Regards
Sakthi.

Hi,
i don't know you checked it or not, but i am able to do it, i send the screen shot also to you check it..
it is possible,with some coding also check it once...
REPORT ZTEST_SCREEN .
DATA : BEGIN OF IT_DYNPFIELDS OCCURS 3.
 INCLUDE STRUCTURE DYNPREAD.
DATA : END OF IT_DYNPFIELDS.
DATA: TEST(10) TYPE C.
RANGES: R_UNAME FOR SY-UNAME.
DATA: V_USERNAME LIKE SY-UNAME.
DATA : V_PROG LIKE D020S-PROG VALUE 'ZTEST_SCREEN',
 V_DNUM LIKE D020S-DNUM VALUE '0100'.
CALL SCREEN 100.
*& Module STATUS_0100 OUTPUT
* text
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'TEST'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
* text
MODULE USER_COMMAND_0100 INPUT.
CASE SY-UCOMM.
 WHEN 'BACK'.
 LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Module GET_CURSOR_USERNAME INPUT
* text
MODULE GET_CURSOR_USERNAME INPUT.
REFRESH IT_DYNPFIELDS.
CLEAR IT_DYNPFIELDS.
MOVE 'V_USERNAME' TO IT_DYNPFIELDS-FIELDNAME.
APPEND IT_DYNPFIELDS.
CLEAR IT_DYNPFIELDS.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 DYNAME = V_PROG
 DYNUMB = V_DNUM
 TRANSLATE_TO_UPPER = 'X'
 TABLES
 DYNPFIELDS = IT_DYNPFIELDS
 EXCEPTIONS
 INVALID_ABAPWORKAREA = 1
 INVALID_DYNPROFIELD = 2
 INVALID_DYNPRONAME = 3
 INVALID_DYNPRONUMMER = 4
 INVALID_REQUEST = 5
 NO_FIELDDESCRIPTION = 6
 INVALID_PARAMETER = 7
 UNDEFIND_ERROR = 8
 DOUBLE_CONVERSION = 9
 STEPL_NOT_FOUND = 10
 OTHERS = 11.
IF SY-SUBRC = 0.
 READ TABLE IT_DYNPFIELDS WITH KEY FIELDNAME = 'V_USERNAME'.
 IF SY-SUBRC = 0.
 V_USERNAME = IT_DYNPFIELDS-FIELDVALUE.
 ENDIF.
ENDIF.
PERFORM GET_MULTIPLE.
ENDMODULE. " GET_CURSOR_USERNAME INPUT
*& Form GET_MULTIPLE
* text
* --> p1 text
* <-- p2 text
FORM GET_MULTIPLE .
* Dynamically holding Field name
FIELD-SYMBOLS: <FST> TYPE STANDARD TABLE.
IF R_UNAME[] IS INITIAL.
 IF NOT V_USERNAME IS INITIAL.
 R_UNAME-SIGN = 'I'.
 R_UNAME-OPTION = 'EQ'.
 R_UNAME-LOW = V_USERNAME.
 APPEND R_UNAME.
 CLEAR R_UNAME.
 ENDIF.
ENDIF.
ASSIGN R_UNAME[] TO <FST>.
CALL FUNCTION 'COMPLEX_SELECTIONS_DIALOG'
 EXPORTING
 TITLE = 'Select Multiple Value'(059)
 TEXT = 'Finish Group'(058)
 SIGNED = 'X'
 LOWER_CASE = ' '
 NO_INTERVAL_CHECK = 'X'
 JUST_DISPLAY = ' '
 JUST_INCL = 'X'
 TABLES
 RANGE = <FST>
 EXCEPTIONS
 NO_RANGE_TAB = 1
 CANCELLED = 2
 INTERNAL_ERROR = 3
 OTHERS = 4.
IF SY-SUBRC = 0.
 READ TABLE R_UNAME INDEX 1.
 IF SY-SUBRC = 0.
 V_USERNAME = R_UNAME-LOW.
 ENDIF.
ENDIF.
ENDFORM. " GET_MULTIPLE
Flow loogic....
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
PROCESS ON VALUE-REQUEST.
*- To capture the cursor and for f4
FIELD V_USERNAME MODULE GET_CURSOR_USERNAME.
in screen i have one field v_username
for that field do this
double click on field which you want to make it as select option, it will display the attributes screen, in that click on program attributes button , now go to poss. entries in the dropdown choose 1 show at selection.
Regards
vijay

Dialog Programming ("Required" Screen Field) Processing

Similar Messages

Maybe you are looking for