What r the list of selection screen events

hi,
chk out the following links...
http://help.sap.com/saphelp_nw04/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9a2e35c111d1829f0000e829fbfe/content.htm
http://www.sap-img.com/abap/different-types-of-selection-screens.htm
Regards,
Viji

Similar Messages

What is the use of selection -screen on field

Hi,
Can anyone tell me the use of at selection-screen on field and its syntax?
Regards,
Hema

Hi Hema,
AT SELECTION-SCREEN selscreen_event.
Effect
This statement defines event blocks for different events selscreen_event that are triggered by the ABAP runtime environment during selection screen processing.
Selection screen events occur immediately before sending a selection screen and after certain user actions on a displayed selection screen. They assist in selection screen processing in the ABAP program.
AT SELECTION-SCREEN is triggered at least twice during actions on selection screens that are linked into another selection screen as a subscreen - first for the linked selection screen itself, and then for the linking selection screens.
Note
The event blocks after AT SELECTION-SCREEN are implemented internally as procedures. Declarative statments in these event blocks create local data.
Differenct Options:
| { ON {para|selcrit} }
| { ON END OF selcrit }
| { ON BLOCK block }
| { ON RADIOBUTTON GROUP radi }
| { }
| { ON {HELP-REQUEST|VALUE-REQUEST}
| FOR {para|selcrit-low|selcrit-high} }
| { ON EXIT-COMMAND }.
Example
REPORT demo_at_selection_screen.
Global data
DATA: sflight_tab TYPE TABLE OF sflight,
 sflight_wa LIKE LINE OF sflight_tab.
Selection screens
PARAMETERS p_carrid TYPE spfli-carrid.
SELECTION-SCREEN BEGIN OF SCREEN 500.
SELECT-OPTIONS s_conn FOR sflight_wa-connid.
DATA s_conn_wa LIKE LINE OF s_conn.
SELECTION-SCREEN END OF SCREEN 500.
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.
AT SELECTION-SCREEN.
IF sy-dynnr = '0500'.
 IF s_conn IS INITIAL.
 MESSAGE 'Please enter values' TYPE 'W'.
 ELSE.
 SELECT *
 FROM sflight
 INTO TABLE sflight_tab
 WHERE carrid = p_carrid AND
 connid IN s_conn.
 IF sy-subrc <> 0.
 MESSAGE 'No flights found' TYPE 'E'.
 ENDIF.
 ENDIF.
ENDIF.
Main program
START-OF-SELECTION.

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

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?
Amol

Hi,
    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

KDMAT need to be included in the current VA01 selection screen or list when

Hello SAP SD Consultants,
Please help me with below requirement or what user exit should we use to implement below requirement. I have discussed with with ABAP and gave some User exits that has related description, however, ABAP confirmed that none of below UE suits the requirement.
1. AD010002 - Delimit selection and/or filter data that is determined
2. CLCLRS01 - Additional Fields on the Result Screen
3. CLCLRS02 - Fill the Additional Fields on the Result Screen
4. V60P0001 - Data provision for additional fields for display in lists
5. WVLB0001 - Display additional data in subscreen for simulation list
Thus, kindly help us on how we can proceed with this.
000----
Requirement:
The field u201CCustomer-material numberu201D or field name KDMAT need to be included in the current VA01 selection screen or list when creating sales orders with reference from a contract.
Currently, customer have its own description or material code to classify or define the product they want to order which are sometimes not exactly the same as the material number maintained in the system or the product / material code used by the Company for sales. These material descriptions were manually entered in the system thru the use of customer-material number field or KDMAT. When sales orders or contracts are created for certain or specific customers, the user or the person who creates that contract / order manually inputs the description in the customer-material number field.
The said entry should also be seen in the Selection List for Reference Document. The transaction to be modified is VA01 under program screen SAPMV45A specific to screen number 4413.
Test Data used:
Reference Transaction: VA41 (create contract), VA43 (display contract)
Order Type: ZCQ (example)
Contract No. 40000040
Transaction: VA01
Order type: ZOR (example)
Contract No. 40000040
a. Go to tcode VA01, input the order type ZOR, click the button CREATE with REFERENCE.
b. Input the reference contract document, since our reference doc is a contract, go to tab CONTRACT and input the contract no..
Expected output:
Upon inputing the contract no. in the contract tab, click u201CSelection Listu201D.
The customer-material number or KDMAT should be included as one of the field and should be displayed in the Selection List for Reference Document window.
Edited by: ria sumagaysay on Mar 26, 2010 11:30 AM

Hello,
Thank you for the responce.
The reason why they want to reflect KDMAT in the selection list is that, during order creation, not all materials or KDMAT will be ordered by that customer, only specific materials. However, during order processing, the customer only gives the details of the KDMAT. Thus, if there are around hundreds of items inside that contract, the sales personnel who creates the order needs to exclude those material not included in the customer order list manually via checking table VBAP and compare the material code from the selection list.
This is very tedious on their part and commonly caused human error, however, when the KDMAT field is available, although the process has manual intervention, it will serve them well and lessen the burden.

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,
Ven

Hi,
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

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
SelectEndselect. 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

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,
Heber

i 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.

HOW TO PASS THE DATA FROM SELECTION SCREEN TO STANDARD TRANSACTION?

HI,
HOW TO PASS THE DATA FROM SELECTION SCREEN TO STANDARD TRANSACTION?
thanks,
samba.

By selection screen, what do you mean? There is no selection screen in WDA as there was in classic dynpro. Do you mean you are using the Select-Options reusable component? Are you wanting to call a standard transaction via ITS - SAPGUI for HTML? Please provide more details to your question.

I am dual booting my mackbook pro with windows 7 64 bit. Yesterday it started locking up at the disk drive selections screen, when you hold down the "option" butting when powering on. I have been searching all morning, and so far nothing. Thanks. :)

Hey folks,
I have been using bootcamp for months now with windows 7 64 bit, and its been fine, yesterday while I was rebooting to do some gaming, at the hard drive selection screen when you boot holding the "options" butting down, it locks up when I select the windows drive and just sits there for ever. It doesn't throw an error, it boots fine into Lion.
I searched all morning and didn't find anything, was hoping that someone might have an idea.
Thanks in advance

Search again. Microsoft has tips on what to do and Windows has a number of features
system restore points
automatic system repair using the Win7 DVD
system restore image creation
Just like you would with OS X Lion and Lion Recovery and Repair
Use WinClone 3 www.twocanoes.com $20 to make an image just like you would with Disk Utility Restore or Carbon Copy Cloner
rollback to last known good boot check point
rollback a driver or program or any changes
clean out temp files
clean registry
chkdsk
https://discussions.apple.com/people/The%20hatter?view=bookmarks

Can I export the list output to screen.

HI,
My concept is I want to export the output of the list into a screen.
Can anybody help
regards
Mave

Hi Mave,
If yours is an ALV list, you can create your own custom button in the application toolbar for Export and using ALV event handling, you can implement the functionality to be incorporated in the custom export button. In the implementation, you can create a screen with table control and then the same internal table data used to display the list can be used to transfer data into the table control.
Cheers
sharmistha

Is it possible to have two at selection-screen events in a program

Hi all,
 I have a selection screen wherein i am using i have 5 radiobuttons and 3 select-options and a parameter. I am trying to use two at selection-screen events
1) at selection-screen on radiobutton group rad1.
2) AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_STATUS.
the second event is not getting triggered.
I have to get certain values for the parameter p_status based on the radiobutton selected from an internal table(the field doesn't belong to any dictionary table i am filling an itab with some values based on the radiobutton selected) pls help. its urgent.
Regards
Tharanath

Hi
TYPES : BEGIN OF ST_OBJID_SH,
 OTYPE TYPE HRP1000-OTYPE,
 OBJID TYPE HRP1000-OBJID,
 END OF ST_OBJID_SH.
DATA : IT_OBJID_SH TYPE STANDARD TABLE OF ST_OBJID_SH.
DATA : WA_OBJID_SH TYPE ST_OBJID_SH.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_OBJID-LOW.
IF S_OBJID IS NOT INITIAL.
 SELECT OTYPE OBJID FROM HRP1000
 INTO TABLE IT_OBJID_SH
 WHERE OTYPE = 'D'.
IF SY-SUBRC EQ 0.
SEARCH HELP FOR QUALIFICATION.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 DDIC_STRUCTURE = ' '
 RETFIELD = 'OBJID'
 PVALKEY = ' '
 DYNPPROG = SY-REPID
 DYNPNR = SY-DYNNR
 DYNPROFIELD = 'S_OBJID'
 STEPL = 0
 WINDOW_TITLE =
 VALUE = ' '
 VALUE_ORG = 'S'
 MULTIPLE_CHOICE = ' '
 DISPLAY = ' '
 CALLBACK_PROGRAM = ' '
 CALLBACK_FORM = ' '
 MARK_TAB =
 IMPORTING
 USER_RESET =
 TABLES
 VALUE_TAB = IT_OBJID_SH
 FIELD_TAB =
 RETURN_TAB = RETURN_TAB
 DYNPFLD_MAPPING =
 EXCEPTIONS
 PARAMETER_ERROR = 1
 NO_VALUES_FOUND = 2
 OTHERS = 3
 IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
ENDIF.
Use in this way it will defently triggers
REward if usefull

Sequence of AT SELECTION-SCREEN events

Hi All,
I have a requirement where i need to have two fields selection screen, where the second field should have f4 help depending on the first field.
So, i have validated the first field through AT SELECTION-SCREEN ON <FIELD1>. and for the second field i am using AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD2>
The problem i am facing over here is when i give first field input and press F4 in the second field it is not validating the First field and instead it is showing FIELD1 as blank to over come this i need to press enter before i press F4 in the second field. Is there any other alternative to over come this problem.
Is there any sequenec for the AT SELECTION-SCREEN events to be used.
Thanks
Shashikanth

Hi Shashi,
Check the below code
and for your future ref
Table Control dynamic F4
DATA : BEGIN OF f4_tab OCCURS 0,
 carrid TYPE sflight-carrid,
 connid TYPE sflight-connid,
 END OF f4_tab.
 CLEAR lin.
" adjust this as per your requirement
DATA : dynpread TYPE TABLE OF dynpread WITH HEADER LINE.
REFRESH dynpread.
CLEAR dynpread.
dynpread-fieldname = 'ITAB-CARRID'.
* dynpread-stepl = lin.
APPEND dynpread.
CLEAR dynpread.
at selection-screen on value-request for YOUR_FIELD " Your Second Field here
CALL FUNCTION 'DYNP_VALUES_READ'
 " This FM gives the First field value before u press Enter/ PAI is triggered
 EXPORTING
 dyname = sy-repid
 dynumb = sy-dynnr
 TABLES
 dynpfields = dynpread
 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 IS INITIAL.
 READ TABLE dynpread WITH KEY fieldname = 'ITAB-CARRID'.
 IF sy-subrc IS INITIAL.
 SELECT carrid connid FROM sflight
 INTO TABLE f4_tab
 WHERE carrid = dynpread-fieldvalue.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 retfield = 'CONNID'
 dynpprog = sy-repid
 dynpnr = sy-dynnr
 dynprofield = 'ITAB-CONNID'
 value_org = 'S'
 TABLES
 value_tab = f4_tab
 ENDIF.
ENDIF.
Cheerz
Ram
Edited by: Rob Burbank on Mar 18, 2010 9:01 AM

What is the price of new screen for mac air 11'', coz mine is broken

what is the price of new screen for mac air 11'' in singapore, coz mine is broken, the lcd crashd, whatever

You may have to check local official authorized Apple service providers for a price or estimate on the cost of repair parts and labor; there may be other companies than those officially listed in the locator page here http://www.apple.com/sg/service/ in the Singapore area, that can do the job. Be wary of those not Authorized or Certified, since these may not use the correct parts or may not be properly trained in the repair procedure.
In the case of a computer still under offiical original or extended Apple warranty, when accidental damages cause need for a repair, be sure to get the damage fixed in an authorized repair facility so as to keep the remainder of the offiical warranty in effect. Unofficial repairs by unqualified persons can void the remainder of a factory warranty; while the damage may not be covered at all, the rest of the computer could retain coverage if it is repaired correctly using Apple trained and authorized service personnel and original equipment parts.
So, be sure if you find a shop that can do a repair, that it won't make matters worse by performing inexact or sub-par service; and if the computer no longer has an official warranty on the remainder of the unit (outside of the accidental damages not covered anyway) you may be able to find a good display, new or used, and have another service company replace the one in your MB/Air. Depending on what build year-model MB/Air 11" you have, the parts may vary; so be sure to research whoever can do this job, so it may be done correctly.
There are independent authorized Apple repair agents with certified technicians who use correct parts, so maybe you can find one in your region; at least to initially research the costs involved in restoring the MB/Air.
Not sure which model you have, but for something out of warranty or damaged in a way to no longer be covered, you may see what may be involved in doing a repair or parts swap, yourself; the following may be helpful in restoring this model.Or give you an idea, should it be too technical for a DIY fix.
MacBook Air Repair - iFixit:
http://www.ifixit.com/Device/MacBook_Air
However that works out...
Good luck & happy computing!

What r the list of selection screen events

Similar Messages

Maybe you are looking for