Alv for parameters on selection screen

hi friends,
what i need is some sample of an selection screen with an alv where i can add lines ( e.g. for fields ) to and the information is then stored to internal table so that it can be used for further steps...how could i do that the best way ? any ideas ?
Clemens

Hi,
Check the program "BCALV_EDIT_01"
there is an option of CREATE entries which can be used to create a record which is captured in the internal table for further processing.
Cheers
VJ

Similar Messages

How to define f4 help for parameters in selection screen.

Hi Folks,
I have declared parametrs of type RLGRAP-FILENAME and i want to select the path for the application server file by pressing f4 during run time , not like typing the path in the field input. Pls help me how to do that.
Thanks in advance.
Regards
Rajesh

Hai Rajesh
DATA: I_FILETABLE TYPE FILETABLE,
 V_RC TYPE I.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. "local file with contracts
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
 EXPORTING
 WINDOW_TITLE = 'Find File'
 DEFAULT_EXTENSION = 'C:\'
 DEFAULT_FILENAME = ''
 FILE_FILTER = ',..'
 INITIAL_DIRECTORY =
 MULTISELECTION =
 WITH_ENCODING =
CHANGING
 FILE_TABLE = I_FILETABLE
 RC = V_RC
 USER_ACTION =
 FILE_ENCODING =
EXCEPTIONS
 FILE_OPEN_DIALOG_FAILED = 1
 CNTL_ERROR = 2
 ERROR_NO_GUI = 3
 NOT_SUPPORTED_BY_GUI = 4
 others = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE I_FILETABLE INTO P_FILE INDEX 1.
Thanks & regards
Sreenivasulu P

F4 help for file on selection screen thro objects

Hi Every one,
this report is working , but as i am working ECC6.0 it is showing the obsolete statements
how to rectify it .
pls anybody let me know,
tables rlgrap.
TYPES : BEGIN OF TAB,
MATNR TYPE MATNR ,
MTART TYPE MTART,
END OF TAB.
DATA : ITAB TYPE STANDARD TABLE OF TAB ,
 WTAB TYPE TAB.
data: it_tab type filetable,
 gd_subrc type i.
data : file0 type string.
selection-screen begin of block m with frame.
 select-options: so_fpath for rlgrap-filename.
selection-screen end of block m.
data wfile like line of so_fpath.
at selection-screen on value-request for so_fpath-low.
REFRESH: it_tab.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
 EXPORTING
 WINDOW_TITLE = 'Select File'
 DEFAULT_FILENAME = '*.txt'
 MULTISELECTION = 'X'
 CHANGING
 FILE_TABLE = it_tab
 RC = gd_subrc.
loop at it_tab into so_fpath-low.
 so_fpath-sign = 'I'.
 so_fpath-option = 'EQ'.
 append so_fpath.
endloop.
move so_fpath+3 to file0.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME = FILE0
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
TABLES
 DATA_TAB = Itab
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
end-of-selection.
write :/ file0.
loop at itab into wtab.
write :/ wtab-matnr.
endloop.
its urgent please...

See the below ex:change file parameter type .
DATA: VFILE TYPE STRING.
DATA: FL(1).
DATA: L_FILETAB TYPE FILETABLE,
 L_FILETAB_H TYPE FILETABLE WITH HEADER LINE,
 INITIAL_DIR_PATH TYPE STRING,
 L_RC TYPE I.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
*PARAMETERS: FNAME LIKE RLGRAP-FILENAME OBLIGATORY.
PARAMETERS: FNAME TYPE LOCALFILE OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FNAME.
REFRESH L_FILETAB.
INITIAL_DIR_PATH = 'C:\'.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
 EXPORTING
 WINDOW_TITLE = 'Select the Asset Master Data file'
 DEFAULT_EXTENSION =
 DEFAULT_FILENAME =
 FILE_FILTER = 'Text Files (.TXT)|.TXT|'
 INITIAL_DIRECTORY = INITIAL_DIR_PATH
 MULTISELECTION = SPACE
 WITH_ENCODING =
 CHANGING
 FILE_TABLE = L_FILETAB
 RC = L_RC
 USER_ACTION =
 FILE_ENCODING =
 EXCEPTIONS
 FILE_OPEN_DIALOG_FAILED = 1
 CNTL_ERROR = 2
 ERROR_NO_GUI = 3
 NOT_SUPPORTED_BY_GUI = 4
 OTHERS = 5
IF SY-SUBRC <> 0.
 WRITE:/ 'Error while selecting the input file'.
ELSE.
 LOOP AT L_FILETAB INTO L_FILETAB_H.
 FNAME = L_FILETAB_H-FILENAME.
 EXIT.
 ENDLOOP.
ENDIF.
FILE = FNAME.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = VFILE
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
 DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
IMPORTING
FILELENGTH =
HEADER =
 TABLES
 DATA_TAB = I_TAB
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

How can i set dynamice for week on Selection screen..pls help me..Urgent

Hi..All
please Help me .. i am very confused..
i need to set a varient for week which is dynamic on selection screen.
b) Week from current week to current week + 2. (Dynamic selection)how can i set dynamice for week on Selection screen,,
how can i do this..i am alrady set dynamice variant for Date.. there is option for D.. but in case of week there is a no option.
pls help me..urgent
thamks in advance.
mayukh

Hi,
I think the way out is use the dynamic select option while setting up the varinat and use sy-datum to sy-datum+9 which should essentially serve the purpose.
While saving the variant, for that particular date field check the Selection variable checkbox, then Choose D
option and then choose current days + or - option from there.
Rgds,
HR

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 Can i SEt Dynamic Variant For WEEK on SELECTION Screen.pls help me..

Hi ALL..
Pls Help Me for this Problem..i am very confused how can i do that...plese tell me proper process..
i want set Dynamice Varient for WEEK on Selection screen..
I have ALrady SET Dynamice Varient for DATE on Selection Screen.ther isd option is D...but in case of WEEK there is a no option...
Plese help me..
thaks in advance..
pls help me..

Hello,
Define your select-option in TVARV (assume Z_THISWEEK). And use a program like:
DATA:
zlv_week TYPE KWEEK.
call function 'DATE_GET_WEEK'
 exporting date = syst-datum
 importing week = zlv_week.
SELECT SINGLE *
 FROM tvarvc
 WHERE name = 'Z_THISWEEK'
 AND type = 'S'
 AND numb = '0000'.
tvarvc-low = zlv_week.
IF syst-subrc <> 0.
 tvarvc-name = 'Z_THISWEEK'.
 tvarvc-type = 'S'.
 tvarvc-opti = 'EQ'.
 tvarvc-sign = 'I'.
 tvarvc-numb = '0000'.
 insert tvarvc.
ELSE.
update tvarc.
ENDIF.
Regards,
John.

How to adjust mouse or trackpad parameters for the user selection screen?

This is not critical, but annoying. I can change the mouse or trackpad parameters by user, so anyone can use their own mouse or trackpad adjustment. However I can not locate how to change this parameters for the welcome or user selection screen. In my case I have two users, both of us use the trackpad with the one touch for click function, so no one press physically the trackpad for a click. However, as the default parameter is the touch function deactivated we have to actually click the trackpad in that exclusive screen.
Another example with mouse, normally we use the mouse with almost double of the default acceleration, but when in the user selection screen the mouse assumes default configuration and feels super SLOWWWWWWW.
Again, this is not critical, but would be very nice to be able to modify this parameters in the welcome screen.
Tyrone Carrion

For the login screen, you are not associated with a normal user, but the system defaults...try logging in to the Admn account and change the behavior there...those settings should then apply to the login screen.

From ALV output list to selection screen

Hi,
I created one ALV report.
After executing the program, it displays an ALV list.
When I click on the back/exit/cancel buttons on the screen, it should take me to the selection screen.
But that is not happening. it is taking to one screen which shows the report heading. IF i click back/cancel/exit buttons in this screen, it is taking me to the selection screen.
I checked the program for any write statement, but therre are no write statements.
Even i tried to remove the end-of-selection event in the program. but not working.
Can any one help me on this how to overcome this issue.
Thank you.
Kumar

hi check this example...
REPORT zalv_sel_screen .TABLES: mara.DATA: BEGIN OF i_alv OCCURS 0,
      matnr TYPE mara-matnr,
      mtart TYPE mara-mtart,
      matkl TYPE mara-matkl,
      groes TYPE mara-groes,
      maktx TYPE makt-maktx,
      END OF i_alv.DATA: alv_container TYPE REF TO cl_gui_docking_container.
DATA: alv_grid       TYPE REF TO cl_gui_alv_grid.
DATA: layout    TYPE lvc_s_layo.
DATA: fieldcat TYPE lvc_t_fcat.PARAMETERS: p_check.INITIALIZATION. PERFORM get_data.AT SELECTION-SCREEN OUTPUT. DATA: variant TYPE disvariant.
DATA: repid TYPE sy-repid. repid = sy-repid. variant-report = sy-repid.
variant-username = sy-uname. layout-zebra = 'X'.
layout-edit_mode = 'X'. CHECK alv_container IS INITIAL. CREATE OBJECT alv_container
              EXPORTING repid     = repid
                        dynnr     = sy-dynnr
                        side      = alv_container->dock_at_left
                        extension = 1500. CREATE OBJECT alv_grid
         EXPORTING
               i_parent          = alv_container.* ALV Specific. Data selection.
Populate Field Catalog
PERFORM get_fieldcatalog. CALL METHOD alv_grid->set_table_for_first_display
    EXPORTING
      is_layout        = layout
      is_variant       = variant
      i_save           = 'U'
      i_structure_name = 'I_ALV'
    CHANGING
      it_outtab        = i_alv[]
      it_fieldcatalog = fieldcat[].
START-OF-SELECTION.
FORM GET_DATA
FORM get_data. SELECT * INTO CORRESPONDING FIELDS OF TABLE i_alv
        FROM mara
          INNER JOIN makt
            ON maramatnr = maktmatnr
                   UP TO 100 ROWS
               WHERE makt~spras = sy-langu. SORT i_alv ASCENDING BY matnr.ENDFORM.                    "get_data***************************************************************
     Form Get_Fieldcatalog - Set Up Columns/Headers
FORM get_fieldcatalog. DATA: ls_fcat TYPE lvc_s_fcat.
REFRESH: fieldcat. CLEAR: ls_fcat.
ls_fcat-reptext    = 'Material Number'.
ls_fcat-fieldname = 'MATNR'.
ls_fcat-ref_table = 'I_ALV'.
ls_fcat-outputlen = '18'.
ls_fcat-fix_column = 'X'.
ls_fcat-key        = 'X'.
ls_fcat-col_pos    = '1'.
APPEND ls_fcat TO fieldcat. CLEAR: ls_fcat.
ls_fcat-reptext    = 'Material Type'.
ls_fcat-fieldname = 'MTART'.
ls_fcat-ref_table = 'I_ALV'.
ls_fcat-outputlen = '10'.
ls_fcat-fix_column = 'X'.
ls_fcat-key        = 'X'.
ls_fcat-col_pos    = '2'.
APPEND ls_fcat TO fieldcat. CLEAR: ls_fcat.
ls_fcat-reptext    = 'Material Group'.
ls_fcat-fieldname = 'MATKL'.
ls_fcat-ref_table = 'I_ALV'.
ls_fcat-outputlen = '12'.
ls_fcat-col_pos    = '3'.
APPEND ls_fcat TO fieldcat. CLEAR: ls_fcat.
ls_fcat-reptext    = 'Size'.
ls_fcat-fieldname = 'GROES'.
ls_fcat-ref_table = 'I_ALV'.
ls_fcat-outputlen = '30'. ls_fcat-col_pos    = '4'.
APPEND ls_fcat TO fieldcat. CLEAR: ls_fcat.
ls_fcat-reptext    = 'Material Description'.
ls_fcat-fieldname = 'MAKTX'.
ls_fcat-ref_table = 'I_ALV'.
ls_fcat-outputlen = '40'. ls_fcat-col_pos    = '5'.
APPEND ls_fcat TO fieldcat.ENDFORM.                    "get_fieldcatalog
regards,
venkat

Alv Output after dynamic selection screen

Hi Guys
I have coded a dynamic selection screen (shown below). I want to create an ALV report based on what the user enters in the selection screen. Is the right way of doing this to code an IF s_matnr is not initial statement then call all the subroutines for output of material data and then else call a second batch of subroutines for billing data. It seems a bit long winded to me but I haven't been able to find anything on google that clearly explains the approach.
REPORT ZTREVOR_DYNAMIC_ALV_MAKT_VBRP.
TABLES : makt,
marc,
t001w,
vbrk,
vbrp.
CONSTANTS : c_yes TYPE c VALUE '1',
c_no TYPE c VALUE '0'.
Selection-screen begin of block b1 with frame title text-sc1.
PARAMETERS : p_opt1 TYPE c RADIOBUTTON GROUP radi USER-COMMAND op1, "Material
p_opt2 TYPE c RADIOBUTTON GROUP radi. "Billing Document
Selection-screen end of block b1.
Selection-screen begin of block b2 with frame title text-sc2.
SELECT-OPTIONS : s_matnr FOR makt-matnr MODIF ID op1, "Material
s_vbeln FOR vbrp-vbeln MODIF ID op2. "Billing Document
Selection-screen end of block b2.
T SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN .
IF screen-group1 = 'OP1' .
IF p_opt1 = 'X' .
screen-invisible = c_no .
screen-active = c_yes .
ELSE.
screen-invisible = c_yes .
screen-active = c_no .
ENDIF.
MODIFY SCREEN .
ENDIF.
IF screen-group1 = 'OP2' .
IF p_opt2 = 'X' .
screen-invisible = c_no .
screen-active = c_yes .
ELSE.
screen-invisible = c_yes .
screen-active = c_no .
ENDIF.
MODIFY SCREEN .
ENDIF.
ENDLOOP.

Hi,
First of all, you should check your radiobutton instead of select-option...
Then you will have to build the output internal table dynamically based on the option chosen. There are lot of example on SDN...
Here is a start: http://wiki.sdn.sap.com/wiki/display/Snippets/Tutorialabap-CodeforDynamicAlv+grid
Kr,
m.

ALV + layout varient on selection screen

hiii
with ALV list i want to know with how to allow to put the layout on the selection screen and when user press F4 he will be able to use the list of layout he has save on the ALV output
Note for the layout button to appear i had to activate shown below:
i_save                   = c_x
please give me sample code where user can choose layout on selection screen and this layout will be used to display on ALV

Hi,
Please refer the code below for layout variants :
DATA:   gt_rsparams TYPE TABLE OF rsparams.
* Data for ALV variant
DATA gv_repname          LIKE sy-repid.
DATA gv_x_variant        LIKE disvariant.
DATA gv_exit(1)          TYPE c.
DATA gv_save(1)          TYPE c.
DATA gv_variant          LIKE disvariant.
PARAMETERS: sp_vari LIKE disvariant-variant.        "Dispaly Variant
INITIALIZATION.
gv_repname = sy-repid.
REFRESH : gt_glacct,
            gr_rcomp,
            gt_output,
            gt_fieldcat,
            gt_sort.
* Initialize ALV Layout variant
PERFORM f_initialize_variant.
FORM f_initialize_variant .
CLEAR gv_variant.
gv_save           = 'X'.
gv_variant-report = gv_repname.
gv_x_variant      = gv_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = gv_save
    CHANGING
      cs_variant = gv_x_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    sp_vari = gv_x_variant-variant.
ENDIF.
ENDFORM.                    " f_initialize_variant
AT SELECTION-SCREEN ON VALUE-REQUEST FOR sp_vari.
PERFORM f_f4_for_variant.
FORM f_f4_for_variant .
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = gv_variant
      i_save     = gv_save
    IMPORTING
      e_exit     = gv_exit
      es_variant = gv_x_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    IF gv_exit = space.
      sp_vari = gv_x_variant-variant.
    ENDIF.
ENDIF.
ENDFORM.                    " f_f4_for_variant
AT SELECTION-SCREEN.
* Validating selection screen fields
PERFORM f_at_selection_screen.
FORM f_at_selection_screen .
* ALV Layout variant
IF NOT sp_vari IS INITIAL.
    MOVE gv_variant TO gv_x_variant.
    MOVE sp_vari    TO gv_x_variant-variant.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        i_save     = gv_save
      CHANGING
        cs_variant = gv_x_variant.
    gv_variant = gv_x_variant.
ELSE.
    PERFORM f_initialize_variant.
ENDIF.
FORM f_initialize_variant .
CLEAR gv_variant.
gv_save           = 'X'.
gv_variant-report = gv_repname.
gv_x_variant      = gv_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = gv_save
    CHANGING
      cs_variant = gv_x_variant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    sp_vari = gv_x_variant-variant.
ENDIF.
ENDFORM.                    " f_initialize_variant
Thanks,
Sriram POnna.

How to create a F4 help for a report selection screen field

hi,
can any one guide me to create F4 help for a field in a selection screen in a report program,plz give me a sample code

hi,
Here are the following ways
1.with the help of match code objects we can create the F4 Functionality for Field.
Syntax is :
PARAMETERS: p_org LIKE t527x-orgeh MATCHCODE OBJECT zorg.
2. One more thing is we can do it with Search Help's also.
3. Even we can do it HELP Views also.
Help Views:
You have to create a help view if a view with outer join is needed as selection method of a search help
The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.
All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here. The first table to be inserted in the help view is called the primary table of the help view. The tables added to this primary table with foreign keys are called secondary tables.
The functionality of a help view has changed significantly between Release 3.0 and Release 4.0. In Release 3.0, a help view was automatically displayed for the input help (F4 help) for all the fields that were checked against the primary table of the help view. This is no longer the case in Release 4.0.
As of Release 4.0, you must explicitly create a search help that must be linked with the fields for which it is offered (see Linking Search Helps with Screen Fields ).
Existing help views are automatically migrated to search helps when you upgrade to a release higher than 4.0.
A help view implements an outer join, i.e. all the contents of the primary table of the help view are always displayed. You therefore should not formulate a selection condition for fields in one of the secondary tables of the help view. If records of these secondary tables cannot be read as a result of this selection condition, the contents of the corresponding fields of the secondary table are displayed with initial value.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 15, 2008 3:15 PM

How to get rid of the loop in ALV output from At selection screen event?

I have several push buttons on a selection screen.
Clikc on a button, then it pops up an editable ALV report. (This gets triggered AT SELECTION SCREEN event.). REUSE_ALV_GRID_DISPLAY_LVC..
On the ALV output, I enabled F4 for a couple of fields. Once I click on the F4 button, ONF4 method gets triggerd and a pop up appears with custom search helps.
choose a line and it fills the cell.
Upto this it works fine.
Now I click on the BACK button at the ALV output, it takes me to the selection screen. I click on the button again, it show the editable ALV. Now when I click on the F4 button, the pop up comes up twice and the cell gets filled from the second pop - up.
How to control this?
Probably I am not refreshing something?
(I am using REUSE_ALV_GRID_DISPLAY_LVC and tooks ome code for ONF4 event from BCALV_*DATATYPES (forgot the exact name) program.)
Thanks,
Ven

Hi,
FORM refresh_grid USING pw_grid TYPE REF TO cl_gui_alv_grid.
*Work area
DATA : wal_stable TYPE lvc_s_stbl.
CHECK NOT pw_grid IS INITIAL.
wal_stable-col = c_check.
wal_stable-row = c_check.
*Method to refresh grid
CALL METHOD pw_grid->refresh_table_display
       EXPORTING
         is_stable      = wal_stable
         i_soft_refresh = c_check
       EXCEPTIONS
         finished       = 1
         OTHERS         = 2.
ENDFORM.                    " refresh_grid
Thanks,
Sree.

To Load ALV Layout in report selection screen

Hi...
I want the selection screen option for user so that he can select any of the saved layouts.
I have done some coding after refering to some threads in here.But I can't proceed further...plz help
selection screen
SELECTION-SCREEN BEGIN OF BLOCK 006 WITH FRAME TITLE text-006.
PARAMETERS: p_layout LIKE disvariant-variant. " layout
SELECTION-SCREEN END OF BLOCK 006.
data declarations
DATA: wa_variant TYPE disvariant.
DATA: w_variant_save TYPE c VALUE 'A'.
DATA: gs_variant TYPE disvariant.
DATA: gs_layout TYPE lvc_s_layo.
DATA: g_repid LIKE sy-repid.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_layout.
PERFORM variant_input_help.
FORM variant_input_help .
DATA: tl_dynpfields TYPE TABLE OF dynpread.
DATA: wl_exit TYPE c.
DATA: wal_variant LIKE wa_variant.
DATA: wal_dynpfields TYPE dynpread.
Get values from the selection screen to determine layout set
wal_dynpfields-fieldname = p_layout.
APPEND wal_dynpfields TO tl_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
 DYNAME = sy-cprog
 DYNUMB = '1000'
TRANSLATE_TO_UPPER = ' '
REQUEST = ' '
PERFORM_CONVERSION_EXITS = ' '
PERFORM_INPUT_CONVERSION = ' '
DETERMINE_LOOP_INDEX = ' '
TABLES
 DYNPFIELDS = tl_dynpfields
EXCEPTIONS
INVALID_ABAPWORKAREA = 1
INVALID_DYNPROFIELD = 2
INVALID_DYNPRONAME = 3
INVALID_DYNPRONUMMER = 4
INVALID_REQUEST = 5
NO_FIELDDESCRIPTION = 6
INVALID_PARAMETER = 7
UNDEFIND_ERROR = 8
DOUBLE_CONVERSION = 9
STEPL_NOT_FOUND = 10
OTHERS = 11
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT tl_dynpfields INTO wal_dynpfields.
 CASE wal_dynpfields-fieldname.
 WHEN 'p_layout'.
 wa_variant-variant = wal_dynpfields-fieldvalue.
 ENDCASE.
ENDLOOP.
wa_variant-report = sy-repid.
wa_variant-variant = p_layout.
wa_variant-username = sy-uname.
**Invoke function to provide drop down entries
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
 EXPORTING
 IS_VARIANT = wa_variant
 I_TABNAME_HEADER =
 I_TABNAME_ITEM =
 IT_DEFAULT_FIELDCAT =
 I_SAVE = w_variant_save
 I_DISPLAY_VIA_GRID = ' '
 IMPORTING
 E_EXIT = wl_exit
 ES_VARIANT = wal_variant
 EXCEPTIONS
 NOT_FOUND = 1
 PROGRAM_ERROR = 2
 OTHERS = 3
IF SY-SUBRC IS INITIAL.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
 IF wl_exit IS INITIAL.
 p_layout = wal_variant-variant.
 ENDIF.
ELSE.
 message I033 WITH TEXT-034.
ENDIF.
*gs_variant-variant = p_layout.
*gs_variant-report = sy-repid.
FREE: tl_dynpfields.
g_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_INTERFACE_CHECK = ' '
 I_BYPASSING_BUFFER = ' '
 I_BUFFER_ACTIVE = ' '
 I_CALLBACK_PROGRAM = g_repid
 I_CALLBACK_PF_STATUS_SET = ' '
 I_CALLBACK_USER_COMMAND = ' '
 I_CALLBACK_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_END_OF_LIST = ' '
 I_STRUCTURE_NAME =
 I_BACKGROUND_ID = ' '
 I_GRID_TITLE =
 I_GRID_SETTINGS =
 IS_LAYOUT = ??
 IT_FIELDCAT = ??
 IT_EXCLUDING =
 IT_SPECIAL_GROUPS =
 IT_SORT =
 IT_FILTER =
 IS_SEL_HIDE =
 I_DEFAULT = 'X'
 I_SAVE = ' '
 IS_VARIANT = wal_variant
 IT_EVENTS =
 IT_EVENT_EXIT =
 IS_PRINT =
 IS_REPREP_ID =
 I_SCREEN_START_COLUMN = 0
 I_SCREEN_START_LINE = 0
 I_SCREEN_END_COLUMN = 0
 I_SCREEN_END_LINE = 0
 I_HTML_HEIGHT_TOP = 0
 I_HTML_HEIGHT_END = 0
 IT_ALV_GRAPHICS =
 IT_HYPERLINK =
 IT_ADD_FIELDCAT =
 IT_EXCEPT_QINFO =
 IR_SALV_FULLSCREEN_ADAPTER =
IMPORTING
 E_EXIT_CAUSED_BY_CALLER =
 ES_EXIT_CAUSED_BY_USER =
 TABLES
 T_OUTTAB = ??
EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " variant_input_help
wat steps shud i take

Hi ,
I have used the below FM for layout help,
data: gs_variant like disvariant,
gs_variant-report = sy-repid.
 call function 'REUSE_ALV_VARIANT_F4'
 exporting
 is_variant = gs_variant
 i_save = 'A'
 i_display_via_grid = 'X'
 importing
 es_variant = gs_variant
 exceptions
 not_found = 1
 program_error = 2
 others = 3
 if sy-subrc = 0.
 pa_var = gs_variant-variant.
 endif.
Note pa_var is your select options field in the SELECTION SCREEN,
call function 'REUSE_ALV_GRID_DISPLAY' "
 exporting
 i_bypassing_buffer = 'X'
 i_buffer_active = 'X'
 i_callback_program = sy-repid
 i_callback_top_of_page = 'TOP_OF_PAGE'
 is_layout = gs_layout
 it_fieldcat = gt_fieldcat
 i_save = 'A'
 is_variant = gs_variant
 it_events = gt_events
 tables
 t_outtab = gt_output
 exceptions
 program_error = 1
 others = 2
hope this helps you.
Regards,
Raghavendra

Radio buttons & Parameters in Selection Screen...

Hi all,
I have a case in Selection Screen :
There are 2 radio buttons(R1 & R2) and 4 parameters (P1, P2, P3, P4).
WHen i select R1 then P1 and P2 should become mandatory
when i select R2 then P1, P2, P3 & P4 should become mandatory.
I have coded it using LOOP AT SCREEN ...
So, by default R1 will be selected then P1, P2 will become mandatory. Now when i select R2, it gives an status message as 'FILL IN THE REQUIRED FIELDS' .....So how can i overcome this and be able to select R2 which enables P1, P2, P3,P4 as mandatory ?
Please provide some feasible solution. Thanks!

Hi Jayati,
Below is the code...i have used.
parameters : R1 radiobutton group rad modif id RAD user-command com,
R2 radiobutton group rad modif id RAD.
parameters : p1 type char10 modif id grp ,
p2 type char10 modif id grp ,
p3 type char10 modif id gr2,
p4 type char10 modif id gr2.
INITIALIZATION.
r1 = 'X'.
At selection-screen output.
if R1 = 'X'.
loop at screen.
if screen-group1 = 'GRP'.
screen-required = '1'.
modify screen.
endif.
if screen-group1 = 'GR2'.
screen-required = '0'.
modify screen.
endif.
endloop.
else.
loop at screen.
if screen-group1 = 'GRP'.
screen-required = '1'.
modify screen.
endif.
if screen-group1 = 'GR2'.
screen-required = '1'.
modify screen.
endif.
endloop.
endif.
Now while we execute this....R1 is selected by default...which enables P1 & P2 as mandatory. okay ? ...Now when i select R2 at this point of time. it says 'FILL IN ALL REQUIRED ENTRY FIELDS'. (and it shows only P1 & P2 as mandatory).
But the user don't want to fill P1 & P2. ...(just for selecting R2)..
Instead he wants R2 to get selected with the below
      a) Without entering values for P1 & P2
      b) WIthoug displaying any Error Meassage as 'FILL IN ALL REQUIRED ENTRY FIELDS'.
      c) P1 P2 P3 P4 should become mandatory
Hope u understood it now.

Path for Directory in Selection Screen

I have one field in selection screen Error log.
I have to pick path for dirctory in that parameter, so that I can save my error log there on that path.
how i can do it ?
F4 for the path is needed. how i will define that parameter in selection screen?

Hi
Check the below logic:
DATA :G_DIR1 TYPE STRING.
DATA : G_T_FILENAMES TYPE SETST_TYPE_STANDARD_TABLE,
 G_WA_FILES LIKE LINE OF G_T_FILENAMES.
PARAMETERS: P_FOLDER TYPE RLGRAP-FILENAME OBLIGATORY
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FOLDER.
PERFORM F1000_GET_DIR.
START-OF-SELECTION.
IF G_DIR IS INITIAL.
 G_DIR = P_FOLDER.
ENDIF.
PERFORM F1100_GET_FILENAMES USING G_DIR.
FORM F1000_GET_DIR .
CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_BROWSE
 EXPORTING
 WINDOW_TITLE = 'Folder for ADP Files'
 INITIAL_FOLDER = G_DIR1
 CHANGING
 SELECTED_FOLDER = G_DIR1
 EXCEPTIONS
 CNTL_ERROR = 1
 ERROR_NO_GUI = 2
 NOT_SUPPORTED_BY_GUI = 3
 OTHERS = 4.
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
 P_FOLDER = G_DIR1.
ENDIF.
ENDFORM.
FORM F1100_GET_FILENAMES USING P_DIR.
DATA : L_DIR TYPE STRING,
 L_COUNT TYPE I,
 L_COUNT1 TYPE I.
DATA : L_T_FILES TYPE SETST_TYPE_STANDARD_TABLE,
 WA_FILES LIKE LINE OF L_T_FILES.
L_DIR = P_DIR.
CLEAR : G_T_FILENAMES[], G_T_FILENAMES.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_LIST_FILES
 EXPORTING
 DIRECTORY = L_DIR
 FILTER = '.'
 FILES_ONLY =
 DIRECTORIES_ONLY =
 CHANGING
 FILE_TABLE = L_T_FILES
 COUNT = L_COUNT
 EXCEPTIONS
 CNTL_ERROR = 1
 DIRECTORY_LIST_FILES_FAILED = 2
 WRONG_PARAMETER = 3
 ERROR_NO_GUI = 4
 NOT_SUPPORTED_BY_GUI = 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.
G_T_FILENAMES[] = L_T_FILES[].
LOOP AT G_T_FILENAMES INTO G_WA_FILES.
 IF G_WA_FILES CS SY-DATUM.
 G_WA_FILES1 = G_WA_FILES.
 APPEND G_WA_FILES1 TO G_T_FILENAMES1.
 ENDIF.
ENDLOOP.
Regards,
Ravinder

Alv for parameters on selection screen

Similar Messages

Maybe you are looking for