About ALV report

Hi experts,
this is kalyan.
im new to this topic i.e,ALV.
according to my document i want the fields names of the fields with respect to their table names
the document is as below:
Invoice creation date
Invoice Type
Material
Customer
Name
Sales Order
Approved by
Product
Qty
COGS
Selling Price
Sales order
Invoice
i hope that the experts could help me.
regards,
kalyan.

goto se80
|
click on repository information system
|
expand ABAP Dictionary
|
expand fields
|
double click on table fields
on the right side of the screen enter the description of the field and press execute to find the tables where the field is present. once you get into one table you can know the others by clicking on the where used list.
Thats the way to search any fields!
regards,
srinivas
*reward for useful answers*

Similar Messages

Re : about ALV Reporting

hi all,
 what are the events in alv reporting?
Thanks in advance.

Hi there
If you read my post in the OO ABAP thread you should find an EASY way of generating your reports with all the functionality you need EDIT, Data entry, double click, create EXCEL spread sheet etc etc.
I can't seem to get the thread ID for a LINK but look for post entitled
For all users having probs with OO ALV Grid it's in the ABAP OBJECTS forum.
If you follow the steps outlined there you'll be able to generate complex reports very quickly with minimal code and you won't have to do all the tedious FCAT building etc etc.
The example there uses dynamic tables, and FCATS and the new RTTI (RunTime Information) functionality so your structure can be built FROM ANY ITAB --DDIC or not at run time.
Your application program will then only need to be about 1 or 2 pages long.
Copy the CLASS from that post and save it as an INCLUDE.
Here's just a taster to show you how easy it is.
This program reads 200 sales orders from VAPMA and displays it in a GRID
If you double click on a cell transaction VA02 is called. After you leav VA02 the GRID table is updated with a 'C' in the sales order line where you doyble clicked.
The Toolbar EXCEL will create an EXCEL spreadsheet directly with column headings etc where you can save the data as a file.
Do these 2 things first
Create a Blank Screen with a custom container on it called CCONTAINER 1. (SE51)
(optional) create a STATUS (SE41) so you can have the standard SAP toolbar at the top of the SAP screen .
Copy this program and the CLASS referred to in my post in the ABAP OBJECTS FORUM.
Program ZZORDERDISP.
DEFINE col_name.
read table it_fldcat into wa_it_fldcat index &1.
 wa_it_fldcat-coltext = &2.
 modify it_fldcat from wa_it_fldcat index &1.
END-OF-DEFINITION.
Jimbo 2007.
FIELD-SYMBOLS :
<fs1> TYPE ANY,
<fs2> TYPE STANDARD TABLE,
<fs3> TYPE ANY,
<field_catalog> TYPE STANDARD TABLE,
<dyn_table> TYPE STANDARD TABLE,
<orig_table> TYPE STANDARD TABLE,
<dyn_field>,
<dyn_wa>.
INCLUDE ZZJIMBOXX_INCL. ===> copy the CLASS definition
From my post in ABAP OBJECTS FORUM.
INCLUDE <icon>.
TABLES : VAPMA.
TYPES: BEGIN OF s_elements,
vbeln TYPE vapma-vbeln,
posnr TYPE vapma-posnr,
matnr TYPE vapma-matnr,
kunnr TYPE vapma-kunnr,
werks TYPE vapma-werks,
vkorg TYPE vapma-vkorg,
vkbur TYPE vapma-vkbur,
status TYPE c,
END OF s_elements.
DATA: z_object TYPE REF TO zcl_dog, "Instantiate our class
 grid_container1 TYPE REF TO cl_gui_custom_container,
 t_elements TYPE TABLE OF s_elements, "refers to our ITAB
 wa_elements TYPE s_elements,
 wa_dyn_table_line TYPE REF TO DATA,
 it_fldcat TYPE lvc_t_fcat,
 i_gridtitle TYPE lvc_title,
 wa_it_fldcat TYPE lvc_s_fcat,
 new_table TYPE REF TO DATA,
 dy_table TYPE REF TO data,
 dy_line TYPE REF TO data,
 row_id TYPE sy-index.
START-OF-SELECTION.
CALL SCREEN 100.
END-OF-SELECTION.
MODULE status_0100 OUTPUT.
break-point 2.
ASSIGN wa_elements TO <fs1>.
CREATE OBJECT z_object EXPORTING z_object = z_object.
CALL METHOD z_object->build_dynamic_structures
 CHANGING it_fldcat = it_fldcat.
Here before displaying you can change the field catalog to
adjust your own names
Method call just uses the names in the table structure.
 col_name 1 'Order Nr'.
 col_name 2 'Item'.
 col_name 3 'Material'.
 col_name 4 'Customer'.
 col_name 5 'Plant'.
 col_name 6 'Sales Org'.
 col_name 7 'Sales Office'.
 col_name 8 'Status'.
PERFORM populate_dynamic_itab.
CALL METHOD z_object->display_grid
 CHANGING it_fldcat = it_fldcat.
SET PF-STATUS '0001'.
SET TITLEBAR '000'.
ENDMODULE.
MODULE user_command_0100 INPUT.
CASE sy-ucomm.
 WHEN 'BACK'.
 LEAVE PROGRAM.
 WHEN 'EXIT'.
 LEAVE PROGRAM.
 WHEN 'RETURN'.
 LEAVE PROGRAM.
 WHEN OTHERS.
ENDCASE.
ENDMODULE.
FORM populate_dynamic_itab.
SELECT vbeln posnr matnr kunnr werks vkorg vkbur
 UP TO 200 rows
 FROM vapma
 INTO CORRESPONDING FIELDS OF TABLE <dyn_table>.
Populate Dynamic table and save a copy
create 2nd Dyn table to hold original data
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_fldcat
 IMPORTING
 ep_table = dy_table.
 ASSIGN dy_table->* TO <orig_table>.
CREATE DATA dy_line LIKE LINE OF <orig_table>.
ASSIGN dy_line->* TO <dyn_wa>.
<orig_table> = <dyn_table>.
ENDFORM.
FORM VERWERK.
break-point 1.
Orig table is in dynamic table <orig_table>
ALV GRID changed table is in <dyn_table>.
Loop at <orig_table> into <dyn_wa>.
Do what you want
end
endloop.
ENDFORM.
FORM refresh.
data: ord_nr TYPE vapma-vbeln.
READ TABLE <dyn_table> index row_id into wa_elements.
 ord_nr = wa_elements-vbeln.
set parameter id 'AUN' field ord_nr.
CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
wa_elements-status = 'C'.
modify <dyn_table> from wa_elements index row_id.
break-point 1.
CALL METHOD z_object->refresh_grid.
ENDFORM.
form dubbleklik using
 e_row type LVC_S_ROW
 e_column type LVC_S_col
 es_row_no type lvc_s_roid.
 break-point 1.
Get Row id into a variable for this program.
 row_id = e_row.
 SET TITLEBAR '001'.
 i_gridtitle = 'Grid Title Changed'.
 CALL METHOD z_object->change_title
 EXPORTING i_gridtitle = i_gridtitle.
 PERFORM refresh.
endform.
That's it --code exactly as shown and it will work --you can have a lot of fun with the toolbar options including the excel spread sheet creation without usiing GUI download or whatever.
Have fun -- and if you ever need to take more than about 5 mins to generate an ALV report in the future your Boss will be upset.
Cheers
Jimbo

ALV report - copy layout to another user

Hello,
I have a question about ALV reports.
In ALV we have option to select layout and save it by user-specific.
How to copy this layout to another user?
Is there some function/Bapi?
Thanks in advance,
Michal

Hi Michael,
Here are the steps I documented for managing this procedure:
First Step is to READ the Layout into the Program
 The parameters for the layout can be found in table LTDX
Goto SE37 and enter: LT_DBDATA_READ_FROM_LTDX
When (READ) you will input information for the following parameters:
Report Name
Handle
Log Group
User
Variant
Type
An example is shown below:
<screen shots didn't load in my response> email if you'd like the document with screen shots>
Execute.
Now our next step is to WRITE the information from the program into table: LTDX
While at the Function Builder Screen enter the new function module: LT_DBDATA_WRITE_TO_LTDX
When you (WRITE) you will input information for the following parameters:
Report Name
Handle
Log Group
User
Variant
Type
When completed, your input screen for (WRITE) should look like the screen below:
<screen shots didn't load in my response> email if you'd like the document with screen shots>
IMPORTANT When entering information for IS_VARKEY, remember to use the u201Cnew useru201D ID
When entering information for IS_VARIANT, remember to enter information exactly as found in table LTDX and remember that the parameter: DEPENDVARS may be needed to complete your entry
Now Execute the Function Module. When completed go to table: LTDX and confirm that your new entry has been added.
Pre Checklist:
1.) Capture entries (users) you want to copy from table: LTDX
2.) Make sure you have access to execute function modules/eCATT scripts
3.) Make sure you have table display access (needed to find and validate updates)
If you'd like the documentation with screen shots please reply with your email address.
Cheers,
Robert

Alv reports from scratch

i want to make some MM ALV REPORT please send me detail step by step or send me any detail document about alv report.
email address: [email protected]
mobile: 0569156323

Hi Ahmed,
Check these links.
http://www.geocities.com/mpioud/Abap_programs.html
http://www.sapdevelopment.co.uk/reporting/reportinghome.htm
Simple ALV report
http://www.sapgenie.com/abap/controls/alvgrid.htm
http://wiki.ittoolbox.com/index.php/Code:Ultimate_ALV_table_toolbox
Regards,
Priyanka.

About double click event in ALV report

Hi all,
I want to program a double-click event in ALV reprot.
I am not suppose to use module pool approach for the same.
If a user double clicks on the any of the row of ALV report, the transaction should get called.
Again, I am using function 'REUSE_ALV_GRID_DISPLAY' for displaying ALV.
Can you please help me to solve this?
Thanks,
-Siddhi

Hi Sidhi,
You can do it easily by using Reuse_ALV_GRID_DISPALY.
The User Command subroutine which you pass to this function module in that you can check which field is selected and what is the value of that and also you can get the table index.
I am giving you a code example where interactivity of ALV report is done .
*& Report ZRAIL_LOT_REPORT
REPORT zrail_lot_report.
TABLES :qals,aufk.
TYPE-POOLS:slis.
TYPES:BEGIN OF x_lot,
 sel(1) TYPE c, "SELECTION
 prueflos TYPE qals-prueflos, "INSPECTION LOT NUMBER
 werk TYPE qals-werk, "PLANT
 losmenge TYPE qals-losmenge, "LOT QUANTITY
 mengeneinh TYPE qals-mengeneinh, "BASE UNIT OF MEASURE FOR THE INSPECTION LOT QUANTITY
 matnr TYPE qals-matnr, " MATERIAL NO. ATTACHED TO ORDER
 zzequnr TYPE qals-zzequnr, "EQUIPMENT NO.
 zzassembly TYPE qals-zzassembly, "ASSEMBLY
 herkunft TYPE qals-herkunft, "INSPECTION LOT ORIGIN
 aufnr TYPE qals-aufnr, "ORDER NO.
 sttxt TYPE qals_d02-sttxt, "LOT STATUS
 objnr TYPE qals-objnr, "OBJECT NUMBER
 enstehdat TYPE qals-enstehdat, "lot creation date
 pruefer TYPE qamr-pruefer, "Name of the Inspector
 END OF x_lot.
TYPES:BEGIN OF x_ordmat,
 aufnr TYPE aufk-aufnr, "Order No.
 equnr TYPE afih-equnr, "Equipment No. attached to Order
 zmatnr TYPE aufk-zmatnr, "Material No. attached to Order
 bautl TYPE afih-bautl, "Assembly attached to Order
 END OF x_ordmat.
TYPES:BEGIN OF x_status,
 objnr TYPE jest-objnr,
 stat TYPE jest-stat,
 txt04 TYPE tj02t-txt04,
 END OF x_status.
DATA:it_qals TYPE STANDARD TABLE OF x_lot,
 wa_qals TYPE x_lot.
DATA:it_ordmat TYPE TABLE OF x_ordmat,
 wa_ordmat TYPE x_ordmat.
DATA:it_status TYPE STANDARD TABLE OF x_status,
 wa_status TYPE x_status.
DATA:mytabix TYPE sy-tabix.
DATA: wa_layout TYPE slis_layout_alv,
 wa_fieldcat TYPE slis_fieldcat_alv,
 it_fieldcat TYPE TABLE OF slis_fieldcat_alv,
 it_fcat TYPE TABLE OF slis_fieldcat_alv.
DATA:mytabix1 TYPE sy-tabix.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_werks FOR qals-werk,
 s_zmatnr FOR aufk-zmatnr,
 s_assbly FOR qals-zzassembly,
 s_equnr FOR qals-zzequnr,
 s_lotor FOR qals-herkunft,
 s_lotdat FOR qals-enstehdat.
SELECTION-SCREEN END OF BLOCK b1.
INITIALIZATION.
s_lotdat-low = sy-datum - 7.
s_lotdat-high = sy-datum.
APPEND s_lotdat.
START-OF-SELECTION.
PERFORM get_data_qals.
PERFORM build_fieldcat.
PERFORM display_data.
EXIT.
END-OF-SELECTION.
*& Form get_data_qals
 text
--> p1 text
<-- p2 text
FORM get_data_qals .
IF it_qals[] IS INITIAL.
 SELECT a~prueflos
 a~werk
 a~losmenge
 a~mengeneinh
 a~zzequnr
 a~zzassembly
 a~herkunft
 a~aufnr
 a~objnr
 a~matnr
 a~enstehdat
 b~pruefer
 FROM qals AS a INNER JOIN qamr AS b
 ON aprueflos = bprueflos
 INTO CORRESPONDING FIELDS OF TABLE it_qals
 WHERE werk IN s_werks
 AND zzassembly IN s_assbly
 AND zzequnr IN s_equnr
 AND herkunft IN s_lotor
 AND enstehdat IN s_lotdat.
ENDIF.
IF it_ordmat[] IS INITIAL.
 SELECT a~aufnr
 a~zmatnr
 b~bautl
 b~equnr
 FROM aufk AS a INNER JOIN afih AS b
 ON aaufnr = baufnr
 INTO CORRESPONDING FIELDS OF TABLE it_ordmat FOR ALL ENTRIES IN it_qals
 WHERE a~aufnr = it_qals-aufnr
 AND zmatnr IN s_zmatnr.
ENDIF.
IF it_status[] IS INITIAL.
 SELECT a~objnr
 a~stat
 b~txt04
 FROM tj02t AS b
 INNER JOIN jest AS a ON bistat = astat
 INTO CORRESPONDING FIELDS OF TABLE it_status FOR ALL ENTRIES IN it_qals
 WHERE a~objnr = it_qals-objnr
 AND b~spras = sy-langu
 AND a~inact = space.
ENDIF.
LOOP AT it_qals INTO wa_qals.
 mytabix = sy-tabix.
 READ TABLE it_ordmat INTO wa_ordmat WITH KEY aufnr = wa_qals-aufnr.
 IF sy-subrc = 0.
 IF wa_qals-herkunft = '14'.
 wa_qals-matnr = wa_ordmat-zmatnr.
 wa_qals-zzequnr = wa_ordmat-equnr.
 wa_qals-zzassembly = wa_ordmat-bautl.
 MODIFY it_qals FROM wa_qals INDEX mytabix TRANSPORTING matnr zzassembly zzequnr.
 ENDIF.
 ENDIF.
 LOOP AT it_status INTO wa_status WHERE objnr = wa_qals-objnr.
 CONCATENATE wa_qals-sttxt wa_status-txt04 INTO wa_qals-sttxt SEPARATED BY space.
 CLEAR :wa_status.
 ENDLOOP.
 MODIFY it_qals FROM wa_qals INDEX mytabix TRANSPORTING sttxt.
 CLEAR :wa_qals,wa_ordmat,mytabix.
ENDLOOP.
IF s_zmatnr[] IS NOT INITIAL.
 DELETE it_qals WHERE matnr IS INITIAL.
ENDIF.
ENDFORM. " get_data_qals
*& Form build_fieldcat
 text
--> p1 text
<-- p2 text
FORM build_fieldcat .
wa_layout-zebra = 'X'.
wa_layout-colwidth_optimize = 'X'.
wa_layout-box_fieldname = 'SEL'.
wa_layout-box_tabname = 'IT_QALS'.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 I_PROGRAM_NAME =
 i_internal_tabname = 'IT_QALS'
 i_structure_name = 'QALS_D02'
 I_CLIENT_NEVER_DISPLAY = 'X'
 I_INCLNAME =
 I_BYPASSING_BUFFER =
 I_BUFFER_ACTIVE =
 CHANGING
 ct_fieldcat = it_fieldcat
IF sy-subrc = 0.
 LOOP AT it_fieldcat INTO wa_fieldcat.
 CASE wa_fieldcat-fieldname .
 WHEN 'PRUEFLOS'.
 wa_fieldcat-col_pos = 1.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'WERK'.
 wa_fieldcat-col_pos = 3.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'LOSMENGE'.
 wa_fieldcat-col_pos = 4.
 wa_fieldcat-no_out = ''.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'MENGENEINH'.
 wa_fieldcat-col_pos = 5.
 wa_fieldcat-no_out = ''.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ZZEQUNR'.
 wa_fieldcat-col_pos = 6.
 wa_fieldcat-no_out = ''.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ZZASSEMBLY'.
 wa_fieldcat-col_pos = 7.
 wa_fieldcat-no_out = ''.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'HERKUNFT'.
 wa_fieldcat-col_pos = 8.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'AUFNR'.
 wa_fieldcat-col_pos = 9.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'ENSTEHDAT'."enstehdat
 wa_fieldcat-col_pos = 10.
 APPEND wa_fieldcat TO it_fcat.
 WHEN 'STTXT'.
 wa_fieldcat-col_pos = 12.
 wa_fieldcat-hotspot = 'X'.
 APPEND wa_fieldcat TO it_fcat.
 WHEN OTHERS.
 ENDCASE.
 CLEAR wa_fieldcat.
 ENDLOOP.
 wa_fieldcat-fieldname = 'MATNR'.
 wa_fieldcat-tabname = 'IT_QALS'.
 wa_fieldcat-col_pos = 2.
 wa_fieldcat-ref_tabname = 'AUFK'.
 wa_fieldcat-hotspot = 'X'.
 wa_fieldcat-seltext_l = 'Material No.'.
 APPEND wa_fieldcat TO it_fcat.
 wa_fieldcat-fieldname = 'PRUEFER'.
 wa_fieldcat-tabname = 'IT_QALS'.
 wa_fieldcat-col_pos = 11.
 wa_fieldcat-ref_tabname = 'QAMR'.
 wa_fieldcat-seltext_l = 'Name of the Inspector'.
 APPEND wa_fieldcat TO it_fcat.
ENDIF.
ENDFORM. " build_fieldcat
*& Form display_data
 text
--> p1 text
<-- p2 text
FORM display_data .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = 'ZRAIL_LOT_REPORT'
I_CALLBACK_PF_STATUS_SET = ' '
 i_callback_user_command = 'USER_COMMAND'
 is_layout = wa_layout
 it_fieldcat = it_fcat
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_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 =
 TABLES
 t_outtab = it_qals
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. " display_data
*& Form USER_COMMAND
 text
 -->R_UCOMM text
 -->RS_SELFIELD text
FORM user_command USING r_ucomm TYPE sy-ucomm rs_selfield TYPE slis_selfield.
CASE rs_selfield-fieldname .
 WHEN 'PRUEFLOS'.
 SET PARAMETER ID 'QLS' FIELD rs_selfield-value.
 CALL TRANSACTION 'QA03' AND SKIP FIRST SCREEN.
 WHEN 'ZZEQUNR'.
 SET PARAMETER ID 'EQN' FIELD rs_selfield-value.
 CALL TRANSACTION 'IE03' AND SKIP FIRST SCREEN.
 WHEN 'ZMATNR'.
 SET PARAMETER ID 'MAT' FIELD rs_selfield-value.
 CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
 WHEN 'ZZASSEMBLY'.
 SET PARAMETER ID 'MAT' FIELD rs_selfield-value.
 CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
 WHEN 'AUFNR'.
 SET PARAMETER ID 'ANR' FIELD rs_selfield-value.
 CALL TRANSACTION 'IW33' AND SKIP FIRST SCREEN.
 WHEN 'STTXT'.
 MOVE rs_selfield-tabindex TO mytabix1.
 PERFORM show_status.
ENDCASE.
ENDFORM. "USER_COMMAND
*& Form show_status
 text
--> p1 text
<-- p2 text
FORM show_status .
DATA:it_systat TYPE TABLE OF bapi2045ss,
 wa_sysstat TYPE bapi2045ss,
 it_bapi2045us TYPE TABLE OF bapi2045us.
DATA:it_fsys TYPE TABLE OF slis_fieldcat_alv.
DATA:insplot TYPE bapi2045d_il0-insplot.
DATA:language TYPE bapi2045la.
CLEAR wa_qals.
READ TABLE it_qals INTO wa_qals INDEX mytabix1.
insplot = wa_qals-prueflos.
language-langu = sy-langu.
CALL FUNCTION 'BAPI_INSPLOT_GETSTATUS'
 EXPORTING
 number = insplot
 language = language
 TABLES
 system_status = it_systat
 user_status = it_bapi2045us.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
 EXPORTING
 i_program_name = 'ZRAIL_LOT_REPORT'
 i_internal_tabname = 'IT_SYSTAT'
 i_structure_name = 'BAPI2045SS'
 CHANGING
 ct_fieldcat = it_fsys.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = 'ZRAIL_LOT_REPORT'
 it_fieldcat = it_fsys
 TABLES
 t_outtab = it_systat.
ENDFORM. " show_status
IIn the subrouitne the User command the Parameter rs_selfield will give you the selected or clicked field and its value its record no .
I hope this will help you.

Urgent: about the checkbox in OOP ALV report

Hi Experts,
I had use OOP method to display my ALV report. In the report I have a checkbox for each line. I had set this check box use below statements:
    gt_fieldcat_record-tabname = 'GT_ISSUE_INT'.
    gt_fieldcat_record-fieldname = 'CHECKBOX'.
    gt_fieldcat_record-checkbox = 'X'.
    gt_fieldcat_record-edit = 'X'.
    APPEND gt_fieldcat_record.
When I press the save button, then I will save the lines to my Z-table which its GT_ISSUE_INT-CHECKBOX = 'X'.
Now I click the checkbox to select several lines in my ALV report and then press save, but it do not work. Then I check the internal table GT_ISSUE_INT in debugger, I found the GT_ISSUE_INT-CHECKBOX = ' '. Above statements is not correct for the checkbox?? Or I need additional statements to move 'X' to GT_ISSUE_INT-CHECKBOX?? Please help!!!Thanks.

Hi,
If u want to read check box status from list, need to call function module explicitly.
see the sample code:
case sy-ucomm.
when 'SAVE'.
Data ref1 type ref to cl_gui_alv_grid.
      CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
        IMPORTING
           E_GRID = ref1.
       call method ref1->check_changed_data.
loop at GT_ISSUE_INT to workarea.
____ continue writing ur code.
function module read the data from list . and save the changes that made on list.
when u debug, u can see the check box status as 'X' after exucut\ing this fm and method.
reward if helpful.
regards,
swapna

Field description in two line in ALV report

Hi ,
In ALV report I want the description for each field to be displayed in two lines . For example
the description for field matnr is " Material No for grade A " which is displayed in one line . But i want to display it as : Material No
for grade A
in two lines . Is it possible . Please help me out .
Neetesh

Hi Neetesh,
Its not possible to display as you like in 2 lines header for single column. But i can provide the alternative way , it won't good logically. Please try the following logic.
Let suppose you have 10 fields F1-f10. Each field has the 2 lines header. So take 20fields in your fields catalog ie take 10 dummy fields which are equal lenght of the fields F1-f10. and for the last 10 fields(F11-F20) set the row pos as 2, set the second line header to these field(F11-F20). So you will succed to display the 2 level header for single column. But the problem here is you will get one empty row additional row for each row. Because you have taken (F11-F20) fields are dummy and don't have the data also. This solution will works only in the case of ALV List display not in Grid Display.
But Before that tell to your customer about this problem , Because I have done the same things when my customer giving important to 2 lines header and he accepeted that also.
If suppose you have the data in 2 lines for each column then this solution will work fine. Thats what i implemented in my ALV Report.
Warm Regards,
Vijay.

ALV Report not getting displayed in Background

Hi All,
I am using Object Oriented approach of ALV to display the Report, in foreground it works fine but in background I don't get the Report.
I am using the below piece of code but doesn't seems to be working well.
CALL METHOD cl_gui_alv_grid=>offline
 RECEIVING
e_offline = OFF.
if OFF is initial.
*----Creating custom container instance
 CREATE OBJECT gr_ccontainer
 EXPORTING
 container_name = gc_custom_control_name
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 create_error = 3
 lifetime_error = 4
 lifetime_dynpro_dynpro_link = 5
 others = 6 .
 IF sy-subrc <> 0.
*--Exception handling
 ENDIF.
 CREATE OBJECT gr_alvgrid
 EXPORTING
 i_parent = gr_ccontainer.
Its not working. If anyone of you could let me know what can be done to get the ALV report with all the fields in the background.
Thanks.

Hi Geeta,
I was about to say this...
If that is the case u don hav to design a custom control in ur screen, instead use ur screen as a
dummy container which will work well in fore/back ground
CREATE OBJECT go_grid
 EXPORTING
 i_parent = cl_gui_container=>default_screen. "Default scrren taken as dummy container
But u got the answer in previous post : )..
For ur second question:
goto SP01->give spool no->exec->select the spool no(check)-> press shift+F4...
Cheers,
Jose.

Short dump when I do total or sub total in the ALV report

Hi,
When I do total or sub-total on the currency field in the ALV report, it'll give a short dump like
" The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X)".
 Short text of error message:
 Technical information about the message:
 Message classe...... "0K"
 Number.............. 000
 Variable 1.......... " "
 Variable 2.......... " "
 Variable 3.......... " "
 Variable 4.......... " "
 Variable 3.......... " "
 Variable 4.......... " "
Trigger Location of Runtime Error
 Program SAPLSLVC
 Include LSLVCF36
 Row 2,726
 Module type (FORM)
 Module Name FILL_DATA_TABLE
sometime when I do the page down on the ALV report, the same short dump is coming.
Can anyone help me out.
Thanks
Selva

Hi,
I'm getting this short dump in the standard program.
I'm getting ALV report display perfectly. the problem is, when I do total or subtotal on the currency fields.
2704
2705 ************************************
2706 * Column per Fieldcat Entry
2707 ************************************
2708 ls_lvc_data-value = space.
2709 clear ls_lvc_data-style.
2710 loop at it_fcat_local assigning <ls_fcat>
2711 where tech ne 'X' and no_out ne 'X'.
2712 if l_invisible eq 'X'.
2713 clear l_invisible.
2714 if <ls_fcat>-do_sum is initial.
2715 continue.
2716 else.
2717 clear ls_lvc_data-col_pos.
2718 endif.
2719 endif.
2720
2721 add 1 to ls_lvc_data-col_pos.
2722
2723 assign component <ls_fcat>-fieldname
2724 of structure <ls_data> to <l_field_value>.
2725 if sy-subrc ne 0.
>>>>> message x000(0k).
2727 endif.
2728
in this standard program, I'm getting the dump. the line is mentioned above in the code.

OOP ALV report custom control performance problem

HI
how to write OOP ALV report without custom control.. Actually with custom control which taking long time... and time out happens for huge selection of data..
Regards
Roops.

timeout is not an alv problem. If you try to display a "huge" amount of data, any display technology will fail. Even sap programs fail, their wise solution is to ask user to restrict data to be displayed. Or reduce database selection time, or display amount. Or propose the user to download data as a spool, or output to a file on server.
Otherwise, read some advices about how to handle timeout in [Note 25528 - Parameter rdisp/max_wprun_time|http://service.sap.com/sap/support/notes/25528].
About your question, if you still want to try, look at [example code with alv class cl_salv_table for simple display|http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/1ab54099de3726e10000000a1550b0/frameset.htm]

Adding Button to REPORT to call a ALV report

Hi,
 I have a standard report RPT1. In this report I have a button in the application toolbar which I created using the statement.
SELECTION-SCREEN FUNCTION KEY 1.
 When I click on this button it should take me to an ALV report which is coded in the same program RPT1 in a subroutine f_alv_sub.
 But when I click on the button it does not take me to the report.
 How do we go about it? Points will be awarded to the best answer.THANKS.
 regards,
 dev.

Hi,
Check this sample code.
tables:sscrfields. "Fields on selection screens
selection-screen function key 1.
selection-screen function key 2.
Initialization.
sscrfields-functxt_01 = 'Report'.
sscrfields-functxt_02 = 'Exit'.
at selection-screen.
 if sscrfields-ucomm = 'FC01'.
perform f_alv_sub.
 elseif sscrfields-ucomm = 'FC02'.
 endif.
Hope it helps.

Summing up a Column in ALV report

Hi All,
I have developed an ALV Report which will display Invoices and other details.
Now i need to display the sum of NETWR column, if user wish to select that column and click the "SUM" icon.
As of now, if i select the NETWR column and click 'SUM" column, i am getting Runtime error.
How to resolve this issue?
Regards
Pavan

Hi Pavan,
ALV GRID CONTROL:
This task is performed by the SAP Control Framework.
The R/3 System allows you to create custom controls using ABAP Objects. The application server is the Automation Client, which drives the custom controls (automation server) at the front end.
If custom controls are to be included on the frontend, then the SAPGUI acts as a container for them.
Custom controls can be ActiveX Controls or JavaBeans.
The system has to use a Remote Function Call (RFC) to transfer methods for creating and using a control to the front end.
ABAP objects are used to implement the controls in programs.
An SAP Container can contain other controls (for example, SAP ALV Grid Control, Tree Control, SAP Picture Control, SAP Splitter Control, and so on). It administers these controls logically in one collection and provides a physical area for the display.
Every control exists in a container. Since containers are themselves controls, they can be nested within one another. The container becomes the parent of its control. SAP containers are divided into five groups:
SAP custom container: Displays within an area defined in Screen Painter on screens or sub screens.
Class: CL_GUI_CUSTOM_CONTAINER
SAP dialog box container: Displays in a modeless dialog box or as a full screen. Class:
CL_GUI_DIALOGBOX_CONTAINER
SAP docking container: Displays as docked, resizable sub-window with the option of displaying it as a modeless dialog box. Class: CL_GUI_DOCKING_CONTAINER
SAP splitter container: Displays and groups several controls in one area - that is, splits the area into cells Class: CL_GUI_SPLITTER_CONTAINER
SAP easy splitter container: Displays controls in two cells, which the user can resize using a split bar. Class: CL_GUI_EASY_SPLITTER_CONTAINER.
In the control, you can adjust the column width by dragging, or use the 'Optimum width' function to adjust the column width to the data currently displayed. You can also change the column sequence by selecting a column and dragging it to a new position.
Standard functions are available in the control toolbar. The details display displays the fields in the line on which the cursor is positioned in a modal dialog box.
The sort function in the ALV Control is available for as many columns as required. You can set complex sort criteria and sort columns in either ascending or descending order.
You can use the 'Search' function to search for a string (generic search without *) within a selected area by line or column.
You can use the 'Sum' function to create totals for one or more numeric columns. You can then use the "Subtotals" function to set up control level lists: You can use the 'Subtotal' function to structure control level lists: select the columns (non-numeric columns only) that you want to use and the corresponding control level totals are displayed.
For 'Print' and 'Download' the whole list is always processed, not just the sections displayed on the screen.
You can define display variants to meet your own specific requirements. For information on saving variants, see 'Advanced Techniques'.
The ALV grid control is a generic tool for displaying lists in screens. The control offers standard functions such as sorting by any column, adding numeric columns, and fixed lead columns .
Data collection is performed in the program (with SELECT statements, for example) or by using a logical database. The data records are saved in an internal table and passed on to the ALV control along with a field description.
The field description contains information about the characteristics of each column, such as the column header and output length. This information can defined either globally in the Dictionary (structure in the Dictionary) or in the field catalog in the program itself. You can also merge both techniques.
The ALV link is a standard function of Query and QuickViewer. If multiline queries or Quick View lists have been defined, they will automatically be compressed to a single line and output in the ALV control as a long, single line list.
Use Screen Painter to create a sub screen container for the ALV grid control. The control requires an area where it can be displayed in the screen. You have to create a container control that determines this area.
Use the corresponding icon in the Screen Painter layout to create the container control. The size of area "MY_CONTROL_AREA" determines the subsequent size of the ALV control.
The valid GUI status must be set at the PBO event in the flow logic of the ALV subscreen container.
The OK_CODE processing for the cancel functions must be programmed at the PAI event.
The reference variables for the custom container and the ALV grid control must be declared.
To create reference variables, use ABAP statement TYPE REF TO .
The global classes you need to do this are called cl_gui_custom_container (for the custom container control) and cl_gui_alv_grid (for the ALV grid control).
The global classes are defined in the Class Builder. You can use the Class Builder to display information for the methods, their parameters, exceptions, and so on.
Use ABAP statement CREATE OBJECT to create the objects for the container and the ALV control. Objects Are instances of a class.
When an object is created (CREATE), method CONSTRUCTOR of the corresponding class is executed. The parameters of method CONSTRUCTOR determine which parameters have to be supplied with data when the object is created. In the above example, object alv_grid is given the name of the container control (g_custom_container) in exporting parameter i_parent, which links the two controls. For information on which parameters method CONSTRUCTOR possesses and which of these parameters are required, see the Class Builder.
Objects should only be created once during the program. To ensure that this is the case, enclose the CREATE OBJECT statement(s) in an IF IS INITIAL. ... ENDIF clause. The objects must be generated before the control is displayed for the first time - that is, during the PBO event of the ALV subscreen container.
To display the requested dataset in the ALV control, the data must be passed on to the control as an internal table, and a field description must exist indicating the order in which the columns will be output.
In the simplest case, the field description can use a structure from the Dictionary. The Dictionary also determines the technical field attributes like type and length, as well as the semantic attributes like short and long texts. The ALV control uses this information to determine the column widths and headers. The column sequence is determined by the field sequence in the structure.
If no suitable structure is active in the Dictionary, or you want to output internal program fields in the control, then you will have to define information like the output length and column header in the field catalog.
In a typical program run, the dataset is read first (SELECT ....), the internal table is filled with the data to display (... INTO TABLE ...), and ABAP statement CALL SCREEN is then used to call the ALV sub screen container.
The data transfer to the ALV control takes place during the call of method
set_table_for_first_display from class cl_gui_alv_grid. The method call must be programmed at the PBO event of the ALV subscreen container.
The name of the Dictionary structure that supplies the field description is specified in exporting parameter i_structure_name. The name of the internal table that contains the data records to display is specified in changing parameter it_outtab.
The field description for the ALV control can be ta ken from an active Dictionary structure (fully automatic), by passing a field catalog (manual), or through a mixture of the two options (merge).
The field catalog is in internal table with type lvc_t_fcat. This type is defined globally in the Dictionary.
Each line in the field catalog table corresponds to a column in the ALV control.
The field characteristics (= column characteristics) are defined in the field catalog. The field catalog is in internal table with type lvc_t_fcat. Each line that is explicitly described in the ALV control corresponds to a column in the field catalog table.
The link to the data records to output that are saved in internal table is established through field name . This name must be specified in column "fieldname" in the field catalog.
This field can be classified through a Dictionary reference (ref_table and ref_field) or by specifying an ABAP data type (inttype).
Column headers and field names in the detail view of an ALV control line can be determined in the field catalog in coltext and seltext, respectively.
The position of a field during output can be determined with col_pos in the field catalog.
If you want to hide a column, fill field no_out with an "X" in the field catalog. Hidden fields can be displayed again in a user display variant.
Icons can be displayed in the ALV control. If you want a column to be interpreted as an icon, then the icon name must be known to the program (include .) and icon = "X" must be specified for this column in the field catalog.
The above example shows a semi-automatic field description: Part of the field description comes from the Dictionary structure (sflight), while another part is explicitly defined in the field catalog (gt_fieldcat).
The field catalog (internal table) is filled in the program and is passed on together with the name of the Dictionary structure during the method call. The information is merged accordingly in method set_table_for_first_display.
For a user to save display variants, parameters is_variant and i_save must be passed on during method call set_table_for_first_screen. To assign display variants uniquely to a program, at least the program name must be supplied in the transferred structure (gs_variant).
Program names can be up to 30 characters long.
If you only pass on the current parameters for is_variant, then existing variants can be loaded, but no new ones can be saved. If you use parameter i_save, you must pass on a variant structure with is_variant.
I_SAVE = SPACE No variants can be saved.
I_SAVE = 'U' The user can only save user-specific variants.
I_SAVE = 'X' The user can only save general (shared) variants.
I_SAVE = 'A' The user can save both user-specific and general (shared) variants.
You can use parameter is_layout of method set_table_for_first_display, for example, to define the header in the ALV control and the detail display.
To do this, define a query area in the program in accordance with Dictionary structure lvc_s_layo, and pass on the text to display in field -grid_title or -detailtitl.
If you want to create print lists with zebra stripes, set field -zebra to "X". You can display a print preview for print lists by requesting standard function "Print".
All parameters of method SET_TABLE_FOR_FIRST_DISPLAY from global class
CL_GUI_ALV_GRID are defined in the Class Builder.
Events are defined in global class cl_gui_alv_grid; you can use these events to implement user interaction within the program. To respond to a double -click on a table line, you must respond to event DOUBLE_CLICK.
You receive control in the program, allowing you to implement interactive reporting - such as a full screen details list. The events for cl_gui_alv_grid are located in the Class Builder.
To define an implement a local class in the program, you use a handler method. In this handler method, you program the functionality to trigger by a double -click in the output table.
To activate a handler method at runtime, a class or an object from that class registers itself with an event using command SET HANDLER. The names of the IMPORTING parameters in the handler method correspond to the names of the EXPORTING parameters of the related event.
In the above example, the local class is LCL_ILS and the handler method is ON_DBLCLICK. An object - ALV_DBLCLICK - is created and registers itself for event DOUBLE_CLICK.
You can query parameter e_row-index to determine which output line was requested by the double -click. This parameter corresponds to the line number of the output table (internal table with the data records to output). If you need information for the selected line, you have to read it with READ TABLE itab INDEX e_row-index.
This subsequent read in the output table generally corresponds to the HIDE area in conventional reporting. You first have to make sure that the user has double -clicked a line in the output table (similar to the valid line selection with the HIDE technique).
A field group can contain global data objects, but not data objects that have been defined locally in a subroutine or function module.
You can use INSERT to specify both fields and field symbols. This makes it possible to dynamically insert a data object referred to by a field symbol into a field group at runtime. Any field symbols that have not been assigned are ignored, which means no new field is inserted into the field group.
The EXTRACT statement writes all the fields of a field group as one record to a sequential dataset (transport takes place with similarly named fields). If a HEADER field group is defined, then its fields are placed ahead of each record as sort keys. You can then sort the dataset with SORT and process it with LOOP ...ENDLOOP. In this case, no further EXTRACT is possible.
The INSERT statement is not a declarative statement: This means field groups can also be expanded in the program flow section.
As soon as the first dataset of a field group has been extracted with EXTRACT, that field group can no longer be expanded with INSERT. In particular, the HEADER field group cannot be expanded after the first EXTRACT (regardless of the field group).
When the GET events are processed, the logical database automatically writes hexadecimal zeros in all the fields of a node when it returns to an upper-level node in the hierarchy. Since the HEADER normally contains sort fields for all field groups, these hexadecimal zeros in the HEADER serve as a type of hierarchy key: The more zeros there are, the further up in the control level hierarchy you go.
The SORT statement sorts the extract dataset in accordance with the defined field sequence in field group HEADER. The addition BY ... sets a new sort key.
Each must be either a field of field group HEADER or a field group that consists only of fields of the field group HEADER. You can use the additions ASCENDING and DESCENDING to determine whether the fields are sorted in ascending (default) or descending order.
Fields containing X'00' in the logical databases are always displayed before all other values during a SORT.
Processing of an extract dataset always takes places within a LOOP. The contents of the extract dataset field are placed in program fields with the same names.
The group change always involves the fields of the HEADER. Single record processing for extract datasets is performed using language element AT ( = field group).
CNT() is not a statement, but instead a field that is automatically create d and filled when is a non-numeric field from field group HEADER and is part of the sort key. At the end of the group, CNT() contains the number of different values that the field recorded in this group level.
SUM() is not a statement, but instead a field that is automatically created and filled when is a numeric field of an extract dataset. At the end of the group, SUM() contains the control total of field .
*** and CNT are only available at the end of the group level or at AT LAST.
Single record processing for extract datasets AT WITH is only performed when field group is immediately followed by field group in the temporary dataset.
Loops over an extract dataset cannot be nested. However, several contiguous loops are permitted.
The sequence of the control level changes within the LOOP must correspond to the sort sequence.
Totals can only be calculated within control footer processing.
Extracts allow only appends (EXTRACT), sorting (SORT) and sequential processing (LOOP).
Once a SORT or LOOP has occurred, the intermediate dataset is frozen and cannot be expanded with EXTRACT. Operations that insert into or delete from EXTRACT datasets are not supported.
Extracts allow for several record types (FIELD-GROUPS) with fields that can be set dynamically (INSERT is not a declarative statement!). Internal tables have a single, statically-defined line type.
Internal tables use the sequence of table fields according to the declaration for the hierarchy of the control leve l. The control level structure for internal tables is therefore static, and is independent of which criteria were used to sort the internal table.
Extracts do not depend on the field sequence for control level processing: a re-sort or a completely different control level process can take place. The control level structure for extract datasets is therefore dynamic. It corresponds exactly to the sort key of the extract dataset. The sort key is the sequence of fields from the field group HEADER, and is used to sort the extract dataset.
Extracts rely on the compiler to determine which combinations of group levels and a cumulating field the control level totals desire. The desired control level totals are determined by the processing of LOOP ... ENDLOOP blocks. Internal tables build the control level total with the SUM statement.
This procedure leads to high resource depletion for totaling control levels in internal tables.
Regards,
Chandru

Value in ALV report

Hi experts,
I have an ALV report.
In the ALV report one of the field is Currency conversion rate to USD.
For this i am fetching value from TCURR-UKURS.
The value is taken into an internal table.
I have seen in the internal table the value is coming correctly. like: suppose the value is 1,114.10000- in that perticulat field. then the same value is coming in my final internal table.
But in the report display it is coming as /1,114.10000
Please help me out
regards,
charles

Check the field-reference what is your ALV-field pointing at. Maybe this reference is pointing at a field, which enables only positive numbers.
And if you just modified it, don't forget about the ALV-cache, which stores a lot of setting about ALV grids while you are logged in.
To clear ALV cache you can use a transaction (but I forgot it ), or you can log off and relogin to SAP.
Happy developing
Tamá

End of Page event in ALV report using SALV class[cl_salv_hierseq_table]

Hi ,
have been working on a ALV report using the class SALV cl_salv_hierseq_table
I am facing few issues pertaining to two things:
1. Displaying some subtotal text along with the subtotals.
Example refer the standard demo example: SALV_DEMO_HIERSEQ_FORM_EVENTS
Now instead of A 17 and A26 I would like to show text like Subtotal for the Carrid.for subtotals and grand totals
Like Subtotal for A 17 is : XXXXXXX
GrandTotal is : YYYYYY
2. We have a page break and a new page for every purchasing group as in the standard example SALV_DEMO_HIERSEQ_FORM_EVENTS for CARRID.
I need to display some variable values as number of documents ,total number of records etc at the end of each CARRID group before a new page starts for the next CARRID.Please note i do not want it on every page.it should only be diaplyed at the end of page whose next page would be for next CARRID.[basically at end of every carrid]Example:after displaying all details for AA need to display the number of records for that carrid at the end of the page[as page break is based on CARRID]/
Thanks
Jyotsna

at end of page event, for CL_SALV_EVENTS_HIERSEQ, has some useful parameters allowing to know where you are at the time of event
parameter VALUE is of type CL_SALV_FORM which contains public attribute IF_SALV_FORM~ACCDESCRIPTION; you can slo get contents of it
about text of total/subtotal, this is normally set in the layout

Calling infotype 0002 in ALV report for showing employee photo

Hi all,
The requirment from business side is a report in which employees personal data shuold be shown with employee photo, I had tried for employee photo in ALV report but it didnt sucessed, then I went for other solution like calling transaction in ALV report.
In this case I am calling Infotype 0002 but the issue is that the transaction PA20 is coming with PERNR but I am not able to go directlly to infotype which shows employee Photo,please suggest any solution.
Thaks.
JAY

Hi Jay,
It is possible. Please refer the syntax for the CALL TRANSACTION
CALL TRANSACTION ta { [AND SKIP FIRST SCREEN]
                    | [USING bdc_tab [bdc_options]] }.
You can do a recording till the required page comes & call the transaction accordingly. Hope, you are aware about the same.
For example, I just had a solution to go to the roles tab in the user profile and I did as below:
    CLEAR wa_bdcdata.
    wa_bdcdata-program = 'SAPLSUU5'.
    wa_bdcdata-dynpro   = '0050'.
    wa_bdcdata-dynbegin = k_ok.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_CURSOR'.
    wa_bdcdata-fval   = 'USR02-BNAME'.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'USR02-BNAME'.
    wa_bdcdata-fval   = g_value.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_OKCODE'.
    wa_bdcdata-fval   = 'SHOW'.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-program = 'SAPLSUU5'.
    wa_bdcdata-dynpro   = '0100'.
    wa_bdcdata-dynbegin = k_ok.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_OKCODE'.
    wa_bdcdata-fval   = '=ACTG'.
    APPEND wa_bdcdata TO it_bdcdata.
    g_opt-dismode = 'E'.
    g_opt-defsize = k_ok.
*** if user click on the User Name, call SU01
    CALL TRANSACTION 'SU01' USING it_bdcdata
                OPTIONS FROM g_opt.
Regards,
Selva K.

About ALV report

Similar Messages

Maybe you are looking for