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

Function FOPC_CLONE_CASE_DOCUMENTS 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_CLONE_CASE_DOCUMENTS'".
EXPORTING
IS_CASE_CLONE = "Technical Key of Case (Case GUID)
IR_APPL_LOG = "SAP Application Log Handler Class
* I_LOG_DETLEVEL = "Application Log: Level of Detail
* I_LOG_PROBCLASS = "Application Log: Message Problem Class
IMPORTING
E_CLONED_CNT = "
E_WRITTEN_CNT = "
ER_DOCUMENTS_EXCEPTION = "Document Subsystem Exception
IMPORTING Parameters details for FOPC_CLONE_CASE_DOCUMENTS
IS_CASE_CLONE - Technical Key of Case (Case GUID)
Data type: FOPCD_S_CASE_CLONEOptional: No
Call by Reference: Yes
IR_APPL_LOG - SAP Application Log Handler Class
Data type: CL_FOPC_APPLICATION_LOGOptional: No
Call by Reference: Yes
I_LOG_DETLEVEL - Application Log: Level of Detail
Data type: BALLEVELOptional: Yes
Call by Reference: Yes
I_LOG_PROBCLASS - Application Log: Message Problem Class
Data type: BALPROBCLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FOPC_CLONE_CASE_DOCUMENTS
E_CLONED_CNT -
Data type: IOptional: No
Call by Reference: Yes
E_WRITTEN_CNT -
Data type: IOptional: No
Call by Reference: Yes
ER_DOCUMENTS_EXCEPTION - Document Subsystem Exception
Data type: CX_FOPC_DOCUMENTSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FOPC_CLONE_CASE_DOCUMENTS 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_e_cloned_cnt | TYPE I, " | |||
| lv_is_case_clone | TYPE FOPCD_S_CASE_CLONE, " | |||
| lv_ir_appl_log | TYPE CL_FOPC_APPLICATION_LOG, " | |||
| lv_e_written_cnt | TYPE I, " | |||
| lv_i_log_detlevel | TYPE BALLEVEL, " | |||
| lv_er_documents_exception | TYPE CX_FOPC_DOCUMENTS, " | |||
| lv_i_log_probclass | TYPE BALPROBCL. " |
|   CALL FUNCTION 'FOPC_CLONE_CASE_DOCUMENTS' " |
| EXPORTING | ||
| IS_CASE_CLONE | = lv_is_case_clone | |
| IR_APPL_LOG | = lv_ir_appl_log | |
| I_LOG_DETLEVEL | = lv_i_log_detlevel | |
| I_LOG_PROBCLASS | = lv_i_log_probclass | |
| IMPORTING | ||
| E_CLONED_CNT | = lv_e_cloned_cnt | |
| E_WRITTEN_CNT | = lv_e_written_cnt | |
| ER_DOCUMENTS_EXCEPTION | = lv_er_documents_exception | |
| . " FOPC_CLONE_CASE_DOCUMENTS | ||
ABAP code using 7.40 inline data declarations to call FM FOPC_CLONE_CASE_DOCUMENTS
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