Initializing Selection-Screen as dynpro subscreen

Hello!
I wrote a dynpro program that includes a selection screen as subscreen. In the flow logic the subscreen is called before output like this.
process before output.
call subscreen sub including sy-repid '110'.
module status_0100.
The program works fine to this point. Now I want to initialize a select-options table in the selection screen with some values. Doing this in the status_0100 module doesn't work. I suppose at this point it is too late to change values of the selection screen. I can't change the flow logic of the selection-screen 110 because it is generated automatically.
My questions are:
1. Is there any kind of initialization block or something like this where i can place the code to fill the select-options table?
2. Filling a select-options table by appending lines to it is the common way to do this, isn't it?
Thank you for your answers,
Georg

There is nothing stopping your from doing this?
process before output.
module status_0100. "<-- Put this here
call subscreen sub including sy-repid '110'.
And then fill your select-option in the STATUS_0100 module, make sure that you apend to the internal table!
Regards,
Rich HEilman

Similar Messages

Calling a selection screen in a subscreen of a tabstrip

hi,
I have created a tabstrip where i have included a subscreen.
I want to create and call a selection screen within that subscreen.
Can anybody tell me the steps required?
thanks in advance,
Abhishek

hi
good
try this
In the same way that you can define a screen as a subscreen in the Screen Painter, it is now possible to define selection screens as subscreens in an ABAP program:
SELECTION-SCREEN BEGIN OF SCREEN scrn AS SUBSCREEN
[NO INTERVALS]
[NESTING LEVEL n].
SELECTION-SCREEN END OF SCREEN scrn.
go through this link
http://help.sap.com/saphelp_nw2004s/helpdata/en/e7/deb237b9a9a968e10000009b38f8cf/content.htm
http://sap.niraj.tripod.com/id40.html
thanks
mrutyun^

Order of the variables in the initial selection screen.

Hi all,
How can I change the order of the variables in the initial selection screen.
Thanks in advance.
Regards,
Kumar.

In the query designer goto query properties screen.. In the first screen you will see the order and you can move up and down the variables there as per your need ..
Regards.

Initial selection screen missing when execting a query via web

Hello all.
We have a problem when we try to execute a query in web. We developped queries via query designer and we published all in a role. By doing it system generates a link that makes possible to execte this query via web. The issue is that sometimes the initial selection screen doesn´t appear (and the variables are "ready to input".
Could anybody help me?
Thanks in advance.

Dear Carmen Rodríguez,
In the WAD properties of the webtemplate.. carefully look for 'Force Variable Screen' Check that option..
Save and rerun the same.. it should be able to see the screen after that..
regards,
Hari

Selection-Screen in Dynpro

Hi experts,
I'm trying to createa selection-screen in a dynpro, but i'm not capable.
I've followed the next steps:
1. I created a dynpro (100) Type: Normal
2. I created a subarea (Sub_area) inside the dynpro 100
3. I created the selection-screen in the top of my modulepool.
TABLES: pernr.
SELECTION-SCREEN BEGIN OF SCREEN 101 AS SUBSCREEN.
SELECT-OPTIONS r_pernr FOR pernr-pernr.
SELECTION-SCREEN end of screen 101.
4. I defined the PBO y the PAI of the screen 100.
PROCESS BEFORE OUTPUT.
MODULE status_0100.
CALL SUBSCREEN sub_area INCLUDING sy-cprog '0101'.
PROCESS AFTER INPUT.
CALL SUBSCREEN sub_area.
But the program returns the next error:
Dynpro 0100
Line 3 --> CALL SUBSCREEN sub_area INCLUDING sy-cprog '0101'.
"Include block not specified, not defined, or spelt incorrectly ."
What is the error????
Thanks anyway.

Hi Lydia,
your code seems to work in my system. This may be a typo with sub_area. Go to screen painter, copy the name and paste it in your statement.
Klaus Babl will try
Regards,
Clemens

Question on selection screen in a subscreen in dialog prorgamming

hi,
i have a module pool in which the main program has the definition of the selection screen as follows:
SELECTION-SCREEN BEGIN OF SCREEN 0101 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B1.
SELECT-OPTIONS: S_VSTEL FOR TVST-VSTEL,
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN END OF SCREEN 0101.
In the PBo of screen 100 this is called
CALL SUBSCREEN SUBSCREEN1 INCLUDING SY-REPID L_DYNNR.
The subscreen is displayed as
Shipping point _______ To _________ =>
When I click that arrow (( extension )) nothing happens !! I am supposed to get the standard extension screen in whcih i can select single values, ranges, exclude values, ranges !!
why is this not displayed..any idea ?
i have the same code in a normal report program and it works fine ..
thks

in module pool you need to add code for the => this is not been handled by SAP in module pool whereas it is been handled in report program.
There is one FM which needs to be used so that when => is clicked it works...

Call selection screen from DYNPRO

I created a report with std selection screen 1000...
From this selection screen we reach Dynrpro 9000 with a table control etc etc
Once a line has been selected and the user click on a specific button a selection screen is called...
SELECTION-SCREEN BEGIN OF SCREEN 9005.
SELECTION-SCREEN: FUNCTION KEY 1.
SELECT-OPTIONS : SO_PERSA FOR L_PERSA,
                 SO_BTRTL FOR L_BTRTL,
                 SO_PERSG FOR L_PERSG,
                 SO_PERSK FOR L_PERSK.
SELECTION-SCREEN END OF SCREEN 9005.
Unfortunatly when I try to fill in the range but pressing mutliple line button nothing happens...
Do you have any clue to solve this issue ?

what is the purpose of defining a func which is triggered for eac selection field ??
what is the function of it that you need it and don't want the user to use the available searchoptions ??
kind regards
arthur de smidt

Validation for a selection screen used as a subscreen

Hi friends,
I have a screen say '0001' in that screen i have three subscreens 0002 0003 0004
In the subscreen 0002, i have declared three selection screens 0102, 0202, 0302
In the Application toolbar of the screen 0001 (PF Status) i have declared three push buttons A, B, C,
On click of A i ll invoke 0102 selection screen inside the subscreen 0002.
Similarly On click of B i ll invoke 0202 selection screen inside the subscreen 0002
Similarly On click of C i ll invoke 0302 selection screen inside the subscreen 0002.
I have completed till the above ...
My problem is ........................
The selection screens will have their own Parameters and select options .....
some of them are mandatory & some of them not .......
Now when i switch from one push button to another say from A to B and then again to C .... for each and every click it is asking to fill in the mandatory paramters and select options ........ and then only allowing to move to the next sel screen .......
Needed solution:
~~~~~~~~~~~~~
1. How can i avoid this message "Fill in the required fields" ?
2. How can i validate the user entries if i take away all the "OBLIGATORY"
    additions in the selection screen declaration part
3. Where can i write "At selection screen" validation? becoz iam using a function
    group for the creation of screens and all and have included the selection
    screen declaration in the top include of the Function group?
Hope iam clear with my question!!
Revert back if you need more clarrifications on the question itself
Cheers
Kripa Rangachari .....

Hi,
   In the pf status - for push buttons give the type as E.
Write the processing for this in at exit command.
Validation should be done in AT SELECTION-SCREEN ON field.
Reward if helpful.

How can I add a new field in selection screen for this report

*& Report ZGS_BARKODLA_HIZLI_GIRIS
report zgs_barkodla_hizli_giris.
tables: mara,
        mseg,
        mch1,
        *mch1,
        mkpf,
        mchb ,
        makt.
type-pools: esp1.
data: i_message_tab type esp1_message_tab_type,
      wa_message_tab type esp1_message_wa_type ,
      sc_count type i.
ALV
type-pools: slis, kkblo.
data: gs_layout   type slis_layout_alv                     ,
      gt_fldcat   type slis_t_fieldcat_alv with header line,
      gt_header   type slis_t_listheader   with header line,
      gt_sortin   type slis_t_sortinfo_alv with header line,
      g_repid     like sy-repid                            .
define add-fieldcat.
gt_fldcat-fieldname     = &1.
gt_fldcat-ref_tabname   = &2.
gt_fldcat-seltext_s     = &3.
gt_fldcat-seltext_m     = &3.
gt_fldcat-seltext_l     = &3.
gt_fldcat-reptext_ddic = &3.
gt_fldcat-ddictxt       = 'M'.
append gt_fldcat.
clear gt_fldcat.
end-of-definition.
types: begin of titab,
        sel   type xfeld,
        matnr type matnr,
        maktx type maktx,
        charg type charg_d,
        menge type menge_d,
        erfmg type erfmg,
       end of titab.
data : witab type titab.
data : itab type table of titab.
data : ok_code type sy-ucomm.
controls: tc_itab type tableview using screen 0100.
data: gv_header like bapi2017_gm_head_01,
      gv_code   like bapi2017_gm_code.
BAPI export parameters
data: gv_headret type bapi2017_gm_head_ret,
      gv_matdoc type bapi2017_gm_head_ret-mat_doc,
      gv_matyear type bapi2017_gm_head_ret-doc_year.
data : lv_objek like inob-objek .
data : ls_inob like inob .
data : imseg type ty_t_mseg.
data : wmseg type mseg.
data : answer.
data : count type i.
data : v_atinn type atinn.
BAPI movement details
data: i_goodsmvt_items type bapi2017_gm_item_create occurs 0
      with header line.
data: i_return type bapiret2 occurs 0 with header line.
start-of-selection.
call function 'CONVERSION_EXIT_ATINN_INPUT'
   exporting
     input = 'Z_ORAN'
   importing
     output = v_atinn.
call screen 100.
*&      Module status_0100 OUTPUT
module status_0100 output.
set pf-status '100'.
set titlebar '100'.
mseg-werks = 1000.
mseg-umwrk = 1000.
**added
sc_count = sc_count + 1.
if sc_count eq 1.
    mseg-bwart = 313.
endif.
mkpf-budat = sy-datum.
**added
describe table itab lines tc_itab-lines.
endmodule.                 " status_0100 OUTPUT
*&      Module user_command_0100 INPUT
module user_command_0100 input.
data field(20).
data: line_t like sy-index.
data: lines like sy-index.
data line_count like sy-loopc.
data: begin of cols,
         screen      like screen,
         index       type i,
         selected(1) type c,
         vislength   like icon-oleng,
         invisible(1) type c,
       end   of cols.
case ok_code.
    when 'DELE'.
      delete itab where sel eq 'X'.
    when 'ENTE'.
      check *mch1-charg is not initial.
      read table itab into witab with key charg = *mch1-charg.
      if not sy-subrc is initial.
        witab-charg = *mch1-charg.
        select single matnr from mch1 into witab-matnr
                           where charg eq witab-charg.
        if not syst-subrc is initial.
          set cursor field '*MCH1-CHARG'.
          message e115(12) with *mch1-charg.
        endif.
        select single maktx from makt into witab-maktx
                           where matnr eq witab-matnr
                             and spras eq syst-langu.
        witab-erfmg = 1.
        concatenate witab-matnr witab-charg into lv_objek .
        clear ls_inob .
        select single * into ls_inob
                        from inob
                        where objek = lv_objek and
                              klart = '023'    and
                              obtab = 'MCH1' .
        select single atflv from ausp into witab-menge
                 where objek = ls_inob-cuobj and
                       klart = '023' .
        append witab to itab.
**added
        clear *mch1-charg.
**added
      endif.
    when 'SAVE'.
      if mkpf-budat is initial.
        set cursor field 'MKPF-BUDAT'.
        message e055(00).
      endif.
      if mseg-lgort is initial.
        set cursor field 'MSEG-LGORT'.
        message e055(00).
      endif.
      if mseg-umlgo is initial.
        set cursor field 'MSEG-UMLGO'.
        message e055(00).
      endif.
      if mseg-bwart is initial.
        set cursor field 'MSEG-BWART'.
        message e055(00).
      endif.
      refresh imseg.
      loop at itab into witab.
        move-corresponding witab to wmseg.
        append wmseg to imseg.
      endloop.
      call function 'ZMM_POPUP_WITH_DATA'
        exporting
          imseg = imseg
        importing
          answer = answer.
      if answer eq 'Y'.
        perform create_goods_movement.
      endif.
    when 'P--'.
      clear ok_code.
      perform paging using 'P--'.
      set cursor field 'MARA-MATNR' line 1.
    when 'P-'.
      clear ok_code.
      perform paging using 'P-'.
      set cursor field 'MARA-MATNR' line 1.
    when 'P+'.
      clear ok_code.
      clear lines.
      perform paging using 'P+'.
      set cursor field 'MARA-MATNR' line 1.
    when 'P++'.
      clear ok_code.
      perform paging using 'P++'.
      set cursor field 'MARA-MATNR' line 1.
    when 'SORA'.
      read table tc_itab-cols into cols with key selected = 'X'.
      if sy-subrc is initial.
        field = cols-screen.
        field = field+5(10).
        sort itab ascending by (field).
      endif.
    when 'SORZ'.
      read table tc_itab-cols into cols with key selected = 'X'.
      if sy-subrc is initial.
        field = cols-screen.
        field = field+5(10).
        sort itab descending by (field).
      endif.
    when 'PRNT'.
      perform write_alv.
endcase.
endmodule.                 " user_command_0100 INPUT
*&      Module read_table OUTPUT
module read_table output.
mara-matnr = witab-matnr.
makt-maktx = witab-maktx.
mch1-charg = witab-charg.
mseg-menge = witab-menge.
mseg-erfmg = witab-erfmg.
line_count = sy-loopc.
endmodule.                 " read_table OUTPUT
*&      Module write_table INPUT
module write_table input.
witab-matnr = mara-matnr.
witab-maktx = makt-maktx.
witab-charg = mch1-charg.
witab-menge = mseg-menge.
witab-erfmg = mseg-erfmg.
modify itab from witab index tc_itab-current_line.
endmodule.                 " write_table INPUT
*&      Module exit INPUT
module exit input.
leave to screen 0 .
endmodule.                 " exit INPUT
*&      Form create_goods_movement
form create_goods_movement .
clear : gv_header, i_return[], i_goodsmvt_items[].
gv_header-doc_date = gv_header-pstng_date = mkpf-budat.
gv_header-pr_uname = sy-uname.
GM with reference to reservation
loop at itab into witab.
    i_goodsmvt_items-material   = witab-matnr.
    i_goodsmvt_items-entry_qnt = witab-erfmg.
    i_goodsmvt_items-entry_uom = 'ST'.
    i_goodsmvt_items-move_type = mseg-bwart.
    i_goodsmvt_items-plant      = mseg-werks.
    i_goodsmvt_items-stge_loc   = mseg-lgort.
    i_goodsmvt_items-move_plant = mseg-umwrk.
    i_goodsmvt_items-move_stloc = mseg-umlgo.
    i_goodsmvt_items-batch      = witab-charg.
    append i_goodsmvt_items.
endloop.
find BAPI processing transaction
if gv_code is initial.
    perform determine_bapi_code using mseg-bwart
                             changing gv_code.
endif.
call function 'BAPI_GOODSMVT_CREATE'
    exporting
      goodsmvt_header = gv_header
      goodsmvt_code    = gv_code
    importing
      goodsmvt_headret = gv_headret
      materialdocument = gv_matdoc
      matdocumentyear = gv_matyear
    tables
      goodsmvt_item    = i_goodsmvt_items
      return           = i_return[].
cancel blocking process
loop at i_return where type eq 'E' or type eq 'A' or type eq 'X'.
    exit.
endloop.
if sy-subrc ne 0.
    refresh i_message_tab.
    call function 'BAPI_TRANSACTION_COMMIT'
      exporting
        wait = 'X'.
    wa_message_tab-msgid = 'M7'..
    wa_message_tab-msgty = 'S'.
    wa_message_tab-msgno = '060'.
    wa_message_tab-msgv1 = gv_matdoc.
    wa_message_tab-msgv2 = ''.
    wa_message_tab-msgv3 = ''.
    wa_message_tab-msgv4 = ''.
    append wa_message_tab to i_message_tab.
else.
    refresh i_message_tab.
    call function 'BAPI_TRANSACTION_ROLLBACK'.
write a message as there is an unexpected error.
    loop at i_return.
      wa_message_tab-msgid = i_return-id.
      wa_message_tab-msgty = i_return-type.
      wa_message_tab-msgno = i_return-number.
      wa_message_tab-msgv1 = i_return-message_v1.
      wa_message_tab-msgv2 = i_return-message_v2.
      wa_message_tab-msgv3 = i_return-message_v3.
      wa_message_tab-msgv4 = i_return-message_v4.
      append wa_message_tab to i_message_tab.
    endloop.
endif.
call function 'C14Z_MESSAGES_SHOW_AS_POPUP'
    tables
      i_message_tab = i_message_tab.
endform.                    " create_goods_movement
*&      Form determine_bapi_code
form determine_bapi_code using p_bwart type bwart
changing p_code type bapi2017_gm_code.
data: lt_t158b type table of t158b with header line.
clear p_code.
select tcode from t158b into corresponding fields of table lt_t158b
where bwart eq p_bwart.
loop at lt_t158b.
    select single gmcode from t158g into p_code
    where tcode eq lt_t158b-tcode.
    if sy-subrc is initial.
      exit.
    endif.
endloop.
endform. " determine_bapi_code
*&      Form paging
form paging using code.
data: i type i,
        j type i.
case code.
    when 'P--'. tc_itab-top_line = 1.
    when 'P-'.
      tc_itab-top_line = tc_itab-top_line - line_count.
      if tc_itab-top_line le 0.
        tc_itab-top_line = 1.
      endif.
    when 'P+'.
      i = tc_itab-top_line + line_count.
      j = tc_itab-lines - line_count + 1.
      if j le 0.
        j = 1.
      endif.
      if i le j.
        tc_itab-top_line = i.
      else.
        tc_itab-top_line = j.
      endif.
    when 'P++'.
      tc_itab-top_line = tc_itab-lines - line_count + 1.
      if tc_itab-top_line le 0.
        tc_itab-top_line = 1.
      endif.
endcase.
endform.                    " paging
*&      Form write_alv
form write_alv .
perform find_list_header.
perform fill_field_cat.
perform fill_sortinfo.
g_repid = sy-repid.
gs_layout-colwidth_optimize = 'X'.
gs_layout-zebra             = 'X'.
answer = 'Y'.
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
      i_buffer_active        = ''
      i_callback_program     = g_repid
      i_save                 = 'A'
    i_callback_top_of_page = 'TOP_OF_PAGE'
      is_layout              = gs_layout
      it_fieldcat            = gt_fldcat[]
     it_sort                = gt_sortin[]
    tables
      t_outtab               = itab[].
endform.                    " write_alv
     Form find_list_header
form find_list_header.
data : v_datum(10),
         v_datlo(10),
         v_dathi(10),
         v_uzeit(8).
clear: gt_header, gt_header[].
gt_header-typ = 'H'.
gt_header-info = sy-title.
append gt_header.
clear gt_header.
gt_header-typ = 'S'.
gt_header-key = 'Çalıştırma Zamanı : '.
write syst-datum to v_datum.
write syst-uzeit to v_uzeit.
concatenate v_datum '/' v_uzeit into gt_header-info.
append gt_header.
endform.                    " find_list_header
     Form fill_field_cat
form fill_field_cat.
refresh gt_fldcat.
clear   gt_fldcat.
gt_fldcat-key = 'X'.
add-fieldcat 'MATNR' 'MARA' ''.
add-fieldcat 'MAKTX' 'MAKT' ''.
add-fieldcat 'CHARG' 'MSEG' ''.
gt_fldcat-do_sum = 'X'.
add-fieldcat 'MEINS' 'MARA' 'Olcu Birimi '.
gt_fldcat-do_sum = 'X'.
add-fieldcat 'ERFMG' 'MSEG' 'Adet'.
endform.                    " fill_field_cat
     Form fill_sortinfo
form fill_sortinfo.
gt_sortin-up            = 'X'.
gt_sortin-fieldname     = 'MATNR'. append gt_sortin.
endform.                    " fill_sortinfo
     Form top_of_page                                              *
form top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
      i_logo             = 'ZKUTAS'
      it_list_commentary = gt_header[].
endform.                    " top_of_page

HI,
if it is a normal report program then you can directly create a Selection screen field.
After the Type-pool you can use Parameters or Select-options to create the selection screen field..
If it is a Modulpool program then you can create a selection scren field like
SELECTION-SCREEN BEGIN OF SCREEN 1100 AS SUBSCREEN.
PARAMETERS: p1(10) TYPE c.
SELECTION-SCREEN END OF SCREEN 1100.
defines a selection screens 1100 as subscreens.
The next screen number of screen 100 is 100 (statically-defined).
PROCESS BEFORE OUTPUT.
MODULE status_0100.
CALL SUBSCREEN area INCLUDING sy-repid number.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
CALL SUBSCREEN area.
MODULE user_command_0100.
look at the below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/e7/deb237b9a9a968e10000009b38f8cf/content.htm
Regards
Sudheer

At selection-screen output and at selection-screen on

Hi Experts,
I had coded in both at selection-screen output for disabling input of certain fields and at selection-screen for validation like this:
AT SELECTION-SCREEN output.
IF p_amt = 'X'.
    LOOP AT SCREEN.
      CASE screen-name.
        WHEN 'P_AMT'.
          screen-input = '1'.
        WHEN 'P_TST'.
          screen-input = '1'.
        WHEN 'P_B4C'.
          screen-input = '1'.
        WHEN 'P_AFC'.
          screen-input = '1'.
        WHEN 'P_COM'.
          screen-input = '1'.
        WHEN 'P_COM1'.
          screen-input = '1'.
        WHEN 'P_COM2'.
          screen-input = '1'.
        WHEN OTHERS.
          screen-input = '0'.
      ENDCASE.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
IF p_amt = 'X'.
    LOOP AT SCREEN.
      CASE screen-name.
        WHEN 'P_AMT'.
          screen-input = '1'.
        WHEN 'P_TST'.
          screen-input = '1'.
        WHEN 'P_B4C'.
          screen-input = '1'.
        WHEN 'P_AFC'.
          screen-input = '1'.
        WHEN 'P_COM'.
          screen-input = '1'.
        WHEN 'P_COM1'.
          screen-input = '1'.
        WHEN 'P_COM2'.
          screen-input = '1'.
        WHEN OTHERS.
          screen-input = '0'.
      ENDCASE.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
IF p_pdf = 'X'.
    LOOP AT SCREEN.
      CASE screen-name.
        WHEN 'P_PDF'.
          screen-input = '1'.
        WHEN 'P_TST'.
          screen-input = '1'.
        WHEN 'P_PATH'.
          screen-input = '1'.
        WHEN OTHERS.
          screen-input = '0'.
      ENDCASE.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
IF p_afc = 'X'.
    LOOP AT SCREEN.
      CASE screen-name.
        WHEN 'P_TST'.
          screen-input = '1'.
        WHEN 'S_FID-LOW' OR 'S_FID-HIGH'.
          screen-input = '0'.
        WHEN 'S_ORG-LOW' OR 'S_ORG-HIGH'.
          screen-input = '0'.
        WHEN 'S_OFF-LOW' OR 'S_OFF-HIGH'.
          screen-input = '0'.
        WHEN 'S_DAT-LOW' OR 'S_DAT-HIGH'.
          screen-input = '0'.
      ENDCASE.
      MODIFY SCREEN.
    ENDLOOP.
ENDIF.
AT selection-screen on block b5.
if p_tst is initial.
message text-016 type 'E'.
endif.
AT selection-screen on block b2.
if p_amt ne 'X' and p_pdf ne 'X'.
if s_fid is initial and s_org is initial.
message text-000 type 'E'.
endif.
if s_dat is initial.
message text-000 type 'E'.
endif.
endif.
when i comment out at selection-screen validations the input is disabled for the screen fields as set, else the validations are executed first.
Any solution for this???
Thanks in advance.

AT SELECTION-SCREEN
Syntax
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.

SAP Selection Screen

Hi All,
i was trying to call the Selection Screen on the basis of the Radio button present on the initial selection screen.
can you please to let me know where i can give call to second selection screen and where to declare that selection screen.
currently i am calling my second selection screen in EVENT 'AT SELECTION-SCREEN' .
but i am getting a dump 'Dynpro does not exist'.
thnaks in advance for your help
Regards,
Himanshu Sharma

Hi,
Refer to the following code:
PARAMETERS : p_rb1 RADIOBUTTON GROUP grp1 USER-COMMAND ucom DEFAULT 'X',
             p_rb2 RADIOBUTTON GROUP grp1.
SELECT-OPTIONS s_matnr FOR mara-matnr MODIF ID nit.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF screen-group1 = 'NIT'.
      IF p_rb1 EQ 'X'.
        screen-active = 0.
      ELSE.
        screen-active = 1.
      ENDIF.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
Regards,
Rajesh Kumar

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.

Selection screen 1000

hi,
Can i include a table control in selection screen 1000.
thank in advance
joseph fryda

I would not suggest it. Instead embed a selection screen in a subscreen of a dynpro with the table control.
Here is a sample program of how to embed a selection screen in a dynpro.
report zrich_0006 .
tables: mara.
* Custom Selection Screen 1010
selection-screen begin of screen 1010 as subscreen.
selection-screen begin of block b1 with frame title text-001.
parameters: p_rad1 radiobutton group grp1 default 'X',
            p_rad2 radiobutton group grp1,
            p_rad3 radiobutton group grp1.
select-options: s_matnr for mara-matnr,
                s_matkl for mara-matkl,
                s_mtart for mara-mtart.
selection-screen end of block b1.
selection-screen end of screen 1010.
start-of-selection.
call screen 100.
*&      Module STATUS_0100 OUTPUT
module status_0100 output.
* SET PF-STATUS 'xxxxxxxx'.
* SET TITLEBAR 'xxx'.
endmodule.
*&      Module USER_COMMAND_0100 INPUT
module user_command_0100 input.
endmodule.
* Screen screen 100 with a subscreen area called "subscreen_1010"
* Screen Flow Logic follows
*process before output.
* module status_0100.
* call subscreen subscreen_1010 including sy-repid '1010'.
*process after input.
* call subscreen subscreen_1010 .
* module user_command_0100.
Regards,
Rich Heilman
Message was edited by: Rich Heilman

Issue with tabbed block in selection screen

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

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

FEBA selection screen in ECC 6.0

Hi all,
We are migrating from 4.6C to ECC 6.0 and in the FEBA transaction, the initial selection screen looks totally different.
Rather than the "usual" screen starting with the selection fields application, company code, etc., we get a window in which many statement selections can be entered and once we select a statement, the statement is shown.
We do have 2 separate ECC 6.0 test systems and on 1 system FEBA shows the same as we have in 4.6C, but in the second ECC 6.0 test system, FEBA acts as just described. I've looked in the FEBA-view menu as well as customising but without luck.
So getting the "old" FEBA look is apparently possible, but does anyone know how to set it up?
Thanks!
Rene

Do you have the EA-FIN extension set active on the system where FEBA is different? I think that may be the reason.
We've been on ECC 6.0 for 2 years (we upgraded from 4.7). We had been using FEBA prior to the upgrade and did not see any changes with FEBA after the upgrade, however we did not activate EA-FIN as a part of the upgrade. Recently we have activated EA-FIN on our Development system only - and I just found that on that system, when I go into FEBA, I'm automatically re-routed to the new EBS post-processing transaction FEBAN. The FEBAN transaction has the statement selections that you describe. So I'm wondering if on your system where FEBA is different, the EA-FIN extension set is active and you are actually getting routed into FEBAN when you try to access FEBA on that system.
I have not, however, figured out if there is a setting that can be changed to get the "old" FEBA back. It could be that this is SAP's way of forcing companies to start using FEBAN instead of FEBA - and we'll just have to adjust. If you figure out how to get the old FEBA back - let us know!
Regards,
Shannon

Initializing Selection-Screen as dynpro subscreen

Similar Messages

Maybe you are looking for