ALV USING OBJECTS

I AM USING LVC_T_FCAT. BUT I CAN GET THE TOTAL IN ALV REPORT DISPLAY. PLS, SOMEBODY HELP

Hi
while creating fieldcatalog, for which field you want t calculate SUM for that field set
fieldcatalg-DO_SUM = 'X'-----> Totals calculation for column values
check these links
http://www.sapfans.com/forums/viewtopic.php?t=20386
http://www.sapfans.com/forums/viewtopic.php?t=85191
http://www.sapfans.com/forums/viewtopic.php?t=88401
http://www.sapfans.com/forums/viewtopic.php?t=17335
Reward all helpfull answers
Regards
Pavan

Similar Messages

Remove / set focus on ALV using objects

I have a screen with 6 subscreen and 6 customercontainers with each 1 ALV, I have 6 ALV's on the same screen, some of the ALV's are only display, and some are for input, my problem is that each alv have fokus on the first cell I want to remove the fokus in all display alv's, I am using the method "set_current_cell_via_id" to place the fokus in edit cell for the alv's with editable cell's, but how to remove fokus in alv, where only display ?
Best regards Jørgen Jensen INIT A/S

Hello Jørgen
This is one of the rare occasion where I believe that something is NOT possible with SAP.
You may have a look at my sample report
ZUS_SDN_SPLITTER_CONTAINER and play around with various methods yet I doubt you will be successful.
*& Report ZUS_SDN_SPLITTER_CONTAINER
REPORT zus_sdn_splitter_container.
**type-pools: abap.
TYPES: ty_t_knb1    TYPE STANDARD TABLE OF knb1
                    WITH DEFAULT KEY.
TYPES: BEGIN OF ty_s_control.
TYPES: cell    TYPE REF TO cl_gui_container.
TYPES: grid    TYPE REF TO cl_gui_alv_grid.
TYPES: data    TYPE ty_t_knb1.
TYPES: row     TYPE lvc_s_row.
TYPES: layout TYPE lvc_s_layo.
TYPES: variant TYPE disvariant.
TYPES: END OF ty_s_control.
TYPES: ty_t_control TYPE STANDARD TABLE OF ty_s_control
                     WITH DEFAULT KEY.
DATA:
gs_control       TYPE ty_s_control,
gt_controls      TYPE ty_t_control.
DATA:
gd_repid         TYPE syst-repid,
gd_okcode        TYPE ui_func,
go_docking       TYPE REF TO cl_gui_docking_container,
go_splitter      TYPE REF TO cl_gui_splitter_container,
** go_cell          TYPE REF TO cl_gui_container,
** go_grid          TYPE REF TO cl_gui_alv_grid,
gs_layout        TYPE lvc_s_layo.
DATA:
gd_msg           TYPE bapi_msg,
gd_perc          TYPE i,
gd_lines         TYPE i,
gd_idx           TYPE i,
gd_cnt           TYPE i,
gt_knb1          TYPE STANDARD TABLE OF knb1.
PARAMETERS:
p_row    TYPE i DEFAULT '3',
p_col    TYPE i DEFAULT '3'.
START-OF-SELECTION.
PERFORM init_controls.
DESCRIBE TABLE gt_controls.
gd_lines = syst-tfill.
SELECT * FROM knb1 INTO TABLE gt_knb1 UP TO 100 ROWS
    WHERE bukrs = '1000'.
LOOP AT gt_controls INTO gs_control.
    gd_idx = syst-tabix.
    gd_cnt = syst-tabix * 5.
    gd_perc = ( syst-tabix * 100 ) / gd_lines.
    CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
      EXPORTING
        percentage       = gd_perc
*       TEXT             = ' '
    gs_control-data = gt_knb1.
    DELETE gt_knb1 INDEX 1.
    "   Set individual layout and variant
    gs_control-layout-cwidth_opt = abap_true.
    gs_control-layout-zebra      = abap_true.
    gs_control-layout-no_toolbar = abap_true.
    gs_control-layout-smalltitle = abap_true.
    gs_control-row-index = gd_idx.
    WRITE gd_idx TO gs_control-layout-grid_title NO-ZERO.
    CONDENSE gs_control-layout-grid_title NO-GAPS.
    CONCATENATE gs_control-layout-grid_title
                '. Customer'
      INTO gs_control-layout-grid_title.
    CALL METHOD gs_control-grid->set_table_for_first_display
      EXPORTING
        i_structure_name = 'KNB1'
        is_layout        = gs_control-layout
        i_save           = 'A'
        is_variant       = gs_control-variant
      CHANGING
        it_outtab        = gs_control-data
      EXCEPTIONS
        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.
    ENDIF.
    IF ( gd_idx > 1 ).
      CALL METHOD gs_control-grid->set_current_cell_via_id
        EXPORTING
          is_row_id = gs_control-row.
      CALL METHOD gs_control-grid->refresh_table_display
*        EXPORTING
*          IS_STABLE      =
*          I_SOFT_REFRESH =
*        EXCEPTIONS
*          FINISHED       = 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.
    ENDIF.
    MODIFY gt_controls FROM gs_control INDEX gd_idx.
ENDLOOP.
gd_msg = gd_lines.
CONDENSE gd_msg NO-GAPS.
CONCATENATE gd_msg 'grids displayed on single screen.'
    INTO gd_msg
    SEPARATED BY space.
MESSAGE gd_msg TYPE 'S'.
* Link the docking container to the target dynpro
gd_repid = syst-repid.
CALL METHOD go_docking->link
    EXPORTING
      repid                       = gd_repid
      dynnr                       = '0100'
*      CONTAINER                   =
    EXCEPTIONS
      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.
ENDIF.
* NOTE: dynpro does not contain any elements
CALL SCREEN '0100'.
* Flow logic of dynpro (does not contain any dynpro elements):
*PROCESS BEFORE OUTPUT.
* MODULE STATUS_0100.
*PROCESS AFTER INPUT.
* MODULE USER_COMMAND_0100.
END-OF-SELECTION.
*&      Module STATUS_0100 OUTPUT
*       text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'. " contains push button "DETAIL"
* SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
*       text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
    WHEN 'BACK' OR
         'END' OR
         'CANC'.
      SET SCREEN 0. LEAVE SCREEN.
    WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Form INIT_CONTROLS
*       text
* --> p1        text
* <-- p2        text
FORM init_controls .
* define local data
DATA:
    ld_column TYPE i,
    ls_control TYPE ty_s_control.
REFRESH: gt_controls.
* Create docking container
CREATE OBJECT go_docking
    EXPORTING
      parent                      = cl_gui_container=>screen0
      ratio                       = 90
    EXCEPTIONS
      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.
CALL METHOD go_docking->set_extension( 99999 ).
* Create splitter container
CREATE OBJECT go_splitter
    EXPORTING
      parent            = go_docking
      rows              = p_row
      columns           = p_col
*      NO_AUTODEF_PROGID_DYNNR =
*      NAME              =
    EXCEPTIONS
      cntl_error        = 1
      cntl_system_error = 2
      OTHERS            = 3.
IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
DO p_col TIMES.
    ld_column = syst-index.
    DO p_row TIMES.
* Get cell container
      CLEAR: ls_control.
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = syst-index
          column    = ld_column
        RECEIVING
          container = ls_control-cell.
*   Create ALV grid
      CREATE OBJECT ls_control-grid
        EXPORTING
          i_parent          = ls_control-cell
        EXCEPTIONS
          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.
      APPEND ls_control TO gt_controls.
    ENDDO. " rows
ENDDO. " columns
ENDFORM.                    " INIT_CONTROLS
Regards
Uwe

How to write Block ALV using Object-oriented methodology?

Hi all,
How to write a Block ALV without using 'Reuse_ALV.....' FMs? I want to use the CL_GUI....' methods. What is the procedure? Any sample block ALV?
Thanks,
Charles.

Currently there is not an OO method of implementing the block ALV, it is only available using the REUSE function module.
Regards,
RIch Heilman

ALV using Object oriented programming concepts

Hi All,
I am unable to call a transaction after a hotspot click on a field.... I have used CALL METHOD w_grid->get_current_cell to get the cell info.....but this is not happening.... Can anyone plz tell me how to call a transaction on doing a hotspot click on a field?

One reason why your code is not working is i think the method you are using is Protected. ie it can't be used outside the class.
Try the following code.
In the method definition define the method as follows.
methods : HOTSPOT_CLICK
                 FOR EVENT HOTSPOT_CLICK OF CL_GUI_ALV_GRID
                 IMPORTING E_ROW_ID
                                   E_COLUMN_ID
                                   ES_ROW_NO.
The E_ROW_ID   E_COLUMN_ID   ES_ROW_NO are the parameters returnned by the event HOT-SPOT click.
Let us suppose I_MARA is your internal table using which you have displayed your ALV HRID.
Now in the method Implementation part use the following code.
METHOD HOTSPOT_CLICK.
    CLEAR : WA_MARA.
    READ TABLE I_MARA INDEX E_ROW_ID INTO WA_MARA.
    IF SY-SUBRC EQ 0.
      IF E_COLUMN_ID-FIELDNAME EQ C_MATNR.
        SET PARAMETER ID 'MAT' FIELD WA_MARA-MATNR.
        SET PARAMETER ID 'WRK' FIELD C_WERKS.
        CALL TRANSACTION 'MD04' AND SKIP FIRST SCREEN.
      ELSE.
        CALL SCREEN 0130 starting at 35 15.
      ENDIF.
    ENDIF.
ENDMETHOD.
At the call Transaction point you can call which ever Transaction you want.
And aslo please check if you have registered the event HOTSPOT.
Hope this code works.
Thanks & regards,
Y Gautham

Sum in ALV grid display using objects

Hi Experts,
I have created a Report with ALV using objects and also am able to get SUM for some fields using do_sum = 'X'.
My problem is i want to do some calculation using the total amount which i have got, how can i do that (or can it be done??).
Thanks in Advance...
Santosh

Hi this may be of some help.
ABAP List Viewer
The common features of report are column alignment, sorting, filtering, subtotals, totals etc. To implement these, a lot of coding and logic is to be put. To avoid that we can use a concept called ABAP List Viewer (ALV).
This helps us to implement all the features mentioned very effectively.
Using ALV, We can have three types of reports:
1. Simple Report
2. Block Report
3. Hierarchical Sequential Report
There are some function modules which will enable to produce the above reports without much effort.
All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.
1. SIMPLE REPORT.
The important function modules are
a. Reuse_alv_list_display
b. Reuse_alv_fieldcatalog_merge
c. Reuse_alv_events_get
d. Reuse_alv_commentary_write
e. Reuse_alv_grid_display
A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.
The important parameters are :
I. Export :
i. I_callback_program : report id
ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status
iii. I_callback_user_command : routine where the function codes are handled
iv. I_structure name : name of the dictionary table
v. Is_layout : structure to set the layout of the report
vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE
vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.
II. Tables :
i. t_outtab : internal table with the data to be output
B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
The Important Parameters are :
I. Export :
i. I_program_name : report id
ii. I_internal_tabname : the internal output table
iii. I_inclname : include or the report name where all the dynamic forms are handled.
II Changing
ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
declared in the type pool SLIS.
C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type
Parameters :
I. Import :
Et_Events : The event table is returned with all possible CALLBACK events
for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.
II. Export :
I_List_type :
0 = simple list REUSE_ALV_LIST_DISPLAY
1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY
2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND
3 = hierarchical-sequential block list
REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.
Parameters :
I. it_list_commentary : internal table with the headings of the type slis_t_listheader.
This internal table has three fields :
Typ : H header, S selection , A - action
Key : only when typ is S.
Info : the text to be printed
E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.
Parameters : same as reuse_alv_list_display
This is an example for simple list.
2. BLOCK REPORT
This is used to have multiple lists continuously.
The important functions used in this report are:
A. REUSE_ALV_BLOCK_LIST_INIT
B. REUSE_ALV_BLOCK_LIST_APPEND
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_BLOCK_LIST_DISPLAY
A. REUSE_ALV_BLOCK_LIST_INIT
Parameters:
I. I_CALLBACK_PROGRAM
II. I_CALLBACK_PF_STATUS_SET
III. I_CALLBACK_USER_COMMAND
This function module is used to set the default gui status etc.
B. REUSE_ALV_BLOCK_LIST_APPEND
Parameters :
Export :
I. is_layout : layout settings for block
II. it_fieldcat : field catalog
III. i_tabname : internal table name with output data
IV. it_events : internal table with all possible events
Tables :
i. t_outtab : internal table with output data.
This function module adds the data to the block.
Repeat this function for all the different blocks to be displayed one after the other.
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
This function module is used for hierarchical sequential blocks.
D. REUSE_ALV_BLOCK_LIST_DISPLAY
Parameters : All the parameters are optional.
This function module display the list with data appended by the above function.
Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.
3. Hierarchical reports :
Hierarchical sequential list output.
The function module is
A. REUSE_ALV_HIERSEQ_LIST_DISPLAY
Parameters:
I. Export:
i. I_CALLBACK_PROGRAM
ii. I_CALLBACK_PF_STATUS_SET
iii. I_CALLBACK_USER_COMMAND
iv. IS_LAYOUT
v. IT_FIELDCAT
vi. IT_EVENTS
vii. i_tabname_header : Name of the internal table in the program containing the
output data of the highest hierarchy level.
viii. i_tabname_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
ix. is_keyinfo : This structure contains the header and item table field
names which link the two tables (shared key).
II. Tables
i. t_outtab_header : Header table with data to be output
ii. t_outtab_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using REUSE_ALV_FIELDCATALOG_MERGE.
Important Attributes :
A. col_pos : position of the column
B. fieldname : internal fieldname
C. tabname : internal table name
D. ref_fieldname : fieldname (dictionary)
E. ref_tabname : table (dictionary)
F. key(1) : column with key-color
G. icon(1) : icon
H. symbol(1) : symbol
I. checkbox(1) : checkbox
J. just(1) : (R)ight (L)eft (C)ent.
K. do_sum(1) : sum up
L. no_out(1) : (O)blig.(X)no out
M. outputlen : output length
N. seltext_l : long key word
O. seltext_m : middle key word
P. seltext_s : short key word
Q. reptext_ddic : heading (ddic)
R. ddictxt(1) : (S)hort (M)iddle (L)ong
S. datatype : datatype
T. hotspot(1) : hotspot
with regards,
Hema Sundara.
pls reward if u find it helpful.

Comparing OO ALV and ALV using Function modules

Hi All,
Please provide me what are the advantages of developing ALV using Objects compared to creation using function modules. What are the disadvantages of creating using the conventional FM way.
I have not worked much on ALV using Function modules, have been developing using standard abap classes. I wanted to have an detailed understanding and differences between the two.
Please provide your views on the same.
I have searched SDN forum, but didnt find much information, so it will be of great help if you provide some inputs.
Thanks & Regards,
Navneeth K.

Hi, Navneeth,
With ALV functions, you can everything that you would do otherwise with the OOPS ALV. However , I don't think you can possibily have more controls in case of alv function because it occupies the entire screen and the function only calls 2 screens internally ( screen numbers 500 and 700 (for popup alv)).
But with OOPS on the other hand, you can have many controls on one screen, for example, you can have 2 ALV lists, or a splitter control with one of them having a Tree control and the other alv grid/list, pictures etc.
So the sole motive of the function is if you want to display a list, but when developing a serious application, I would go for OOPs ALV.
regards,
Advait

Comparing ALV using Function modules and OO ALV

Hi All,
Please provide me what are the advantages of developing ALV using Objects compared to creation using function modules. What are the disadvantages of creating using the conventional FM way.
I have not worked much on ALV using Function modules, have been developing using standard abap classes. I wanted to have an detailed understanding and differences between the two.
Please provide your views on the same.
I have searched SDN forum, but didnt find much information, so it will be of great help if you provide some inputs.
Thanks & Regards,
Navneeth K.

Hello,
Check this link
ALV FUNCTION MODULE AND OBJECT ORIENTED ?
Example programs
http://saplab.blogspot.com/2007/10/sample-abap-program-of-alv-grid-control.html
http://www.abapcode.info/2007/06/object-oriented-alv-using-two.html

How to display horizontal line in top-of-page by using object oriented ALV?

How to display horizontal line in top-of-page by using object oriented ALV.
I am created top-of-page in object oriented alv.
But not be successes in showing horizontal line in it.
Can any one pls give solution for this..
Thanks and regards..

Hi
Try like this
data: gt_list_top_of_page type slis_t_listheader. " Top of page text.
Initialization.
perform comment_build using gt_list_top_of_page[].
form top_of_page.
* Note to self: the gif must be loaded into transaction OAOR with
* classname 'PICTURES' AND TYPE 'OT' to work with ALV GRID Functions.
* I Loaded NOVALOGO2 into system.
call function 'REUSE_ALV_COMMENTARY_WRITE'
     exporting
* I_LOGO = 'NOVALOGO2'
* i_logo = 'ENJOYSAP_LOGO'
         it_list_commentary = gt_list_top_of_page.
endform. " TOP_OF_PAGE
form comment_build using e04_lt_top_of_page type slis_t_listheader.
data: ls_line type slis_listheader.
      clear ls_line.
      ls_line-typ = 'A'.
      ls_line-info = 'Special'(001).
      fgrant = xgrant.
      concatenate ls_line-info fgrant
      'Stock Option Report to the board'(002)
             into ls_line-info separated by space.
                    condense ls_line-info.
      append ls_line to e04_lt_top_of_page.
endform. " COMMENT_BUILD
Use following syntex for footer print in alv:
* For End of Page
form END_OF_PAGE.
data: listwidth type i,
        ld_pagepos(10) type c,
        ld_page(10)    type c.
write: sy-uline(50).
skip.
write:/40 'Page:', sy-pagno .
endform.
* For End of Report
form END_OF_LIST.
data: listwidth type i,
        ld_pagepos(10) type c,
        ld_page(10)    type c.
skip.
write:/40 'Page:', sy-pagno .
endform.
check this link
http://abapprogramming.blogspot.com/
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5dc3e690-0201-0010-1ebf-b85b3bed962d
Changing width of a custom container dynamically
Display Page numbers in ALV
Insert picture in selection screen.
Logo in OO ALV Grid
Reward all helpfull answers
Regards
Pavan

Set cursor alv grid (not using objects)

I got a question on ALV GRID (not using objects), please let me know if you have pointers. Thanks.
Output has 2 screens both has different contents. The output is generated using internal table1 and 2 and using FM 'REUSE_ALV_GRID_DISPLAY_LVC' (both screen use same FM).
First screen has multiple pages of output (say 10 pages). User scrolled page 5 and line 10 of first screen and then double clicked it takes to screen #2. After completion of screen #2, the back arrow should get back to page 5 and line 10 of screen #1. Currently the back arrow gets to screen#1 page 1 and line 1. How to remember the cursor position in alv grid and instruct the cursor to go there?
Appreciate the input.
Note: I tried "set cursor line n" with "Scroll" command but no luck. http://help.sap.com/saphelp_nw70/helpdata/EN/9f/dba47e35c111d1829f0000e829fbfe/content.htm

Thanks for the inputs.
FYI, I got it implemented using method CALL METHOD <ref.var. to CL_GUI_ALV_GRID > ->set_current_cell_via_id
The method is called by 'REUSE_ALV_GRID_DISPLAY_LVC' form 'PF_STATUS_SET' when the ALV grid output is presented each time.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY_LVC'
    EXPORTING
      i_bypassing_buffer       = 'X'
      i_callback_program       = gc_repid
      i_callback_pf_status_set = 'PF_STATUS_SET'
      i_callback_user_command = 'USER_COMMAND'
      is_layout_lvc            = lwa_layout
      it_fieldcat_lvc          = git_fc_lvc
      i_default                = ' '
    TABLES
      t_outtab                 = git_data
    EXCEPTIONS
      program_error            = 1
      OTHERS                   = 2.
FORM alv_event_pf_status_set USING rt_extab
                             TYPE slis_t_extab.
DATA lo_ref1 TYPE REF TO cl_gui_alv_grid.
*Get the reference to class "lo_ref1" for the ALV report
CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
    IMPORTING
      e_grid = lo_ref1.
*set the focus of cursor in ALV
CALL METHOD lo_ref1->set_current_cell_via_id
    EXPORTING
      is_row_no = gv_row. "row number where you want to focus the cursor
ENDFORM.

Upload an excel file input into an itab,display in ALV using ABAP objects

Requirement:
Create a selection screen which takes an excel file as input with parameters emp id, emp name, salary, mnth, ph no.
Create a database table with the same fields.
The program needs to have two modes. Display mode and update mode.
Display mode only displays the file data in alv grid and update mode updates database table with similar parameters as above and also shows alv grid output.
task is to do using Object oriented approach. This should also have the facility to modify the cell values in ALV grid and once saved then it needs to update the database accordingly.
I have done the same functionality in a report program without using ABAP objects but finding difficulty in using object oriented approach.Please help me as i am new to abap-objects.
Thanks in advance.......

Hi,
The selection screen design and all remains the same.
Get all the detials which you need in your final internal table.
This internal table will be used to display in the ALV grid.
The approach remains the same as the normal programing.
Prepare a field catalog table and then use it along with the internal table to display in the grid.
The only change is that instead of FM you will have to make us of classes and their methods.
Firstly you will have to create a screen.
On this screen create a custom control object and give it some name. say for eg. CC_CONTAINER.
This will be a container on which the ALV grid object will be placed.
2 objects are needed to display the grid
CL_GUI_CUSTOM_CONTAINER and CL_GUI_ALV_GRID.
In the PBO of the screen first create an instance of object CL_GUI_CUSTOM_CONTAINER
CREATE OBJECT y_lobj_cont
      EXPORTING
         container_name              = 'CC_CONTAINER'
      EXCEPTIONS
        cntl_error                  = 1
        cntl_system_error           = 2
        create_error                = 3
        lifetime_error              = 4
        lifetime_dynpro_dynpro_link = 5
        OTHERS                      = 6.
    IF sy-subrc NE 0.
      MESSAGE ID sy-msgid TYPE y_k_s NUMBER sy-msgno
               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Then create a instance of the GRID
IF y_lobj_grid IS INITIAL.
      CREATE OBJECT y_lobj_grid
        EXPORTING
          i_parent          = y_lobj_cont
         EXCEPTIONS
           error_cntl_create = 1
           error_cntl_init   = 2
           error_cntl_link   = 3
           error_dp_create   = 4
           OTHERS            = 5 .
      IF sy-subrc NE 0.
        MESSAGE ID sy-msgid TYPE y_k_s NUMBER sy-msgno
                   WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    ENDIF.
Then call the method SET_TABLE_FOR_FIRST_DISPLAY to display the grid.
CALL METHOD y_lobj_grid->set_table_for_first_display
      EXPORTING
        it_toolbar_excluding          = y_v_lt_exclude
      CHANGING
        it_outtab                     = y_li_tbl
        it_fieldcatalog               = y_li_fcat
      EXCEPTIONS
        invalid_parameter_combination = 1
        program_error                 = 2
        too_many_lines                = 3
        OTHERS                        = 4.
    IF sy-subrc NE 0.
      MESSAGE ID sy-msgid TYPE y_k_s NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Check the example program BCALV_GRID_EDIT for better understanding.
Regards,
Ankur Parab

Downloading ALV Grid (using objects) output to Excel

Hi all,
I'm using objects for ALV Grid. I have few other fields (few are above and few are below the custom control) on screen other than custom control. I want to download the entire screen to excel (including other fields). But using Export option I'm able to download only ALV Grid. I did tried with Excel in place option which is not pulling data from ALV Grid control.
Please suggest me the solution.
Regards
Jaker.

hi
use this code in ALV format
TABLES USR03.
DATA: BEGIN OF ISAPDAT OCCURS 0,
          BNAME LIKE USR03-BNAME,
          NAME1 LIKE USR03-NAME1,
          NAME2 LIKE USR03-NAME2,
      END OF ISAPDAT.
PARAMETERS P_FNAME LIKE RLGRAP-FILENAME
                    DEFAULT 'd:\sapdata.xls' OBLIGATORY.
SELECT * FROM USR03 INTO CORRESPONDING FIELDS OF TABLE ISAPDAT.
SORT ISAPDAT.
CALL FUNCTION 'SAP_CONVERT_TO_XLS_FORMAT'
     EXPORTING
          I_FILENAME        = P_FNAME
     TABLES
          I_TAB_SAP_DATA    = ISAPDAT
     EXCEPTIONS
          CONVERSION_FAILED = 1
          OTHERS            = 2.
IF SY-SUBRC EQ 0.
WRITE:/ 'Download to Excel complete'.
ELSE.
WRITE:/ 'Error with download'.
ENDIF.
Code Formatted by: Alvaro Tejada Galindo on Jan 8, 2009 2:34 PM

How to capture index/row no of row in table using object oriented alv.

i have a table with many fields. i have an alv grid table displayed using object oriented alv. when i double click on a record, i call another screen. there i want to display the record number. eg, if i doubleclick on the third row, i will go to next screen and display 3 there.
please let me know how it is done as it is urgent.
thanks in advance.

Hi,
Use the following code to get rowno.
CLASS lcl_grid_events DEFINITION DEFERRED.
DATA:
grid1_events      TYPE REF TO lcl_grid_events.
CLASS lcl_grid_events DEFINITION.
PUBLIC SECTION.
    METHODS:
      dbclk
       FOR EVENT double_click OF cl_gui_alv_grid
       IMPORTING e_row
                 e_column
                 es_row_no.
ENDCLASS.                    "lcl_grid_events DEFINITION
CLASS lcl_grid_events IMPLEMENTATION.
METHOD dbclk.
*access e_row variable, which contains the record no.
ENDMETHOD.                    "dbclk
ENDCLASS.                    "lcl_grid
write the following code after method call of set_table_for_first_display
    CREATE OBJECT grid1_events.
    SET HANDLER grid1_events->dbclk
                FOR grid1.
reward point if useful.

Advanced ALV using ABAP objects

Hi All ABAPers,
I have a question in Advanced ALV using ABAP objects.Can we display the output ie., ALV Grid without defining the custom cointainer?ie., just as we do in the classical ALV without defining any screens.Can we do that as a normal executable program ie., without using module pool programming.Please give me a solution.
Thanks & Regards,
Chaitanya.

If you want editable grids then the cl_salv_table method won't unfortunately be of use since (currently) there's no editable facility / method.
So if you are using cl_gui_alv_grid here's how to "get round" the problem.
I'm essentially using my own alv class which is a reference to cl_gui_alv_grid but the methodology shown here is quite simple.
What you can do is to create a method which calls a function module for example ZZ_CALL_SCREEN so you only have to code a Screen and a GUI in ONE function module and not in every ALV report.
for example you could create something like this
My version has the option of 2 screens - so when I double click on a cell in one grid I can perform some actions and then display a 2nd grid before returning back to the ist grid.You can easily modify this to suit your applications.
The parameters are fairly self evident from the code. You can just use this as a model for your own applications.
I agree that having to code a separate screen and GUI for OO ALV GRID reports was for some people a "show stopper" in switching from the old SLIS to OO ALV reports.
I Hope if any SAP development guys are reading this PLEASE PROVIDE EDITABLE FUNCTIONALITY IN THE NEW CL_SALV_TABLE class. Thanks in advance.
method display_data.
call function 'ZZ_CALL_SCREEN'
exporting
    screen_number       = screen_number
    program             = program
    title_text          = title_text
   i_gridtitle         = i_gridtitle
    i_zebra             = i_zebra
    i_edit              = i_edit
    i_opt               = i_opt
    i_object            = z_object
changing
    e_ucomm             = e_ucomm
    it_fldcat           = it_fldcat
    gt_outtab           = gt_outtab.
e_ucomm = sy-ucomm.
endmethod.
function zz_call_screen .
*"*"Local interface:
*" IMPORTING
*"     REFERENCE(SCREEN_NUMBER) TYPE SY-DYNNR
*"     REFERENCE(PROGRAM) TYPE SY-REPID
*"     REFERENCE(TITLE_TEXT) TYPE CHAR50
*"     REFERENCE(I_GRIDTITLE) TYPE LVC_TITLE
*"     REFERENCE(I_ZEBRA) TYPE LVC_ZEBRA
*"     REFERENCE(I_EDIT) TYPE LVC_EDIT
*"     REFERENCE(I_OPT) TYPE LVC_CWO
*"     REFERENCE(I_OBJECT) TYPE REF TO ZZHR_ALV_GRID
*" CHANGING
*"     REFERENCE(E_UCOMM) TYPE SY-UCOMM
*"     REFERENCE(IT_FLDCAT) TYPE LVC_T_FCAT
*"     REFERENCE(GT_OUTTAB) TYPE STANDARD TABLE
assign gt_outtab to <dyn_table>.
move title_text to screen_title.
assign i_object to <zogzilla>.
export <dyn_table> to memory id 'dawggs'.
export i_gridtitle to memory id 'i_gridtitle'.
export i_edit to memory id 'i_edit'.
export i_zebra to memory id 'i_zebra'.
export i_opt to memory id 'í_opt'.
export it_fldcat to memory id 'it_fldcat'.
case screen_number.
when '100'.
call screen 100.
when '200'.
call screen 200.
endcase.
endfunction.
process before output.
module status_0100.
process after input.
module user_command_0100.
rocess before output.
module status_0200.
process after input.
module user_command_0200.
*   INCLUDE LZHR_MISCO01                                               *
*&      Module STATUS_0100 OUTPUT
*       text
module status_0100 output.
import <dyn_table> from memory id 'dawggs'.
import i_gridtitle from memory id 'i_gridtitle'.
import i_edit from memory id 'i_edit'.
import i_opt from memory id 'í_opt'.
import it_fldcat from memory id 'it_fldcat'.
i_object = <zogzilla>.
call method i_object->display_grid
exporting
    i_gridtitle = i_gridtitle
    i_edit = i_edit
    i_zebra = i_zebra
    i_opt = i_opt
    g_fldcat = it_fldcat
    g_outtab = <dyn_table>
   changing
     it_fldcat = it_fldcat
     gt_outtab = <dyn_table>.
set pf-status '001'.
set titlebar '000' with screen_title.
endmodule.                 " STATUS_0100 OUTPUT
*&      Module STATUS_0200 OUTPUT
*       text
module status_0200 output.
import <dyn_table> from memory id 'dawggs'.
import i_gridtitle from memory id 'i_gridtitle'.
import i_edit from memory id 'i_edit'.
import i_opt from memory id 'í_opt'.
import it_fldcat from memory id 'it_fldcat'.
i_object = <zogzilla>.
call method i_object->display_grid
exporting
    i_gridtitle = i_gridtitle
    i_edit = i_edit
    i_zebra = i_zebra
    i_opt = i_opt
    g_fldcat = it_fldcat
    g_outtab = <dyn_table>
   changing
     it_fldcat = it_fldcat
     gt_outtab = <dyn_table>.
set pf-status '001'.
set titlebar '000' with screen_title.
endmodule.                 " STATUS_0200 OUTPUT
*   INCLUDE LZHR_MISCI01                                               *
*&      Module USER_COMMAND_0100 INPUT
*       text
module user_command_0100 input.
case sy-ucomm.
    when 'BACK'.
      leave to screen 0.
    when 'EXIT'.
      leave program.
    when 'RETURN'.
      leave program.
    when others.
endcase.
endmodule.                 " USER_COMMAND_0100 INPUT
*&      Module USER_COMMAND_0200 INPUT
*       text
module user_command_0200 input.
case sy-ucomm.
    when 'BACK'.
      leave to screen 0.
    when 'EXIT'.
      leave program.
    when 'RETURN'.
      leave program.
    when others.
endcase.
endmodule.                 " USER_COMMAND_0200 INPUT
Cheers
jimbo

ALV using ABAP Classes and Objects

Hi All,
I am trying to print the values in my internal table using ALV, using ABAP classes and objects. Here the title for columns are picked based on the title specified in the data element. I want to set the title of my columns by my own. how to achieve this ?. Please provide me a sample code if possible.
thanks & regards,
Navneeth.K

Hello Navneeth
The following sample report shows how to build and modify a fieldcatalog (routine <b>BUILD_FIELDCATALOG_KNB1</b>).
*& Report ZUS_SDN_ALVGRID_EVENTS
REPORT zus_sdn_alvgrid_events.
DATA:
gd_okcode        TYPE ui_func,
gt_fcat          TYPE lvc_t_fcat,
go_docking       TYPE REF TO cl_gui_docking_container,
go_grid1         TYPE REF TO cl_gui_alv_grid.
DATA:
gt_knb1          TYPE STANDARD TABLE OF knb1.
PARAMETERS:
p_bukrs      TYPE bukrs DEFAULT '2000' OBLIGATORY.
*       CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS:
      handle_hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid
        IMPORTING
          e_row_id
          e_column_id
          es_row_no
          sender.
ENDCLASS.                    "lcl_eventhandler DEFINITION
*       CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_hotspot_click.
*   define local data
    DATA:
      ls_knb1     TYPE knb1,
      ls_col_id   TYPE lvc_s_col.
    READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row_id-index.
    CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
    CASE e_column_id-fieldname.
      WHEN 'KUNNR'.
        SET PARAMETER ID 'KUN' FIELD ls_knb1-kunnr.
        SET PARAMETER ID 'BUK' FIELD ls_knb1-bukrs.
        CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
      WHEN 'ERNAM'.
*        SET PARAMETER ID 'USR' FIELD ls_knb1-ernam.
*        NOTE: no parameter id available, yet simply show the priciple
        CALL TRANSACTION 'SU01' AND SKIP FIRST SCREEN.
      WHEN OTHERS.
*       do nothing
    ENDCASE.
*   Set active cell to field BUKRS otherwise the focus is still on
*   field KUNNR which will always raise event HOTSPOT_CLICK
    ls_col_id-fieldname = 'BUKRS'.
    CALL METHOD go_grid1->set_current_cell_via_id
      EXPORTING
        is_row_id    = e_row_id
        is_column_id = ls_col_id.
ENDMETHOD.                    "handle_hotspot_click
ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
SELECT        * FROM knb1 INTO TABLE gt_knb1
         WHERE bukrs = p_bukrs.
* Create docking container
CREATE OBJECT go_docking
    EXPORTING
      parent                      = cl_gui_container=>screen0
      ratio                       = 90
    EXCEPTIONS
      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.
* Create ALV grid
CREATE OBJECT go_grid1
    EXPORTING
      i_parent          = go_docking
    EXCEPTIONS
      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.
* Set event handler
SET HANDLER:
    lcl_eventhandler=>handle_hotspot_click FOR go_grid1.
* Build fieldcatalog and set hotspot for field KUNNR
PERFORM build_fieldcatalog_knb1.
* Display data
CALL METHOD go_grid1->set_table_for_first_display
    CHANGING
      it_outtab       = gt_knb1
      it_fieldcatalog = gt_fcat
    EXCEPTIONS
      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.
ENDIF.
* Link the docking container to the target dynpro
CALL METHOD go_docking->link
    EXPORTING
      repid                       = syst-repid
      dynnr                       = '0100'
*      CONTAINER                   =
    EXCEPTIONS
      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.
ENDIF.
* ok-code field = GD_OKCODE
CALL SCREEN '0100'.
END-OF-SELECTION.
*&      Module STATUS_0100 OUTPUT
*       text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
*       text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
    WHEN 'BACK' OR
         'END' OR
         'CANC'.
      SET SCREEN 0. LEAVE SCREEN.
    WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Form BUILD_FIELDCATALOG_KNB1
*       text
* --> p1        text
* <-- p2        text
FORM build_fieldcatalog_knb1 .
* define local data
DATA:
    ls_fcat        TYPE lvc_s_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
    EXPORTING
*     I_BUFFER_ACTIVE              =
      i_structure_name             = 'KNB1'
*     I_CLIENT_NEVER_DISPLAY       = 'X'
*     I_BYPASSING_BUFFER           =
*     I_INTERNAL_TABNAME           =
    CHANGING
      ct_fieldcat                  = gt_fcat
    EXCEPTIONS
      inconsistent_interface       = 1
      program_error                = 2
      OTHERS                       = 3.
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 gt_fcat INTO ls_fcat
          WHERE ( fieldname = 'KUNNR' OR
                  fieldname = 'ERNAM' ).
    ls_fcat-hotspot = abap_true.
    ls_fcat-scrtext_s = '<short text>'. " short text of column
    ls_fcat-scrtext_m = '<medium text>'. " medium text of column
    ls_fcat-scrtext_l   = '<long text>'. " longtext text of column
    ls_fcat-tooltip      = '...'. " ALV control: Tool tip for column header
    ls_fcat-coltext    = '...'.   " ALV control: Column heading
    MODIFY gt_fcat FROM ls_fcat.
ENDLOOP.
ENDFORM.                    " BUILD_FIELDCATALOG_KNB1
Regards
Uwe

ALV tree using Objects

Hi,
I am making an ALV tree using objects and the code is crashing due to an error in the Screen 100 ( which I am using ). I tried to implement the example provided at http://www.sapdevelopment.co.uk/reporting/alv/alvtree.htm but that is not working.
Can anyone please tell me a working example or a brief tutorial so that I can correct the logical errors in my code.
Thanks,
Gaurav

Hi,
Check whether u have uncommented the PAI and PBO modules.
Try this one.
REPORT ZZZTEST_3
       NO STANDARD PAGE HEADING
       MESSAGE-ID zcs_cs_001.
1/ Report Name: ZZZ_ALV_TREE_DEMO
The definition and implementation of the event reciever class
include <icon>.
Predefine a local class for event handling to allow the
declaration of a reference variable before the class is defined.
class lcl_event_receiver definition deferred.
data :
     Alv Containers
     tree definition
       o_tree type ref to cl_gui_simple_tree,
     Event Handler
       o_eventreceiver     type ref to lcl_event_receiver,
       o_dockingcontainer TYPE REF TO cl_gui_docking_container.
data :
    node structures for tree building
      i_nodes type table of abdemonode, " node table def create bespoke
      w_nodes like line of i_nodes,     " work area
      i_tree_event type cntl_simple_events, " Itab for Tree Events
      w_tree_event type cntl_simple_event.   " Work area for Tree Events
data:
       v_ratio1            type i,     "docking container screen area
container screen area
       v_action(12)        type c.
Internal Tables Used for Object ALV Display.
data:
      i_toolbar           type table of stb_button, "Tool bar for Grid1
      i_exclude1          type ui_functions,
      i_exclude2          type ui_functions,
      i_groups            type lvc_t_sgrp, " Group Definitions
      i_selected_rows     type lvc_t_row.   " Select row type
constants: c_x(1)    type c value 'X',             "Checked
           c_a(1)    type c value 'A'.             "All Layouts
      CLASS lcl_event_receiver DEFINITION
class lcl_event_receiver definition.
event receiver definitions for ALV actions
public section.
    class-methods:
Status bar
       handle_user_command
        for event user_command of cl_gui_alv_grid
            importing e_ucomm,
Tree Actions
      handle_node_double_click
        for event node_double_click of cl_gui_simple_tree
        importing node_key,
Row Double click for dirll down.
       handle_double_click
         for event double_click of cl_gui_alv_grid
            importing e_row
                      e_column
                      es_row_no.
endclass.
Implementation
Every event handler that is specified below should also be set after
the object has been created. This is done in the PBO processing.
with the following command
SET HANDLER oEventreceiver->handle_toolbar FOR o_Alvgrid.
class lcl_event_receiver implementation.
method handle_user_command.
In event handler method for event USER_COMMAND: Query your
function codes defined in step 2 and react accordingly.
endmethod.
*&      Method handle_double_click
This method is called when the user double clicks on a line to drill
down.
The following are exported from the ALV
LVC_S_ROW
LVC_S_COL
LVC_S_ROID
method handle_double_click.
The double click drill down processing should be
coded in the form below.
endmethod.
*&      Method handle_node_double_click
This method handles the node double click event of the tree
LVC_S_ROW
LVC_S_COL
LVC_S_ROID
method handle_node_double_click.
   perform f9903_handle_node_double_click using node_key.
endmethod.
endclass.
INITIALIZATION
INITIALIZATION.
PERFORM f050_initialize_values.
FORM f050_initialize_values.
v_ratio1 = 30. "tree size
ENDFORM.                    " f050_initialize_values
START-OF-SELECTION
START-OF-SELECTION.
END-OF-SELECTION
END-OF-SELECTION.
CALL SCREEN 9001.
*Data Selection
FORM f9000_objects_create USING    value(pobject)
                             pparent
                             value(pratio)
                             value(prows)
                             value(pcolumns).
CASE pobject.
    WHEN 'o_dockingcontainer'.
      IF o_dockingcontainer IS INITIAL.
        CREATE OBJECT o_dockingcontainer
          EXPORTING
           side                        = v_dock_side1
            ratio                       = pratio "amount of screen
          EXCEPTIONS
            cntl_error                  = 1
            cntl_system_error           = 2
            create_error                = 3
            lifetime_error              = 4
            lifetime_dynpro_dynpro_link = 5
            others                      = 6.
        PERFORM f9800_error_handle USING text-e06.
      ENDIF.
      WHEN 'o_tree'.
      IF o_tree IS INITIAL.
        CREATE OBJECT o_tree
         EXPORTING
        LIFETIME                    =
           parent                      = pparent
        SHELLSTYLE                  =
           node_selection_mode         = o_tree->node_sel_mode_single
        HIDE_SELECTION              =
          name                        = 'Transactions'
         EXCEPTIONS
           lifetime_error              = 1
           cntl_system_error           = 2
           create_error                = 3
            failed                     = 4
           illegal_node_selection_mode = 5
           others                      = 6.
        PERFORM f9800_error_handle USING text-e06.
      ENDIF.
    WHEN 'o_eventreceiver'.
      IF o_eventreceiver IS INITIAL.
        CREATE OBJECT o_eventreceiver.
        PERFORM f9800_error_handle USING text-e08.
      ENDIF.
    WHEN OTHERS.
   do nothing
ENDCASE.
ENDFORM.                    " f9000_objects_create
*&      Form f9100_create_tree
      Create the Tree
     -->P_O_TREE tree data
FORM f9100_create_tree USING p_o_tree TYPE REF TO cl_gui_simple_tree.
REFRESH: i_nodes.
CLEAR: w_nodes.
Header Tree Folder
w_nodes-node_key = 'ROOT'.
w_nodes-isfolder = c_x.
w_nodes-expander = c_x.
w_nodes-text = 'Transactions'.
APPEND w_nodes TO i_nodes.
Adding Root Nodes for the tree.
Key:
NODE_KEY, RELATKEY, RELATSHIP, HIDDEN, DISABLED, ISFOLDER, N_IMAGE,
EXP_IMAGE, STYLE, LAST_HITEM, NO_BRANCH, EXPANDER, DRAGDROPID, TEXT
PERFORM f9101_node_list USING: '1' 'ROOT' '' '' '' c_x '' '' '' '' ''
                          c_x '' 'Sales Orders'.
Adding subitems for the root node.
PERFORM f9101_node_list USING:
                        Material Details
                          'VA01' '1' '' '' '' '' '@15@' '' '' '' '' ''
                          '' 'Create Sales Orders',
                        Document Details
                          'VA02' '1' '' '' '' '' '@15@' '' '' '' '' ''
                           '' 'Change Sales Orders'.
PERFORM f9101_node_list USING: '2' 'ROOT' '' '' '' c_x '' '' '' '' ''
                          c_x '' 'Deliveries'.
Adding subitems for the root node.
PERFORM f9101_node_list USING:
                        Material Details
                          'VL01' '2' '' '' '' '' '@15@' '' '' '' '' ''
                          '' 'Create Outbound Delivery',
                        Document Details
                          'VL02' '2' '' '' '' '' '@15@' '' '' '' '' ''
                          '' 'Change Outbound Delivery'.
add the nodes to the tree object,
PERFORM f9102_add_treenodes TABLES i_nodes
                             USING 'ABDEMONODE' "node definition
                                    p_o_tree.       "tree declaration
enabling event handlers for the tree
PERFORM f9103_tree_event_handle USING p_o_tree.
ENDFORM.                    " f9100_create_tree
*&      Form f9101_node_list
      Adding Nodes in a TREE
FORM f9101_node_list USING    value(pnodekey)
                             value(prelatkey)
                             value(prelatship)
                             value(phidden)
                             value(pdisabled)
                             value(pisfolder)
                             value(pimage)
                             value(pexpimage)
                             value(pstyle)
                             value(plastitem)
                             value(pnobranch)
                             value(pexpander)
                             value(pdragdropid)
                             value(ptext).
w_nodes-node_key   = pnodekey.
w_nodes-relatkey   = prelatkey.
w_nodes-relatship = prelatship. "Natural number
w_nodes-hidden     = phidden.
w_nodes-disabled   = pdisabled.
w_nodes-isfolder   = pisfolder.
w_nodes-n_image    = pimage. "Icons / embedded bitmap
w_nodes-exp_image = pexpimage. "Icons / embedded bitmap
w_nodes-style      = pstyle.
w_nodes-last_hitem = plastitem. "Tree Control: Column Name / Item
"Name
w_nodes-no_branch = pnobranch.
w_nodes-expander   = pexpander.
w_nodes-dragdropid = pdragdropid.
w_nodes-text       = ptext.
APPEND w_nodes TO i_nodes.
ENDFORM.                    " f9101_node_list
*&      Form f9102_add_treenodes
      Adding the Nodes to the Tree
     -->PI_NODES Table containg the Nodes
     -->PTABLE    Name of the Table structure name
     -->PO_TREE   tree object
FORM f9102_add_treenodes TABLES pi_nodes TYPE STANDARD TABLE
                        USING value(ptable)
                               po_tree TYPE REF TO cl_gui_simple_tree.
CALL METHOD po_tree->add_nodes
    EXPORTING
      table_structure_name           = ptable    "may need to change
      node_table                     = pi_nodes[]
    EXCEPTIONS
      error_in_node_table            = 1
      failed                         = 2
      dp_error                       = 3
      table_structure_name_not_found = 4
      OTHERS                         = 5
PERFORM f9800_error_handle USING text-e10.
ENDFORM.                    " f9102_add_treenodes
*&      Form f9103_tree_event_handle
      Event Handling for Tree.
     -->P_P_O_TREE text
FORM f9103_tree_event_handle USING
                            p_o_tree TYPE REF TO cl_gui_simple_tree.
w_tree_event-eventid = cl_gui_simple_tree=>eventid_node_double_click.
w_tree_event-appl_event = ' '. " process PAI if event occurs
APPEND w_tree_event TO i_tree_event.
CALL METHOD p_o_tree->set_registered_events
      EXPORTING
        events = i_tree_event
      EXCEPTIONS
        cntl_error                = 1
        cntl_system_error         = 2
        illegal_event_combination = 3.
IF sy-subrc <> 0.
   MESSAGE A000.
ENDIF.
IF o_eventreceiver IS INITIAL.
    CREATE OBJECT o_eventreceiver.
ENDIF.
SET HANDLER o_eventreceiver->handle_node_double_click FOR p_o_tree.
ENDFORM.                    " f9103_tree_event_handle
     -->P_IEXCLUDE text
     -->P_1150   text
FORM f9200_exclude_functions USING   pexclude LIKE i_exclude1
                               value(pfunction).
DATA: l_exclude TYPE ui_func.
l_exclude = pfunction.
APPEND l_exclude TO pexclude.
ENDFORM.                    " f9200_exclude_functions
*&      Form f9903_handle_node_double_click
      This form is used to handle the double click event for the tree
     -->P_NODE_KEY Node clicked.
FORM f9903_handle_node_double_click USING p_node_key.
CASE p_node_key.
    WHEN 'VA01'.
     SUBMIT ZZZ_TEST AND RETURN.
     CALL TRANSACTION 'VA01'. " and skip first screen.
    WHEN 'VA02'.
      CALL TRANSACTION 'VA02'. " and skip first screen.
    WHEN 'VL01'.
      CALL TRANSACTION 'VL01'. " and skip first screen.
    WHEN 'VL02'.
      CALL TRANSACTION 'VL02'. " and skip first screen.
    WHEN OTHERS.
    do nothning.
ENDCASE.
ENDFORM.                    " f9903_handle_node_double_click
*&      Form f9700_free_objects
This form handles the freeing of the following objects
ALV
Docking Container
     -->P_O_ALVGRID text
     -->P_0020   text
     -->P_0021   text
FORM f9700_free_objects USING pobject
                    value(ptype)
                    value(ptext).
Need to type the field symbol or it does not work
CASE ptype.
    WHEN 'DOCKING'.
      DATA: l_odock TYPE REF TO cl_gui_docking_container.
      l_odock = pobject.
      IF NOT ( l_odock IS INITIAL ).
        CALL METHOD l_odock->free
          EXCEPTIONS
            cntl_error        = 1
           cntl_system_error = 2
            OTHERS            = 3.
        CLEAR: pobject, l_odock.
        PERFORM f9800_error_handle USING ptext.
      ENDIF.
    WHEN 'TREE'.
      DATA: l_otree TYPE REF TO cl_gui_simple_tree.
      l_otree = pobject.
      IF NOT ( l_otree IS INITIAL ).
        CALL METHOD l_otree->free
          EXCEPTIONS
            cntl_error        = 1
           cntl_system_error = 2
            OTHERS            = 3.
        CLEAR: pobject, l_otree.
        PERFORM f9800_error_handle USING ptext.
      ENDIF.
    WHEN OTHERS.
   do something.
ENDCASE.
ENDFORM.                    " f9700_free_objects
*&      Form f9800_error_handle
      Handles Errors
     -->P_PTEXT text
FORM f9800_error_handle USING    value(ptext).
IF sy-subrc NE 0.
add your handling, for example
    CALL FUNCTION 'POPUP_TO_INFORM'
         EXPORTING
              titel = text-e01
              txt2 = sy-subrc
              txt1 = ptext.
ENDIF.
ENDFORM.                    " f9800_error_handle
*PBO & PAI Modules
*&      Module STATUS_9001 OUTPUT
      text
module status_9001 output.
Set the Status Bar
set pf-status 'Z_STATUS'.
Set the Title
set titlebar 'Z_TITLE'.
perform f9000_objects_create using:
            create docking container
              'o_dockingcontainer' '' v_ratio1 '' '',
            create a tree
              'o_tree' o_dockingcontainer '' '' '',
            Create the event reciever
              'o_eventreceiver' '' '' '' ''.
Create the Tree View.
perform f9100_create_tree using o_tree.
endmodule.                 " STATUS_9001 OUTPUT
*&      Module USER_COMMAND_9001 INPUT
      text
module user_command_9001 input.
case sy-ucomm.
    when 'EXIT' or 'CANC'.
      perform f9700_free_objects using:
                    o_tree 'TREE' text-E03,
                    o_dockingcontainer 'DOCKING' text-E05,
                    o_eventreceiver 'EVENT' text-e09.
leave program.
      leave.    " to SCREEN 0.
    when 'BACK'.
      perform f9700_free_objects using:
                    o_tree 'TREE' text-E03,
                    o_dockingcontainer 'DOCKING' text-e05,
                    o_eventreceiver 'EVENT' text-E09.
      set screen '0'.
      leave screen.
    when others.
endcase.
endmodule.                 " USER_COMMAND_9001 INPUT
Get back to me if u have any queries. Give me ur mail id, i will send one more sample code for ALV tree. This sample program will display only Tree not grid u can add ALV grid too.
Thanks & Regards,
Judith.

ALV USING OBJECTS

Similar Messages

Maybe you are looking for