Reports(Selection screen events)
Hi guys,
What are the 11 selection screen events?
Hai Raj Singh
Here is the Report Event
Check it
This is the order of execution in Classical/Interactive Report Events
Classical Reports
Reports which are properly formatted (header, footer, page numbers etc.,) with the help of one or more external events like top-of-page,end-of-page etc., are called as CLASSICAL REPORTS.
Standard list.
Output of Report program is nothing but Standard list. It consists of one continuous page of 60,000 lines.
To restrict number of lines per page.
Report Zxxxxx line-count 25.
OR
Report Zxxxxx line-count 25(3).
( In this case 3 lines are reserved for footer)
To restrict Output width.
Report Zxxxx line-size 125.
To suppress standard page heading.
Report Zxxxx no standard page heading
Above all at a time:
Report Zxxxx line-count 25(3)
line-size 125
no standard page heading.
Screen Events List Events
Initialization. Start-of-selection
At selection-screen. Top-of-page.
At selection-screen on <field>. End-of-page.
End-of-selection.
We can initialize the selection-screen with calculated default values under this event.
Initialization.
s_date-high = sy-datum.
s_date-low = sy-datum - 15.
Append s_date.
We can validate all the inputs on selection screen fields under this event.
At selection-screen.
If s_carrid-low is initial or
s_connid-low is initial or
s_date is initial.
< ... code for validation... >.
Endif.
We can validate a particular field input on selection screen under this event.
At selection-screen on s_carrid.
If s_carrid-low < > LH.
<
code for validation
>
Endif.
If any of the other event comes before
Select
Endselect. statements, then to break
that event, we require this S-O-S event.
Start-of-selection.
Select * from
Endselect.
If we need some portion of the output (like
column headings) to appear in all the pages,
then we use this event.
Top-of-page.
Write:/ Carrier,10 Connection 20 Date.
If there is no external output statement before
Top-of-page event, then this event will not
work.
Once the cursor reaches the last line of the
page, automatically this event will be triggered.
Report Zxxx line-count 25(3).
In this case line numbers 23, 24 and 25 are
reserved for footer.
Once the cursor reaches 23rd line, this event
will be triggered.
End-of-page.
Write:/ sy-uline(75).
Write:/ This is end of page:,sy-pagno.
Write:/ sy-uline(75).
This event is used for concluding part of List.
End-of-selection.
Write:/ This is end of the Report.
Interactive Report
A simple report or even a classical report displays a clustered list with all the requested output at one go.
What ever it is displayed, it is final. That means, the user can not interact with with that list.
A simple report or even a classical report displays a clustered list with all the requested output at one go.
What ever it is displayed, it is final. That means, the user can not interact with with that list.
In the interactive reports, we can create as many as 21 lists.
The first list is called Basic list and all the successive lists are called Secondary lists. Each list is again an interactive.
The Basic list is not deleted when secondary list is created.
A secondary list may either overlay the basic list or appear in an additional dialog window on the same screen.
The system variable associated with list number is SY-LSIND.
For basic list SY-LSIND = 0 and for secondary lists, SY-LSIND varies from 1 to 20.
User can interact with the list by the following ways.
Double clicking or single click and pressing F2 (function key) or single click with hotspot on.
OR
Selecting from menu bar or from application tool bar.
All the events used in classical reports can be used in Basic List.
The event End-of-page can be used in Secondary Lists also.(the other six events can not be used in secondary lists)
You can not place select-options in secondary lists.
The following additional events are
applicable to secondary lists.
Top-of-page during line-selection.
At line-selection.
At user-command.
When you double click on any field in the basic list, you will be navigating to secondary list with detailed information pertaining to clicked field.
As such we need to store the clicked field information at some variable.
Hide temporarily stores the content of clicked field for later use.
The default title of the out put is the text what we enter during creation of program.
This title can be changed using:
SET TITLEBAR AAA.
GUI status includes:
Menu bar
Application tool bar and
Activating standard tool bar
GUI status can be created using
SET PF-STATUS BBB.
You can have 8 menus ( out of which, 2 menus are reserved for System and Help).
Each menu can have 15 menu items.
Each menu item can have 3 levels of submenus.
You can create 35 items in application tool bar.
Thanks & Regards
Sreenivasulup
Similar Messages
-
How to get rid of the loop in ALV output from At selection screen event?
I have several push buttons on a selection screen.
Clikc on a button, then it pops up an editable ALV report. (This gets triggered AT SELECTION SCREEN event.). REUSE_ALV_GRID_DISPLAY_LVC..
On the ALV output, I enabled F4 for a couple of fields. Once I click on the F4 button, ONF4 method gets triggerd and a pop up appears with custom search helps.
choose a line and it fills the cell.
Upto this it works fine.
Now I click on the BACK button at the ALV output, it takes me to the selection screen. I click on the button again, it show the editable ALV. Now when I click on the F4 button, the pop up comes up twice and the cell gets filled from the second pop - up.
How to control this?
Probably I am not refreshing something?
(I am using REUSE_ALV_GRID_DISPLAY_LVC and tooks ome code for ONF4 event from BCALV_*DATATYPES (forgot the exact name) program.)
Thanks,
VenHi,
FORM refresh_grid USING pw_grid TYPE REF TO cl_gui_alv_grid.
*Work area
DATA : wal_stable TYPE lvc_s_stbl.
CHECK NOT pw_grid IS INITIAL.
wal_stable-col = c_check.
wal_stable-row = c_check.
*Method to refresh grid
CALL METHOD pw_grid->refresh_table_display
EXPORTING
is_stable = wal_stable
i_soft_refresh = c_check
EXCEPTIONS
finished = 1
OTHERS = 2.
ENDFORM. " refresh_grid
Thanks,
Sree. -
How to catch the select-options value in AT SELECTION-SCREEN event?
Hi,all
This is my code:
SELECT-OPTIONS: P_BUKRS FOR T012-BUKRS.
PARAMETERS: P_BNKA TYPE BANKA.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_BNKA.
select single bankl from bnka where bukrs = p_bukrs.
Last statement failed because p_bukrs was null.
So, How can I got the value of p_bukrs in AT SELECTION-SCREEN event?Hi Jie,
try following code.
REPORT zanu_test.
TABLES : t012.
PARAMETERS: p_bukrs LIKE t012-bukrs.
PARAMETERS: p_bnka TYPE banka.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_bnka.
DATA: BEGIN OF dynpfields OCCURS 0.
INCLUDE STRUCTURE dynpread.
DATA: END OF dynpfields.
*--- IT for changing fields on the screen
DATA : t_dynp_flds LIKE dynpread OCCURS 0 WITH HEADER LINE,
t_dynpfields LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: l_bukrs LIKE t012-bukrs.
DATA: BEGIN OF it_bank OCCURS 0,
banka LIKE bnka-banka,
END OF it_bank.
DATA: l_tabix LIKE sy-tabix.
dynpfields-fieldname = 'P_BUKRS'. APPEND dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
dyname = 'ZANU_TEST'
dynumb = sy-dynnr
TABLES
dynpfields = 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 EQ 0.
READ TABLE dynpfields WITH KEY fieldname = 'P_BUKRS'.
IF sy-subrc EQ 0.
MOVE dynpfields-fieldvalue TO l_bukrs.
ENDIF.
ELSE.
EXIT.
ENDIF.
SELECT b~banka INTO CORRESPONDING FIELDS OF TABLE it_bank
FROM t012 AS a
INNER JOIN bnka AS b
ON abanks = bbanks AND abankl = bbankl
WHERE a~bukrs = l_bukrs.
CLEAR l_tabix.
CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'
EXPORTING
endpos_col = 85
endpos_row = 20
startpos_col = 50
startpos_row = 10
titletext = text-035
IMPORTING
choise = l_tabix
TABLES
valuetab = it_bank
EXCEPTIONS
break_off = 1
OTHERS = 2.
IF sy-subrc EQ 0.
READ TABLE it_bank INDEX l_tabix.
IF sy-subrc EQ 0.
*--- Clear IT t_dynp_flds
CLEAR : t_dynp_flds,
t_dynp_flds[].
*--- Append screen values
t_dynp_flds-fieldname = 'P_BNKA'.
t_dynp_flds-fieldvalue = it_bank-banka.
APPEND t_dynp_flds.
CLEAR t_dynp_flds.
ENDIF.
ENDIF.
*--- Change screen field contents w/o PBO
CALL FUNCTION 'DYNP_VALUES_UPDATE'
EXPORTING
dyname = 'ZANU_TEST'
dynumb = sy-dynnr
TABLES
dynpfields = t_dynp_flds
EXCEPTIONS
invalid_abapworkarea = 1
invalid_dynprofield = 2
invalid_dynproname = 3
invalid_dynpronummer = 4
invalid_request = 5
no_fielddescription = 6
undefind_error = 7
OTHERS = 8.
START-OF-SELECTION.
-Anu -
How to prevent AT SELECTION-SCREEN event on second Selection Screen
Hi All
I have a program in which I am entering some parameters in a selection screen and also validating them in AT SELECTION-SCREEN events. After validating them the program shows another selection screen in which I have some push-buttons. I have some events on those push-buttons also.
However I am facing a different problem now. When I execute the second selection screen I get the report, and when I click on back button then it again triggers the AT SELECTION SCREEN event of the first selection screen and displays the related messages.
How to prevent this ? Is there any way where I can restrict the execution of selection screen events for a particular selection screen?
AmolHi,
try this logic when Ist selection screen validation
is done set a flag = 'X' .
at selection-screen.
if glag is initial
*screen validation
flag = 'X..
endif.
regards
amole -
Subscreen with Select-Options called from At Selection Screen event
Dear friends,
I'm trying to call a subscreen that contains a select-options, from an 'at selection screen' event, in a report program, but without sucess.
Here's go what I'm doing:
I declared a selection-screen as subscreen in my main program, and I'm calling it from a module-pool subscreen area, to make the module-pool select-options magic.
In my main report program, I have a customized status GUI with a new toolbar button and I'm handling it at the 'at selection screen' event.
What I need to do is to call the subscreen that contains the select-options when this new customized button get pressed, but when It happens, the select-option selections pop-up doesn't appear.
If I call the subscreen from the 'start-of-selection' event, it goes fine, just don't work from the 'at selection screen'.
Any ideas on how can I do it?
Thank you,
Heberi think you should try something like this:
at selection screen.
if condition handled ....
show_popup = 'X'.
endif.
at selection screen output.
if show_popup EQ 'X.
call subscreen
endif. -
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.
ThanksHi 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
<u><b>Effect</b></u>
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.
<b>
Addition 6</b>
... ON BLOCK block
Effect
<b><i>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.</i></b>
<u><b>Note</b></u>
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?
<i>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".</i>
<b>Example</b>
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.
<b>Sequence:</b>
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.
<b>Addition 7</b>
... OUTPUT
<u>Effect</u>
<b>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.</b>
<u><b>Example</b></u>
<b>Output all fields of the
SELECT-OPTION NAME
highlighted:</b>
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.
<i><b>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.
</b></i>
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 -
Capture Selection-screen events
Dear SAP friends,
I have created OOP report.
At the runtime the program creates toolbar and adds pushbuttons to it.
Every button has fcode assigned.
On button click the below method is called.
The below statement "CALL SELECTION-SCREEN 1200 STARTING AT 10 10" calls selection screen as popup.
I need to capture when User closes the selection popup and when he clicks Cancel button located in the selection popup.
Please advise.
Regards
Tatyana.
METHOD handle_pushbutton_click.
CASE fcode.
WHEN 'CHECKS_EXP'.
CALL SELECTION-SCREEN 1200 STARTING AT 10 10.
PERFORM at_selection_1200.
CHECK w_continue = abap_true.
PERFORM build_options_range.
PERFORM build_options_norange.
PERFORM start_selection_1200.
PERFORM fcat_init_1200.
w_title = 'Checks -> Expenditures'.
PERFORM set_layout USING w_title.
PERFORM getdata_1200.
DESCRIBE TABLE lt_rpt LINES w_count. " Get number of records.
PERFORM populate_selection USING w_count.
ENDDCASE.Hello Tatyana
The following sample report ZUS_SDN_OO_REPORT_SELSCREEN should simulate your scenario.
If you push the EXECUTE button you will find ok-code='CRET'.
If you close the popup or push the CANCEL button ok-code=' ' (space; empty). This way you know that the popup was closed by the user.
*& Report ZUS_SDN_OO_REPORT_SELSCREEN
*& Thread: Capture Selection-screen events
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1205127"></a>
REPORT zus_sdn_oo_report_selscreen.
* CLASS lcl_myclass DEFINITION
CLASS lcl_myclass DEFINITION.
PUBLIC SECTION.
CLASS-DATA:
md_okcode TYPE ui_func.
CLASS-METHODS:
handle_pushbutton_click.
ENDCLASS. "lcl_myclass DEFINITION
* CLASS lcl_myclass IMPLEMENTATION
CLASS lcl_myclass IMPLEMENTATION.
METHOD handle_pushbutton_click.
DATA: ld_msg TYPE bapi_msg.
BREAK-POINT.
CLEAR: lcl_myclass=>md_okcode.
DO.
CALL SELECTION-SCREEN 1200 STARTING AT 10 10.
EXIT.
ENDDO.
CONCATENATE 'ok-code =' md_okcode INTO ld_msg
SEPARATED BY space.
MESSAGE ld_msg TYPE 'I'.
MESSAGE 'Continue after SelScreen' TYPE 'S'.
ENDMETHOD. "handle_pushbutton_click
ENDCLASS. "lcl_myclass IMPLEMENTATION
SELECTION-SCREEN BEGIN OF SCREEN 1200.
PARAMETERS:
p_bukrs TYPE bukrs.
SELECTION-SCREEN END OF SCREEN 1200.
AT SELECTION-SCREEN OUTPUT.
BREAK-POINT.
CLEAR: syst-ucomm.
AT SELECTION-SCREEN.
BREAK-POINT.
lcl_myclass=>md_okcode = syst-ucomm.
START-OF-SELECTION.
lcl_myclass=>handle_pushbutton_click( ).
END-OF-SELECTION.
Regards
Uwe -
Hiding Screen fields in a Report selection screen
Hi Experts,
I have a requirement to hide/disable screen fields in a report selection screen when the user clicks on some radio buttons .
Here is the scenario,
1) There are 4 radio buttons four radiobuttons in one group on the selection screen:--
Block no:1
PARAMETER: r_not TYPE c RADIOBUTTON GROUP a1 DEFAULT 'X'.
PARAMETER: r_prgs TYPE c RADIOBUTTON GROUP a1.
PARAMETER: r_remv TYPE c RADIOBUTTON GROUP a1.
PARAMETER: r_noresp TYPE c RADIOBUTTON GROUP a1.
2) Based on the user clicking/selecting the radio buttons no.2,3 nad 4 i need to hide some fields in the other selection block
in the selection screen.The parameters are as follows:
Block no:2( These fields need to be hidden/disabled)
PARAMETER: r_occ(3) TYPE c OBLIGATORY DEFAULT '1'.
PARAMETER: r_and TYPE c RADIOBUTTON GROUP g1.
PARAMETER: r_or TYPE c RADIOBUTTON GROUP g1.
PARAMETER: r_days(3) TYPE c OBLIGATORY DEFAULT '1'.
ThanksContd.....
AT SELECTION-SCREEN.
CASE SSCRFIELDS-UCOMM.
"When Customer button is clicked set flag 1
WHEN 'FC01'.
L_FLAG = '1'.
"When Sales Order button is clicked set flag 2
WHEN 'FC02'. "Sales order
L_FLAG = '2'.
"When Execute button is clicked set flag 4
WHEN OTHERS.
L_FLAG = '4'.
ENDCASE.
AT SELECTION-SCREEN OUTPUT.
CASE L_FLAG.
WHEN '1'. "When Customer button is clicked
LOOP AT SCREEN.
"Set the Production and Customer Block as inactive
IF SCREEN-GROUP1 = 'BL1' OR SCREEN-GROUP1 = 'BL3'.
SCREEN-ACTIVE = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
WHEN '2'. "When Sales Order button is clicked
LOOP AT SCREEN.
"Set the Production and Customer Block as inactive
IF SCREEN-GROUP1 = 'BL1' OR SCREEN-GROUP1 = 'BL2'.
SCREEN-ACTIVE = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
WHEN '3'. "When Refresh button is clicked
LOOP AT SCREEN.
"Set the all Blocks as active
IF SCREEN-GROUP1 = 'BL2' OR SCREEN-GROUP1 = 'BL3' OR SCREEN-GROUP1 = 'BL1'.
SCREEN-ACTIVE = '1'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
WHEN OTHERS."When Execute button is clicked
"Set the Sales order and Customer Block as inactive
LOOP AT SCREEN.
IF SCREEN-GROUP1 = 'BL2' OR SCREEN-GROUP1 = 'BL3'.
SCREEN-ACTIVE = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
ENDCASE.
ENDFORM. -
How can we read the screen field values from the report selection screen wi
Hi expart,
How can we read the screen field values from the report selection screen with out having an ENTER button pressed .
Regards
Razzuse this code...
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_posnr.
**Read the Values of the SCREEN FIELDs
CALL FUNCTION 'DYNP_VALUES_READ' -
Add a button in report selection screen
Hi Experts,
I want to add a userdefined button in report selection screen....so far i have written code like this,...
TABLES : sscrfields.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-010.
PARAMETERS: P_ID LIKE ZBAPITABLE-ID,
P_NM LIKE ZBAPITABLE-NAME.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-020.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (11) TEXT-001 FOR FIELD R1.
PARAMETERS: R1 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (10) TEXT-002 FOR FIELD R1.
PARAMETERS: R2 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (10) TEXT-003 FOR FIELD R1.
PARAMETERS: R3 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (10) TEXT-004 FOR FIELD R1.
PARAMETERS: R4 RADIOBUTTON GROUP G1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN: FUNCTION KEY 1.
MOVE 'SAVE' TO sscrfields-functxt_01.
If i use code like this button was added in application tool bar
but in my selection screen i have two blocks ....in first block i have input fields, and in second there is set of radio buttons...Just below that i want to put one button ....how it is possible...
can anyone plz help me?
Regards,
veena.Here's th docu link:
[Pushbuttons on the Selection Screen|http://help.sap.com/saphelp_nw70/helpdata/en/9f/dba81635c111d1829f0000e829fbfe/frameset.htm]
Regards,
Clemens -
Object text not coming in report selection screen
Hi,
i have an object task type for which text has been loaded.this is included in one reports selection screen.But in F4 only kee is displayed and not text.If check button is pressed text is displayed besides key.Also text doesnt come after report is executed.
please help.
Thanks,
Prasanna N.Hi Prasanna,
In the Query Designer goto the properties of the required object that you want to display key and text for it, Select the Key and Text Display option. Then you can see in report key and text for that object.
Hope this helps.
Veerendra. -
Problen in report selection screen
Hi ,
I had a problem in the report.In the report selection screen user asking to keep page no option.So when they select the page no in the selection screen,so from that page number report out put should display.
how to do this.
Thanks,If you generating the LIST using the classical approch you cah use the SCROLL LIST keyword for this purpose.
Like:
DATA: L_PAGENO TYPE I.
L_PAGENO = 3.
START-OF-SELECTION.
DO 100 TIMES.
WRITE: / SY-ABCDE.
ENDDO.
SCROLL LIST INDEX 0 TO: PAGE L_PAGENO.
TOP-OF-PAGE.
WRITE: 'Top-of-page'.
Regards,
Naimesh Patel -
ECCS : custom characteristics into standard report selection screen
Hello guys,
I have added a custom characteristic which is also a subasignment to the EC-CS module.
This field now appears into the standard report selection screen as expected.
I want to define this field as a mandatory selection field, do you know if this is possible? (exemple of standard report CX34A)
Thank you in advance for your help
best regards
Pascal.Hi Thereza,
This field is already flaged
I have found the following solution : create a variant and assign it to the standard transcation with transaction SE93..
Best regards -
Call report selection screen in module pool program with tab strip control
Hi,
Could anyone explain in detail to call report selection screen in module pool program with tab strip control.
Thanks
ManoHi,
Refer std program:
demo_sel_screen_in_tabstrip.
demo_sel_screen_with_tabstrip.
Call your program with SUBMIT stmt form module program.
Reward points if this Helps.
Manish -
BEx web report selection screen entries retain when closing and opening the report again
Hello all,
please help me in the below query.
Till last month the entries we made in BEx web report selection screen are retained in the selection screen even when we close the web report and open it again from portal without logging off. But recently this functionality is missing and the entries in selection screen are not remembered when we close and open the same report again. It is a good feature for the users. Have you come across this issue?No...I think i can reframe the question very clearly......For ex: we are opening a Bex Web report...so initally we would be prompted by the variable selection screen...in which we have to give the entries(Values) for those variables like Cal month, Sales org, Company code, etc.....Later on the report will get open based on the values we have given......
Now if we close the particular report without logging off then if i try to open the same report that selected values are missing.....earlier it used to remember the values we have given until we log off....But now that functionality is missing....It was very useful feature.....Can you please tel me what can be done to resolve this??
I hope the explanation would be clear now.
Maybe you are looking for
-
Need info on Cloning Server Services in BOXi3.1
Hi All, I am looking for information on Cloning Server Services in BOXi3.1. The specific points that i am looking for are mentioned below: 1. How cloning is of advantage, specially in areas where we are facing network traffic? 2. Can we monitor WEBI
-
In which table does fnd_file.put_line writes the messages
Hi All, I have a requirement where i have to write the log messages and for this i am using FND_FILE.PUT_LINE. can some one help me in getting the tabel name where this package writes the messages so that i can get the messages from there. Thanks in
-
Smart Objects Problem : Templates : CS3 : WIN
Hello, I am trying to create some reusable templates in Photoshop CS3 using Smart Objects. Basically I want to layout the page with some place-holder photos that are smart objects and then when I need to create a page simply load the template PSD, ri
-
How do I remove image camera metadata? Any help would be appreciated. [email protected]
-
Huge MemoryAllocation - ColorMatrix on 3 - 4 MB images
Hi all i am currently working on the medical project (built with Flex SDK3.3. and Flash Player 10.0), the project provides the drawing and image manuipulation feature on the (*.JPEG) photos, those JPEG photos are extracted from a medical DICOM format