Re: OOPS ALV

Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.

You can create them from TCode SE37.

Go through the following doc:

Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.

Function Module Interfaces

The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:

Syntax

... IMPORTING parameters

EXPORTING parameters

CHANGING parameters

TABLES table_parameters

{RAISING

The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with CLASS-METHODS. The additional option of defining table parameters using TABLES is obsolete.

Interface parameters

The interface parameters are defined on the relevant tab pages in the Function Builder.

IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.

EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.

CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.

TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.

Exceptions

The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.

The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.

The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.

Note

For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.

RFC is a technology which is used to access a functions (Modules) from

the remote systems.

If a function module is set as remote enabled which can be access from

the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.

A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".

But Normal function modules can not accessd from the remote system.

Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)

Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.

CALLING A FUNCTION MODULE:

1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"

--> Write the Corresponding FM name --> Hit Enter

2)The appropriate import ,export Parameters will be displayed in ur editor

3)Pass the Values Here.

events in report :-

Events in Dialog Program

PBO - Process Before Output

PAI - Process After Input

POH - Process on Help Request

POV - Process on Value Request.

Events in ABAP Programming

Classical Reporting:

INITIALIZATION

AT SELECTION-SCREEN OUTPUT

AT SELECTION-SCREEN

START-OF–SELECTION.

TOP-OF-PAGE

END-OF-PAGE

END-OF-SELECTION.

Events in Interactive Report

TOP-OF-PAGE DURING LINE-SELECTION

AT USER-COMMAND.

AT LINE-SELECTION

AT PF-FUNCTION KEY

Control Break events related to Internal Tables:

AT NEW FIELD

AT END OF FIELD

AT FIRST

AT LAST

Amit.

Former Member · ‎2008 Jun 28

Check out this code:



*&---------------------------------------------------------------------*
*& Report  ZTEST5
*&
*&---------------------------------------------------------------------*

REPORT  ZTEST5.
*&---------------------------------------------------------------------*
*& Report  ZCC_OOALV_CL_SALV_FUNCTIONS                                 *
*&                                                                     *
*&---------------------------------------------------------------------*
*&  Developer Name: Chidanand Chauhan                                  *
*&  Date: 15/05/2008                                                   *
*&  Description: SALV for the Program for the functionality.           *
*&                                                                     *
*&                                                                     *
*&---------------------------------------------------------------------*

*report  zcc_ooalv_cl_salv_functions.

data: ispfli type table of spfli.
field-symbols: <fs> type spfli.
data: gr_table type ref to cl_salv_table.
data: gr_functions type ref to cl_salv_functions.

data: gr_display type ref to cl_salv_display_settings.


data: gr_columns type ref to cl_salv_columns_table.
data: gr_column type ref to cl_salv_column_table.
data: color type lvc_s_colo.


data: gr_sorts type ref to cl_salv_sorts.

data: gr_agg type ref to cl_salv_aggregations.

data: gr_filter type ref to cl_salv_filters.

data: gr_layout type ref to cl_salv_layout.
data: key type salv_s_layout_key.

data: gr_selections type ref to cl_salv_selections.
data: xspfli type spfli.
data: gr_events type ref to cl_salv_events_table.


*----------------------------------------------------------------------*
* CLASS lcl_handle_events DEFINITION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
class lcl_handle_events definition.
  public section.
    methods:
    on_user_command for event added_function of cl_salv_events
    importing e_salv_function,

    on_double_click for event double_click of cl_salv_events_table
    importing row column,

    on_link_click for event link_click of cl_salv_events_table
    importing row column.

endclass. "lcl_handle_events DEFINITION


data: event_handler type ref to lcl_handle_events.

data: lt_celltype  type salv_t_int4_column,
      ls_celltype  type salv_s_int4_column.


*&>>>>-----------------------------------------------------------------*
*                  START OF SELECTION
*&>>>>-----------------------------------------------------------------*

start-of-selection.

  select * into table ispfli from spfli.



  cl_salv_table=>factory( importing r_salv_table = gr_table
  changing t_table = ispfli ).
  gr_functions = gr_table->get_functions( ).
  gr_functions->set_all( abap_true ).
*&>>>>-----------------------------------------------------------------*
* Next, add functions to the application toolbar. For this, use the
* CL_SALV_FUNCTIONS class. Create the object reference variable and
* receive the object using the GET_FUNCTIONS method of the GR_TABLE
* object. Call the method SET_ALL to force the ALV grid to show all
* standard functions.
*&---------------------------------------------------------------------*
  gr_display = gr_table->get_display_settings( ).
  gr_display->set_striped_pattern( cl_salv_display_settings=>true ).
  gr_display->set_list_header( 'Test Program for ZSALV By Sourav' ).
*&<<<<-----------------------------------------------------------------*

*&----------------------------------------------------------------------
* change the Heading Text of a column as well as the color of a column.
*&----------------------------------------------------------------------

  gr_columns = gr_table->get_columns( ).
  gr_column ?= gr_columns->get_column( 'CITYTO' ).
  gr_column->set_long_text( 'This is long text' ).
  gr_column->set_medium_text( 'This is med text' ).
  gr_column->set_short_text( 'This is sh' ).
  gr_column ?= gr_columns->get_column( 'CITYFROM' ).
  color-col = '6'.
  color-int = '1'.
  color-inv = '0'.
  gr_column->set_cell_type( if_salv_c_cell_type=>hotspot ).

  gr_column->set_color( color ).


*  data: val type SALV_DE_CONSTANT.
*  val = 1.
*  gr_column->SET_DROPDOWN_ENTRY( val ).
*&----------------------------------------------------------------------
*sorting to the ALV grid.
*&----------------------------------------------------------------------
  gr_sorts = gr_table->get_sorts( ).

**&----------------------------------------------------------------------
** sorted by CITYTO, we can add an aggregation to subtotal the DISTANCE
** by CITYTO. Create the object reference variable and receive the object
** using the GET_AGGREGATIONS method of the GR_TABLE object. Next, add
** the aggregation by calling the ADD_AGGREGATION method of the GR_SORTS
** object. We also need to modify the call to ADD_SORT to set
** the SUBTOTAL = ABAP_TRUE.
**&----------------------------------------------------------------------


  gr_sorts->add_sort( columnname = 'CITYTO' subtotal = abap_true ).
  gr_agg = gr_table->get_aggregations( ).
  gr_agg->add_aggregation( 'DISTANCE' ).
*&>>>>-----------------------------------------------------------------*
* Using the CL_SALV_FILTERS class setup some filters for the data
* in our ALV GRID. Create the object reference variable and receive the
* object using the GET_FILTERS method of the GR_TABLE object,and then
* simply called the method ADD_FILTER with the parameters.
*&>>>>-----------------------------------------------------------------*
  gr_filter = gr_table->get_filters( ).
  gr_filter->add_filter( columnname = 'CARRID' low = 'LH' ).

*&>>>>-----------------------------------------------------------------*
* If you want to allow the user to manage layouts of the ALV grid, you
* must use the class CL_SALV_LAYOUT.Create the object reference variable
* and receive the object using the GET_LAYOUT method of the GR_TABLE
* object. Then simply call the method SET_KEY with the parameters and
* set the save restriction using the SET_SAVE_RESTRICTION method.
*&>>>>-----------------------------------------------------------------*
  gr_layout = gr_table->get_layout( ).
  key-report = sy-repid.
  gr_layout->set_key( key ).
  gr_layout->set_save_restriction( cl_salv_layout=>restrict_none ).


*&>>>>-----------------------------------------------------------------*
*----------------------------SET GUI STATUS ---------------------------
* Go to function group SALV_METADATA_STATUS and copy the gui status
* ZSALV_TABLE_STANDARD into the ZCC_OOALV_CL_SALV_FUNCTIONS program.This
* is the standard gui status for the 2 Dimensional Table ALV grid. Once
* you have copied the status, set the screen status using the appropriate
* method of the object GR_TABLE. Go to the gui status and add a new
* button on the application toolbar and name it as #MYFUNCTION#.
*&>>>>-----------------------------------------------------------------*

  gr_table->set_screen_status(
  pfstatus = 'ZSALV_TABLE_STANDARD'
  report = sy-repid
  set_functions = gr_table->c_functions_all ).

*&>>>>-----------------------------------------------------------------*
* -----------------Get Event Handler.----------------------------------*
* Define the event handler method for DOUBLE_CLICK event and add the
* implementation for the ON_DOUBLE_CLICK event handler method. Remember
* to set the handler for the event.
*&>>>>-----------------------------------------------------------------*

  gr_events = gr_table->get_event( ).
  create object event_handler.
  set handler event_handler->on_user_command for gr_events.
  set handler event_handler->on_double_click for gr_events.
  set handler event_handler->on_link_click for gr_events.
* Set up selections.
  gr_selections = gr_table->get_selections( ).
  gr_selections->set_selection_mode( 1 ).       "Single


  gr_table->display( ).



*----------------------------------------------------------------------*
* CLASS lcl_handle_events IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
class lcl_handle_events implementation.
  method on_user_command.
* Get the selection rows
    data: lr_selections type ref to cl_salv_selections.
    data: lt_rows type salv_t_row.
    data: ls_rows type i.
    data: message type string.
    case e_salv_function.
      when '&FUNCTION'.
        lr_selections = gr_table->get_selections( ).
        lt_rows = lr_selections->get_selected_rows( ).
        read table lt_rows into ls_rows index 1.
        read table ispfli into xspfli index ls_rows.
        concatenate xspfli-carrid xspfli-connid
        xspfli-cityfrom xspfli-cityto
        into message separated by space.
        message i001(00) with 'You Clicked the button!' message.
    endcase.
  endmethod. "on_user_command

  method on_double_click.
    data: message type string.
    data: row_c(4) type c.
    row_c = row.
    concatenate 'Row' row_c 'Column' column
    into message separated by space.
    message i001(00) with 'You double-clicked on ' message.
  endmethod. "on_double_click



  method on_link_click.

    data: message type string.
    data: row_c(4) type c.
    row_c = row.
    concatenate 'Row' row_c 'Column' column
    into message separated by space.
    message i001(00) with 'You link-clicked on ' message.

  endmethod.      "lcl_handle_events IMPLEMENTATION

endclass. "lcl_handle_events IMPLEMENTATION

Former Member · ‎2008 Jun 28

Hi Srinivas,

Please go through the code regarding SALV this is the new technology which is being introduced in ECC6.0.

Please let me know if you want any more information.

&********** Please Reward Point if helpful************&


*&---------------------------------------------------------------------*
*& Report  ZCC_OOALV_CL_SALV_FUNCTIONS                                 *
*&                                                                     *
*&---------------------------------------------------------------------*
*&  Developer Name: Chidanand Chauhan                                  *
*&  Date: 15/05/2008                                                   *
*&  Description: SALV for the Program for the functionality.           *
*&                                                                     *
*&                                                                     *
*&---------------------------------------------------------------------*

report  zcc_ooalv_cl_salv_functions.

data: ispfli type table of spfli.
field-symbols: <fs> type spfli.
data: gr_table type ref to cl_salv_table.
data: gr_functions type ref to cl_salv_functions.

data: gr_display type ref to cl_salv_display_settings.


data: gr_columns type ref to cl_salv_columns_table.
data: gr_column type ref to cl_salv_column_table.
data: color type lvc_s_colo.


data: gr_sorts type ref to cl_salv_sorts.

data: gr_agg type ref to cl_salv_aggregations.

data: gr_filter type ref to cl_salv_filters.

data: gr_layout type ref to cl_salv_layout.
data: key type salv_s_layout_key.

data: gr_selections type ref to cl_salv_selections.
data: xspfli type spfli.
data: gr_events type ref to cl_salv_events_table.


*----------------------------------------------------------------------*
* CLASS lcl_handle_events DEFINITION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
class lcl_handle_events definition.
  public section.
    methods:
    on_user_command for event added_function of cl_salv_events
    importing e_salv_function,

    on_double_click for event double_click of cl_salv_events_table
    importing row column,

    on_link_click for event link_click of cl_salv_events_table
    importing row column.

endclass. "lcl_handle_events DEFINITION


data: event_handler type ref to lcl_handle_events.

data: lt_celltype  type salv_t_int4_column,
      ls_celltype  type salv_s_int4_column.


*&>>>>-----------------------------------------------------------------*
*                  START OF SELECTION
*&>>>>-----------------------------------------------------------------*

start-of-selection.

  select * into table ispfli from spfli.



  cl_salv_table=>factory( importing r_salv_table = gr_table
  changing t_table = ispfli ).
  gr_functions = gr_table->get_functions( ).
  gr_functions->set_all( abap_true ).
*&>>>>-----------------------------------------------------------------*
* Next, add functions to the application toolbar. For this, use the
* CL_SALV_FUNCTIONS class. Create the object reference variable and
* receive the object using the GET_FUNCTIONS method of the GR_TABLE
* object. Call the method SET_ALL to force the ALV grid to show all
* standard functions.
*&---------------------------------------------------------------------*
  gr_display = gr_table->get_display_settings( ).
  gr_display->set_striped_pattern( cl_salv_display_settings=>true ).
  gr_display->set_list_header( 'Test Program for ZSALV By Chidanand' ).
*&<<<<-----------------------------------------------------------------*

*&----------------------------------------------------------------------
* change the Heading Text of a column as well as the color of a column.
*&----------------------------------------------------------------------

  gr_columns = gr_table->get_columns( ).
  gr_column ?= gr_columns->get_column( 'CITYTO' ).
  gr_column->set_long_text( 'This is long text' ).
  gr_column->set_medium_text( 'This is med text' ).
  gr_column->set_short_text( 'This is sh' ).
  gr_column ?= gr_columns->get_column( 'CITYFROM' ).
  color-col = '6'.
  color-int = '1'.
  color-inv = '0'.
  gr_column->set_cell_type( if_salv_c_cell_type=>hotspot ).

  gr_column->set_color( color ).


*  data: val type SALV_DE_CONSTANT.
*  val = 1.
*  gr_column->SET_DROPDOWN_ENTRY( val ).
*&----------------------------------------------------------------------
*sorting to the ALV grid.
*&----------------------------------------------------------------------
  gr_sorts = gr_table->get_sorts( ).

**&----------------------------------------------------------------------
** sorted by CITYTO, we can add an aggregation to subtotal the DISTANCE
** by CITYTO. Create the object reference variable and receive the object
** using the GET_AGGREGATIONS method of the GR_TABLE object. Next, add
** the aggregation by calling the ADD_AGGREGATION method of the GR_SORTS
** object. We also need to modify the call to ADD_SORT to set
** the SUBTOTAL = ABAP_TRUE.
**&----------------------------------------------------------------------


  gr_sorts->add_sort( columnname = 'CITYTO' subtotal = abap_true ).
  gr_agg = gr_table->get_aggregations( ).
  gr_agg->add_aggregation( 'DISTANCE' ).
*&>>>>-----------------------------------------------------------------*
* Using the CL_SALV_FILTERS class setup some filters for the data
* in our ALV GRID. Create the object reference variable and receive the
* object using the GET_FILTERS method of the GR_TABLE object,and then
* simply called the method ADD_FILTER with the parameters.
*&>>>>-----------------------------------------------------------------*
  gr_filter = gr_table->get_filters( ).
  gr_filter->add_filter( columnname = 'CARRID' low = 'LH' ).

*&>>>>-----------------------------------------------------------------*
* If you want to allow the user to manage layouts of the ALV grid, you
* must use the class CL_SALV_LAYOUT.Create the object reference variable
* and receive the object using the GET_LAYOUT method of the GR_TABLE
* object. Then simply call the method SET_KEY with the parameters and
* set the save restriction using the SET_SAVE_RESTRICTION method.
*&>>>>-----------------------------------------------------------------*
  gr_layout = gr_table->get_layout( ).
  key-report = sy-repid.
  gr_layout->set_key( key ).
  gr_layout->set_save_restriction( cl_salv_layout=>restrict_none ).


*&>>>>-----------------------------------------------------------------*
*----------------------------SET GUI STATUS ---------------------------
* Go to function group SALV_METADATA_STATUS and copy the gui status
* ZSALV_TABLE_STANDARD into the ZCC_OOALV_CL_SALV_FUNCTIONS program.This
* is the standard gui status for the 2 Dimensional Table ALV grid. Once
* you have copied the status, set the screen status using the appropriate
* method of the object GR_TABLE. Go to the gui status and add a new
* button on the application toolbar and name it as u201CMYFUNCTIONu201D.
*&>>>>-----------------------------------------------------------------*

  gr_table->set_screen_status(
  pfstatus = 'ZSALV_TABLE_STANDARD'
  report = sy-repid
  set_functions = gr_table->c_functions_all ).

*&>>>>-----------------------------------------------------------------*
* -----------------Get Event Handler.----------------------------------*
* Define the event handler method for DOUBLE_CLICK event and add the
* implementation for the ON_DOUBLE_CLICK event handler method. Remember
* to set the handler for the event.
*&>>>>-----------------------------------------------------------------*

  gr_events = gr_table->get_event( ).
  create object event_handler.
  set handler event_handler->on_user_command for gr_events.
  set handler event_handler->on_double_click for gr_events.
  set handler event_handler->on_link_click for gr_events.
* Set up selections.
  gr_selections = gr_table->get_selections( ).
  gr_selections->set_selection_mode( 1 ).       "Single


  gr_table->display( ).



*----------------------------------------------------------------------*
* CLASS lcl_handle_events IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
class lcl_handle_events implementation.
  method on_user_command.
* Get the selection rows
    data: lr_selections type ref to cl_salv_selections.
    data: lt_rows type salv_t_row.
    data: ls_rows type i.
    data: message type string.
    case e_salv_function.
      when '&FUNCTION'.
        lr_selections = gr_table->get_selections( ).
        lt_rows = lr_selections->get_selected_rows( ).
        read table lt_rows into ls_rows index 1.
        read table ispfli into xspfli index ls_rows.
        concatenate xspfli-carrid xspfli-connid
        xspfli-cityfrom xspfli-cityto
        into message separated by space.
        message i001(00) with 'You Clicked the button!' message.
    endcase.
  endmethod. "on_user_command

  method on_double_click.
    data: message type string.
    data: row_c(4) type c.
    row_c = row.
    concatenate 'Row' row_c 'Column' column
    into message separated by space.
    message i001(00) with 'You double-clicked on ' message.
  endmethod. "on_double_click



  method on_link_click.

    data: message type string.
    data: row_c(4) type c.
    row_c = row.
    concatenate 'Row' row_c 'Column' column
    into message separated by space.
    message i001(00) with 'You link-clicked on ' message.

  endmethod.      "lcl_handle_events IMPLEMENTATION

endclass. "lcl_handle_events IMPLEMENTATION

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My Account

My Account

OOPS ALV