Complex selection screen

my require ment:
On selection screen two fields material,location with range of values need to be appear.
2nd step : read data from table /sapapo/v_matloc table based on selection criteria.
if we enter material no and the location then all the related fields has to be displayed in the another window.
out put should be classical type report.

Moderator message - Welcome to SCN.
This doesn't seem like a selection screen to me. Why don't you put your two SELECT OPTIONS only on the selection screen and then produce an ALV report with all af the material/location values? Then when the user clicks on a line, go to the report.
Rob

Similar Messages

How to haveour own titles/captions in selection screen & in column headings

we have SAP B1 2005 A, MS SQL 2005
though i am new to MSSQL/T-SQL programming, purely through lot of trials & errors i have learnt & managed to develop many reports/queries !
but, i am facing some problems : how to have our own captions/title for the options in selection screen & aso in reports/queries column headings.
e.g. :
for Customer Aging analysis, i would like to accept a set of 3 parameters (aging days) from the user. where the user may enter the values 30, 60 & 90 OR any other values.
i have the following codes for this purpose (considering my question's (over) size, only small portions of my program are given below)
declare @mdue1 int,
 @mdue2 int,
 @mdue3 int
set @mdue1 = [%1]
set @mdue2 = [%2]
set @mdue3 = [%3]
but, in the selection screen, the system displays "%1 Debit Amount Greater than" as the caption & 0.00 as the default value. the same is the case for the other two parameters [%2] & [%3] also.
i tried defining the variable @mdue1 as smallint & also tinyint, but the result is the same.
how to have our own captions/title for the options in selection screen instead of the ones displayed by t-sql based on our SELECT statement.
how to have our own column headings, dynamically defined/coined using variables instead of hard coded columns headings (within quotes).
e.g. in the select statement, instead of defining a column as '<= 30 Days' = T0.due_1
i would like to get the number of days from the user, who may enter 30 or 40 or whatever.
i would like to display the value that the user entered in the column heading using a variable say @mcol1
declare @mcol1 varchar(10)
set @mcol1 = '<= 'convert(varchar(10), @mdue1)' Days'
SELECT T0.CardCode,@mcol1 = T0.due_1 from #CustAging T0
but, this ends up in error.
i have already searched the net for ebooks, articles, etc. for a solution to this problem, but till now, i could not find any addressing these problems.
i have just registered in this forum with a hope to get a solution. thanks a lot in advance.
Thanks & Regards,
Raghu Iyer
Place : Vapi, Gujarat, India

thanks a lot, lstvan.
i think, it i a good "trick" worth trying out.
well, i will now mark this question as answered, but still, if anyone has a direct solution "problem", please do share with us.
i am able to write queries (in fact, full fledged programs) in T-SQL & getting the desired output and for such a trivial thing i do not want to go for an add-on SDK module. but, considering the limitations of T-SQL and the complex requirements of real business world, i think, we have to go the .net way only.
regarding add-ons, i heard that add-ons will slow down SAP B1. is it true ?
Thanks & Regards,
Raghu iyer

To get plant field in my selection screen based on user profile maintained

Hi All,
I have plant (WERKS) field in my selection screen. Now I need to get the plant value maintained in the user profile for that user. So how to get the plant value based on the user profile.
Please let me know if anyone having idea on this. I will reward to you with the valid points.
Regards
raghu.

Hi Raghu,
I have searched and found this information, check it may help you
Check the SY-UNAME with the the name of the Plant
User Plant user data take it from T001W table
and All logon User data will be in USR02 table
take the data from corresponding tables and check.
If you are working in SRM
Use FM BBP_READ_ATTRIBUTES to get the User plant after passing the User ID to the FM.
in SUIM go to Users by Complex Selection criterion.
In that there would be the Authorization Object..select an object which has the value plant in it and enter the value inthat....
Also u can enter WERKS value as 1120 in the object field and get the list,
Regards,
Satish

Remove arrow from selection screen

Hallow I have a arrow in my selection screen (for multiefile selection) and I wont to remove
It from my selection screen how can I do that?
(i remove x from set_mode but its not working)
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
SELECT-OPTIONS c_course FOR pchdy-objid_str NO INTERVALS OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR c_course-low.
*======================================================
REFRESH: c_course.
CLEAR: c_course.
PERFORM get_objid USING 'E '
 CHANGING c_course-low.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR c_course-high.
*======================================================
REFRESH: c_course.
CLEAR: c_course.
PERFORM get_objid USING 'E '
 CHANGING c_course-high.
CALL FUNCTION 'RH_OBJID_REQUEST'
 EXPORTING
 plvar = '01'
 otype = p_otype
 seark = '*'
 seark_begda = sy-datum
 so_date-low
 seark_endda = sy-datum
 so_date-high
 set_mode = 'X' "When active moltefile selection
DYNPRO_REPID = ' '
DYNPRO_DYNNR = ' '
DYNPRO_PLVARFIELD = ' '
DYNPRO_OTYPEFIELD = ' '
DYNPRO_SEARKFIELD = ' '
CALLBACK_PROG = ' '
CALLBACK_FORM = ' '
RESTRICT_FB = ' '
RESTRICT_DATA = ' '
WITHOUT_RSIGN =
WITHOUT_RELAT =
WITHOUT_SCLAS =
ORGBEG = SY-DATUM
ORGEND = SY-DATUM
WIN_TITLE =
APP_DATA =
 IMPORTING
 sel_plvar = wa_plvar
 sel_otype = wa_otype
 sel_object = wa_objid
 TABLES
OTYPE_TABLE =
CONDITION =
BASE_OBJECTS =
MARKED_OBJECTS =
 sel_objects = itab_object
SEL_HROBJECT_TAB =
SEL_HRSOBID_TAB =
 EXCEPTIONS
 cancelled = 1
 wrong_condition = 2
 nothing_found = 3
 internal_error = 4
 illegal_mode = 5
 OTHERS = 6
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF wa_otype = 'E' .
 REFRESH: c_course.
 CLEAR: c_course.
 LOOP AT itab_object.
 CLEAR c_course.
 c_course-low = itab_object-objid.
 c_course-option = 'EQ'.
 c_course-sign = 'I'.
 APPEND c_course.
 ENDLOOP.
 CLEAR: itab_object.
 REFRESH: itab_object.
ENDIF.

Add the NO-EXTENSION to your SELECT-OPTIONS will remove the arrow.
For more complex control off the SELECT-OPTIONS you can use FM: SELECT_OPTIONS_RESTRICT where you can almost completelly control the options.
(Look at <a href="http://www.geocities.com/victorav15/sapr3/abapfun.html#screen">SELECT_OPTIONS_RESTRICT</a>
Regards

Create a custom multiple selection on screen - not selection-screen block

Dear expert,
I created a text field on screen for input selection, e.g field bname for USR02-BNAME. How can i create a CUSTOMIZE multiple selection plus a paste (from clipboard) feature on this screen (e.g. SCREEN 0002) like standard selection-screen from SAP when we create a report.
For a better view on what i want:
This text field already use F4 customize search help. I need a multiple selection lines (like standard selection-screen a button on the right side of select-options field).
Remember, i don't create textfield from select-options parameter (e.q. SELECT-OPTIONS : XBNAME FOR USR02-BNAME),
but on a screen.
Anyone can help my case?.
Thanks and Warm regards,
Dondi.

Had the same question from my users. This was the first hit i found but unfortunately without an answer. So for those with the same question, this is how i solved it (goede voornemen voor 2014). In my case the request is a complex selection on the LFA1 table.
The screen contains two fields to enter the low/high value for lifnr (zdy_droogteschade-lifnr and zdy_droogteschade-lifnr_tot)
Created a button on the screen, mark this as output only, when pressed the routine multi_select_crediteuren is performed wich uses the fm 'COMPLEX_SELECTIONS_DIALOG'.
To top it all of, the icon on the button changes depending on the contains of the range table (in a routine called from the PBO).
This only works when the button is marked as 'output only',
Include the icon type pool: 'type-pools: icon.'

How to display Selection screen on Web for RSCRM_BAPI

HI,
For a customer we want to create the possibility to extract data from BI2004s to other systems, therefore we want to use RSCRM_BAPI.
Thing is that we want to provide the possibility for them to enter selectioncriteria, but we don't want them to log on using the Gui.
We want to use the VC to create an interface cockpit.
question is how we can allow users to use selectioncriteria but:
variants can not be used
TVARV can not be used
is there any way to capture the selection screen and to display it on the web/VC?
Anyone ever did this?
Tnx
rogier

Gili.
thank you for your quick reply,.
Reason why we are looking into the RSCRM_BAPI is due to the layout
requirements of the extract. the recieving systems requires specific layouts. If we do this with the infospoke we will have to use a BADI to perfom complex transformations which will need additional knowlegde (of BADI's) of the support organisation whereas with RSCRM_BAPI they can adjust the query.
and as far as i know you can not define the variable input via the web for open hub.
Grtz
rogier

Issue In Providing 255 Charcters From The Selection Screen Select-Option

Dear Guru,
I am searching for table field with having length = 255 character.
which i want to use in select-option for proving data from the selection screen.
I have found the table myhlp and it associated field allvals which is having length = 255.
I am using it as below in my selection screen for the value to be provided 255 character long.
SELECTION-SCREEN : BEGIN OF BLOCK b3 WITH FRAME TITLE text-003.
SELECT-OPTIONS   : s_mlbody FOR myhlp-allvals NO INTERVALS.
SELECTION-SCREEN : END OF BLOCK b3.
Now when i am going for the multiple selection option --> It is providing me the Multiple selection popup and giving me the provision of provide multiple line .
But the issue is that --> For a particular single value line in the popup i am able to enter only 45 charcters not 255 character.
But i need to put 255 charcter for particular line in a single value..
Please give me some guideline how resolve this or any other alternative way of reading the 255 charcter from the selection screen
Thanks & regards
Saifur Rahaman

Hi,
     As said by A@s selction screen with table control will be a good option.
design a custom screen with SUBSCREEN as screeen attribute using tcode se51.
For table control sample - go through Tcode ABAPDOCU - abap user dialogs-screens-complex screen- table control
Try Following,
REPORT Zsample .
controls: tc type tableview using screen 200.
parameters: p_user type myhlp-username.
data: begin of itab occurs 50,
      field1(255) type c,
      end of itab.
data: i_out type standard table of myhlp.
SELECTION-SCREEN BEGIN OF TABBED BLOCK MAX FOR 22 LINES.
SELECTION-SCREEN TAB (25) TABS1 USER-COMMAND UCOMM1
         DEFAULT SCREEN 200.
SELECTION-SCREEN END OF BLOCK MAX.
start-of-selection.
select * from myhlp into table i_out for all entries in itab
          where username eq p_user
                and allvals = itab-field1.
MODULE READ_ITAB INPUT.
insert itab index tc-current_line.
ENDMODULE.                 " READ_ITAB INPUT

Posting in Enjoy Screen and Complex Posting Screens

Hi,
I want to know the difference of posting in FB60/FB70 enjoy screens and the F-02 complex posting screens. Can someone tell me in what cases i have to use the F-02 screen by explaining a sample business transaction which cannot be posted in FB60 or FB70 but can be posted in F-02.
Thanks.

Hi,
Both F-02 and the enjoy transactions FB60/70 serve the same purpose. However, enjoy transaction make the entry look more simple and encourage a non functional user to enter correctly without any conflict as to debit/credit.
In case of F-02, you need to select the posting keys. These posting keys will define either the transaction needs to be debited or credited. Though all the tcodes serve the same purpose, the following are the key differences
1. F-02 is used for different document types (AB, SA, RE etc.,). It will be used for accounting as well as AP/AR entries if required.
2. In F-02, the posting keys define the document type. For eg., if you use KN as the document type, you need to use posting key 21 or 31 to allow the system to enter the vendor code. However, in case of FB60/70, you just need to select if the entry is a invoice or a credit memo and the credit and debit is already identified in the screen.
3. FB60/70 is more easier and exhaustive for the accountants to enter the data. F-02 may not be useful in day to day entry of invoices.

Icon at selection screen

Hi All,
how i can add icon on the menu bar of selection screen and it should work as user command.

Hi Sandeep,
Please refer to the below help link:
http://help.sap.com/saphelp_47x200/helpdata/en/9f/dba80935c111d1829f0000e829fbfe/frameset.htm
If you want to make it more complex (with icon):then using transaction SE41
Copy the PFSTATUS %_00 of program RSSYSTDB to PFSTATUS Z_00 and your program.
Then modify the PF status as you desire.
In your program:
AT SELECTION-SCREEN OUTPUT.
SET PF-STATUS 'Z_00'
Sorry forgot to add - then at
AT SELECTION-SCREEN.
event you can do
CASE SY-UCOMM. WHEN '<your_fcode>'. Do something .... ENDCASE.
Cheers,
Adi
Edited by: Aditya Laud on Apr 9, 2009 8:15 AM
Edited by: Aditya Laud on Apr 9, 2009 8:20 AM

Disabling complex selection button

Hi Experts,
   In my select-options, based on the user ( sy-uname ), I am disabling the select-option-High value.
   i.e.      if screen-name = 'S_DATE-HIGH'.
                screen-input = 0.
             endif.
But at the same time I need to disable the complex selection button also. It means that the user has to give only one input like parameter.
How can I disable complex selection button.
Thanks and regards,
Venkat

hi,
please check this below code
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-027 .
PARAMETERS: P_RADIO1 RADIOBUTTON GROUP RAD DEFAULT 'X' USER-COMMAND UCOM .
PARAMETERS : P_KEY TYPE SYDATUM DEFAULT sy-datum MODIF ID MO1.
PARAMETERS: P_RADIO2 RADIOBUTTON GROUP RAD.
SELECT-OPTIONS: SO_BUDAT FOR BSIS-BUDAT MODIF ID MO2 .
SELECTION-SCREEN END OF BLOCK B2.
*--AT SELECTION-SCREEN OUTPUT STATMENTS--
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
     IF P_RADIO1 = 'X'.
       CHECK SCREEN-group1 = 'MO1'.
       SCREEN-INPUT = 1.
     ELSE.
       CHECK SCREEN-group1 = 'MO1'.
       SCREEN-INPUT = 0.
    ENDIF.
    MODIFY SCREEN.
ENDLOOP.
LOOP AT SCREEN.
    if P_RADIO2 = 'X'.
      CHECK SCREEN-GROUP1 = 'MO2'.
      SCREEN-INPUT = 1.
    ELSE.
      CHECK SCREEN-GROUP1 = 'MO2'.
      SCREEN-INPUT = 0.
   endif.
       MODIFY SCREEN.
ENDLOOP.

Selection screen within tree control model

Hello,
I am very new in ABAP OO, and have to make a module program for SD to handle the status of shipment.
I need to make a tree model of 3 parts that the first part has the selection screen.
There is a Sap standard model: program /DSD/SL_COCKPIT who has the same modle.
Is someone know how to do that ? which Class to use?
Any help would be appreciated...
Fariba

Hello Fariba
The target you have choosen to start with ABAP OO is not really the easiest one.
The three-parted screen in program /DSD/SL_COCKPIT is created using class /DSD/SL_CL_FRAME_COCKPIT. Simply display the class in the class builder (SE24), push F8 (Test) and create an instance of the class.
Perhaps this may be useful in starting you analyzing the details of this rather complex program and class.
Regards
Uwe

Can you giv me a brief introduction regarding selection screen with one eg:

Hello
can you giv me a brief introduction regarding selection screen with one eg:

Hi Ranjith,
Selection Screens
Selection screens are one of the three types of screen in the R/3 System, along with dialog screens and lists. You use them whenever you want the user to enter either a single value for a field or fields, or to enter selection criteria.
Function
ABAP programs use screens to obtain input from users. The most general type of screen is a dialog screen, which you create using the ABAP Workbench tools Screen Painter and Menu Painter These tools allow you to create screens for data input and output. However, each of these screens requires its own flow logic.
Defining and Calling Selection Screens
You often use screens purely for data input . In these cases, you can use a selection screen. Selection screens provide a standardized user interface in the R/3 System. Users can enter both single values and complex selections. Input parameters are primarily used to control the program flow, while users can enter selection criteria to restrict the amount of data read from the database. You can create and save predefined sets of input values in the ABAP Editor for any selection screen. These are called variants. Texts on the selection screen are stored as language-specific selection texts in the program text elements. If you start an executable report using the SUBMIT statement, the input fields of the selection screen also serve as a data interface.
Defining and Calling Selection Screens
You define selection screens using ABAP statements in a program. Simple statements allow you to create input fields, checkboxes, and radio buttons, and design the screen layout. If you want to create a screen exclusively for data input, you do not need to create it using the normal dialog programming tools. When you create a selection screen, the system automatically assumes the tasks of the Screen Painter and Menu Painter.
The rules for calling and defining selection screens in ABAP programs depend on the program type:
·         Executable program (type 1) without logical database
You can use a single standard selection screen and as many user-defined selection screens as you wish. The standard selection screen is called automatically when you start the program. User-defined selection screens, on the other hand, are called using the CALL SELECTION-SCREEN statement in a program. The standard selection screen always has the screen number 1000. User-defined selection screens can have any screen number except 1000.
·         Executable program (type 1) with logical database
The standard selection screen for an executable program linked to a logical database is made up of the logical database selections and the program selections.
·         Module pools (type M) and function modules (type F)
You can only use user-defined selection screens in module pools and function modules. These can have any number apart from 1000. You can only call a selection screen from a function module using the CALL SELECTION-SCREEN statement. You can also define selection screens as Subscreens and incorporate them in screens or tabstrip controls.
Hope this is useful.
regards
Ram
Message was edited by:
        Ramanujan Chitrakootam

WHAT IS ACTUALLY SELECTION SCREEN

WHEN DOES ACTUALLY SELECTION SREEN WILL BE EXECUTED ACCORDING TO PRIORITY.

Hai Raghu
Go through the following Document
SELECTION-SCREEN
Variants
1. SELECTION-SCREEN BEGIN OF LINE.
2. SELECTION-SCREEN END OF LINE.
3. SELECTION-SCREEN SKIP n.
4. SELECTION-SCREEN ULINE.
5. SELECTION-SCREEN POSITION pos.
6. SELECTION-SCREEN COMMENT fmt name.
7. SELECTION-SCREEN PUSHBUTTON fmt name USER-COMMAND ucom.
8. SELECTION-SCREEN BEGIN OF BLOCK block.
9. SELECTION-SCREEN END OF BLOCK block.
10. SELECTION-SCREEN FUNCTION KEY n.
11. SELECTION-SCREEN BEGIN OF VERSION ver TEXT-xxx.
12. SELECTION-SCREEN END OF VERSION ver.
13. SELECTION-SCREEN EXCLUDE ... .
14. SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE dbtab.
15. SELECTION-SCREEN FIELD SELECTION FOR TABLE dbtab.
Effect
The key word SELECTION-SCREEN only makes sense in reports, i.e. programs specified as type "1" in the attributes. You use it to design the selection screen in the program or logical database access routine.
The selection screen is normally generated from the SELECT-OPTIONS and PARAMETERS statements in the report and logical database access routine. Each of these objects occupies a separate line on the selection screen.
SELECTION-SCREEN allows you to form blocks, combine several parameters and comments together on one line, generate pushbuttons on the screen or activate them in the application toolbar, as well as insert blank lines, underscore lines and comments.
Like SELECT-OPTIONS and PARAMETERS , you can use SELECTION-SCREEN statements in reports and in the include program DBldbSEL of the logical database ldb assigned to the report in the attributes. Some variants are defined only for logical databases and can therefore only be used in the include program DBldbSEL .
Variant 1
SELECTION-SCREEN BEGIN OF LINE.
Variant 2
SELECTION-SCREEN END OF LINE.
Effect
Allows you to combine several parameters and comments specified between the SELECTION-SCREEN BEGIN OF LINE and SELECTION-SCREEN END OF LINE statements and output them on one line. As a result, there is no automatic new line for each PARAMETER and no selection texts are displayed.
Example
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(10) TEXT-001.
PARAMETERS: P1(3), P2(5), P3(1).
SELECTION-SCREEN END OF LINE.
Selection screen:
Comment ___ _____ _
Note
You cannot order SELECT-OPTIONS between SELECTION-SCREEN BEGIN OF LINE and SELECTION-SCREEN END OF LINE because several objects are generated on the selection screen for a SELECT-OPTION (e.g. fields for the lower and upper limits of ranges).
Variant 3
SELECTION-SCREEN SKIP n.
Additions
1. ... FOR TABLE dbtab
2. ... ID id
Effect
Generates n blank lines (see also SKIP ).
You must specify a value for n between 1 and 9. If you want to output just one blank line, you can omit n .
Addition 1
... FOR TABLE dbtab
Effect
This addition is allowed only in the database include program DBldbSEL . It is, in fact, a requirement. If you use SELECTION-SCREEN SKIP in DBldbSEL , you must assign the statement to a table (or to a field - see the variant COMMENT .
This assignment is necessary in order to restrict the SELECTION-SCREEN statements for a report selection screen to those relevant for the tables used in the report, i.e. those which refer to a table used in the report. Any SELECTION-SCREEN statement assigned to a table not used in the report with the addition FOR TABLE dbtab are ignored when the report selection screen is generated.
Note
A table dbtab of the logical database ldb is considered as "used in the report" if it is either declared in a TABLES statement or its position in the database hierarchy lies somewhere between the root and a table dbtab_2 declared in the report.
Example
Hierarchy of logical database ldb :
SPFLI
SAPLANE
SFLIGHT
 |
SBOOK
In the report:
TABLES SFLIGHT.
Tables considered as "used" include SFLIGHT (since it is
declared directly), as well as SAPLANE and SPFLI (since
they lie on the path from the hierarchy root " SPFLI " to the
declared table SFLIGHT ). The table SBOOK is not
considered as used, i.e. all the SELECTION-SCREEN statements
qualified with the addition " FOR TABLE SBOOK " in DBldbSEL
are ignored.
Addition 2
... ID id
Effect
This addition is allowed only in the database include program DBldbSEL . It is used to identify a SELECTION-SCREEN object (in this case blank lines) via an ID which can be up to 3 characters long. This ID is then specified in SELECTION-SCREEN EXCLUDE IDS id in order to exclude the object from a selection screen version.
Variant 4
SELECTION-SCREEN ULINE.
Additions
1. ... fmt
2. ... FOR TABLE dbtab
3. ... MODIF ID mod
4. ... ID id
Effect
Generates an underline (see also ULINE ).
Addition 1
... fmt
Effect
Format specification with the form /pos(len) , pos(len) or (len) . The slash ( / ) generates a new line and is therefore not allowed between BEGIN OF LINE and END OF LINE . The effect of the statement is to underscore the current line starting from the position pos for the length len . The variant (len) (without position specification) is allowed only between BEGIN OF LINE and END OF LINE . In this case, the current position in the line is used. See also WRITE .
You can specify the position pos as a number (in this case, it is relative to the frame if the statement comes between SELECTION-SCREEN BEGIN OF BLOCK ... WITH FRAME ... and SELECTION-SCREEN END OF BLOCK ... ). Also allowed are the symbolic positions POS_LOW and POS_HIGH . These are the positions at which the input fields of the SELECT-OPTI ONS are output ( POS_LOW is also the position of PARAMETERS .
Note
Format specifications which do not generate a new line can produce overlapping objects on the selection screen. Therefore, you should be particularly careful with position and length specifications.
Example
SELECTION-SCREEN ULINE /1(10).
SELECTION-SCREEN ULINE POS_LOW(10).
SELECTION-SCREEN ULINE POS_HIGH(10).
This generates three underscore blocks, each with a length of 10, on one line.
Addition 2
... FOR TABLE dbtab
Effect
See variant 3 ( SELECTION-SCREEN SKIP ).
Addition 3
... MODIF ID mod
Effect
The specified modification group ( SCREEN-GROUP1 ) is assigned to the underscore. You can use this under AT SELECTION-SCREEN in the report or in the PAI routine of the database program SAPDBldb to modify the screen.
Note
The name of the modification group must be specified without quotation marks. It can be up to three characters long.
Addition 4
... ID id
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Variant 5
SELECTION-SCREEN POSITION pos.
Addition
... FOR TABLE dbtab
Effect
Outputs the parameter starting from the position pos .
This variant is allowed only between SELECTION-SCREEN BEGIN OF LINE< /> and SELECTION-SCREEN END OF LINE .
As with the addition ULINE , you can specify the position as fixed (if necessary relative to the frame) or symbolically in the form POS_LOW or POS_HIGH .
Addition
... FOR TABLE dbtab
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Variant 6
SELECTION-SCREEN COMMENT fmt name.
Additions
1. ... FOR TABLE dbtab
2. ... FOR FIELD f
3. ... MODIF ID mod
4. ... ID id
Effect
Generates a comment on the selection screen. For the name name , there are two options:
name takes the form TEXT-xxx where xxx is a three-character name for a text symbol. In this case, the contents of the text symbol are displayed at runtime, i.e. the text cannot be changed dynamically. name is another eight-character name. Here, you create a field with the name name in the length specified in the format fmt< /> and it is then generated as an output field on the selection screen. The contents of these comments must therefore be set at runtime (e.g. at INITIALIZATION or - in the case of comments in the database include program DBldbSEL - in the routine INIT of the database program SAPDBldb . They can also be changed when the selection screen is being processed.
Note
The field name is generated automatically and so cannot be defined with DATA .
With comments, you must always specify a format fmt (see variant ULINE ).
Note
You must program a new line yourself via the format fmt .
Addition 1
... FOR TABLE dbtab
Note
See variation 3 (SELECTION-SCREEN SKIP).
Addition 2
... FOR FIELD f
Effect
Since the comment is assigned to a parameteror a select-option , the help display shows the documentation of the reference field if this parameter or selection option.
In addition, the comment is suppressed if the reference object was set to 'invisible' via a selection variant.
Note
In database access routines, the comment is generated whenever the reference field is output. Therefore, you should not use the addition FOR TABLE with this variant.
Example
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 10(20) TEXT-001
 FOR FIELD PARM.
SELECTION-SCREEN POSITION POS_LOW.
PARAMETERS PARM LIKE SAPLANE-PLANETYPE.
SELECTION-SCREEN END OF LINE.
This code displays a 20-byte long comment followed by the parameter at the normal position ( POS_LOW ) on the same line. If the user presses F1 for both objects, the documentation of SAPLANE-PLANETYPE is displayed.
Addition 3
... MODIF ID mod
Effect
See variant 4 ( SELECTION-SCREEN ULINE )
Addition 4
... ID id
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Variant 7
SELECTION-SCREEN PUSHBUTTON fmt name USER-COMMAND ucom.
Additions
1. ... FOR TABLE dbtab
2. ... MODIF ID mod
3. ... ID id
Effect
Generates a pushbutton on the selection screen. Also specified is the user command ucom (without quotation marks) which can be up to 4 characters long. This is generated when the user presses the button. Apart from this, the syntax is largely similar to that of SELECTION-SCREEN COMMENT :
For the name name , there are two options:
name takes the form TEXT-xxx where xxx is a three-character name for a text symbol. In this case, the contents of the text symbol are displayed at runtime, i.e. the text cannot be changed dynamically. name is another eight-character name. Here, you create a field with the name name in the length specified in the format fmt< /> and it is then generated as an output field on the selection screen. The contents of these comments must therefore be set at runtime (e.g. at INITIALIZATION or - in the case of comments in the database include program DBldbSEL - in the routine INIT of the database program SAPDBldb . They can also be changed when the selection screen is being processed.
Note
The field name is generated automatically and so cannot be defined with DATA .
With pushbuttons, you must always specify a format fmt (see variant ULINE ).
Note
You must program a new line yourself via the format fmt .
The best way to respond to the user pressing the pushbutton is in the event AT SELECTION-SCREEN or - in the case of pushbuttons in the database include program DBldbSEL - in the routine PAI (with FNAME = '*' and MARK = SPACE ) in the database program SAPDBldb . Here, the field SSCRFIELDS-UCOMM contains the user command ucom (the table SSCRFIELDS must be declared with the TABLES statement).
Addition 1
... FOR TABLE dbtab
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Addition 2
... MODIF ID mod
Effect
See variant 4 ( SELECTION-SCREEN ULINE )
Addition 3
... ID id
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Example
TABLES SSCRFIELDS.
SELECTION-SCREEN PUSHBUTTON /10(20) CHARLY USER-COMMAND ABCD.
INITIALIZATION.
MOVE 'My text' TO CHARLY.
AT SELECTION-SCREEN.
IF SSCRFIELDS-UCOMM = 'ABCD'.
ENDIF.
The selection screen displays a pushbutton with the text 'My text' . With AT SELECTION-SCREEN , the field SSCRFIELDS-UCOMM contains ABCD after the user has pressed the button.
Variant 8
SELECTION-SCREEN BEGIN OF BLOCK block.
Additions
1. ... WITH FRAME
2. ... TITLE title
3. ... NO INTERVALS
Effect
Starts a logical block on the selection screen. If you use the addition WITH FRAME , a frame is generated around the block. The addition TITLE title is allowed only in conjunction with WITH FRAME .
For the title title ,there are two options (see also the variants COMMENT and PUSHBUTTON ):
title takes the form TEXT-xxx where xxx is a three-character name for a text symbol. In this case, the contents of the text symbol are displayed at runtime, i.e. the text cannot be changed dynamically. title is another eight-character name. Here, you create a field with the name title in the length specified in the format fmt< /> and it is then generated as an output field on the selection screen. The contents of these comments must therefore be set at runtime (e.g. at INITIALIZATION or - in the case of comments in the database include program DBldbSEL - in the routine INIT of the database program SAPDBldb . They can also be changed when the selection screen is being processed.
Note
The field title is generated automatically and so cannot be defined with DATA .
At runtime, the event AT SELECTION-SCREEN ON BLOCK block is executed for every block in the PAI module of the selection screen (with database- specific blocks, the PAI module in the program SAPDBldb is also executed with the parameters FNAME = BLOCK_block and MARK = SPACE ). If this produces an error message, just the fields of this block are ready for input.
You can nest blocks. The maximum nesting depth for blocks with frames is 5.
Addition 3
... NO INTERVALS
Effect
Displays all SELECT-OPTIONS within the block in simplified form without a 'to' field on the selection screen (like the addition " NO INTERVALS " with SELECT-OPTIONS ). If the block has a frame, this is correspondingly small.
Note
In the case of blocks without frames, the attribute " NO INTERVALS " is not inherited by subordinate blocks. However, all subordinate blocks of blocks with frames inherit this attribute because the generated frame is smaller and there is no space for the 'to' field.
Variant 9
SELECTION-SCREEN END OF BLOCK block.
Effect
Closes the block opened by SELECTION-SCREEN BEGIN OF BLOCK block . If the block has a frame, the frame is closed here. Blocks opened in the include program DBldbSEL must also be closed there.
Note
Blocks defined in the database include program DBldbSEL must also be close there. As with SELECTION-SCREEN BEGIN OF LINE and SELECTION-SCREEN END OF LINE , you cannot use the addition FOR TABLE with blocks. Instead, the objects in the blocks (selection options , parameters , comments, underscores ...) are omitted if the table to which they belong is not used in the report (see note under variant SELECTION-SCREEN SKIP ). Empty blocks (possibly with frames) are also omitted.
Example
TABLES SAPLANE.
SELECTION-SCREEN BEGIN OF BLOCK CHARLY
 WITH FRAME TITLE TEXT-001.
PARAMETERS PARM(5).
SELECT-OPTIONS SEL FOR SAPLANE-PLANETYPE.
SELECTION-SCREEN END OF BLOCK CHARLY.
(Let TEXT-001 contain 'Block Charly' ).
Selection screen:
Block Charly--
PARM _____
| SEL ________ bis ________ |
Variant 10
SELECTION-SCREEN FUNCTION KEY n.
Additions
1. ... FOR TABLE dbtab
2. ... ID id
Effect
With this variant, you can activate up to 5 function keys in the application toolbar on the selection screen ( n is one of the numbers 1 to 5).
At runtime, the text must be placed in the Dictionary field SSCRFIELDS-FUNCTXT_01 or ... SSCRFIELDS-FUNCTXT_05 .
The function code placed in the field SSCRFIELDS-UCOMM is 'FC01' or ... 'FC05' . You can read this function code under AT SELECTION-SCREEN or in the PAI module of the database access program SAPDBldb .
Addition 1
... FOR TABLE dbtab
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Addition 2
... ID id
Effect
See variant 3 ( SELECTION-SCREEN SKIP )
Example
TABLES SSCRFIELDS.
SELECTION-SCREEN FUNCTION KEY 1.
INITIALIZATION.
MOVE 'My text' TO SSCRFIELDS-FUNCTXT_01.
AT SELECTION-SCREEN.
IF SSCRFIELDS-UCOMM = 'FC01'.
ENDIF.
The selection screen displays a pushbutton with the text 'My text' . With AT SELECTION-SCREEN , the field SSCRFIELDS-UCOMM contains FC01 after the user has pressed the button.
Variant 11
SELECTION-SCREEN BEGIN OF VERSION ver TEXT-xxx.
Variant 12
SELECTION-SCREEN END OF VERSION ver.
Variant 13
SELECTION-SCREEN EXCLUDE ... .
Effect
Defines a selection screen version (with a three-character name ver ). These variants are only allowed in the database include program DBldbSEL . Between BEGIN OF VERSION and END OF VERSION , you can exclude selection screen objects for the version ver , i.e. remove them from the selection screen with SELECTION-SCREEN EXCLUDE. .
For a report, you activate a selection screen by making an entry in the attributes. If the database access program SAPDBldb itself has a selection screen version in the attributen, this applies for all reports which use this logical database and have attributes where no separate selection screen version is declared.
The text symbol TEXT -xxx is used merely to facilitate selection of a selection screen version via F4 help when maintaining the attributes.
Additions
(to SELECTION-SCREEN EXCLUDE )
1. ... PARAMETERS par
2. ... SELECT-OPTIONS sel
3. ... RADIOBUTTON GROUPS radi
4. ... BLOCKS block
5. ... IDS id
Effect
Excludes selection screen objects between SELECTION-SCREEN BEGIN and END OF VERSION . This allows you to exclude individual parameters or selection options , radiobutton groups , blocks defined by SELECTION-SCREEN BEGIN/END OF BLOCK and other objects such as comments and underscores specified by the addition ID id .
Note
The database program SAPDBldb can get the active version for the current report with the function module RS_SELSCREEN_VERSION .
Example
PARAMETERS PAR_1 LIKE dbfield_1 FOR TABLE dbtab_1.
SELECT-OPTIONS SEL_1 FOR dbfield_01.
SELECT-OPTIONS SEL_2 FOR dbfield_02.
SELECT-OPTIONS SEL_3 FOR dbfield_03.
SELECTION-SCREEN COMMENT /10(20) TEXT-100 FOR TABLE dbtab_1 ID 001.
SELECTION-SCREEN COMMENT /8(30) TEXT-200 FOR TABLE dbtab_2 ID 002.
PARAMETERS PAR_2 LIKE dbfield_1 FOR TABLE dbtab_2.
PARAMETERS PAR_3 LIKE dbfield_1 FOR TABLE dbtab_2.
SELECTION-SCREEN BEGIN OF VERSION ABC TEXT-008.
SELECTION-SCREEN EXCLUDE PARAMETERS: PAR_1, PAR_3.
SELECTION-SCREEN EXCLUDE SELECT-OPTIONS: SEL_2.
SELECTION-SCREEN EXCLUDE IDS: 001.
SELECTION-SCREEN END OF VERSION ABC.
If the report attributes (or the attributes of the database program SAPDBldb ) contain the selection screen version ABC , the parameters PAR_1 and PAR_3 , the selection option SEL_2 and the comment with the text number 100 ( ID 001 ) are not displayed on the selection screen. When you maintain the attributes, the text symbol 008 of SAPDBldb is displayed if you press F4 on the field 'Selection screen version'.
Variant 14
SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE dbtab.
Addition
... ID id
Effect
This variant is allowed only in the database include program DBldbSEL . It informs you for which logical database tables additional selections are supported. If one of these tables is active in the report (i.e. it is declared under TABLES or lies somewhere on the path from the root of the database hierarchy to a table declared with TABLES ), a psuhbutton called 'Dynamic selections' appears on the selection screen. On pressing this button, the user branches to a dialog Taste where it is possible to enter selections for the fields of the relevant tables in the logical database. You can define the field list in two different ways:
Via a selection view defined for the purpose:
You can maintain selection views within the logical database maintenance transaction. They consist of a set of fields from logical database tables which are divided into groups. It is also possible to preselect fields. Customers can overlay these selection views with their own (i.e. in this case, the system searches first for the customer selection view and only accesses the SAP selektion view if no customer-specific view exists).
If a preselection has already been made in the selection view, the user immediately sees the selection screen for the preselected fields and can enter selections. Otherwise, a fields must be selected first.
Via all fields of all tables
In this case, the user must first choose the tables and then select the fields for which additional selections are to be made before branching to the selection screen to enter the dynamic selections.
The database access programm SAPDBldb then receives the WHERE clauses generated from the user entries in the form of a complex data object DYN_SEL .
Addition
... ID id
Effect
Similar to the addition 2 ( SKIP ). This allows you to exclude tables from the possibility of dynamic selection via the selection screen versions.
Note
The exact definition of the object DYN_SEL is stored in the TYPE-POOL RSDS and is as follows:
TYPES: BEGIN OF RSDS_WHERE,
 TABLENAME LIKE RSDSTABS-PRIM_TAB,
 WHERE_TAB LIKE RSDSWHERE OCCURS 5,
 END OF RSDS_WHERE.
TYPES: BEGIN OF RSDS_TYPE,
 CLAUSES TYPE RSDS_WHERE OCCURS 5,
 TEXPR TYPE RSDS_TEXPR,
 TRANGE TYPE RSDS_TRANGE,
 END OF RSDS_TYPE.
DATA DYN_SEL TYPE RSDS_TYPE.
The object DYN_SEL thus contains a component ( CLAUSES ) which is an internal table. Each line of this internal table contains a table name ( TABLENAME ) and another table ( WHERE_TAB ) which contains the WHERE clauses for the table ( TABLENAME ).
You can find the structure of the other components in the type pool RSDS .
TEXPR contains the selections in a format which allows storage and can be used for the "freely callable" function modules when entering dynamic selections ( FREE_SELECTIONS_INIT , FREE_SELECTIONS_DIALOG ). TRANGE contains the selections in the form of RANGES tables which can be used with the IN operator in SELECT , CHECK and IF .
Note
Neither the TYPE-POOL RSDS nor the declaration of DYN_SEL must appear in the database program. Both are automatically included by the system.
In the database program SAPDBldb , an access to a table XXXX could look something like below:
FORM PUT_XXXX.
DATA L_DS_CLAUSES TYPE RSDS_WHERE.
MOVE 'XXXX' TO L_DS_CLAUSES-TABLENAME.
READ TABLE DYN_SEL-CLAUSES WITH KEY L_DS_CLAUSES-TABLENAME
 INTO L_DS_CLAUSES.
SELECT * FROM XXXX
 WHERE field1 IN ...
 AND field2 ....
 AND (L_DS_CLAUSES-WHERE_TAB).
 PUT XXXX.
ENDSELECT.
ENDFORM.
Note
If the table L_DS_CLAUSES-WHERE_TAB is empty, i.e. if no dynamic selections are entered for the table XXXX , the addition ... AND (L_DS_CLAUSES-WHERE_TAB) is ignored during the SELECT .
Variant 15
SELECTION-SCREEN FIELD SELECTION FOR TABLE dbtab.
Addition
... ID id
Effect
This variant is allowed only in the database include program DBldbSEL . It informs you for which logical database tables field selection is supported.
For these tables, you can fill just those database fields which the report actually needs. In the report, you determine these fields with GET dbtab FIELDS f1 ... fn or GET dbtab LATE FIELDS f1 ... fn (the field list is then supplemented by the key fields of the table dbtab ).
By restricting to the really necessary field, you considerably improve performance. The database access program SAPDBldb receives the desired fields for the dynamic field selection in the form of an internal table SELECT_FIELDS .
Note
The exact definition of the object SELECT_FIELDS is stored in the TYPE-POOL RSFS and looks something like below:
TYPES: BEGIN OF RSFS_TAB_FIELDS,
 TABLENAME LIKE RSDSTABS-PRIM_TAB,
 FIELDS LIKE RSFS_STRUC OCCURS 10,
 END OF RSFS_TAB_FIELDS.
TYPES: RSFS_FIELDS TYPE RSFS_TAB_FIELDS OCCURS 10.
DATA SELECT_FIELDS TYPE RSFS_FIELDS.
SELECT_FIELDS is thus an internal table. Each line of this internal table contains a table name ( TABLENAME ) and another internal table ( FIELDS ) which contains the desired fields of the table ( TABLENAME ).
Note
Neither the TYPE-POOL RSFS nor the declaration of SELECT_FIELDS has to appear in the database program. Both are automatically included by the system. Unlike the objects connected with the addition DYNAMIC SELECTIONS , SELECT_FIELDS is also available in the report.
In the database program SAPDBldb , an access to a table XXXX could look something like below:
FORM PUT_XXXX.
DATA L_TAB_FIELDS TYPE RSFS_TAB_FIELDS.
MOVE 'XXXX' TO L_TAB_FIELDS-TABLENAME.
READ TABLE SELECT_FIELDS WITH KEY L_TAB_FIELDS-TABLENAME
 INTO L_TAB_FIELDS.
SELECT (L_TAB_FIELDS-FIELDS)
 INTO CORRESPONDING FIELDS OF XXXX
 FROM XXXX
 WHERE field1 IN ...
 AND field2 ....
 PUT XXXX.
ENDSELECT.
ENDFORM.
Note
If the table L_TAB_FIEDLS is empty, i.e. if no dynamic selections are entered for the table XXXX , SELECT (L_TAB_FIELDS) ... works like SELECT * ... , i.e. all fields of the table XXXX are filled.
The internal table SELECT_FIELDS already contains values when the routine INIT is executed in the database program or when the INITIALIZATION processing is executed in the report. It can be manipulated by the appropriate program if it is absolutely necessary to fill another field for the logical database.
Regards
Sreeni

Regarding Selection Screen field making display field in ALV report

Hi All,
In ALV Report, at runtime how can i make the field as Display Field in selection screen .
Thks & Regds
Shailesh

hii,
Go to se38 and give the below progra name execute.... check the source code it is very easy to understand.
1.demo_dynpro_modify_simple
2.demo_dynpro_modify_screen
if tou are using grid,u can refer to foll link
sequencing / choosing fields in report screen at runtime,
Display the Columns in the grid at run time
rgrds,
Shweta

Help Needed in At selection screen output

Hi Experts,
I need your help in AT SELECTION SCREEN OUTPUT event. My issue is i have 4 radio button and with each radio button couple of parameters that need to be filled in selection screen of report. My requirement is that sometimes user enters details in second radio button parameters but forgot to change the radio button to second one so kindly suggest a solution so that radio button gets selected as per user input in parameter like if user clicks on certain parameter to enter value then automatically corresponding radio button gets selected.
Thanks in advance for all your help.

example from a checkbox in one of my progs..but you can do same approach with radio butts
parameters p_test as checkbox default abap_on user-command test.
at selection-screen.
    if sy-ucomm = 'TEST'.
      perform birth_mnth_chck.
    endif.

Complex selection screen

Similar Messages

Maybe you are looking for