Write stmt before at selection-screen

can we execute the write stmt before at selection-screen event?
Edited by: anil ajmera on Sep 20, 2009 3:42 AM

Hi Anil , This can not be achived as selection screen will always be displayed and you will not be able to get the write statement .
You should program your logic in such a way that you can display the message which you want on the selection screen itself.
Hope its help you.

Similar Messages

Can i write write statement at AT SELECTION-SCREEN

Hi all,
can i write write statement at AT SELECTION-SCREEN
Thanks

Hi,
If u want show something on the selection screen then u can write the logic like this instead of write statement
selection-screen begin of block b3 with frame title text-057.
selection-screen comment /1(66) text-056.
selection-screen comment /1(12) txtgl1.
selection-screen comment 14(3) splgl1.
selection-screen comment /1(8) txtgl2.
selection-screen comment 14(3) splgl2.
selection-screen comment /1(6) txtgl3.
selection-screen comment 14(3) splgl3.
selection-screen end of block b3.
For Display of the 'SPLGL Indicator Help'
initialization.
txtgl1 = 'Chq Dishonor'.
splgl1 = '- D'.
txtgl2 = 'WCT TDS'.
splgl2 = '- L'.
txtgl3 = 'IT TDS'.
splgl3 = '- I'.

How to write text on the selection screen of a report

Hi all,
I need to write some user defined text on the selection screen of an ALV GRID Report.
Please suggest me how can i do this
Thanks
Ajay.

SELECTION-SCREEN BEGIN OF LINE .
SELECTION-SCREEN COMMENT 12(31) text-024.<-----Goto text elements and add text.
PARAMETERS:P_FILEN LIKE RLGRAP-FILENAME .
SELECTION-SCREEN END OF LINE

AUTHORITY-CHECK before Selection-screen?

Hi,
i want to check the authority before the selection-screen. I do it in this way:
AT SELECTION-SCREEN OUTPUT.
AUTHORITY-CHECK OBJECT 'Z_REPORT'
           ID 'PROGRAM' FIELD SY-REPID
           ID 'ACTVT'   FIELD '16'. "Ausführen
IF SY-SUBRC <> 0.
    MESSAGE E010 WITH 'Keine Berechtigung für Programm: '
    SY-REPID.
ENDIF.
But the selection appears without any parameters.
Is there a way to check without the selection-screen?
thanks.
regards, Dieter

Hi Dieter,
Please check the below code for at selection screen authorization check.
Handling selection screen events
AT SELECTION-SCREEN ON p_carrid.
IF p_carrid IS INITIAL.
    MESSAGE 'Please enter a value' TYPE 'E'.
ENDIF.
AUTHORITY-CHECK OBJECT 'S_CARRID'
                      ID 'CARRID' FIELD p_carrid
                      ID 'ACTVT' FIELD '03'.
IF sy-subrc = 4.
    MESSAGE 'No authorization for carrier' TYPE 'E'.
ELSEIF sy-subrc <> 0.
    MESSAGE 'Error in authority check' TYPE 'A'.
ELSE.
    IF sy-ucomm = 'ONLI'.
      CALL SELECTION-SCREEN '0500'.
    ENDIF.
ENDIF.
Regards,
Md Ziauddin

Pop up before selection screen

hi all,
i need to give a pop up screen before the selection screen which will take the value for the number of records to be displayed. how to do this ?
thanks,
Amit

You could do something like this.
report zrich_0001.
data: value1 type spop-varvalue1.
data: answer type c.
parameters: p_check type c.
load-of-program.
check sy-ucomm = space.
call function 'POPUP_TO_GET_ONE_VALUE'
    exporting
      textline1            = 'Number of Records:'
*   TEXTLINE2            = ' '
*   TEXTLINE3            = ' '
      titel                = 'Number of Records'
      valuelength          = '5'
   importing
      answer               = answer
      value1               = value1.
start-of-selection.
But I really don't understand your requirement. Why not ask for this value on the selection screen itself?
Regards,
Rich Heilman

Can we display a message before selection screen

hi experts,
               I need to give a message to user's to give information abt the selection screen .
like select values between 1000 to 2000 only.
date must be todays date.
so how i can display a message before the selection screen is displayed

try like this it may be useful for you.
load-of-program.
CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
EXPORTING
   TITEL              = 'Selection screen info'
    TEXTLINE1          = 'Material no should be between 1000 and 2000'
   TEXTLINE2          = 'Plant should be 1000'
*   START_COLUMN       = 25
*   START_ROW          = 6
start-of-selection.
if you want some more fields to pass then search popup* fn module in se37 which can be useful 4 you.
regards
shiba dutta

Issue with tabbed block in selection screen

Hi All,
I have created a report program with the following code.
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
PARAMETERS: p1 TYPE c LENGTH 10.
SELECTION-SCREEN END OF SCREEN 100.
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
PARAMETERS: q1 TYPE c LENGTH 10.
SELECTION-SCREEN END OF SCREEN 200.
SELECTION-SCREEN: BEGIN OF TABBED BLOCK mytab FOR 10 LINES,
                  TAB (20) button1 USER-COMMAND push1,
                  TAB (20) button2 USER-COMMAND push2,
                  END OF BLOCK mytab.
INITIALIZATION.
button1 = 'Selection Screen 1'.
button2 = 'Selection Screen 2'.
mytab-prog = sy-repid.
mytab-dynnr = 0100.
mytab-activetab = 'PUSH1'.
AT SELECTION-SCREEN.
CASE sy-dynnr.
    WHEN 1000.
      CASE sy-ucomm.
        WHEN 'PUSH1'.
          mytab-dynnr = 100.
        WHEN 'PUSH2'.
          mytab-dynnr = 200.
      ENDCASE.
ENDCASE.
Execute the program and click on the second tab-page. Now, click on the 'Execute' button or press F8 (there is no specific functionality coded here).
The issue now is that the first tab-page is displayed, instead of the second tab remaining displayed. I require the navigation to remain within the second tab-page after the EXECUTE button is clicked.
Could someone help me out with this issue?
Regards,
Dinup
Edited by: Dinup Sudhakaran on Feb 18, 2008 1:40 PM

Hi,
Go through below document with example code.
It will help you.
Tabstrip Controls on Selection Screens
As with screens, you can now use tabstrip controls on selection screens. To do this, you must define a tabstrip area and the associated tab pages, and assign a subscreen to the tab pages. You do not have to (indeed, cannot) declare the tabstrip control or program the screen flow logic in your ABAP program, since both are automatically generated.
To define a tabstrip area with tab pages, use the following statements in your selection screen definition:
SELECTION-SCREEN: BEGIN OF TABBED BLOCK <tab_area> FOR <n> LINES,
                  TAB (<len>) <tab1> USER-COMMAND <ucom1>
                              [DEFAULT [PROGRAM <prog>] SCREEN <scrn>],
                  TAB (<len>) <tab2> USER-COMMAND <ucom2>
                              [DEFAULT [PROGRAM <prog>] SCREEN <scrn>],
                  END OF BLOCK <tab_area>.
This defines a tabstrip control <tab_area> with size <n>. The tab pages <tab1>, <tab2> are assigned to the tab area. <len> defines the width of the tab title. You must assign a function code <ucom> area to each tab title. You can find out the function code from the field SY-UCOMM in the AT SELECTION-SCREEN event.
For each tab title, the system automatically creates a character field in the ABAP program with the same name. Before the selection screen is displayed, you can assign a text to the field. This then appears as the title of the corresponding tab page on the selection screen.
You must assign a subscreen to each tab title. This will be displayed in the tab area when the user chooses that title. You can assign one of the following as a subscreen:
A subscreen screen defined using the Screen Painter.
A selection screen subscreen, defined in an ABAP program.
You can make the assignment either statically in the program or dynamically at runtime. If, at runtime, one of the tab titles has no subscreen assigned, a runtime error occurs.
Static assignment
Use the DEFAULT addition when you define the tab title. You can specify an ABAP program and one of its subscreens. If you do not specify a program, the system looks for the subscreen in the current program. When the user chooses the tab title, it is activated, and the subscreen is assigned to the tabstrip area. The static assignment is valid for the entire duration of the program, but can be overwritten dynamically before the selection screen is displayed.
Dynamic assignment
For each tab area, the system automatically creates a structure in the ABAP program with the same name. This structure has three components PROG, DYNNR, and ACTIVETAB. When you assign the subscreens statically, the structure contains the name of the ABAP program containing the subscreen, the number of the subscreen, and the name of the tab title currently active on the selection screen (and to which these values are assigned). The default active tab page is the first page. You can assign values to the fields of the structure before the selection screen is displayed, and so set a subscreen dynamically.
If you assign a normal subscreen screen to a tab title, the dialog modules containing its flow logic must be defined in the current ABAP program. If the subscreen is a selection screen, user actions will trigger the AT SELECTION-SCREEN event and its variants (see Selection Screen Processing). This includes when the user chooses a tab title. If one selection screen is included on another, AT SELECTION-SCREEN will be triggered at least twice firstly for the "included" selection screen, then for the selection screen on which it appears.
REPORT demo_sel_screen_with_tabstrip.
DATA flag(1) TYPE c.
SUBSCREEN 1
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS: p1(10) TYPE c,
            p2(10) TYPE c,
            p3(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN END OF SCREEN 100.
SUBSCREEN 2
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME.
PARAMETERS: q1(10) TYPE c OBLIGATORY,
            q2(10) TYPE c OBLIGATORY,
            q3(10) TYPE c OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN END OF SCREEN 200.
STANDARD SELECTION SCREEN
SELECTION-SCREEN: BEGIN OF TABBED BLOCK mytab FOR 10 LINES,
                  TAB (20) button1 USER-COMMAND push1,
                  TAB (20) button2 USER-COMMAND push2,
                  TAB (20) button3 USER-COMMAND push3
                                   DEFAULT SCREEN 300,
                  END OF BLOCK mytab.
INITIALIZATION.
button1 = text-010.
button2 = text-020.
button3 = text-030.
mytab-prog = sy-repid.
mytab-dynnr = 100.
mytab-activetab = 'BUTTON1'.
AT SELECTION-SCREEN.
CASE sy-dynnr.
    WHEN 1000.
      CASE sy-ucomm.
        WHEN 'PUSH1'.
          mytab-dynnr = 100.
          mytab-activetab = 'BUTTON1'.
        WHEN 'PUSH2'.
          mytab-dynnr = 200.
          mytab-activetab = 'BUTTON2'.
      ENDCASE.
    WHEN 100.
      MESSAGE s888(sabapdocu) WITH text-040 sy-dynnr.
    WHEN 200.
      MESSAGE s888(sabapdocu) WITH text-040 sy-dynnr.
ENDCASE.
MODULE init_0100 OUTPUT.
LOOP AT SCREEN.
    IF screen-group1 = 'MOD'.
      CASE flag.
        WHEN 'X'.
          screen-input = '1'.
        WHEN ' '.
          screen-input = '0'.
      ENDCASE.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
ENDMODULE.
MODULE user_command_0100 INPUT.
MESSAGE s888(sabapdocu) WITH text-050 sy-dynnr.
CASE sy-ucomm.
    WHEN 'TOGGLE'.
      IF flag = ' '.
        flag = 'X'.
      ELSEIF flag = 'X'.
        flag = ' '.
      ENDIF.
ENDCASE.
ENDMODULE.
START-OF-SELECTION.
WRITE: / 'P1:', p1,'Q1:', q1,
         / 'P2:', p2,'Q2:', q2,
         / 'P3:', p3,'Q3:', q3.
This program defines two selection screens 100 and 200, as subscreens, and places a tabstrip control area with three tab pages on the standard selection screen. A subscreen screen 300 (from the same program) is assigned statically to the third tab page.
The layout of screen 300 is:
The input/output fields P1 to Q3 are defined by using the parameters from the ABAP program The pushbutton has the function code TOGGLE.
The screen flow logic for screen 300 is as follows:
PROCESS BEFORE OUTPUT.
MODULE init_0100.
PROCESS AFTER INPUT.
MODULE user_command_0100.
Both dialog modules are defined in the ABAP program.
When you run the program, the standard selection screen appears. In the INITIALIZATION event, the texts are defined on the tab titles, the subscreen selection screen 100 is assigned to the tab area, and the first tab title is activated.
User actions on the selection screen are processed in the AT SELECTION-SCREEN event block. In particular, it is here that the subscreens are assigned and tab titles activated when the user chooses one of the first two tab titles. This is not necessary for the third tab title, since the dynamic assignment (screen 300) is always placed in the structure MYTAB when the user chooses it.
Before the subscreen screen is displayed, the PBO module INIT_100 is executed. User actions on the subscreen screen trigger the PAI module. This includes when the user chooses a tab title. After that, the AT SELECTION-SCREEN event is triggered.
Messages in the status line show where an action has been processed.

Botton on selection screen

Hello gurus ,
           guru I want to make a selection screen like fint tcode . suppose I have two button one is open and another is close , when user will press the open button one bolck will come wih close button and open button will disappear , and viceversa . Just like FINT .
How to do , if any one have any sample prog plz healp .
I am waiting for your valuable reply .
Regards ,
Joy .

hi,
You can modify the selection-screen properties so that it will work like fint transaction. For getting the push buttons on the screen refer to the following documentation and example. You can use the event at selection-screen for modifying their properties based on ucomm value.
Pushbuttons on the Selection Screen
To create a pushbutton on the selection screen, you use:
SELECTION SCREEN PUSHBUTTON [/]<pos(len)> <push>
                            USER-COMMAND <ucom> [MODIF ID <key>].
The [/]<pos(len)> parameters and the MODIF IF addition have the same function as for the formatting options for underlines and comments.
<push> determines the pushbutton text. For <push>, you can specify a text symbol or a field name with a maximum length of eight characters. This character field must not be declared with the DATA statement, but is generated automatically with length <len>. The field must be filled before the selection screen is called.
For <ucom>, you must specify a code of up to four characters. When the user clicks the pushbutton on the selection screen, <ucom> is entered in the UCOMM of the SSCRFIELDS interface work area. You must use the TABLES statement to declare the SSCRFIELDS structure. The contents of the SSCRFIELDS-UCOMM field can be processed during the AT SELECTION-SCREEN event.
REPORT DEMO.
TABLES SSCRFIELDS.
DATA FLAG.
SELECTION-SCREEN:
BEGIN OF SCREEN 500 AS WINDOW TITLE TIT,
    BEGIN OF LINE,
      PUSHBUTTON 2(10) BUT1 USER-COMMAND CLI1,
      PUSHBUTTON 12(10) TEXT-020 USER-COMMAND CLI2,
    END OF LINE,
    BEGIN OF LINE,
      PUSHBUTTON 2(10) BUT3 USER-COMMAND CLI3,
      PUSHBUTTON 12(10) TEXT-040 USER-COMMAND CLI4,
    END OF LINE,
END OF SCREEN 500.
AT SELECTION-SCREEN.
CASE SSCRFIELDS.
    WHEN 'CLI1'.
      FLAG = '1'.
    WHEN 'CLI2'.
      FLAG = '2'.
    WHEN 'CLI3'.
      FLAG = '3'.
    WHEN 'CLI4'.
      FLAG = '4'.
ENDCASE.
START-OF-SELECTION.
TIT = 'Four Buttons'.
BUT1 = 'Button 1'.
BUT3 = 'Button 3'.
CALL SELECTION-SCREEN 500 STARTING AT 10 10.
CASE FLAG.
    WHEN '1'.
      WRITE / 'Button 1 was clicked'.
    WHEN '2'.
      WRITE / 'Button 2 was clicked'.
    WHEN '3'.
      WRITE / 'Button 3 was clicked'.
    WHEN '4'.
      WRITE / 'Button 4 was clicked'.
    WHEN OTHERS.
      WRITE / 'No Button was clicked'.
ENDCASE.
This example defines four pushbuttons on a selection screen that is displayed as a dialog box. The selection screen is defined in a statement chain for keyword SELECTION-SCREEN.
Regards,
Veeresh

Push buttons are not triggering on the selection screen

selection-screen begin of block a with frame title text-001.
selection-screen skip.
parameters:z like vbap-vbeln.
selection-screen skip.
selection-screen begin of block b with frame title text-002.
selection-screen skip.
parameters:sales radiobutton group g default 'X',
           trans radiobutton group g.
selection-screen end of block b.
selection-screen skip.
selection-screen pushbutton 10(12) pu_text user-command CANC.
selection-screen pushbutton 30(12) qu_text user-command STAT.
selection-screen end of block a.
Initialization.
pu_text = 'Cancel Order'.
qu_text = 'Status'.
TABLES SSCRFIELDS.
AT SELECTION-SCREEN.
CASE SSCRFIELDS.
WHEN 'CANC'.
WRITE 'CANCEL'.
WHEN 'STAT'.
WRITE 'STATUS'.
ENDCASE.

hi,
in your program declare SSCRFIELDS table before defining selection-screen with push-buttons.
To create a pushbutton on the selection screen, you use:
<b>SELECTION SCREEN PUSHBUTTON [/]<pos(len)> <push>
                            USER-COMMAND <ucom> [MODIF ID <key>].</b>
The [/]<pos(len)> parameters and the MODIF IF addition have the same function as for the formatting options for underlines and comments.
<b>follow this sample program.</b>
REPORT DEMO.
TABLES SSCRFIELDS.
DATA FLAG.
SELECTION-SCREEN:
BEGIN OF SCREEN 500 AS WINDOW TITLE TIT,
    BEGIN OF LINE,
      PUSHBUTTON 2(10) BUT1 USER-COMMAND CLI1,
      PUSHBUTTON 12(10) TEXT-020 USER-COMMAND CLI2,
    END OF LINE,
    BEGIN OF LINE,
      PUSHBUTTON 2(10) BUT3 USER-COMMAND CLI3,
      PUSHBUTTON 12(10) TEXT-040 USER-COMMAND CLI4,
    END OF LINE,
END OF SCREEN 500.
AT SELECTION-SCREEN.
CASE SSCRFIELDS.
    WHEN 'CLI1'.
      FLAG = '1'.
    WHEN 'CLI2'.
      FLAG = '2'.
    WHEN 'CLI3'.
      FLAG = '3'.
    WHEN 'CLI4'.
      FLAG = '4'.
ENDCASE.
START-OF-SELECTION.
TIT = 'Four Buttons'.
BUT1 = 'Button 1'.
BUT3 = 'Button 3'.
CALL SELECTION-SCREEN 500 STARTING AT 10 10.
CASE FLAG.
    WHEN '1'.
      WRITE / 'Button 1 was clicked'.
    WHEN '2'.
      WRITE / 'Button 2 was clicked'.
    WHEN '3'.
      WRITE / 'Button 3 was clicked'.
    WHEN '4'.
      WRITE / 'Button 4 was clicked'.
    WHEN OTHERS.
      WRITE / 'No Button was clicked'.
ENDCASE.
regards,
Ashok Reddy

How to Add Push Button On Selection Screen

Hi Experts,
How to add Push button on Selection Screen.
Points will b rewarded for useful help.
Bohra.

Hi,
To create a pushbutton on the selection screen, you use:
SELECTION SCREEN PUSHBUTTON [/]<pos(len)> <push>
USER-COMMAND <ucom> [MODIF ID <key>].
The [/]<pos(len)> parameters and the MODIF IF addition have the same function as for the formatting options for underlines and comments.
<push> determines the pushbutton text. For <push>, you can specify a text symbol or a field name with a maximum length of eight characters. This character field must not be declared with the DATA statement, but is generated automatically with length <len>. The field must be filled before the selection screen is called.
For <ucom>, you must specify a code of up to four characters. When the user clicks the pushbutton on the selection screen, <ucom> is entered in the UCOMM of the SSCRFIELDS interface work area. You must use the TABLES statement to declare the SSCRFIELDS structure. The contents of the SSCRFIELDS-UCOMM field can be processed during the AT SELECTION-SCREENevent.
Ex.
REPORT DEMO.
TABLES SSCRFIELDS.
DATA FLAG.
SELECTION-SCREEN:
BEGIN OF SCREEN 500 AS WINDOW TITLE TIT,
BEGIN OF LINE,
PUSHBUTTON 2(10) BUT1 USER-COMMAND CLI1,
PUSHBUTTON 12(10) TEXT-020 USER-COMMAND CLI2,
END OF LINE,
BEGIN OF LINE,
PUSHBUTTON 2(10) BUT3 USER-COMMAND CLI3,
PUSHBUTTON 12(10) TEXT-040 USER-COMMAND CLI4,
END OF LINE,
END OF SCREEN 500.
AT SELECTION-SCREEN.
CASE SSCRFIELDS.
WHEN 'CLI1'.
FLAG = '1'.
WHEN 'CLI2'.
FLAG = '2'.
WHEN 'CLI3'.
FLAG = '3'.
WHEN 'CLI4'.
FLAG = '4'.
ENDCASE.
START-OF-SELECTION.
TIT = 'Four Buttons'.
BUT1 = 'Button 1'.
BUT3 = 'Button 3'.
CALL SELECTION-SCREEN 500 STARTING AT 10 10.
CASE FLAG.
WHEN '1'.
WRITE / 'Button 1 was clicked'.
WHEN '2'.
WRITE / 'Button 2 was clicked'.
WHEN '3'.
WRITE / 'Button 3 was clicked'.
WHEN '4'.
WRITE / 'Button 4 was clicked'.
WHEN OTHERS.
WRITE / 'No Button was clicked'.
ENDCASE.
This example defines four pushbuttons on a selection screen that is displayed as a
dialog box. The selection screen is defined in a statement chain for keyword
SELECTION-SCREEN.
If the text symbols TEXT-020 and TEXT-040 are defined as 'Button 2' and 'Button 4',
the four pushbuttons appear as follows on the selection screen displayed as a dialog box.
Regards,
Bhaskar

Selection-screen output , initialaization confusion

we have selectionscreen output, initialization events
first initializatuion,
than at selection-screen output
execute it, than we pressed f3 came bact to selection-screen
than which event ll trigger
thank you
kals.

The different events in a report Program are:
Load-of-program
Triggers the associated event in an internal session after loading a program of type 1, M, F, or S. Also runs the associated processing block once and once only for each program and internal session. The processing block LOAD-OF-PROGRAM has roughly the same function for an ABAP program of type 1, M, F or S as a constructor has for classes in ABAP Objects
Initialization.
This event is executed before the selection screen is displayed .
Initialization of all the values.
You can assign different values other than the values defaulted on the selection screen .
You can fill your selection screen with some values at runtime.
At Selection-Screen.
The event is processed when the selection screen has been processed (at the end of PAI ).
Validation & Checks of inputted values happen here
Extras :
ON VALUE-REQUEST FOR psel_low_high .
The pushbutton for F4 (Possible entries) appears beside the appropriate field.
... ON HELP-REQUEST FOR psel_low_high
. ... OUTPUT
This event is executed at PBO of the selection screen every time the user presses ENTER
Start-of-Selection.
Here the program starts selecting values from tables.
End-of-selection.
After all the data has been selected this event writes the data to the screen.
Interactive Events
Used for interactive reporting. It is used to create a detailed list from a basic list.
Events in an ABAP/4 Report Program
Start-Of-Selection
Processing block is executed after processing the selection screen
All the data is selected in this block.
All the main processing on the data except for interactive reporting is handled in this block.
End-Of-Selection
Data which is selected and has been processed is printed to the screen in this block.
List Processing happens in this block
Top-of-Page.
New-Page.
End-of-Page.
Events during List Processing
Top-of-Page.
Triggered by the first write statement in the program
It is used to have a standard header in the program for all the pages.
TOP-OF-PAGE is only executed before outputting the first line on a new page
New-Page.
Can be used when one wants to display different data on different pages
Terminates the current page and continues output on a new page.
Will not trigger the Top-of-Page or End-of-Page.
End-of-Page.
It is used to have a standard footer for all the pages.
Triggered by the program if the number of records exceed the line-count of the program.
Hope u understood....

AT SELECTION-SCREEN OUTPUT not working!

Hi,
I am useing the statement AT SELECTION-SCREEN OUTPUT to disable some input fields based on a check box(PR_FILE).however when I execute the program the changes on the screen are not reflected!I have written the AT SELECTION-SCREEN OUTPUT stmt immediately after SELECTION-SCREEN stmt .
Defination for the screen elements is as follows:
SELECT-OPTIONS s_plants FOR ls_selected_plant-plant
                                                     NO INTERVALS.
SELECTION-SCREEN BEGIN OF BLOCK filesel WITH FRAME TITLE text-012.
PARAMETERS pr_file TYPE xfeld .
PARAMETER : pr_path LIKE rlgrap-filename .
SELECTION-SCREEN END OF BLOCK filesel.
AT SELECTION-SCREEN OUTPUT.
IF pr_file = 'X'.
    LOOP AT SCREEN.
      IF screen-name = 's_plants'.
        screen-input    = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSE.
    LOOP AT SCREEN.
      IF screen-name = 'pr_path'.
        screen-input    = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
Can anybody suggest what wrong i have done??

You need to use the User Command for the checkbox and the Modificaiton ID (Group) for the fields.
Try like this:
TABLES: VBRP.
SELECT-OPTIONS S_PLANTS FOR VBRP-WERKS NO INTERVALS MODIF ID GP1.
SELECTION-SCREEN BEGIN OF BLOCK FILESEL WITH FRAME TITLE TEXT-012.
PARAMETERS PR_FILE TYPE XFELD USER-COMMAND USR1.
PARAMETER : PR_PATH LIKE RLGRAP-FILENAME MODIF ID GP2 .
SELECTION-SCREEN END OF BLOCK FILESEL.
AT SELECTION-SCREEN OUTPUT.
    IF PR_FILE = 'X'.
      LOOP AT SCREEN.
        if screen-group1 = 'GP1'.
          SCREEN-active = '0'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ELSE.
      LOOP AT SCREEN.
        IF SCREEN-group1 = 'GP2'.
          SCREEN-active = '0'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
Regards,
Naimesh Patel

LDB Selection-screen

Hello ,
In my program selection-screen is coming from LDB(logical database) and i want my own selection-screen in the top means before LDB selection-screen.
Pls solve this ASAP.
Thanks.

Hi,
Create your own selection-screen in your report with Parameters and select-option and activate.
Then automatically it will come.
Regards,
N.L.Narayana

User option in selection screen of report

In a report, want to give user an initial option of Calendar year/month OR calendar year/week...
Only the one the user wants should be displayed on the selection screen.
1 Is there a way to give user an option while running the query before the selection screen(variables - uesr input) of the report appears
OR
2 Is there a way to give user a toggle option on the selection screen which displays either calendar year/month or calendar year/week based on user choice but not both.
I am aware that user can easily toggle once the report has been executed, but the purpose is to give user this option initially.
As of now, in the report at the selection screen there are four periods based on calendar year/month. (to facilitate comparison of periods)
eg (m- cal year/month, w - cal year/week)
P1(m)
P2(m)
P3(m)
P4(m)
If we add four more for week
then user will have a cluttered selection screen (as there are many other selection options apart from time)
eg 8 time choices
P1(m)
P2(m)
P3(m)
P4(m)
P1(w)
P2(w)
P3(w)
P4(w)
What I need is a way for at any time, either cal year/month or cal year/week is visible based on user choice.

In a report, want to give user an initial option of Calendar year/month OR calendar year/week...
Only the one the user wants should be displayed on the selection screen.
1 Is there a way to give user an option while running the query before the selection screen(variables - uesr input) of the report appears
OR
2 Is there a way to give user a toggle option on the selection screen which displays either calendar year/month or calendar year/week based on user choice but not both.
I am aware that user can easily toggle once the report has been executed, but the purpose is to give user this option initially.
As of now, in the report at the selection screen there are four periods based on calendar year/month. (to facilitate comparison of periods)
eg (m- cal year/month, w - cal year/week)
P1(m)
P2(m)
P3(m)
P4(m)
If we add four more for week
then user will have a cluttered selection screen (as there are many other selection options apart from time)
eg 8 time choices
P1(m)
P2(m)
P3(m)
P4(m)
P1(w)
P2(w)
P3(w)
P4(w)
What I need is a way for at any time, either cal year/month or cal year/week is visible based on user choice.

Opening a selection screen in display mode

I have an ALV grid created in OOPS. Each line of this ALV has name of a report and its variant name. Here I have created a button on toolbar. When a user selects a line and clicks this button, selection screen of the selected report is to be opened in display mode with selection screen filled as per its variant. Both the report name and varaint name will be same as the selected line. I am able to open the selection with varaint filled, but it comes in editable mode. How do I make it non-editable mode?

Hi,
For making your selection screen non editable you will have to disable them for input.
For this you will have to modify the screen structure.
try this:
loop at screen
if screen-fieldname = 'XYZ'.
screen-input = '0'.
endif.
modify screen.
endloop.
You can write this code at selection screen of the program which calls this selection screen.
Call this code under a condition, so that it get triggeres only when you call this screen form the ALV.

Write stmt before at selection-screen

Similar Messages

Maybe you are looking for