SAP ICM_CALL_PLUGIN Function Module for
ICM_CALL_PLUGIN is a standard icm call plugin 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 icm call plugin FM, simply by entering the name ICM_CALL_PLUGIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: SICM
Program Name: SAPLSICM
Main Program: SAPLSICM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICM_CALL_PLUGIN 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 'ICM_CALL_PLUGIN'".
EXPORTING
SUBHDLRQ = "Structure for the Subhandler Call
ACTION = "
IMPORTING
SUBHDL = "Subhandler Type
CENTRIES = "Type for a Cache Entry
CSTAT = "Cache Statistical Data
CHANGING
* INVALENT = "Invalidation of a Cache Entry
* INVALETAB = "Table of Cache Entries To Be Invalidated
* UPLOADENT = "Structure for Loading Data for the Cache
* LSTAT = "Structure for Querying Data from the Log Handler
* UPLURLTAB = "Table of Cache Entries To Be Invalidated
* LSTAT2 = "
* AUTHSTAT = "
* MODSTAT = "
* ESID = "
TABLES
* LINETAB = "Table for 128 Character Long Text
EXCEPTIONS
ICM_OP_FAILED = 1
IMPORTING Parameters details for ICM_CALL_PLUGIN
SUBHDLRQ - Structure for the Subhandler Call
Data type: ICM_SHDLRQOptional: No
Call by Reference: Yes
ACTION -
Data type: IOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ICM_CALL_PLUGIN
SUBHDL - Subhandler Type
Data type: ICM_SHDL_TOptional: No
Call by Reference: Yes
CENTRIES - Type for a Cache Entry
Data type: ICM_CENTRY_TOptional: No
Call by Reference: Yes
CSTAT - Cache Statistical Data
Data type: ICM_CSTATOptional: No
Call by Reference: Yes
CHANGING Parameters details for ICM_CALL_PLUGIN
INVALENT - Invalidation of a Cache Entry
Data type: ICM_INVALEOptional: Yes
Call by Reference: Yes
INVALETAB - Table of Cache Entries To Be Invalidated
Data type: ICM_INVALETABOptional: Yes
Call by Reference: Yes
UPLOADENT - Structure for Loading Data for the Cache
Data type: ICM_UPLOADOptional: Yes
Call by Reference: Yes
LSTAT - Structure for Querying Data from the Log Handler
Data type: ICM_LSTATOptional: Yes
Call by Reference: Yes
UPLURLTAB - Table of Cache Entries To Be Invalidated
Data type: ICM_UPLURLTABOptional: Yes
Call by Reference: Yes
LSTAT2 -
Data type: ICM_LSTAT2Optional: Yes
Call by Reference: Yes
AUTHSTAT -
Data type: ICM_AUTHSTATOptional: Yes
Call by Reference: Yes
MODSTAT -
Data type: ICM_MODSTATOptional: Yes
Call by Reference: Yes
ESID -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ICM_CALL_PLUGIN
LINETAB - Table for 128 Character Long Text
Data type: ICM_LINESOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ICM_OP_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICM_CALL_PLUGIN 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_subhdl | TYPE ICM_SHDL_T, " | |||
| lt_linetab | TYPE STANDARD TABLE OF ICM_LINES, " | |||
| lv_invalent | TYPE ICM_INVALE, " | |||
| lv_subhdlrq | TYPE ICM_SHDLRQ, " | |||
| lv_icm_op_failed | TYPE ICM_SHDLRQ, " | |||
| lv_action | TYPE I, " | |||
| lv_centries | TYPE ICM_CENTRY_T, " | |||
| lv_invaletab | TYPE ICM_INVALETAB, " | |||
| lv_cstat | TYPE ICM_CSTAT, " | |||
| lv_uploadent | TYPE ICM_UPLOAD, " | |||
| lv_lstat | TYPE ICM_LSTAT, " | |||
| lv_uplurltab | TYPE ICM_UPLURLTAB, " | |||
| lv_lstat2 | TYPE ICM_LSTAT2, " | |||
| lv_authstat | TYPE ICM_AUTHSTAT, " | |||
| lv_modstat | TYPE ICM_MODSTAT, " | |||
| lv_esid | TYPE STRING. " |
|   CALL FUNCTION 'ICM_CALL_PLUGIN' " |
| EXPORTING | ||
| SUBHDLRQ | = lv_subhdlrq | |
| ACTION | = lv_action | |
| IMPORTING | ||
| SUBHDL | = lv_subhdl | |
| CENTRIES | = lv_centries | |
| CSTAT | = lv_cstat | |
| CHANGING | ||
| INVALENT | = lv_invalent | |
| INVALETAB | = lv_invaletab | |
| UPLOADENT | = lv_uploadent | |
| LSTAT | = lv_lstat | |
| UPLURLTAB | = lv_uplurltab | |
| LSTAT2 | = lv_lstat2 | |
| AUTHSTAT | = lv_authstat | |
| MODSTAT | = lv_modstat | |
| ESID | = lv_esid | |
| TABLES | ||
| LINETAB | = lt_linetab | |
| EXCEPTIONS | ||
| ICM_OP_FAILED = 1 | ||
| . " ICM_CALL_PLUGIN | ||
ABAP code using 7.40 inline data declarations to call FM ICM_CALL_PLUGIN
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