Difference between Imlicit and Explicit enhancement

<b>Implecit enhancement :</b> These are provided in specific areas of standard source code:
1. At the end of the programs ( reports, includes, function pools, module pools)
2. At the begin and end of subroutine forms.
3. At the end of the functional module
4. At the end of all visabilities areas
In this case you do not need to create and enhancment spot. You directly put your curosr on the enhancement option and create your inplementations by right click.
<b>Explicit enhancement :</b> It can be anywhere in your source code. You need to explicitly have a enhancement point.It is of two types:
1. Enhancement spot : It is the point where you can add your code. It can have multiple implementations. All the implementations can active at a time but the sequince of executions of the implementations can be anything.
2. enhancement section : If you want to execute your own code instead of some portion standard code. Only the active implementation is execute. Only one implementation is active at a time.
2. Enhancement section

Comments

Post a Comment

Popular posts from this blog

Export data to xls using OOPS

* REPORT  ZDEMO_EXCEL20 * Demo for method zcl_excel_worksheet-bind_alv: * export data from ALV (CL_GUI_ALV_GRID) object to excel *--------------------------------------------------------------------* REPORT  zdemo_excel20. *----------------------------------------------------------------------* *       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. ENDCLASS.                    "lcl_handle_events DEFINITION *---------------------------------------------------------------------...
Read more

Factory method ALV sap abap

DATA lo_salv TYPE REF TO cl_salv_table , lo_functions TYPE REF TO cl_salv_functions_list , lo_columns TYPE REF TO cl_salv_columns_table , lo_columns2 TYPE REF TO cl_salv_columns_table , lo_column TYPE REF TO cl_salv_column_table , l_short TYPE scrtext_s , l_long TYPE scrtext_l , l_medium TYPE scrtext_m , lo_display TYPE REF TO cl_salv_display_settings , l_header_text TYPE lvc_title , not_found TYPE REF TO cx_salv_not_found , data_error TYPE REF TO cx_salv_data_error , l_string TYPE string , text TYPE string , oref TYPE REF TO cx_root . CONSTANTS : lc_info TYPE c VALUE 'I' , wc_error TYPE c VALUE wc_e . CLEAR : lo_salv , lo_functions . IF w_alv IS NOT INITIAL . * Use factory method TRY . CALL METHOD cl_salv_table => factory EXPORTING list_display = if_salv_c_bool_sa...
Read more

Delete Selected Record in ALV Report

form delete_selected_information.        data : i_lines type i.      *       Reading the index of the selected row in the ALV grid.   call method addressbook_grid->get_selected_rows        importing             et_index_rows = i_index_rows.      *       Check whether a row is selected or not. If not it popups a *       dialog box as warning to select a row.   describe table i_index_rows lines i_lines.        if i_lines = 0.     message i002.     exit.   endif.      *        Reads the selected rows into work area for display   loop at i_index_rows into i_selected_row.     if sy-tabix = 1.   ...
Read more