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

Function FOPC_CASE_DELETE_CORRUPT 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 'FOPC_CASE_DELETE_CORRUPT'".
EXPORTING
I_CASE_GUID = "Technical Key of Case (Case GUID)
I_CASE_TYPE = "Case Type
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FOPC_CASE_DELETE_CORRUPT
I_CASE_GUID - Technical Key of Case (Case GUID)
Data type: SCMG_CASE_GUIDOptional: No
Call by Reference: Yes
I_CASE_TYPE - Case Type
Data type: SCMGCASE_TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FOPC_CASE_DELETE_CORRUPT 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_failed | TYPE STRING, " | |||
| lv_i_case_guid | TYPE SCMG_CASE_GUID, " | |||
| lv_i_case_type | TYPE SCMGCASE_TYPE. " |
|   CALL FUNCTION 'FOPC_CASE_DELETE_CORRUPT' " |
| EXPORTING | ||
| I_CASE_GUID | = lv_i_case_guid | |
| I_CASE_TYPE | = lv_i_case_type | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FOPC_CASE_DELETE_CORRUPT | ||
ABAP code using 7.40 inline data declarations to call FM FOPC_CASE_DELETE_CORRUPT
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