SAP ISU_COM_CONTROL_ACCESS Function Module for
ISU_COM_CONTROL_ACCESS is a standard isu com control access 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 isu com control access FM, simply by entering the name ISU_COM_CONTROL_ACCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: EIDE_COM_CONTROL
Program Name: SAPLEIDE_COM_CONTROL
Main Program: SAPLEIDE_COM_CONTROL
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_COM_CONTROL_ACCESS 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 'ISU_COM_CONTROL_ACCESS'".
EXPORTING
X_COMEVENT = "
* X_CONTRACT = "
* X_ANLAGE = "
* X_EXT_POD = "
* X_INT_POD = "
* X_KEYDATE = SY-DATUM "
* X_COMMETHOD = "
IMPORTING
Y_EXT_POD = "
Y_INT_POD = "
TABLES
T_COMPARTNER = "
* T_ALL_SERVICES = "
* T_EVER = "
EXCEPTIONS
NOT_FOUND = 1 SERVPROV_NOT_FOUND = 2 PROGRAMMING_ERROR = 3 GENERAL_FAULT = 4
IMPORTING Parameters details for ISU_COM_CONTROL_ACCESS
X_COMEVENT -
Data type: ECOMEVENT-COMEVENTOptional: No
Call by Reference: No ( called with pass by value option)
X_CONTRACT -
Data type: EVER-VERTRAGOptional: Yes
Call by Reference: Yes
X_ANLAGE -
Data type: EANL-ANLAGEOptional: Yes
Call by Reference: Yes
X_EXT_POD -
Data type: EUITRANS-EXT_UIOptional: Yes
Call by Reference: Yes
X_INT_POD -
Data type: EUITRANS-INT_UIOptional: Yes
Call by Reference: Yes
X_KEYDATE -
Data type: DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_COMMETHOD -
Data type: IDE_COMMETHODOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_COM_CONTROL_ACCESS
Y_EXT_POD -
Data type: EUITRANS-EXT_UIOptional: No
Call by Reference: Yes
Y_INT_POD -
Data type: EUITRANS-INT_UIOptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_COM_CONTROL_ACCESS
T_COMPARTNER -
Data type: IECOMPARTNEROptional: No
Call by Reference: Yes
T_ALL_SERVICES -
Data type: IALLSERVICESOptional: Yes
Call by Reference: Yes
T_EVER -
Data type: IEEVEROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
SERVPROV_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
PROGRAMMING_ERROR -
Data type:Optional: No
Call by Reference: Yes
GENERAL_FAULT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_COM_CONTROL_ACCESS 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_not_found | TYPE STRING, " | |||
| lv_y_ext_pod | TYPE EUITRANS-EXT_UI, " | |||
| lv_x_comevent | TYPE ECOMEVENT-COMEVENT, " | |||
| lt_t_compartner | TYPE STANDARD TABLE OF IECOMPARTNER, " | |||
| lv_y_int_pod | TYPE EUITRANS-INT_UI, " | |||
| lv_x_contract | TYPE EVER-VERTRAG, " | |||
| lt_t_all_services | TYPE STANDARD TABLE OF IALLSERVICES, " | |||
| lv_servprov_not_found | TYPE IALLSERVICES, " | |||
| lt_t_ever | TYPE STANDARD TABLE OF IEEVER, " | |||
| lv_x_anlage | TYPE EANL-ANLAGE, " | |||
| lv_programming_error | TYPE EANL, " | |||
| lv_x_ext_pod | TYPE EUITRANS-EXT_UI, " | |||
| lv_general_fault | TYPE EUITRANS, " | |||
| lv_x_int_pod | TYPE EUITRANS-INT_UI, " | |||
| lv_x_keydate | TYPE DATUM, " SY-DATUM | |||
| lv_x_commethod | TYPE IDE_COMMETHOD. " |
|   CALL FUNCTION 'ISU_COM_CONTROL_ACCESS' " |
| EXPORTING | ||
| X_COMEVENT | = lv_x_comevent | |
| X_CONTRACT | = lv_x_contract | |
| X_ANLAGE | = lv_x_anlage | |
| X_EXT_POD | = lv_x_ext_pod | |
| X_INT_POD | = lv_x_int_pod | |
| X_KEYDATE | = lv_x_keydate | |
| X_COMMETHOD | = lv_x_commethod | |
| IMPORTING | ||
| Y_EXT_POD | = lv_y_ext_pod | |
| Y_INT_POD | = lv_y_int_pod | |
| TABLES | ||
| T_COMPARTNER | = lt_t_compartner | |
| T_ALL_SERVICES | = lt_t_all_services | |
| T_EVER | = lt_t_ever | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| SERVPROV_NOT_FOUND = 2 | ||
| PROGRAMMING_ERROR = 3 | ||
| GENERAL_FAULT = 4 | ||
| . " ISU_COM_CONTROL_ACCESS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_COM_CONTROL_ACCESS
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.| "SELECT single EXT_UI FROM EUITRANS INTO @DATA(ld_y_ext_pod). | ||||
| "SELECT single COMEVENT FROM ECOMEVENT INTO @DATA(ld_x_comevent). | ||||
| "SELECT single INT_UI FROM EUITRANS INTO @DATA(ld_y_int_pod). | ||||
| "SELECT single VERTRAG FROM EVER INTO @DATA(ld_x_contract). | ||||
| "SELECT single ANLAGE FROM EANL INTO @DATA(ld_x_anlage). | ||||
| "SELECT single EXT_UI FROM EUITRANS INTO @DATA(ld_x_ext_pod). | ||||
| "SELECT single INT_UI FROM EUITRANS INTO @DATA(ld_x_int_pod). | ||||
| DATA(ld_x_keydate) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects