SAP ISM_SD_SQP_EVENT_UPD_TABLE_SET Function Module for
ISM_SD_SQP_EVENT_UPD_TABLE_SET is a standard ism sd sqp event upd table set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ism sd sqp event upd table set FM, simply by entering the name ISM_SD_SQP_EVENT_UPD_TABLE_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDQEVENTMNG_SQP_DB
Program Name: SAPLJKSDQEVENTMNG_SQP_DB
Main Program: SAPLJKSDQEVENTMNG_SQP_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SD_SQP_EVENT_UPD_TABLE_SET pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ISM_SD_SQP_EVENT_UPD_TABLE_SET'".
EXPORTING
IN_ACTIVITY = "
* IN_EVENTEX_OLD_TAB = "
IN_EVENTEX_TAB = "
* IN_FEATURE_OLD_TAB = "
IN_FEATURE_TAB = "
* IN_EVENT_ISSUE_NEW_TAB = "
* IN_EVENT_ISSUE_OLD_TAB = "
IMPORTING
EX_EVENTEX_UPDATE_TAB = "
EX_FEATURE_UPDATE_TAB = "
EX_EVENT_ISSUE_UPDATE_TAB = "
IMPORTING Parameters details for ISM_SD_SQP_EVENT_UPD_TABLE_SET
IN_ACTIVITY -
Data type: ACTIV_AUTHOptional: No
Call by Reference: Yes
IN_EVENTEX_OLD_TAB -
Data type: JKSDQPLANEVENTEX_TABOptional: Yes
Call by Reference: Yes
IN_EVENTEX_TAB -
Data type: JKSDQPLANEVENTEX_TABOptional: No
Call by Reference: Yes
IN_FEATURE_OLD_TAB -
Data type: JKSDQEVENTFEAT_TABOptional: Yes
Call by Reference: Yes
IN_FEATURE_TAB -
Data type: JKSDQEVENTFEAT_TABOptional: No
Call by Reference: Yes
IN_EVENT_ISSUE_NEW_TAB -
Data type: JKSDSQPEVENTISS_TABOptional: Yes
Call by Reference: Yes
IN_EVENT_ISSUE_OLD_TAB -
Data type: JKSDSQPEVENTISS_TABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_SQP_EVENT_UPD_TABLE_SET
EX_EVENTEX_UPDATE_TAB -
Data type: RJKSDQPLANEVENTEX_DB_TABOptional: No
Call by Reference: Yes
EX_FEATURE_UPDATE_TAB -
Data type: RJKSDQPLANEVENTFEATURE_DB_TABOptional: No
Call by Reference: Yes
EX_EVENT_ISSUE_UPDATE_TAB -
Data type: RJKSDSQPEVENTISSUE_DB_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_SD_SQP_EVENT_UPD_TABLE_SET Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_in_activity | TYPE ACTIV_AUTH, " | |||
| lv_ex_eventex_update_tab | TYPE RJKSDQPLANEVENTEX_DB_TAB, " | |||
| lv_in_eventex_old_tab | TYPE JKSDQPLANEVENTEX_TAB, " | |||
| lv_ex_feature_update_tab | TYPE RJKSDQPLANEVENTFEATURE_DB_TAB, " | |||
| lv_in_eventex_tab | TYPE JKSDQPLANEVENTEX_TAB, " | |||
| lv_ex_event_issue_update_tab | TYPE RJKSDSQPEVENTISSUE_DB_TAB, " | |||
| lv_in_feature_old_tab | TYPE JKSDQEVENTFEAT_TAB, " | |||
| lv_in_feature_tab | TYPE JKSDQEVENTFEAT_TAB, " | |||
| lv_in_event_issue_new_tab | TYPE JKSDSQPEVENTISS_TAB, " | |||
| lv_in_event_issue_old_tab | TYPE JKSDSQPEVENTISS_TAB. " |
|   CALL FUNCTION 'ISM_SD_SQP_EVENT_UPD_TABLE_SET' " |
| EXPORTING | ||
| IN_ACTIVITY | = lv_in_activity | |
| IN_EVENTEX_OLD_TAB | = lv_in_eventex_old_tab | |
| IN_EVENTEX_TAB | = lv_in_eventex_tab | |
| IN_FEATURE_OLD_TAB | = lv_in_feature_old_tab | |
| IN_FEATURE_TAB | = lv_in_feature_tab | |
| IN_EVENT_ISSUE_NEW_TAB | = lv_in_event_issue_new_tab | |
| IN_EVENT_ISSUE_OLD_TAB | = lv_in_event_issue_old_tab | |
| IMPORTING | ||
| EX_EVENTEX_UPDATE_TAB | = lv_ex_eventex_update_tab | |
| EX_FEATURE_UPDATE_TAB | = lv_ex_feature_update_tab | |
| EX_EVENT_ISSUE_UPDATE_TAB | = lv_ex_event_issue_update_tab | |
| . " ISM_SD_SQP_EVENT_UPD_TABLE_SET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SD_SQP_EVENT_UPD_TABLE_SET
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects