AT SELECTION-SCREEN defined in inlcude

Hi all,
I use the inlcude BDCRECX1 within my program.
In the include, the "AT SELECTION-SCREEN" event is defined.
Within my main program, I defined a pushbutton
SELECTION-SCREEN BEGIN OF BLOCK B99.
SELECTION-SCREEN PUSHBUTTON /1(30) DOKU
USER-COMMAND SHOW_DOCU
MODIF ID DOK.
SELECTION-SCREEN END OF BLOCK B99.
My problem is, that the SSCRFIELDS-UCOMM field is only filled with the value "SHOW_DOCU" when processing the include.
After that, i.e. in the main program, the field is empty and I cannot query that value and check if the user pressed that button.
Also, I cannot define the "AT SELECTION-SCREEN" event in my main program as it is already defined in the include.
Is there any solution without changing the include?
TIA
Markus

Hi
U can manage it in AT SELECTION-SCREEN only.
Try to manage it in a new event AT SELECTION-SCREEN ON BLOCK B99 defined in your program
Max

Similar Messages

Issue with CALL SELECTION-SCREEN

Hi experts,
I am working on a report.
Here on the selection screen , based on the selection of some radiobuttons ,i want to call a secondary selection screen.
So i am using the following program code ,
AT SELECTION-SCREEN on BLOCk blk.
IF p_abc = c_x.
 CALL SELECTION-SCREEN 100 STARTING AT 20 5.
 IF sy-subrc <> 0.
 MESSAGE text-011 TYPE c_e .
 ENDIF.
ENDIF.
so currently , once i complete my slection on the screen 100 , the popup screen stays there and rest of the programing logic is executed correctly.
My issue is that , once i complete my slection on the screen 100, i want that the pop up should be closed
And then the the rest of the program logic should continue.
please guide me how ,this can be done.
Regards,
Rajesh Kumar.

Hi
The event AT SELECTION-SCREEN and AT SELECTION-SCREEN ON BLOCK are very similar, only the second event see the part of selection-screen defined in the block.
This events are triggered as soon as the user does something: so press ENTER, F8,........
If u want the second-selction screen is shown once and the main selection-screen has to be displayed under the second one, u can try to run the second one only if the report has to run, so if the user has pressed F8, code ONLI.
AT SELECTION-SCREEN on BLOCk blk.
CHECK SY-UCOMM = 'ONLI'.
IF p_abc = c_x.
CALL SELECTION-SCREEN 100 STARTING AT 20 5.
IF sy-subrc 0.
 MESSAGE text-011 TYPE c_e .
ENDIF.
ENDIF.
In tihs way the rest of the program will be executed, else u need to move all code of the event START-OF-SELECTION and END-OF-SELECTION in the event AT SELECTION-SCREEN, or, just as I said before, to move the calling of POPUP to event START-OF-SELECTION.
Max

Selection-screen validations

Hi Experts ,
I have module pool program there in first screen user have choice to select screen if user select the first screen .The selection will be displayed with two parameters using key word
selection-screen begin of screen 2002.
parameters : p_date type sy-datum,
                     p_num type kunnr.
selection-screen end of screen 2002.
call screen '2003'.
now i want to do validations on these parameters ,
please let me know how can i validate these selection-screen fields there i try chain and endchain in screen 2003 , it says no fields in screen 2003. screen 2002 was developed dynamically by systemplease let me know how to do validations i search it i cant find it plz solve issue .

hi
i think there are two methods two create selection screen
1. using layout here we can create selection screen with screen painter
here we can validate using chain end endchain.
Plz try this on
Selection Screen
Defined within an ABAP program; called by the runtime environment or using the CALL SELECTION-SCREEN statement; processed in event blocks of the corresponding ABAP program.
in main screen we have 3 selections for screen 2002 ,2004, 2006.
if sy-ucomm = 2002.
2 . selection-screen begin of screen 2002.
parameters : .........
      selection-screen end of screen 2002.
call selection-screen '2002'.
once this was triggered after entering vales it return to the next step then
call screen 2003.
then it goes to PBO and PAI events.
endif.
if sy-ucomm = 2003.
selection-screen begin of screen 2003.
parameters : .........
      selection-screen end of screen 2003.
call selection-screen '2003'.
once this was triggered after entering vales it return to the next step then
call screen 2004.
then it goes to PBO and PAI events.
endif.
all these are done in initial screen PBO . and those are created dynamically now i want to do validations on selection-screen fields. we can;t use at selection-screen in module end end module .
plz let me know if you know any thing more.

Selection screen problem in module pool

Hi friends,
I am working on module pool programming, I need to put select screen on the screen of the module pool porgramming. I used Input/Output field to do that and activated. But I am getting message invalid field format (screen error) can any one tell me why I am not able to run the seletion screen when I am using input/output field, also please let me know how to solve this problem.
Regards,
Line

Hello,
Think that this is useful for u/
SELECTION-SCREEN - Defining selection screens
Variants:
1a. SELECTION-SCREEN BEGIN OF SCREEN scr.
1b. SELECTION-SCREEN END OF SCREEN scr.
2. SELECTION-SCREEN BEGIN OF SCREEN scr AS SUBSCREEN.
Effect
Defines a selection screen with the number scr. scr may be up to 4 digits.
SELECTION-SCREEN BEGIN OF SCREEN scr.
Additions:
(zu SELECTION-SCREEN BEGIN OF SCREEN scr) 1. ... TITLE title
2. ... AS WINDOW
Notes
In reports (type 1 programs), a selection screen with number 1000 is created automatically when you use the SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statments. This selection screen appears when you SUBMIT the report.
In any type of program (apart from subroutine pools - type S), you can define further selection screens using SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN. You enclose these statements between the SELECTION-SCREEN BEGIN OF SCREEN and SELECTION-SCREEN END OF SCREEN statements.
You call these screens using the CALL SELECTION-SCREEN statement.
Screen number 1000 is not allowed (reserved for standard selection screen).
When you generate the program, all user-defined selection screens are also generated.
Within a report (type 1 program), all SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statements outside a SELECTION-SCREEN BEGIN/END OF SCREEN block form part of selection screen 100 (standard selection screen)
Regards,
LIJO JOHN.

Common SELECTION-SCREEN in reports for reuse

Dear ABAPERS,
I have a number of ABAP reports with similar but complicated customized selection screen (i.e. implemented using SELECTION-SCREEN statement). I would like to "package" the codes for SELECTION-SCREEN in a common routine in an include program, so that all my reports can just use it (instead of all reports duplicating the same selection screen codes). Any changes to the selection screen can be made through the single source.
However, an error :
Within FORM routines and function modules, the SELECTION-SCREEN statement is not allowed.
Is there any other way to accomplish this goal ? Thank you.
Regards
KC

Hello Kir,
The only way to be able to re-use a screen, selection-screen or otherwise, is when the screen is a subscreen.
Have one report program where you have got the selection screen defined as follows -
report ztest.
selection-screen begin of screen 1010 as subscreen.
parameters : test like t001-mandt.
selection-screen end of screen 1010.
Have a second program with normal screen, which has a subscreen area.
report ztest1.
data : repid type syrepid,
dynnr type sydynnr.
repid = 'ZTEST'.
dynnr = '1010'.
call screen 100.
Screen 100 has a subscreen area and its flow logic will be something like this -
PROCESS BEFORE OUTPUT.
call subscreen subscreen_area_name including repid
dynnr.
PROCESS AFTER INPUT.
call subscreen sub1.
Now, each time you make a change to the selection-screen's definition in program ZTEST, the change will always be reflected in all the other programs which are using it as their subscreen.
Regards,
Anand Mandalika.

Selection screen for custom table

We have developed a custom table and user want to have a selection selection screen similar to SE16. There are 9 fields in the table and user can enter data to the selection screen with any combination. My question is how do I filter based on the user input ? DO I need to write multiple SQL for different combination of selection screen parameter within IF ELSEIF statement ? If so then there will be huge number of SQL within IF & ELSEIF statment for 9 selection parameter. Please suggest if you have any better ideas.

Even after using select-option along with IN statement in where clause , it did not work.
I used following selection screen defination :
SELECTION-SCREEN: BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002.
SELECT-OPTIONS: P_PCBUS FOR MARA-ZZPC_BUSINESS NO-EXTENSION NO INTERVALS,
                P_PCBUS1 FOR MARA-ZZPC_BUS_SUB1 NO-EXTENSION NO INTERVALS,
                P_PLNFMT FOR MARA-ZZPLNG_FORMAT NO-EXTENSION NO INTERVALS,
                P_PRDB FOR MARA-ZZPROD_BRAND NO-EXTENSION NO INTERVALS,
                P_SEASCD FOR MARA-ZZSEASON_CODE NO-EXTENSION NO INTERVALS,
                P_SNP FOR MARA-ZZSUP_NET_PATH NO-EXTENSION NO INTERVALS,
                P_MAT_DC FOR MARA-MATNR NO-EXTENSION NO INTERVALS,
                P_MAT_MG FOR MARA-MATNR NO-EXTENSION NO INTERVALS.
SELECTION-SCREEN: END OF BLOCK B2.
and SQL statement :
SELECT ZZPC_BUSINESS
      FROM ZTB_RTL_TO_WHS
      INTO TABLE TA_ZZPCBUS
      WHERE ZZPC_BUSINESS = P_PCBUS
      AND ZZPC_BUS_SUB1 IN P_PCBUS1
      AND   ZZPROD_BRAND   IN P_PRDB
      AND ZZPLNG_FORMAT   IN P_PLNFMT
      AND ZZSEASON_CODE   IN P_SEASCD
      AND ZZSUP_NET_PATH IN P_SNP
      AND ZZD_MATNR       IN P_MAT_DC
      AND ZZM_MATNR       IN P_MAT_MG.
While executing program, I only enterd value for the field P_PCBUS. Though record present for that value, I rcvd SY-SUBRC = 4.
ANy Idea?
Edited by: J. Bakshi on Jul 14, 2009 10:17 AM

Difference between screen and selection screen

explain the difference between
call screen
and
call selection-screen
with easy understandable explanation with simple example
thanks guyz

Hi,
CALL SCREEN interrupts the processing of the current screen to call a new screen or a chain of screens, processing of the current screen is resumed directly after the call.
Call selection-screen
Similar to CALL SCREEN, except the screen you are calling must be a selection screen defined using SELECTION-SCREEN BEGIN/END OF SCREEN or the standard selection screen of a report.
It calls the selection screen with in the program.
If you call a selection screen using CALL SCREEN instead of CALL SELECTION-SCREEN, the initialization necessary for selection screens is not carried out, and the screen will not run properly when displayed.
EG:
SELECTION-SCREEN BEGIN OF SCREEN 123 AS WINDOW TITLE TEXT-456.
SELECTION-SCREEN BEGIN OF BLOCK BL1 WITH FRAME TITLE TEXT-BL1
 NO INTERVALS.
 SELECT-OPTIONS SEL1 FOR SY-SUBRC.
 PARAMETERS PAR1 LIKE SPFLI-CARRID.
 SELECTION-SCREEN COMMENT /10(20) TEXT-COM.
SELECTION-SCREEN END OF BLOCK BL1.
SELECTION-SCREEN END OF SCREEN 123.
CALL SELECTION-SCREEN 123 STARTING AT 20 5.
IF SY-SUBRC = 0.
ELSE.
ENDIF.
rewards if useful,
regards,
nazeer

PBO Event at Sub screen as Selection-Screen

Hello
I would like to do the following: in a function group I have a main screen which includes a sub screen
1300 as selection screen defined with the following command:
SELECTION-SCREEN BEGIN OF SCREEN 1300 AS SUBSCREEN.
SELECTION-SCREEN END OF SCREEN 1300.
Now, I would like to process within the PBO of this sub screen 1300 to manipulate some fields (such as deactivate or set a default value using
LOOP AT SCREEN ENDLOOP.). I need an event like INITIALIZATION in a report, but here Im not in a report context.
Is it possible to take the PBO event to process the PBO by own functions?
Thanks for your help.
Best regards,
Kurt.
Message was edited by:
        Kurt Weiskopf

Hello Sasi,
Thanks for your information.
On the selection screen some fields shall be displayed only if they are needed. These fields shall be deactivated using:
Loop at screen.
case XXX.
      when T1.
               screen-invisible = 1.
               screen-active    = 0.
endcase.
modify screen.
endloop.
I need the PBO event. Where can I set this code?
Thanks & Regards,
Kurt.

Dynamic selection screens

Hai Friends,
I have a requirement that, in a program two selection screen defined both are having different selection parameters. Based on the dynamic input from the Main Object program, the required selection screen only to be executed for getting input parameters. But actually what happens is, both the selection screens are displayed on the single container itself. How to invoke the required selection screen only.

Hi,
Use Subscreens. With Subscreens, you will have the possibility to decide which subscreen should be called in the main screen.
Check the online help for subscreens.
regards,
Advait

Call Selection Screen

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

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

At Selection-screen Events!

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

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

Addition 6
... ON BLOCK block
Effect
This event is assigned to the blocks on the selection screen defined by SELECTION-SCREEN BEGIN/END OF BLOCK block .
If the report starts an error dialog at this point, precisely these fields of the block block become ready for input again.
Note
In which sequence are the events AT SELECTION-SCREEN ON psel ... , AT SELECTION-SCREEN ON RADIOBUTTON GROUP ... , AT SELECTION-SCREEN ON BLOCK ... , AT SELECTION-SCREEN processed?
The AT SELECTION-SCREEN ON psel ... events assigned to the parameters or selection options are executed in the sequence they are declared in the program, i.e. in the sequence they appear on the selection screen.
The events assigned to the radio button groups are executed according to the first parameter of the radio button group.
The events assigned to the blocks are executed "from the inside to the outside".
Example
SELECT-OPTIONS SEL0 FOR SY-TVAR0.
SELECTION-SCREEN BEGIN OF BLOCK BL0.
SELECT-OPTIONS SEL1 FOR SY-TVAR1.
SELECTION-SCREEN BEGIN OF BLOCK BL1.
PARAMETERS P0 RADIOBUTTON GROUP RADI.
PARAMETERS P1 RADIOBUTTON GROUP RADI.
SELECTION-SCREEN BEGIN OF BLOCK BL2.
PARAMETERS P3.
SELECTION-SCREEN END OF BLOCK BL2.
SELECT-OPTIONS SEL2 FOR SY-TVAR2.
SELECTION-SCREEN END OF BLOCK BL1.
SELECTION-SCREEN END OF BLOCK BL0.
Sequence:
AT SELECTION-SCREEN ON...
SEL0
SEL1
RADIOBUTTON GROUP RADI
P3
BLOCK BL2
SEL2
BLOCK BL1
BLOCK BL0
AT SELECTION-SCREEN is executed at the very end.
Addition 7
... OUTPUT
Effect
This event is executed at PBO of the selection screen every time the user presses ENTER - in contrast to INITIALIZATION . Therefore, this event is not suitable for setting selection screen default values. Also, since AT SELECTION-SCREEN OUTPUT is first executed after the variant is imported (if a variant is used) and after adopting any values specified under SUBMIT in the WITH clause, changing the report parameters or the selection options in AT SELECTION-SCREEN OUTPUT would destroy the specified values.
Here, however, you can use LOOP AT SCREEN or MODIFY SCREEN to change the input/output attributes of selection screen fields.
Example
Output all fields of the
SELECT-OPTION NAME
highlighted:
SELECT-OPTIONS NAME FOR SY-REPID MODIF ID XYZ.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
 CHECK SCREEN-GROUP1 = 'XYZ'.
 SCREEN-INTENSIFIED = '1'.
 MODIFY SCREEN.
ENDLOOP.
The addition MODIF ID XYZ to the key word SELECT-OPTIONS assigns all fields of the selection option NAME to a group you can read in the field SCREEN-GROUP1 . At PBO of the selection screen, all these fields are then set to highlighted.

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

How to define our own selection screen for logical database in abap-hr?

Hi Friends,
Can u please help me
How to define your own selection screens for logical database.
we use to do like(goto->attributes-HRReportcatagerious ).but How to desin using customer table like t599c, t599f and how to add to my logical database?
Thanks in advance
charan

check out this online help
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/dba65c35c111d1829f0000e829fbfe/frameset.htm
Regards
Raja

Define selection screen for ldb_process

Hi I'm using the call function ldb_process for KDF(lfa1, lfb1, bsik), the trouble is that the information its different than if i do it on a normal report defining the logical database kdf and selection screen 903.
I find that the difference is because the selection screen, this is because the default selection screen for the kdf database is 1000, and this selection has the "Open items at key date" selection with the current date.
The question is:
How can i define the selection screen 903 using the call function ldb_proces?
Thanks
Pablo Santos

Hi,
You cannot define screen version 903 using function LDB_PROCESS. Instead use table "SELECTIONS" of the function module .
Cheers.

Problem with user defined selection-screens

Hi,
in my case, i have a default selection screen and a user defined selection screen. Now, after selecting a radio button in default selection screen, the user defined selection screen is called. after executing it report output is displayed. now if i press f3 (back) it is going to default selection screen. here my requirement is, when i press f3 it should go to the user defined selection.
Can u plz help me solve this.
bye n regards
sree

Any modifications to screen 1000 will be lost the next time the program is generated.
When the user hits the back key from the report output, your ABAP is restarted just like when you originally started it. That is why you are getting the default selection screen again.
Use the AT USER-COMMAND event. When BACK is hit from the report, use the SUBMIT command to re-execute the program, passing it the selections from the default selection screen. Leave out the RETURN option.
For help on filling the selection screen during SUBMIT, help is available at
http://help.sap.com/saphelp_470/helpdata/en/9f/dba51a35c111d1829f0000e829fbfe/frameset.htm

Problem with ALV and user defined selection screen. please help!

Hi Experts,
I have program which has a user defined selection screen 9001. On executing the selection screen i call a ALV using resuse_alv_grid function module.
What problem I am facing is that when I press back button from ALV page it goes to the se38 editor instead of selection screen.
How to resolve this?
Thanks
Gopal

Hi,
This might be due to LEAVE TO TRANSACTION statement. You might be running the program from SE38. Try to run the program using Z-TCode assigned to it.
Thanks and Regards,
Bharat Kumar Reddy.V
Message was edited by: Bharat Reddy V

AT SELECTION-SCREEN defined in inlcude

Similar Messages

Maybe you are looking for