ISM_SD_SQP_EVENT_CHANGED_DATA SAP Function module

ISM_SD_SQP_EVENT_CHANGED_DATA is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISM_SD_SQP_EVENT_CHANGED_DATA into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JKSDQEVENTMNG_SQP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISM_SD_SQP_EVENT_CHANGED_DATA - ISM SD SQP EVENT CHANGED DATA

CALL FUNCTION 'ISM_SD_SQP_EVENT_CHANGED_DATA' "
  EXPORTING
    im_alvexec_tab =            " rjksdqplaneventexec_alv_tab
    im_event_tab =              " rjksdqeventmng_sqp_tab
    im_flag_changed =           " sy-datar
    im_alvfeature_tab =         " rjksdqplanevent_featurealv_tab
*   im_editor_ref =             " cl_gui_textedit
*   im_event_issue_tab =        " jksdsqpeventiss_tab
  IMPORTING
    ex_data_changed =           " xfeld
  EXCEPTIONS
    ERROR_CONTROL = 1           "
    .  "  ISM_SD_SQP_EVENT_CHANGED_DATA

ABAP code example for Function Module ISM_SD_SQP_EVENT_CHANGED_DATA

The ABAP code below is a full code listing to execute function module ISM_SD_SQP_EVENT_CHANGED_DATA including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_ex_data_changed  
 
 TYPE XFELD
.


DATA(ld_im_alvexec_tab) = 'Check type of data required'.

DATA(ld_im_event_tab) = 'Check type of data required'.

DATA(ld_im_flag_changed) = 'some text here'.

DATA(ld_im_alvfeature_tab) = 'some text here'.

DATA(ld_im_editor_ref) = 'some text here'.

DATA(ld_im_event_issue_tab) = 'some text here'.
.

CALL FUNCTION 'ISM_SD_SQP_EVENT_CHANGED_DATA'
  EXPORTING
    im_alvexec_tab =             ld_im_alvexec_tab
    im_event_tab =               ld_im_event_tab
    im_flag_changed =            ld_im_flag_changed
    im_alvfeature_tab =          ld_im_alvfeature_tab
*   im_editor_ref =              ld_im_editor_ref
*   im_event_issue_tab =         ld_im_event_issue_tab
  IMPORTING
    ex_data_changed =            ld_ex_data_changed
  EXCEPTIONS
    ERROR_CONTROL =              1
    .  "  ISM_SD_SQP_EVENT_CHANGED_DATA

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ex_data_changed
 
 TYPE XFELD ,
ld_im_alvexec_tab
 
 TYPE RJKSDQPLANEVENTEXEC_ALV_TAB ,
ld_im_event_tab
 
 TYPE RJKSDQEVENTMNG_SQP_TAB ,
ld_im_flag_changed
 
 TYPE SY-DATAR ,
ld_im_alvfeature_tab
 
 TYPE RJKSDQPLANEVENT_FEATUREALV_TAB ,
ld_im_editor_ref
 
 TYPE CL_GUI_TEXTEDIT ,
ld_im_event_issue_tab
 
 TYPE JKSDSQPEVENTISS_TAB .


ld_im_alvexec_tab = 'some text here'.
ld_im_event_tab = 'some text here'.
ld_im_flag_changed = 'some text here'.
ld_im_alvfeature_tab = 'some text here'.
ld_im_editor_ref = 'some text here'.
ld_im_event_issue_tab = 'some text here'.