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

Function CLM_UTIL2_RESTORE 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 'CLM_UTIL2_RESTORE'".
EXPORTING
I_OBJECT = "
* AUTOM_KORRNUM_SELECTION = 'X' "
* WITHOUT_DB_CHANGES = 'X' "
IMPORTING
DB_CHANGED = "
IT_DIFFERS = "
DB_SAVE_NECESSARY = "
INF_OR_SOURCE_NEW = "
OBJ_STATE = "
CHANGING
* E_GIT_CU_SOURCE = "ABAP Source
* E_GIT_OLD_SOURCE = "ABAP Source
* E_GIT_SMODISRC = "
* E_GIT_SMODILOG = "
* E_GIT_SMODISRC_MOD = "
EXCEPTIONS
BRACKETS_FAULT = 1 NO_MODIFICATION = 2 NO_CUSTOMER_SOURCE = 3 ACTION_ABORTED = 4 TYPE_NOT_SUPPORTED = 5
IMPORTING Parameters details for CLM_UTIL2_RESTORE
I_OBJECT -
Data type: SMODU_OBJECT_KEYOptional: No
Call by Reference: Yes
AUTOM_KORRNUM_SELECTION -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
WITHOUT_DB_CHANGES -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CLM_UTIL2_RESTORE
DB_CHANGED -
Data type: COptional: No
Call by Reference: Yes
IT_DIFFERS -
Data type: COptional: No
Call by Reference: Yes
DB_SAVE_NECESSARY -
Data type: COptional: No
Call by Reference: Yes
INF_OR_SOURCE_NEW -
Data type: COptional: No
Call by Reference: Yes
OBJ_STATE -
Data type: COptional: No
Call by Reference: Yes
CHANGING Parameters details for CLM_UTIL2_RESTORE
E_GIT_CU_SOURCE - ABAP Source
Data type: RSWSOURCETOptional: Yes
Call by Reference: Yes
E_GIT_OLD_SOURCE - ABAP Source
Data type: RSWSOURCETOptional: Yes
Call by Reference: Yes
E_GIT_SMODISRC -
Data type: SMODU_TAB_SMODISRCOptional: Yes
Call by Reference: Yes
E_GIT_SMODILOG -
Data type: SMODU_TAB_SMODILOGOptional: Yes
Call by Reference: Yes
E_GIT_SMODISRC_MOD -
Data type: SMODI_MOD_TABOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
BRACKETS_FAULT -
Data type:Optional: No
Call by Reference: Yes
NO_MODIFICATION -
Data type:Optional: No
Call by Reference: Yes
NO_CUSTOMER_SOURCE -
Data type:Optional: No
Call by Reference: Yes
ACTION_ABORTED -
Data type:Optional: No
Call by Reference: Yes
TYPE_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CLM_UTIL2_RESTORE 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_i_object | TYPE SMODU_OBJECT_KEY, " | |||
| lv_db_changed | TYPE C, " | |||
| lv_brackets_fault | TYPE C, " | |||
| lv_e_git_cu_source | TYPE RSWSOURCET, " | |||
| lv_it_differs | TYPE C, " | |||
| lv_no_modification | TYPE C, " | |||
| lv_e_git_old_source | TYPE RSWSOURCET, " | |||
| lv_autom_korrnum_selection | TYPE C, " 'X' | |||
| lv_e_git_smodisrc | TYPE SMODU_TAB_SMODISRC, " | |||
| lv_db_save_necessary | TYPE C, " | |||
| lv_no_customer_source | TYPE C, " | |||
| lv_without_db_changes | TYPE C, " 'X' | |||
| lv_action_aborted | TYPE C, " | |||
| lv_e_git_smodilog | TYPE SMODU_TAB_SMODILOG, " | |||
| lv_inf_or_source_new | TYPE C, " | |||
| lv_obj_state | TYPE C, " | |||
| lv_e_git_smodisrc_mod | TYPE SMODI_MOD_TAB, " | |||
| lv_type_not_supported | TYPE SMODI_MOD_TAB. " |
|   CALL FUNCTION 'CLM_UTIL2_RESTORE' " |
| EXPORTING | ||
| I_OBJECT | = lv_i_object | |
| AUTOM_KORRNUM_SELECTION | = lv_autom_korrnum_selection | |
| WITHOUT_DB_CHANGES | = lv_without_db_changes | |
| IMPORTING | ||
| DB_CHANGED | = lv_db_changed | |
| IT_DIFFERS | = lv_it_differs | |
| DB_SAVE_NECESSARY | = lv_db_save_necessary | |
| INF_OR_SOURCE_NEW | = lv_inf_or_source_new | |
| OBJ_STATE | = lv_obj_state | |
| CHANGING | ||
| E_GIT_CU_SOURCE | = lv_e_git_cu_source | |
| E_GIT_OLD_SOURCE | = lv_e_git_old_source | |
| E_GIT_SMODISRC | = lv_e_git_smodisrc | |
| E_GIT_SMODILOG | = lv_e_git_smodilog | |
| E_GIT_SMODISRC_MOD | = lv_e_git_smodisrc_mod | |
| EXCEPTIONS | ||
| BRACKETS_FAULT = 1 | ||
| NO_MODIFICATION = 2 | ||
| NO_CUSTOMER_SOURCE = 3 | ||
| ACTION_ABORTED = 4 | ||
| TYPE_NOT_SUPPORTED = 5 | ||
| . " CLM_UTIL2_RESTORE | ||
ABAP code using 7.40 inline data declarations to call FM CLM_UTIL2_RESTORE
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.| DATA(ld_autom_korrnum_selection) | = 'X'. | |||
| DATA(ld_without_db_changes) | = 'X'. | |||
Search for further information about these or an SAP related objects