Selection screen default

Hi,
select-options : s_budat FOR wa_input-budat default high sy-datum.
But i want s_budat-low = sy-datum-2. means 2 days back from today
and s_budat-high = sy-datum. this values should come default when i am displaying selection screen.
Can anybody help me.
Regards,
Vanka

Hi,
Try to do the calculatiions to be displayed in selection screen in INITIALIZATION event.
Ex: s_bdudat-low = sy-datum - 2.
s_bdudat-high = sy-datum .
Hope it will help u to resolve it.
Regards,
Pavan

Similar Messages

Infoset-query-selection-screen-default-values

Hi All,
I am having the requirement as I need to put default values in the selecion-screen of the report by using Infoset query. Let me know the settings required for this.
I am using SQ01, SQ02, SQ03 T.Codes.
And I need display one record only if any field contains mulitple records, for example in the HR-ABAP, field p0105-usrid contains multiple values depending on the subtype.So, I need to display USRID when URSTY = '900'. All these should display by Infoset query only.
Pls help me in this scenario , its an urgent requirement.I am very much thankful for you for reading my proble, if you will provide some sort of solution, I feel very happy.
Advance thanks for this .
Regards,
Prakash.

Prakash,
To default the values on your selection screen, you will need to do some ABAP I guess. (if you do not want to use variant). Open up the infioset in SQ02 and then goto code option for the PNP**** field and then you can code to initialize the selection screen variables. Test with an ABAPer.
To display multiple records as multiple columns, you will have to create custom fields in infoset, and then go from there. Again see ABAPer.

Selection screen default value maintain,user cant chage the default value

hi Friends
SELECTION-SCREEN BEGIN OF BLOCK SCLDBLOCK WITH FRAME.
SELECT-OPTIONS:   S_WERKS FOR EBAN-WERKS DEFAULT 'IN01' NO INTERVALS NO-EXTENSION ,
                  S_MATNR FOR EBAN-MATNR,
                  S_BANFN FOR EBAN-BANFN,
                  S_EBELN FOR EBAN-EBELN,
                  S_LIFNR FOR EBAN-LIFNR,
                  S_BSART FOR EKKO-BSART DEFAULT 'IN03' OBLIGATORY NO INTERVALS NO-EXTENSION,
                  S_EINDT FOR EKET-EINDT OBLIGATORY.
SELECTION-SCREEN END OF BLOCK SCLDBLOCK.
here i need to maintain bsart in03 ,user cant able to chage anything instead of in03.what can i do for that one
Regards
ds

HI,
REPORT ZETA LINE-SIZE 350.
TABLES : EBAN , EKKO,EKET.
SELECTION-SCREEN BEGIN OF BLOCK SCLDBLOCK WITH FRAME.
SELECT-OPTIONS: S_WERKS FOR EBAN-WERKS DEFAULT 'IN01' NO INTERVALS
NO-EXTENSION ,
S_MATNR FOR EBAN-MATNR,
S_BANFN FOR EBAN-BANFN,
S_EBELN FOR EBAN-EBELN,
S_LIFNR FOR EBAN-LIFNR,
S_BSART FOR EKKO-BSART DEFAULT 'IN03' OBLIGATORY NO INTERVALS
NO-EXTENSION,
S_EINDT FOR EKET-EINDT OBLIGATORY.
SELECTION-SCREEN END OF BLOCK SCLDBLOCK.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
      IF SCREEN-NAME = 'S_BSART-LOW'.
        SCREEN-INPUT = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSE.
    LOOP AT SCREEN.
      IF SCREEN-NAME = 'S_BSART-HIGH'.
        SCREEN-INPUT = '1'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.

Selection Screen Default Values

Hi,
The selection screen can have the default values by using the parameter ID. To be the parameter ID value to defaulted we normally add the entry in User Profile>Own data>paramters with Parameter ID and the value.
I would like to know is there any other way to achieve the same, it could be parameter or select-options.
With Regards,
Azhar

For Parameter u can use DEFAULT keyword
eg. PARAMETERS: p_matnr TYPE mara-matnr DEFAULT 'B1200'.
For select option
As u might be knowing select options creates an intenal table, so if u want to have some default values then u can use the following code in the INITIALIZATION event:
DATA: v_matnr TYPE mara-matnr.
INITIALIZATION.
SELECT-OPTIONS: s_matnr FOR v_matnr.
s_matnr-low = 'BT100'.
s_matnr-high = 'BT900'.
append s_matnr.
This will give default values in the selection screen for select-options.

Assign default values in selection screen of CM21

Hi experts,
Our case is that, in CM21 selection screen, default value to the field "Plant" is appeared. W are sure that it is not because of configuration settings but not able to find why it is appearing by default. Please let us know. Thanks in advance.

Dear
Please check this thread which I have posted earlier ; CM21/cm25 sorting of user defined field in table area
Want a change in lau out in CM21
Regards
JH

Enforcing event AT-SELECTION-SCREEN OUTPUT

Hi Gurus
Does anybody know how to force event AT-SELECTION-SCREEN OUTPUT ?
What I'm aiming for is changing screen somewere outside of this event. For example.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_param.
IF p_param = 'change'.
    changes_in_screen = 'X'.
    *???*   "forcing AT-SELECTION-SCREEN OUTPUT event
ENDIF.
AT-SELECTION-SCREEN OUTPUT.
IF changes_in_screen = 'X'.
    LOOP AT SCREEN.
      "do something
    ENDLOOP.
ENDIF.
I would be grateful for any hints.

One alternative to define two selection screens. First selection screen (default selection screen of report #1000) having Client_type. After user hits execute (F8) then show the second selection screen with corresponding parameters.
PARAMETERS: p_client(1).
SELECTION-SCREEN BEGIN OF SCREEN 9000 AS WINDOW.
PARAMETERS: p_name(20),
            p_lname(20),
            p_cname(20),
            p_oname(20).
SELECTION-SCREEN END OF SCREEN 9000.
AT SELECTION-SCREEN OUTPUT.
CHECK sy-dynnr = '9000'.
* Hide corresponding fields on second selection screen
* based on values of P_CLIENT.
* Also should make key parameters obligatory!
START-OF-SELECTION.
CALL SELECTION-SCREEN 9000 STARTING AT 5 5.
Another alternative is to use a dialog/module pool program to handle this. Such screen field controlling can easily be done in dialog programs because you have full PAI/PBO control, unlike report program selection screen 1000. Unfortunately in a dialog program it is not easy to reproduce the functionality of a select-option.

Disable selection screen application toolbar button

Hi All,
Could you please let me know how to hide or disable application toolbar pushbuttons in the selection screen default screen 1000??
Thanks & regards,
Santhosh

Hi,
Try this way.
"Create table for function codes
DATA: it_exclude TYPE TABLE OF sy-ucomm.
PARAMETERS: r1 RADIOBUTTON GROUP gr1 USER-COMMAND uco1,
            r2 RADIOBUTTON GROUP gr1.
INITIALIZATION.
"Create two buttons with function codes FCODE1 and FCODE2.
SET PF-STATUS 'MY_GUI'.
AT SELECTION-SCREEN OUTPUT.
IF r1 = 'X'.
    APPEND 'FCODE1' TO it_exclude.
    CALL FUNCTION 'RS_SET_SELSCREEN_STATUS'
      EXPORTING
        p_status = 'MY_GUI'
      TABLES
        p_exclude = it_exclude.
ELSE.
    REFRESH it_exclude.
ENDIF.
Thanks
Venkat.O

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.

Call Selection Screen

Hi,
can any one give me good links for
All variants of at selection screen..
some thing on call selection screen
Thx,
Shashi

·     AT SELECTION-SCREEN
You should only perform very expensive checks with AT SELECTION-SCREEN if the program is then started. Here, you can read the system field SSCRFIELDS-UCOMM (provided a statement TABLES SSCRFIELDS exists). If the field has one of the values 'ONLI' (= Execute) or 'PRIN' (= Execute and Print), the report is then started, i.e. the selection screen is closed and the processing continues with START-OF-SELECTION.
     Additions:
·     ... ON psel
Effect
This event is assigned to the selection screen fields corresponding to the report parameter or selection criterion psel.
If the report starts an error dialog at this point, precisely these fields become ready for input.
·     ... ON END OF sel
          For each selection criterion sel on the selection screen, you can call a further screen by pressing a pushbutton. On this screen, you can enter any number of single values and ranges for the selection criterion sel..
When this screen has been processed (i.e. at the end of PAI for this screen), the event AT SELECTION-SCREEN ON END OF sel is executed.
At this point, all the values entered are available in the internal table sel.
·     ... ON VALUE-REQUEST FOR psel_low_high
Effect
In this addition, the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH, where sel is the name of a selection criterion. The effect of this is twofold:
1.     The possible entries pushbutton for F4 appears beside the appropriate field.
2.     When the user activates this pushbutton or presses F4 for the field, the event is executed. You can thus implement a self-programmed possible entries routine for the input/output fields of the selection screen. If the program contains such an event and the user presses F4, the system processes this rather than displaying the check table or the fixed values of the Dictionary field.
·     ... ON HELP-REQUEST FOR psel_low_high
Effect
As with the addition ON VALUE-REQUEST the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH, where sel is the name of a selection criterion. When the user presses F1 on the relevant field, the subsequent processing block is executed. You can thus implement a self-programmed help for the input/output fields of the selection screen. If the program contains such an event and the user presses F1, the system processes this rather than displaying the documentation of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field.
·     ... ON RADIOBUTTON GROUP radi
Effect
This event is assigned to the radio button groups on the selection screen defined by PARAMETERS par RADIOBUTTON GROUP radi. If the report starts at an error dialog at this point ,precisely these fields of the radio button group
radi become ready for input again.
·     ... ON BLOCK block
Effect
This event is assigned to the blocks on the selection screen defined by SELECTION-SCREEN BEGIN/END OF BLOCK block. If the report starts at an error
dialog at this point, precisely these fields of the block block become ready for input again.
     The events assigned to the radio button groups are executed according to the first parameter of the radio button group.
The events assigned to the blocks are executed "from the inside to the outside".
·     ... OUTPUT
Effect
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 inout/output attributes of selection screen fields.
·     ... ON EXIT-COMMAND
Effect
This event is executed at the exit command of the selection screen - that is, at Back, Cancel, or End,events executed after the screen is sent that do not cause the system to check the input and execute the PAI.
plz reward if useful
vivek

At Selection-screen Events!

Hi!
Pls tell me the order of selection screen events in sequence
Pls give some sample program for validation of selection screen i/p without using search helps.
Thanks

Hi Rahul
Basic form
AT SELECTION-SCREEN.
Additions
1. ... ON psel
2. ... ON END OF sel
3. ... ON VALUE-REQUEST FOR psel_low_high .
4. ... ON HELP-REQUEST FOR psel_low_high
5. ... ON RADIOBUTTON GROUP radi
6. ... ON BLOCK block
7. ... OUTPUT
Effect
This event only makes sense in reports, i.e. in programs set to type 1 in the attributes. Type 1 programs are started via a logical database and always have a selection screen where the user can specify the database selections.
The event is processed when the selection screen has been processed (at the end of PAI ).
If an error message ( MESSAGE Emnr ) is sent during the event, all fields on the selection screen become ready for input.
After further user input, AT SELECTION-SCREEN is executed again.
Note
You should only perform very expensive checks with AT SELECTION-SCREEN if the program is then started (not every time the user presses ENTER). Here, you can read the system field SSCRFIELDS-UCOMM (provided a statement TABLES SSCRFIELDS exists). If the field has one of the values 'ONLI' (= Execute) or 'PRIN' (= Execute and Print), the report is then started, i.e. the selection screen is closed and the processing continues with START-OF-SELECTION . Remember that the selection screen (and thus also AT SELECTION-SCREE N ) is also processed in variant maintenance and with SUBMIT VIA JOB . You can determine which of these applies by calling the function module RS_SUBMIT_INFO .
Addition 1
... ON psel
Effect
This event is assigned to the selection screen fields corresponding to the report parameter or selection criterion psel .
If the report starts an error dialog at this point, precisely these fields become ready for input.
Addition 2
... ON END OF sel
Effect
For each selection criterion sel on the selection screen, you can call a further screen by pressing a pushbutton. On this screen, you can enter any number of single values and ranges for the selection criterion sel .
When this screen has been processed (i.e. at the end of PAI for this screen), the event AT SELECTION-SCREEN ON END OF sel is executed.
At this point, all the values entered are available in the internal table sel .
Addition 3
... ON VALUE-REQUEST FOR psel_low_high
Effect
With this addition, the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH , where sel is the name of a selection criterion. The effect of this is twofold:
The pushbutton for F4 (Possible entries) appears beside the appropriate field.
When the user selects this pushbutton or presses F4 for the field, the event is executed. You can thus implement a self-programmed possible entries routine for the input/output fields of the selection screen. If the program contains such an event and the user presses F4 , the system processes this rather than displaying the check table or the fixed values of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field. You can, for example, use the CALL SCREEN statement to display a selection list of possible values. The contents of the field psel_low_high at the end of this processing block are copied to the appropriate input/output field.
This addition is only allowed with report-specific parameters (PARAMETERS ) or selection options (SELECT-OPTIONS ). For database-specific parameters or selection options, you can achieve the same effect by using the addition VALUE-REQUEST FOR ... with the key word PARAMETERS or SELECT-OPTIONS in the include DBxyzSEL (where xyz = name of logical database). In this case, you must program the value help in the database program SAPDBxyz .
Addition 4
... ON HELP-REQUEST FOR psel_low_high
Effect
As with the addition ON VALUE-REQUEST the field psel_low_high is either the name of a report parameter or of the form sel-LOW or sel-HIGH , where sel is the name of a selection criterion. When the user presses F1 on the relevant field, the subsequent processing block is executed. You can thus implement a self-programmed help for the input/output fields of the selection screen. If the program contains such an event and the user presses F1 , the system processes this rather than displaying the documentation of the Dictionary field - even if the report parameter or the selection option with LIKE or FOR points to a Dictionary field.
This addition is only allowed with report-specific parameters (PARAMETERS ) or selection options (SELECT-OPTIONS ). For database-specific parameters or selection options, you can achieve the same effect by using the addition HELP-REQUEST FOR ... with the key word PARAMETERS or SELECT-OPTIONS in the include DBxyzSEL (where xyz = name of logical database). In this case, you must program the help in the database program SAPDBxyz .
Addition 5
... ON RADIOBUTTON GROUP radi
Effect
This event is assigned to the radio button groups on the selection screen defined by PARAMETERS par RADIOBUTTON GROUP radi .
If the report starts an error dialog at this point, precisely these fields of the radio button group radi become ready for input again.

Addition 6
... ON BLOCK block
Effect
This event is assigned to the blocks on the selection screen defined by SELECTION-SCREEN BEGIN/END OF BLOCK block .
If the report starts an error dialog at this point, precisely these fields of the block block become ready for input again.
Note
In which sequence are the events AT SELECTION-SCREEN ON psel ... , AT SELECTION-SCREEN ON RADIOBUTTON GROUP ... , AT SELECTION-SCREEN ON BLOCK ... , AT SELECTION-SCREEN processed?
The AT SELECTION-SCREEN ON psel ... events assigned to the parameters or selection options are executed in the sequence they are declared in the program, i.e. in the sequence they appear on the selection screen.
The events assigned to the radio button groups are executed according to the first parameter of the radio button group.
The events assigned to the blocks are executed "from the inside to the outside".
Example
SELECT-OPTIONS SEL0 FOR SY-TVAR0.
SELECTION-SCREEN BEGIN OF BLOCK BL0.
SELECT-OPTIONS SEL1 FOR SY-TVAR1.
SELECTION-SCREEN BEGIN OF BLOCK BL1.
PARAMETERS P0 RADIOBUTTON GROUP RADI.
PARAMETERS P1 RADIOBUTTON GROUP RADI.
SELECTION-SCREEN BEGIN OF BLOCK BL2.
PARAMETERS P3.
SELECTION-SCREEN END OF BLOCK BL2.
SELECT-OPTIONS SEL2 FOR SY-TVAR2.
SELECTION-SCREEN END OF BLOCK BL1.
SELECTION-SCREEN END OF BLOCK BL0.
Sequence:
AT SELECTION-SCREEN ON...
SEL0
SEL1
RADIOBUTTON GROUP RADI
P3
BLOCK BL2
SEL2
BLOCK BL1
BLOCK BL0
AT SELECTION-SCREEN is executed at the very end.
Addition 7
... OUTPUT
Effect
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
Output all fields of the
SELECT-OPTION NAME
highlighted:
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.
The addition MODIF ID XYZ to the key word SELECT-OPTIONS assigns all fields of the selection option NAME to a group you can read in the field SCREEN-GROUP1 . At PBO of the selection screen, all these fields are then set to highlighted.

check these links
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
Reward all helpfull answers
Regards
Pavan

Init & at selection screen o/p

hi !
i need the difference between
initialization and at selection-screen output   events.
please explain with an example.
points will be awarded!

At selection screen o/pevent 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
Output all fields of the SELECT-OPTION NAME highlighted:
    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.
Executed before the selection screen is displayed.
The parameters (PARAMETERS ) and selection criteria (SELECT-OPTIONS ) defined in the program already contain default values (if specified). You can assign different values here and also change the database-specific selections.
In contrast to R/2 , this event is also executed during background processing.
Example
Define the last day of the previous month as the key date:
    PARAMETERS QUAL_DAY TYPE D DEFAULT SY-DATUM.
    INITIALIZATION.
      QUAL_DAY+6(2) = '01'.
      QUAL_DAY      = QUAL_DAY - 1.
Here, the default value of QUAL_DAY is the current date, e.g. 05.04.88 ( QUAL_DAY = '19880405'). Two subseqent statements set the date first to the beginning of the month, e.g. 01.04.88 ( QUAL_DAY = '19880401') and then, by subtracting one day, to the last day of the previous month, e.g. 31.03.88 ( QUAL_DAY = '19880331').
Note
In more precise terms, INITIALIZATION is executed in the following steps:
Specify default values for the selections. Execute the event INITIALIZATION. Import variant (if used to start the report). On SUBMIT , the values specified for each WHERE clause are also transferred, if necessary. Execute the event AT SELECTION-SCREEN OUTPUT , if it occurs in the report (unlike INITIALIZATION , this event is always executed for PBO of a selection screen). Display selection screen. Transport the screen fields containing user input to the report fields. Continue with START-OF-SELECTION .

Default sales org on selection screen using set and get parameter!!

Hi,
I need to default value on selection screen using SET n GET parameter...logic to be used should be:
Sales Organisation:
This field should be filled by default using the user parameter id VKO. (using sentence GET PARAMETER and SET PARAMETER)...
Hope i need to write the code in initialisation and what shud b the content?
Regards
Gunjan

hi,
TABLES <table name>.
SET PARAMETER ID VKO FIELD <tablename-fieldname>.
call transaction 'zxx'.
try this sample program,
REPORT BOOKINGS NO STANDARD PAGE HEADING.
TABLES SBOOK.
START-OF-SELECTION.
WRITE: 'Select a booking',
SKIP.
GET SBOOK.
WRITE: SBOOK-CARRID, SBOOK-CONNID,
 SBOOK-FLDATE, SBOOK-BOOKID.
HIDE: SBOOK-CARRID, SBOOK-CONNID,
 SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
 'CON' FIELD SBOOK-CONNID,
 'DAY' FIELD SBOOK-FLDATE,
 'BOK' FIELD SBOOK-BOOKID.
CALL TRANSACTION 'BOOK'.
regards,
siva
Message was edited by:
 Shan

How to hide some fields in default selection screen in hr abap

Hi experts,
I have created default selection screen,in that in the Period option I wants display only 'Today'.
And in the selection criteria i wants to display personnel number,companycode,personnelsubarea,employee status and instead of payroll area i wants to display 'Org unit'.please tell me step by step procedure,that could be greate helpfull.
Thanks in advance,
mohan

use this logic to display only today in the period option
**Local constants
   CONSTANTS:
          c_0                   VALUE '0' ,
          c_089     TYPE char3 VALUE '089',
          c_091     TYPE char3 VALUE '091',
          c_095     TYPE char3 VALUE '095',
          c_097     TYPE char3 VALUE '097'.
                 At Selection Screen
at selection-screen output.
LOOP AT screen.
      IF
           screen-group4 = c_089 OR
           screen-group4 = c_091 OR
           screen-group4 = c_095 OR
           screen-group4 = c_097 .
      screen-active = c_0.
      MODIFY SCREEN.
     ENDIF.
ENDLOOP.

How to pass a default value in selection screen of logical database pnpce

Dear All,
Can any one tell me how to pass a default value in selection screen of logical database pnpce .
Regards
Rakesh Singh

Hi Rakesh,
Go to SE36 (logical database Builder).First enter PNPCE in Logical Database and press documentation,here you will get the details of exactly what is PNPCE and how it works.After that select selections in subojects in se36 only and enter display ,there you have the include from where you acn get the idea.
Regards,
Rahul

How to add default value to the Exclude single value in selection screen..

Hi Experts,
i have searched in sdn, but not able to get proper results,
in my report i have a selection screen, in that there is a Select-option like status, for this status i need to exclude '02'
for this i need to add the default value under exclude singale values option, not in lower and upper limit.
can anyone help me...
Regards,
Sudha.
Moderator message: please search for available information/documentation before asking, don't just claim you did.
Edited by: Thomas Zloch on Oct 27, 2010 2:50 PM

Hi,
you can use the function module SELECT_OPTIONS_RESTRICT .
This function module simplifies the handling of SELECT-OPTIONS on the selection screen by restricting possible selection options and signs.
By calling this function module, you can restrict the number of selectio options available for the chosen selection field. You can also disable the function allowing users to enter values to be excluded from the selection (SIGN = 'E').
Regards,
S.Velsankar

Selection screen default

Similar Messages

Maybe you are looking for