Creating Editable UDFs in Batch Selection Screen

Hi,
I want to create editable UDFs in Serial/Batches screen.
I already created a field but it appears in Non-Editable format
any suggestion Plz
Regards
Sree

Hello everyone.
I have the same issue. I'd like to create a new field in selection-screen in HRForms, to pass it to the smart-form I'm using, but I'm not sure if that's possible in a standard way.
Can anybody help us?
Swetha, have you solved your problem?
Thanks in advance.
Estela Piçarra

Similar Messages

Can we create serach help for a selection screen field

Can we create serach help for a selection screen field with out creating searchhelp object.
I mean is it possible to create serchelp in the program itself with some specific values i want to give.
E.g say we can define any internal table and fill it with values and using that into selection screen fields
Regards
Mave

AT SELECTION-SCREEN ON VALUE-REQUEST FOR paymeth.
PERFORM PAYMENT_HELP.
FORM PAYMENT_HELP.
DATA: begin of DESCR_TAB occurs 0,
        DESCR LIKE BKPF-BKTXT,
        END OF DESCR_TAB.
DATA: gd_repid like sy-repid.
gd_repid = sy-repid.
DESCR_TAB-DESCR = 'aaaaa'.
append DESCR_TAB.
DESCR_TAB-DESCR = 'bbbbb'.
append DESCR_TAB.
DESCR_TAB-DESCR = 'ccccc'.
append DESCR_TAB.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
            retfield    = 'DESCR'
            DYNPPROG    = gd_repid
            DYNPNR      = '1000'
            DYNPROFIELD = 'paymeth'
            VALUE_ORG   = 'S'
            DISPLAY     = ' '
       TABLES
            value_tab   = DESCR_TAB.
endform.
Svetlin

How to create Option Boxes IN A SELECTION SCREEN

How to create Option Boxes IN A SELECTION SCREEN.
Thanks!

Hi Rajesh,
The following explanation gives clear picture of what is mean of check box and radio button with coding.....................
CHECK BOX :
AS CHECKBOX [USER-COMMAND fcode]
Effect:
This addition specifies that the input field in the first position of the selection screen is displayed as a checkbox, with the corresponding description next to it on the right. The checkbox is selected if the value of para is "X" or r "x". Otherwise, it is not selected.
The parameter must be created with the type c and length 1. An explicit length len is not permitted. If the addition TYPE is used, this can only be followed by the generic type c or a non-generic data type of type c and length 1.
The addition USER-COMMAND can be used to assign a function code fcode to the parameter. The function code fcode must be directly specified and may have a maximum length of 20 characters. To evaluate the function code, an interface work area of the structure SSCRFIELDS from the ABAP Dictionary must be declared using the statement TABLES. When the user selects the checkbox on the selection screen, the runtime environment triggers the event AT SELECTION-SCREEN and transfers the function code fcode to the component ucomm of the interface work area sscrfields.
Notes
If the TYPE addition is used to make a reference to a data type in the ABAP Dictionary of type CHAR and length 1, and for which t the valid values in the domain are defined as "X" and " ", the parameter is automatically displayed as a checkbox on the selection screen.
If the addition USER-COMMAND is specified without the addition AS CHECKBOX, and the parameter is of type c with length 1, it is also displayed as a checkbox.
The addition USER-COMMAND can, for example, be used for screen modifications with the addition MODIF ID (see example).
Coding :
PARAMETERS show_all AS CHECKBOX USER-COMMAND flag.
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 BEGIN OF BLOCK b2 WITH FRAME.
PARAMETERS: p4(10) TYPE c MODIF ID bl2,
 p5(10) TYPE c MODIF ID bl2,
 p6(10) TYPE c MODIF ID bl2.
SELECTION-SCREEN END OF BLOCK b2.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
 IF show_all <> 'X' AND
 screen-group1 = 'BL2'.
 screen-active = '0'.
 ENDIF.
 MODIFY SCREEN.
ENDLOOP.
RADIO BUTTON COMMAND :
RADIOBUTTON GROUP group [USER-COMMAND fcode]
Effect:
This addition specifies that the input field is displayed as a radio button in the first position on the selection screen, and the output field is displayed next to it on the right. The radio button is selected if the value of para is "X" or "x". Otherwise, it is not selected.
group is used to define the radio button group for the parameter. The name group is entered directly as a character string with a maximum of 4 characters. Within a selection screen, there must be a minimum of two parameters in the same radio button group. There cannot be more than one radio button group with the same name in one program, even if they are defined in different selection screens.
The parameter must be specified with the type c and length 1. Explicit length specification using len is not permitted. If the addition TYPE is used, it can only be followed by the generic type c or a non-generic data type of type c and length 1.
In a radio button group, only one parameter can be defined with the addition DEFAULT, and the specified value must be "X". By default, the first parameter in a radio button group is set to the value "X", and the rest are set to " ".
The addition USER-COMMAND can be used to assign a function code fcode to the first parameter in a radio button group. The function code fcode must be specified directly, and have a maximum length of 20 characters. To evaluate the function code, an interface work area of the structure SSCRFIELDS from the ABAP Dictionary must be declared using the statement TABLES. When the user selects any radio button of the radio button group on the selection screen, the runtime environment triggers the event AT SELECTION-SCREEN and transfers the function code fcode to the component ucomm of the interface work area sscrfields.
Note:
It is recommended to define the radio buttons of a radio button group directly underneath each other. If the selection screen also contains other elements, it is recommended to define each radio button group within a block surrounded by a frame.
CODING :
tables : mkpf,mseg,ekko.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETER : P_WERKS LIKE MARC-WERKS MODIF ID S1,
 c as checkbox.
SELECT-OPTIONS : S_EBELN FOR EKKO-EBELN NO INTERVALS MODIF ID S2.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-004.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS : R1 RADIOBUTTON GROUP G1 DEFAULT 'X' USER-COMMAND UC1.
SELECTION-SCREEN COMMENT 5(20) TEXT-002 FOR FIELD R1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS : R2 RADIOBUTTON GROUP G1.
SELECTION-SCREEN COMMENT 5(20) TEXT-003 FOR FIELD R2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK B2.
write :/ p_werks,
 / s_ebeln.
AT SELECTION-SCREEN OUTPUT .
LOOP AT SCREEN .
IF R1 EQ 'X' AND SCREEN-GROUP1 EQ 'S2'.
SCREEN-INPUT = 0.
SCREEN-REQUIRED = 1.
clear s_ebeln[].
clear p_werks.
MODIFY SCREEN.
ENDIF.
IF R2 EQ 'X' AND SCREEN-GROUP1 EQ 'S1'.
SCREEN-INPUT = 0.
SCREEN-REQUIRED = 1.
clear s_ebeln[].
clear p_werks.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
Let me knwo if any doubts.
Reward with points if it helpful
Regards,
Vijay

Batch determination in order doesnt branch into batch selection screen

HI Friends ,
I am doing manual batch determination in the sales order . My intention is to select specific batches if the system branches into batch selection screen . But the order wouldn't branch into that screen but directly the batch field is filled with the batch . Also system is giving message ' number of batch splits is limited to 001" . There are more than one batch in availability .
Could somebody tell me why it wouldn't allow me to select batches eventhough it is manual batch determination ?
Regards
Raghav

Hi,
In logistict genral>>>Batch mgt.>>>B. dtermination & check>>>Strategy type>>>Define SD strstegy types.
Select which type u r using , go to details speciefy u r batch spliting number or make it blank,also tick mark to changes allowed
Regards,
Kapil

How to create a variant for a selection screen button

hi ,
      i have created a selection screen for a normal report .
In the selection screen there is one button after the selct option for company code. when user enters some company code and presses the button the user i call a able contraol in which user gives some additional values for the comapny code.
how do i create variant. when i create varaint for the slection screen it does not take into account the other screen i called .
so every time user has to click that button and enter some values and execute. please suggest some way.
THANKX IN ADAVANCE:)

Hi,
      Inorder to create a variant for selection screen report, you need to enter valid data on the screen and click on the SAVE button which is available in the Menu.
      And regarding the button you were asking about after select option, it is not created manually it comes automatically,, you can remove this by mentioning no-extension after the select-option. You can get clear information of this if you do F1 help on select-option.
My advice to you, make effect use of F1 help.
Edited by: Madhuri on Sep 23, 2008 4:46 PM

To create a variant for a selection screen having invisible fields

Hello All
I am facing a peculiar problem. I have a screen for the program RSEIDOCB in which the following fields are hidden:
                TAOUTPR FOR EDIDC-STATUS NO-DISPLAY,
                STAINPR FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTRS FOR EDIDC-STATUS NO-DISPLAY,
                STAINTA FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTES FOR EDIDC-STATUS NO-DISPLAY,
                STAINTD FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTST FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTDT FOR EDIDC-STATUS NO-DISPLAY,
                STAINBK FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTEI FOR EDIDC-STATUS NO-DISPLAY,
                STAINEI FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTEX FOR EDIDC-STATUS NO-DISPLAY,
                STAINEA FOR EDIDC-STATUS NO-DISPLAY,
                STAOUTDS FOR EDIDC-STATUS NO-DISPLAY,
                STAINDS FOR EDIDC-STATUS NO-DISPLAY.
I want to create a variant for the above program having values for the fields. These fields are basically for specifying the various status of the idocs. I am unable to do to so at the moment. Please help me out. Suitable points will be provided.
Regards
Ankit

Hi Ankit
Follow these steps..
1. in SE38 enter Program name 'RSEIDOCB'.
2. Click on variants button
3. enter variant name click on create
4. in selection screen enter default values
5. Click on attributes
4. Enter meaning
5. Press Shft + F4
6. Bottom of Screen will popup invisible fields
7. go down to screen
8. select field and click on selection variables button
   (you to have to tick selection variable check box)
9. here click on down arrow button very next to field
10.you can choose values from list and assign to field.
then save variant.
Message was edited by:
        Perez C

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN. SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
 para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
 para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
 <area2> INCLUDING [<prog 2>] <dynp 2>,
 <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
 <area2>,
 <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
 SUB2 INCLUDING SY-REPID '0120',
 SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
 SUB2,
 SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ELSE.
 MYTABSTRIP-ACTIVETAB = SAVE_OK.
 CASE SAVE_OK.
 WHEN 'PUSH1'.
 NUMBER = '0110'.
 WHEN 'PUSH2'.
 NUMBER = '0120'.
 WHEN 'PUSH3'.
 NUMBER = '0130'.
 ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control
Pls. reward if useful

How to create check boxes dynamically in selection screen

Hi Experts,
I have a requirement of creating dynamic check boxes based on the number of records that are retrieved from a database table.
Can you please suggest me how to achieve it.
Regards
RP.

Hey RP,
Try this way.
REPORT ztest_program .
DATA: it_data TYPE TABLE OF t001.
DATA:check    TYPE char3.
DATA:sy_index TYPE char2.
DEFINE checkbox.
parameters:&1 as checkbox.
END-OF-DEFINITION.
CHECKbox:c01,c02,c03,c04,c05,c06,c07,c08,c09,c10,
         c11,c12,c13,c14,c15,c16,c17,c18,c19,c20,
         c21,c22,c23,c24,c25,c26,c27,c28,c29,c30,
         c31,c32,c33,c34,c35,c36,c37,c38,c39,c40.
AT SELECTION-SCREEN OUTPUT.
DESCRIBE TABLE it_data LINES sy-tfill.
sy-tfill = 39. "This will be changed based on the itab records. I just hardcoded the value
sy_index = 1.
LOOP AT SCREEN.
    CONCATENATE 'C' sy_index INTO check.
    IF screen-name = check.
      IF sy_index GT sy-tfill.
        screen-active = '0'.
        MODIFY SCREEN.
        sy_index = sy_index + 1.
        CONTINUE.
      ENDIF.
      sy_index = sy_index + 1.
    ENDIF.
ENDLOOP.
Thanks
Venkat.O

Create a flat list from SELECTION-SCREEN

Hi,
I have a selection for date on in an report,
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : dat_rang FOR sy-datum.
SELECTION-SCREEN END OF BLOCK blk1.
I want to create a flat list of dates from this selection. This list should exclude the date(s), which are excluded in the selection.
Please give some starters on how to do this.
Thank you,
CD

Here is another example, adding the dates to an internal table.
REPORT zrich_0001.
TYPES: BEGIN OF t_datum,
        datum TYPE sy-datum,
       END OF t_datum.
DATA: lt_datum TYPE TABLE OF t_datum.
DATA: ls_datum LIKE LINE OF lt_datum.
DATA: lv_date TYPE sy-datum.
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : dat_rang FOR sy-datum.
SELECTION-SCREEN END OF BLOCK blk1.
INITIALIZATION.
lv_date = '19000101'.
START-OF-SELECTION.
DO.
    IF lv_date IN dat_rang.
      ls_datum-datum = lv_date.
      APPEND ls_datum TO lt_datum.
    ENDIF.
    lv_date = lv_date + 1.
    IF lv_date = '20500101'.
      EXIT.
    ENDIF.
ENDDO.
LOOP AT lt_datum INTO ls_datum.
    WRITE:/ ls_datum-datum.
ENDLOOP.
Regards,
Rich Heilman

How to create a selection screen in a FM

Hello,
I have a FM. Here i have an import parameter called Selection.
So when Selection = X i need to show a selection-screen like if it would be a report. Do you know any fm or way to do this?
We have thought to create a report with the selection screen and to do a submit and return in the FM, and import/export the parameters. But maybe there are some clearer an easier way...
Thanks,
Manel
Edited by: Manel Casadesus on Oct 7, 2009 11:57 AM

Hi Manel,
<li>Its absolutely possible. I just tried. It works
<li>Plase the code in the TOP include of the function pool.
FUNCTION-POOL ZTEST_GRP.
SELECTION-SCREEN BEGIN OF SCREEN 1001.
PARAMETERS P_DATA TYPE CHAR2.
SELECTION-SCREEN END OF SCREEN 1001.
<li>Call the above defined selection-screen in the start of the function module.
FUNCTION ZTEST_FUNCTION_BADI.
*"*"Local Interface:
*" IMPORTING
*" REFERENCE(DAT) TYPE CHAR2
CALL SELECTION-SCREEN 1001.
ENDFUNCTION.
I hope that it solves your problem.
Thanks
Venkat.O

Creating Selection Screen version in Logical Database

Hi,
I want to design my own Selection screen while creating a report with Logical Database. My requirement is not to show the Standard Selection screen of LDB.
Can it be achieved by creating Selection Screen Version in SE36 and using that version in Attribute of the Report?
If yes, then how can it be created?

You can change the Selection Include to include your selection screen version.
Go to SE36
Select "Selections"
Change
Create a new version like:
SELECTION-SCREEN BEGIN OF VERSION 904 TEXT-904.
SELECTION-SCREEN EXCLUDE PARAMETERS: KD_STIDA.
SELECTION-SCREEN EXCLUDE SELECT-OPTIONS: KD_GJAHR, KD_BUDAT, KD_AUGDT,
KD_ZUONR, KD_UMSKZ.
SELECTION-SCREEN END OF VERSION 904.
Regards,
Naimesh Patel

Creating push button on Selection screen application toolbar

Hi Friends,
this is a HR-ABAP report. I have to create a push button on Selection screen. when user clicks on that push button 'MODAL DIALOG BOX' has to be displayed containing some data.
plz kindly give some sample code to do this.
Regards,
Radhika Dasharatha.

Hi,
1)Use SELECTION-SCREEN PUSHBUTTON /10(20) PUSH USER-
COMMAND 'ABC'. in selection screen.
2) Give the static name to button in INITIALIZATION event like PUSH = 'PRESS'.
3) At selection screen.
if sy-ucomm eq 'ABC'.
call FM HR_BE_GE_MODAL_DIALOG
endif.
Thanks
Sandeep
Reward if useful

Is it possible to create a variant without selection screen

Hi,
I would like to create a variant for a report(Standard report). It does not have selection screen. Could someone tell me is it possible to creste a varaint for it?
Is it possible to create a variant w/o selection screen? if yes, how?

If some SELECT-OPTIONS are hidden or NO-DISPLAY, you should be able to create a variant for the report.
Rob

Selection screen modification based on various buttons in selection screen

Hi,
I have 1 query related with Selection screen modification.
In my Report Program,I have created GUI Status for my selection screen
Now 2 buttons in application toolbar are coming on selection sceen.
For this i used,'At selection screen output' event.
And there are 2 blocks on selection screen.
If user press button1 then block2 should not display.
and if user press button2 then block1 should not display.
but the problem is i m not getting reqd result and also while doing debugging its not showing me sy-ucomm value.
Any pointers on this.
Thanks,
Mamta

Hi Mamta,
   have it in a group then you can write code accordingly see sample example,
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS       : p_r1 RADIOBUTTON GROUP rad
                        USER-COMMAND clk DEFAULT 'X'.            " upload Radio Button
SELECTION-SCREEN COMMENT 5(35) text-003.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN : BEGIN OF BLOCK 001 WITH FRAME TITLE text-001.
PARAMETERS: p_upl       LIKE rlgrap-filename MODIF ID a           "Upload File
                         DEFAULT 'c:\temp\parbmat.xls',
            p_werks     like t001w-werks MODIF ID a,              "Plant
PARAMETERS: p_rest      LIKE rlgrap-filename MODIF ID a           "Dwonload File Path
                         DEFAULT 'c:\temp\Success.xls'.
SELECTION-SCREEN : END OF BLOCK 001.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS : p_r2 RADIOBUTTON GROUP rad.
SELECTION-SCREEN COMMENT 5(35) text-004.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN : BEGIN OF BLOCK 002 WITH FRAME TITLE text-002.
PARAMETERS     : p_plant LIKE marc-werks MODIF ID b.                "Plant
PARAMETERS     : p_lgort LIKE mard-lgort MODIF ID b.                "Storage Location
PARAMETERS     : p_vkorg LIKE mvke-vkorg MODIF ID b.                "Sales Organization
PARAMETERS     : p_vtweg LIKE mvke-vtweg MODIF ID b.                "Distribution Channel
SELECT-OPTIONS : s_mat FOR mara-matnr MODIF ID b.                  "Material No No
SELECT-OPTIONS : s_dat FOR mara-ersda MODIF ID b.                  "Date on Record Created
PARAMETERS     : p_down LIKE rlgrap-filename MODIF ID b
                  DEFAULT 'c:\temp\Material Master.xls'.           "Download File Path
SELECTION-SCREEN : END OF BLOCK 002.
AT SELECTION-SCREEN OUTPUT.
*Inactive Fields depending on the radio button
LOOP AT SCREEN.
    IF p_r1 = 'X'.
      IF screen-group1 = 'B'.
        screen-active = 0.
      ENDIF.
    ELSEIF p_r2 = 'X'.
      IF screen-group1 = 'A'.
        screen-active = 0.
      ENDIF.
    ENDIF.
    MODIFY SCREEN.
ENDLOOP.
Edited by: suresh suresh on Jul 28, 2009 12:42 PM
Edited by: suresh suresh on Jul 28, 2009 12:42 PM

Adding layout variant to selection screen

Hi all,
         Currently I am working on report program, where I have to allow user to select his own output pattern. i.e layout variant is to be added to selection screen. The report uses object oriented ALV for display purpose. [set_table_for_first_display]
I made following steps,
1.     Declared one parameter of type disvariant.
2.     At selection-screen on value-request I called function REUSE_ALV_VARIANT_F4.
3.     Passed internal table to method set_table_for_first_display.
Now I am able to create save new variant, on selection screen I can select the variant that I have created, but output shows the all the fields though
Only few are selected. Please tell me any modification so as to reflect the changes in output.
I am searching for a function which maintains fieldcat according to user defined variant.
Regards,
Nilesh kulkarni.

U have to use REUSE_ALV_VARIANT_EXISTENCE inorder to use the layout u have selected
After ur code of REUSE_ALV_VARIANT_F4.
try this way
AT SELECTION-SCREEN.
   PERFORM PAI_OF_SELECTION_SCREEN.
G_REPID = SY-REPID.
G_SAVE = 'A'.
FORM PAI_OF_SELECTION_SCREEN .
IF NOT P_LAYOUT IS INITIAL.
    MOVE G_VARIANT TO GX_VARIANT.
    MOVE P_LAYOUT TO GX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
         EXPORTING
              I_SAVE     = G_SAVE
         CHANGING
              CS_VARIANT = GX_VARIANT.
    G_VARIANT = GX_VARIANT.
ELSE.
    PERFORM VARIANT_INIT.
ENDIF.
ENDFORM.                    " PAI_OF_SELECTION_SCREEN
FORM variant_init .
CLEAR G_VARIANT.
G_VARIANT-REPORT = G_REPID.
ENDFORM.                    " variant_init
Then when u call ALV for display, pass ur display variant, in this case = g_variant
Reward if useful
Cheers
~Arun
Message was edited by:
        Arun Shekhar

Creating Editable UDFs in Batch Selection Screen

Similar Messages

Maybe you are looking for