SAP C102_CHECK_SUB_DELETE Function Module for
C102_CHECK_SUB_DELETE is a standard c102 check sub delete 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 c102 check sub delete FM, simply by entering the name C102_CHECK_SUB_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: C102
Program Name: SAPLC102
Main Program: SAPLC102
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function C102_CHECK_SUB_DELETE 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 'C102_CHECK_SUB_DELETE'".
EXPORTING
I_ADDINF = "Additional Information
* I_ACTYPE = "Activity Type
* I_FLG_MESSAGE = ESP1_FALSE "
* I_FLG_MESSAGETAB = ESP1_FALSE "
IMPORTING
E_FLG_WARNING = "
E_FLG_ERROR = "Error Indicator
TABLES
X_IOTAB = "
EXCEPTIONS
ILLEGAL_INPUT = 1 INTERNAL_ERROR = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLC102_001 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLC102_002 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLC102_003 DE-EN-LANG-SWITCH-NO-TRANSLATION
EXIT_SAPLC102_004 DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for C102_CHECK_SUB_DELETE
I_ADDINF - Additional Information
Data type: RCGADDINFOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTYPE - Activity Type
Data type: RCGDIALCTR-ACTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_MESSAGE -
Data type: ESP1_BOOLEANDefault: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_MESSAGETAB -
Data type: ESP1_BOOLEANDefault: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for C102_CHECK_SUB_DELETE
E_FLG_WARNING -
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_ERROR - Error Indicator
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for C102_CHECK_SUB_DELETE
X_IOTAB -
Data type: RCGRHIOTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_INPUT - Invalid Entry
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal System Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for C102_CHECK_SUB_DELETE 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: | ||||
| lt_x_iotab | TYPE STANDARD TABLE OF RCGRHIOT, " | |||
| lv_i_addinf | TYPE RCGADDINF, " | |||
| lv_e_flg_warning | TYPE ESP1_BOOLEAN, " | |||
| lv_illegal_input | TYPE ESP1_BOOLEAN, " | |||
| lv_i_actype | TYPE RCGDIALCTR-ACTYPE, " | |||
| lv_e_flg_error | TYPE ESP1_BOOLEAN, " | |||
| lv_internal_error | TYPE ESP1_BOOLEAN, " | |||
| lv_i_flg_message | TYPE ESP1_BOOLEAN, " ESP1_FALSE | |||
| lv_i_flg_messagetab | TYPE ESP1_BOOLEAN. " ESP1_FALSE |
|   CALL FUNCTION 'C102_CHECK_SUB_DELETE' " |
| EXPORTING | ||
| I_ADDINF | = lv_i_addinf | |
| I_ACTYPE | = lv_i_actype | |
| I_FLG_MESSAGE | = lv_i_flg_message | |
| I_FLG_MESSAGETAB | = lv_i_flg_messagetab | |
| IMPORTING | ||
| E_FLG_WARNING | = lv_e_flg_warning | |
| E_FLG_ERROR | = lv_e_flg_error | |
| TABLES | ||
| X_IOTAB | = lt_x_iotab | |
| EXCEPTIONS | ||
| ILLEGAL_INPUT = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " C102_CHECK_SUB_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM C102_CHECK_SUB_DELETE
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 ACTYPE FROM RCGDIALCTR INTO @DATA(ld_i_actype). | ||||
| DATA(ld_i_flg_message) | = ESP1_FALSE. | |||
| DATA(ld_i_flg_messagetab) | = ESP1_FALSE. | |||
Search for further information about these or an SAP related objects