Input verification while declaration of selection screen

Hi Friends,
Is there a way to verify the input which the user enters on screen
either declared by parameters or select-options
without below techniques at declaration level itself.
1. Provide user a dropdown list ( no error, no verifcation ).
2. By sending back the user input and do select query and then display type E messages
   ex: select f1 from table into wa
         where a1 IN s_first and " s_first user input
         where a2 IN s_second. " s_second user input
         if sy-subrc ne 0
         *display error to user
         endif.
My basic idea is to avoid database hits i.e., minimise select 's
Edited by: DeepakNandikanti on Dec 1, 2010 10:35 AM

Hi,
You can force entries through F4 Help.
Check this link.
<a href = "input does not take any manual entry target="_blank" >input does not take any manual entry

Similar Messages

How can i declare a selection screen in a DP program with transaction code.

hi friends,
How can i declare a selection screen in a DP program with transaction code. What are the events and flow logic..

Search in SCN/Google for Module-pool programming basics.

Disable Screen-Input for checkbox in report selection screen.

I have defined one Selection Screen parameter as follows:
PARAMETERS: CCCDoc as CHECKBOX USER-COMMAND check DEFAULT 'X'.
Now, When Selection Screen comes up I want to have this check box greyed out. I tried this code but is not working for me. What differently should I be doing?
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF SCREEN-NAME = CCCDoc.
      SCREEN-INPUT = '0'.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
Please advise.
- Rohit.

geeee
I tried everything except capitalizing it. Even had tried quotes.
Guess sometimes you do need someone to make it work for you
Thanks Guys...Most appreciated.
PS: Sorry aRs I wasnt able to award you both 10 pts...I tried. Thanks all the same.
Message was edited by:
        rohit singh

Short dump while using call selection-screen mdynnr

Hi ALL,
I need your help and information.
In programmes, We are using the statament " CALL SELECTION-SCREEN MDYNNR "
and passing the screens dynamically into variable mdynnr.
And the programme is going to dump after executing 50 times.
When we
can we use any other statement instead of CALL SELECTION-SCREEN MDYNNR.
Your information helps us lot.
Thanks in advance.
Srinivasa Reddy.

Hi,
As you know Call Screen is the statement, but you will get the problem if you are going to call it in the same LUW repeatedly. So, FM is the only convenient way to do it. This is very easy. Just create a FM and replace you statement with this FM. Hopefully this will solve your problem.
Check this comment " When you call a new main program in order to use a screen sequence (for example, using CALL TRANSACTION), a new SAP LUW begins. This may be an undesired effect, especially when you are trying to modularize a transaction that updates the database.
An alternative to this is to use an external procedure, whose main program is linked to a screen sequence, and which contains the corresponding dialog modules. Procedures run in the same SAP LUW and internal session as their calling program."
Thanks,

Issue with inputting Constants in the WebI selection screen

Hello Members,
We recently upgraded our BO environment from BOBJ XI into BI 4.1.
In this process we are recreating the BW connections for WebI Reports to connect using BICS connection.
We are facing few issues:
Issue 1:
In the design mode when I am trying to input some Constants values (which might not be available in our Dev Environment but are available in Q & P), and trying to execute the WebI Query its throwing the following error:
How can I input Constants in the filter which might not be available in Devlopment?
Issue 2: We are not able to input either Key or Text in the Filter area. It displays the error "Object cannot be used in the Filter Panel"
How can I use Key or Text in the Query Filter section?
I am sure SDN members will have insight on this, please share your thoughts.

Any inputs?

How to validate input's in selection-screen

Hi ,
can any one how to validate input's field's in selection-screen and each field has diffirent tables and what is the table name which has all the validating fields??
Thank's in advance..

hi,
You can use validate selct-options using select query by obtaining the realtionship from table .Using the selection-screen events You can write code for validation as follows.
tables:
kna1.                                " General Customer data
*"Selection screen elements............................................
select-options:
s_kunnr for kna1-kunnr.              " Customer number
*"Data declarations...................................................
Data declaration of the structure to hold kna1 details              *
data:
begin of fs_customer,
    kunnr type kna1-kunnr,             " Customer number
    adrnr type kna1-adrnr,             " Address
    anred type kna1-anred,             " Title
    erdat type kna1-erdat,             " Created on
    ernam type kna1-ernam,             " Created by
end of fs_customer.
*"Constants declarations..............................................
constants
w_path type string value 'D:\DOWNLOAD\CUSTOMER'.
Internal table to hold customer details                             *
data:
t_customer like
    standard table
          of fs_customer.
                      AT SELECTION SCREEN OUTPUT                    *
at selection-screen.
perform retrieve.
Form RETRIEVE                                                     *
This subroutine retrieve customer data from table kna1             *
There are no interface parameters to be passed to this subroutine. *
form retrieve .
select kunnr                         " Customer number
         adrnr                         " Address
         anred                         " Title
         erdat                         " Created on
         ernam                         " Created by
    into corresponding fields of table t_customer
    from kna1
   where kunnr in s_kunnr.             " END SELECT
if sy-subrc ne 0.
    message text-001 type 'E'.
    exit.
endif.                               " IF SY-SUBRC NE 0
endform.                               " RETRIEVE
regards,
veeresh

0FI_GL_4 data source input selection screen

Dear experts,
I have enabled the input selection option tickfor fields PRCTR and KOSTL in data source 0FI_GL_4 with RSA6.
Both the fields are available in extract checker RSA3 too. But while does not have any effect while running the extractor. PRCTR and KOSTL are not having any effect while using in selection screen. Kindly let me know if any process there to enhance the standard program by putting the extra field in the selection (open cursor).
Jigar

Hi Leandro,
First, if you want to change a selection field, you need to do it in RSA6, checking the selection flag. I wouldn't touch the table..
Not always the filter is just checking the flag, I don't know particulary 0FI_GL_4, but the filter might be done in the Function Module logic.
Where have you updated that field? 0GL_ACCOUNT is an infoobject, so it's in BW. If you want to filter in the InfoPackage, you need to filter in ERP, so it's a field (HKONT) and not an Infoobject.
For 0FI_GL_4, if you check transaction RSA2, you'll see that selection is impossible, so I'm not sure if changing the table value manually would be enough.
Hope this helps.
Regards,
Diego

Input box on default selection screen

Hi,
how to create an input box on the default selection screen which will accept only 1275 characters.
Can u please help me?
Thanks in Advance,
Sreekala.

Hi Sreekala,
You need to use the CL_GUI_TEXTEDIT for creating the box, also you need use the dialog program for that.
For more info on that class check this
Usage of CL_GUI_TEXTEDIT
Text box on selection screen
Hope they helps you.
Regards!

How do we validate input fields on the selection screen

How do we validate input fields on the selection screen

hi balram,
u can validate input fields using <b>AT SELECTION-SCREEN</b> Event.
PARAMETERS : p_werks TYPE marc-werks.
AT SELECTION-SCREEN ON p_werks.
SELECT SINGLE *
FROM t001w
WHERE werks = p_werks.
IF sy-subrc <> 0.
MESSAGE 'Invalid Plant' TYPE 'I'.
ENDIF.
Like this, we can validate user input for plant.
check this link:
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/db9a2e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
Reware me if useful......
Harimanjesh AN

How to display in sap-script the data which is input in selection screen by the user.

Hii,
I want to display the data in sap-script that has been input by the user in selection screen.
Suppose the the user has done input for posting date from 25.1.2001 to 25.1.2005,what i want is to display this date in sap script.
How can i do it.
please help asap.
Regards.

Hi,
If select-option name is s_erdat.
then from value will be s_erdat-low and to value will be s_erdat-high.
Arivazhagan S

How to create a report with selection screen that can run in background

Sorry to ask these basic questions but I am knew to ABAP Programming.
To keep it simply, I am attempting to create a report that has a simple parameter driven selections screen with one field. That field takes in a folder path from the user. The user executes the report. The report creates a simply BDC that goes into SE16, gathers data from a table, and exports the results to a text file using the folder path provided. I created a variant for the folder path field in the selection screen hoping to use it while executing the report in the background. The report is not exporting the file as it did when run in the foreground for some reason.
I am wondering what event is triggered when a report is executed in the background. In the foreground (or when I execute the program via SE38->Execute->With Variant) the user needs to execute the program by hitting the execute button once the variant has populated the folder path field. It works then, so I am trying to get the same to work in the background. I am thinking I didn't put the program together correctly to accommodate the running in the background. How can you create a report that can accept user input via variant into a selection screen and then run in the background?
Please, any information would be greatly appreciated.
Thanks you all for reading this!!!

Ok, finally I understand what you're doing. Initially you lost me with the SE16 reference...
Not sure what you're trying to achieve overall, but apart from the fact that you cannot export/download a file to a user's PC via background job (unless you have a mapped network share on the server or something like an FTP server on the user's PC, but both are pretty hypothetical scenarios and unlikely to occur).
Also, the BDC approach to get data via SE16 is pretty awkward. Note that SE16 is guarded by some authorization checks and often users won't have access in production (which might not matter if you intend to always run your program in background via dedicated batch user). However, I have no clue why you wouldn't want to use [open SQL|http://help.sap.com/abapdocu_70/en/ABENOPEN_SQL_READING.htm] to read the data. You could then save it on the application server or if you really have to get it to the user you can consider e-mailing the file (extracts should be compressed before sending). For the latter you'll find plenty of references here, basically it's the [business communication services|http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/1c5d3aebba4c38e10000000a114084/frameset.htm] that you'd need to look at.

AT SELECTION-SCREEN - Urgent

Could anybody tell me what does the event( AT SELECTION-SCREEN ) only do ? I am asking only about AT SELECTION-SCREEN
Regards,
SAURAV LAHIRY

hI,
At selection-screen is the event of a report program in which we have to validate the selection screen fields.
SELECTION SCREEN
Selection screens are special screens that are defined with the help of ABAP statements. As programmers do not have access to the flow logic of selection screens, they cannot define dialog modules for selection screens. The ABAP runtime environment fully controls the processing flow of selection screens. To allow programmers to modify the selection screen before it is called (PBO) and react to user actions on the selection screen (PAI), the ABAP runtime environment generates a number of special selection screen events before the selection screen is displayed and after the user has executed actions on the selection screen
AT SELECTION-SCREEN OUTPUT
This event is executed at PBO of the selection screen every time the user presses ENTER - in contrast to INITIALIZATION . Therefore, this event is not suitable for setting selection screen default values. Also, since AT SELECTION-SCREEN OUTPUT is first executed after the variant is imported (if a variant is used) and after adopting any values specified under SUBMIT in the WITH clause, changing the report parameters or the selection options in AT SELECTION-SCREEN OUTPUT would destroy the specified values.
Here, however, you can use LOOP AT SCREEN or MODIFY SCREEN to change the input/output attributes of selection screen fields.
Example
SELECT-OPTIONS NAME FOR SY-REPID MODIF ID XYZ.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
CHECK SCREEN-GROUP1 = 'XYZ'.
SCREEN-INTENSIFIED = '1'.
MODIFY SCREEN.
ENDLOOP.
AT SELECTION-SCREEN ON VALUE-REQUEST
The event is triggered when the user calls the F4 help for the field field. If no corresponding event block has been defined, no possible values help or values list from the Dictionary is displayed. If a corresponding event block exists, it takes precedence over the default possible values help mechanism. It is then up to the programmer to ensure in the event block that an appropriate list of values is displayed, and that the user can choose a value from it.
No event block AT SELECTION-SCREEN ON VALUE-REQUEST can be created for input fields on the selection screen that are declared within the logical database used. You cannot override the input help mechanism of the logical database within the executable program. You can define separate help within the logical database program using the VALUE-REQUEST option in the PARAMETERS and SELECT-OPTIONSstatements.
Example
INCLUDE DBXYZSEL
PARAMETERS PL_TYPE LIKE SAPLANE-PLANETYPE VALUE-REQUEST.
REPORT SAPDBXYZ DEFINING DATABASE XYZ.
TABLES SAPLANE.
FORM PL_TYPE_VAL.
CALL FUNCTION ...
ENDFORM.
AT SELECTION-SCREEN ON HELP-REQUEST
If the data type of an input field declared in an executable program is defined in the ABAP Dictionary, the documentation of the underlying data element is automatically displayed if the user positions the cursor in that field and presses F1. To create help for input fields that have no Dictionary reference, or to override the help normally linked to the field, you can create an event block for the event
AT SELECTION-SCREEN ON HELP-REQUEST FOR <field>
The event is triggered when the user calls the F1 help for the field <field>. If no corresponding event block has been defined, the help from the ABAP Dictionary is displayed, or none at all if the field has no Dictionary reference. If a corresponding event block exists, it takes precedence over the default help mechanism. It is then up to the programmer to ensure that appropriate help is displayed.
You cannot declare the event block AT SELECTION-SCREEN ON HELP-REQUEST for input fields on the selection screen that are declared within a logical database. You cannot override the help mechanism of a logical database within the program. You can define separate help within the logical database program using the HELP-REQUEST option in the PARAMETERS and SELECT-OPTIONS statements.
REPORT SELECTION_SCREEN_F1_DEMO.
PARAMETERS: P_CARR_1 TYPE S_CARR_ID,
P_CARR_2 TYPE S_CARR_ID.
AT SELECTION-SCREEN ON HELP-REQUEST FOR P_CARR_2.
CALL SCREEN 100 STARTING AT 10 5
ENDING AT 60 10.
This program declares a selection screen with two parameters that both refer to the data element S_CARR_ID in the ABAP Dictionary. The documentation from the ABAP Dictionary is used for P_CARR_1, and a help screen 100 is called for P_CARR_2. The help screen is defined in the Screen Painter as a modal dialog box with next screen 0. It contains the help text defined as help texts. The screen does not require any flow logic.
AT SELECTION-SCREEN ON field
In the PAI event of the selection screen, the event
AT SELECTION-SCREEN ON field
event is triggered. The input field field can be checked in the corresponding event block. If an error message occurs within this event block, the corresponding field is made ready for input again on the selection screen.
Example:
REPORT event_demo.
NODES spfli.
AT SELECTION-SCREEN ON city_fr.
IF carrid-low EQ 'AA' AND city_fr NE 'NEW YORK'.
MESSAGE e010(hb).
ENDIF.
If the user enters AA in the first input field, but not NEW YORK for the departure city, an error message is displayed in the status line until the user enters the correct city.
AT SELECTION-SCREEN ON RADIOBUTTON
In the PAI event of the selection screen, the event
AT SELECTION-SCREEN ON RADIOBUTTON GROUP <radi>
is triggered when the contents of all of the fields in a radio button group are passed from the selection screen to the ABAP program. To define a radio button group <radi>, use the addition RADIOBUTTON GROUP <radi> in the corresponding PARAMETERS statements. This event block allows you to check the whole group. If an error message occurs within this event block, the radio button group is made ready for input again on the selection screen. The individual fields of radio button groups do not trigger the event AT SELECTION-SCREEN ON <field>.
REPORT EVENT_DEMO.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.
PARAMETERS: R1 RADIOBUTTON GROUP RAD1 DEFAULT 'X',
R2 RADIOBUTTON GROUP RAD1,
R3 RADIOBUTTON GROUP RAD1.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME.
PARAMETERS: R4 RADIOBUTTON GROUP RAD2 DEFAULT 'X',
R5 RADIOBUTTON GROUP RAD2,
R6 RADIOBUTTON GROUP RAD2.
SELECTION-SCREEN END OF BLOCK B2.
AT SELECTION-SCREEN ON RADIOBUTTON GROUP RAD1.
IF R1 = 'X'.
MESSAGE W040(HB).
ENDIF.
AT SELECTION-SCREEN ON RADIOBUTTON GROUP RAD2.
IF R4 = 'X'.
MESSAGE W040(HB).
ENDIF.
If the user does not change one of the radio button groups, a warning is displayed.
AT SELECTION-SCREEN ON BLOCK
In the PAI event of the selection screen, the event
AT SELECTION-SCREEN ON BLOCK <block>
is triggered when the contents of all of the fields in a block are passed from the selection screen to the ABAP program. You define a block by enclosing the declarations of the elements in the block between the statements SELECTION-SCREEN BEGIN OF BLOCK <block> and SELECTION-SCREEN END OF BLOCK <block>. You can use this event block to check the consistency of the input fields in the block. If an error message occurs within this event block, the fields in the block are made ready for input again on the selection screen.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

About selection screen

hi all,
i have 3 radio button and corresponding thier 3 input loist box . i just want to deactivate 2 list box on the click of one radio button.
please give the solution if possible .
Thanks and Regards
priyank dixit

Hi,
Check the following code:
TYPE-POOLS : vrm,
             icon.
*SELECTION SCREEN FIELDS
TABLES : sscrfields.
*GLOBAL DECLARATIONS
DATA : flag TYPE c,
      tablename(10),
      mmtable LIKE dd02l-tabname,
      sdtable LIKE dd02l-tabname,
      hrtable LIKE dd02l-tabname.
*DECLARATIONS FOR SELECTION SCREEN STATUS
DATA it_ucomm TYPE TABLE OF sy-ucomm.
***********SELECTION-SCREENS*********************
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
*FOR DYNAMIC DISPLAY OF MODULES
PARAMETERS : pa RADIOBUTTON GROUP rad USER-COMMAND com MODIF ID mod,
              pb RADIOBUTTON GROUP rad MODIF ID rad,
              pc RADIOBUTTON GROUP rad MODIF ID cad.SELECTION-SCREEN SKIP.
**TO INCLUDE DYNAMIC ICONS
SELECTION-SCREEN COMMENT 2(6) text_001.
*DYNAMIC LIST BOX BASED ON USER SELECTIONS
PARAMETERS one AS LISTBOX VISIBLE LENGTH 20 MODIF ID mod.
PARAMETERS two AS LISTBOX VISIBLE LENGTH 20   MODIF ID rad.
PARAMETERS three AS LISTBOX VISIBLE LENGTH 20 MODIF ID cad.
SELECTION-SCREEN END OF BLOCK blk1.
*DISPLAY DYNAMIC PUSHBUTTON ON APP TOOLBAR ON USER CLICKS
SELECTION-SCREEN: FUNCTION KEY 1,
                  FUNCTION KEY 2,
                  FUNCTION KEY 3.
**EVENT ON SELECTION SCREEN FOR OUTPUT DISPLAY
AT SELECTION-SCREEN OUTPUT.
*CLICK OF FIRST RADIO BUTTON
IF pa = 'X'.
    sscrfields-functxt_01 = 'Materials Management'.
    WRITE icon_plant AS ICON TO text_001.
*CODE TO GET DYNAMICS BASED ON THE SELECTED RADIO
    LOOP AT SCREEN.
      IF screen-group1 = 'MOD'.
        screen-intensified = '1'.
        screen-active = 1.
        screen-display_3d = '1'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'RAD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'CAD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
*CLICK OF SECOND RADIO
IF pb = 'X'.
    sscrfields-functxt_02 = 'Sales And Distribution'.
    WRITE icon_ws_ship AS ICON TO text_001.
    LOOP AT SCREEN.
      IF screen-group1 = 'RAD'.
        screen-intensified = '1'.
        screen-active = 1.
        screen-display_3d = '1'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'MOD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'CAD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
*CLICK OF THIRD RADIO
IF pc = 'X'.
    sscrfields-functxt_03 = 'Human Resources'.
    WRITE icon_new_employee AS ICON TO text_001.
    LOOP AT SCREEN.
      IF screen-group1 = 'RAD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'MOD'.
        screen-intensified = '0'.
        screen-active = 0.
        screen-display_3d = '0'.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'CAD'.
        screen-intensified = '1'.
        screen-active = 1.
        screen-display_3d = '1'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
Regards,
Bhaskar

How to disable a field in selection screen based on condition.

Hi,
I have 2 radio buttons- p_normd, p_recov and 2 other controls - like text boxes, say tb1 and tb2. and some mandatory fields below.
If i choose p_normd, i want one control(tb2) to be disabled and if i choose p_recov, i want the other control(tb1) to be disabled(tb2 should be enabled then.)
Currently i am using the following code. The 1'st radiobutton is intially checked. But the problem is when i click on the 2'nd radio button, the other control(tb1) is not getting disabled. When i double click, i get an error telling mandatory field to be filled. Only after the other mandatory fields below are filled, and after i double click on the unchecked radiobutton, the other control gets disabled.
Please suggest what to do..
The current code below:
AT SELECTION-SCREEN OUTPUT. "ON RADIOBUTTON GROUP rg01.
LOOP AT SCREEN.
IF p_normd EQ c_x AND screen-group1 = 'SC2'.
        MOVE 0 TO screen-input.
      MODIFY SCREEN.
ENDIF.
IF p_recov EQ c_x AND screen-group1 = 'SC1'. "IF screen-name = 'ERDAT-LOW' OR screen-name = 'ERDAT-HIGH'.
        MOVE 0 TO screen-input.
        MODIFY SCREEN.
ENDIF.
ENDLOOP.
Thanks,
Ammu

Hi
declare your parameter as below:
parameters: p_x type c radio button group g1 user-command r.
in at selection screen output event .
check for the radio button.
loop at screen.
if screen group is <desired value>
then screen-active = 0 or 1. <do whatever you want to do.>
modify screen.
endloop.
see below the sample code.
<<<<<AT SELECTION SCREEN EVENT>>>>>
AT SELECTION-SCREEN ON BLOCK B1.
IF P_LCOST = C_X.
    PERFORM CLEAR_FIELDS.    " Clearing fields before loading the screen
    CALL SELECTION-SCREEN 100 STARTING AT 20 5.
ELSEIF P_MCOST = C_X.
    PERFORM CLEAR_FIELDS1.          " Clearing fields before loading the screen
    CALL SELECTION-SCREEN 101 STARTING AT 20 5.
ENDIF.
IF SY-SUBRC = 0.
    PERFORM VALIDATION.             " Validating selection screen input
ELSE.
    LEAVE TO TRANSACTION C_TRAN.
ENDIF.
<<<<<<DECLARATION PART>>>>>>
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_LCOST RADIOBUTTON GROUP GI DEFAULT 'X',
            P_MCOST RADIOBUTTON GROUP GI.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF SCREEN 100 AS WINDOW TITLE TEXT-002.
SELECTION-SCREEN BEGIN OF BLOCK B2.
PARAMETERS: P_COAREA TYPE CSKS-KOKRS OBLIGATORY,         " controlling area
            P_FYR    TYPE COEP-GJAHR OBLIGATORY,         " fiscal year
            P_PERIOD TYPE COEP-PERIO OBLIGATORY.         " fiscal period
SELECT-OPTIONS: S_CCNTR FOR V_KOSTL OBLIGATORY,       " Cost Center
                S_COELM FOR V_KSTAR MODIF ID M1,       " Cost element
                S_PDATE FOR V_BUDAT OBLIGATORY.       " posting date.
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN END OF SCREEN 100.
SELECTION-SCREEN BEGIN OF SCREEN 101 AS WINDOW TITLE TEXT-003.
SELECTION-SCREEN BEGIN OF BLOCK B3.
PARAMETERS:     P_CCODE TYPE T001-BUKRS OBLIGATORY,         " Company Code
                P_FYEAR TYPE COEP-GJAHR OBLIGATORY.         " fiscal year
SELECT-OPTIONS:   S_GLACC FOR V_HKONT OBLIGATORY,       " G/L Account
                  S_PCNTR FOR V_PRCTR MODIF ID M2,      " Profit Center
                  S_PODATE FOR V_BUDAT OBLIGATORY.      " posting date.
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN END OF SCREEN 101.
thanks
LG
Edited by: LalitG on Apr 13, 2011 1:38 PM

At selection-screen on field

friends can u tell me the difference between atselection-screen and at selection-screen on field?

First of all the actual order of events
INITIALIZATION
     AT SELECTION-SCREEN OUTPUT
     AT SELECTION-SCREEN ON <field>
     AT SELECTION-SCREEN
START-OF-SELECTION
INITIALIZATION
This event occurs before the standard selection screen is called. You can use it, for example, to initialize the input fields of the standard selection screen or you can assign your own default values.
REPORT EVENT_DEMO.
PARAMETERS DATUM TYPE SY-DATUM DEFAULT SY-DATUM.
NODES SPFLI.
INITIALIZATION.
CITY_FR = 'NEW YORK'.
CITY_TO = 'FRANKFURT'.
CARRID-SIGN   = 'I'.
CARRID-OPTION = 'EQ'.
CARRID-LOW    = 'AA'.
APPEND CARRID.
DATUM+6(2) = '01'.
In the PBO of the selection screen, the
AT SELECTION-SCREEN OUTPUT
event is triggered. This event block allows you to modify the selection screen directly before it is displayed.
PARAMETERS: TEST1(10) MODIF ID SC1,
            TEST2(10) MODIF ID SC2,
            TEST3(10) MODIF ID SC1,
            TEST4(10) MODIF ID SC2.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
IF SCREEN-GROUP1 = 'SC1'.
    SCREEN-INTENSIFIED = '1'.
    MODIFY SCREEN.
    CONTINUE.
ENDIF.
IF SCREEN-GROUP1 = 'SC2'.
    SCREEN-INTENSIFIED = '0'.
    MODIFY SCREEN.
ENDIF.
ENDLOOP.
The parameters TEST1 and TEST3 are assigned to the modification group SC1, while TEST2 and TEST4 are assigned to group SC2. During the AT SELECTION-SCREEN OUTPUT event, the INTENSIFIED field of internal table SCREEN is set to 1 or 0, depending on the contents of the GROUP1 field. On the selection screen, the lines for TEST1 and TEST3 are highlighted while those for TEST2 and TEST4 are not.
In the PAI event of the selection screen, the event
AT SELECTION-SCREEN ON <field>
is triggered when the contents of each individual input field are passed from the selection screen to the ABAP program. The input field <field> can be checked in the corresponding event block. If an error message occurs within this event block, the corresponding field is made ready for input again on the selection screen.
The program below is connected to the logical database F1S:
REPORT EVENT_DEMO.
NODES SPFLI.
AT SELECTION-SCREEN ON CITY_FR.
IF CARRID-LOW EQ 'AA' AND CITY_FR NE 'NEW YORK'.
    MESSAGE E010(HB).
ENDIF.
If the user enters "AA" in the first input field, but not NEW YORK for the departure city, an error message is displayed in the status line until the user enters the correct city.
The AT SELECTION-SCREEN event is triggered in the PAI of the selection screen once the ABAP runtime environment has passed all of the input data from the selection screen to the ABAP program. If an error message occurs in this processing block, the selection screen is redisplayed with all of its fields ready for input. This allows you to check input values for consistency.
The program below is connected to the logical database F1S:
REPORT EVENT_DEMO.
NODES SPFLI.
AT SELECTION-SCREEN.
IF CARRID-LOW IS INITIAL
    OR CITY_FR IS INITIAL
    OR CITY_TO IS INITIAL.
    MESSAGE E000(HB).
ENDIF.
If the user does not enter values in all of the fields on the selection screen, an error message appears in the status line. This makes all of the input fields mandatory, even though they are not defined as such in the logical database.
Reward points, if the issue is resolved.
Regards,
Raman
Message was edited by:
        Raman Vinocha

Input verification while declaration of selection screen

Similar Messages

Maybe you are looking for