SAP ISU_M_KSV_UPDATE Function Module for INTERNAL: IS-U Migration: KSM Update
ISU_M_KSV_UPDATE is a standard isu m ksv update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Migration: KSM Update processing and below is the pattern details for this FM, 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 m ksv update FM, simply by entering the name ISU_M_KSV_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMIM
Program Name: SAPLEMIM
Main Program: SAPLEMIM
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_M_KSV_UPDATE 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_M_KSV_UPDATE'"INTERNAL: IS-U Migration: KSM Update.
EXPORTING
X_TEMKSV = "
X_WMODE = "Processing Type
X_UPDATE = "
IMPORTING
Y_COMMIT = "
EXCEPTIONS
NO_DB_UPD = 1 NO_NEWKEY = 2 NO_OLDKEY = 3 NO_KSV_UPD = 4 WMODE_ERROR = 5
IMPORTING Parameters details for ISU_M_KSV_UPDATE
X_TEMKSV -
Data type: TEMKSVOptional: No
Call by Reference: No ( called with pass by value option)
X_WMODE - Processing Type
Data type: TEMOB-WMODEOptional: No
Call by Reference: No ( called with pass by value option)
X_UPDATE -
Data type: EMGGEN-DB_UPDATEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_M_KSV_UPDATE
Y_COMMIT -
Data type: TEMFD-EMG_CHECKOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DB_UPD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_NEWKEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_OLDKEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_KSV_UPD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WMODE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_M_KSV_UPDATE 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_x_temksv | TYPE TEMKSV, " | |||
| lv_y_commit | TYPE TEMFD-EMG_CHECK, " | |||
| lv_no_db_upd | TYPE TEMFD, " | |||
| lv_x_wmode | TYPE TEMOB-WMODE, " | |||
| lv_no_newkey | TYPE TEMOB, " | |||
| lv_x_update | TYPE EMGGEN-DB_UPDATE, " | |||
| lv_no_oldkey | TYPE EMGGEN, " | |||
| lv_no_ksv_upd | TYPE EMGGEN, " | |||
| lv_wmode_error | TYPE EMGGEN. " |
|   CALL FUNCTION 'ISU_M_KSV_UPDATE' "INTERNAL: IS-U Migration: KSM Update |
| EXPORTING | ||
| X_TEMKSV | = lv_x_temksv | |
| X_WMODE | = lv_x_wmode | |
| X_UPDATE | = lv_x_update | |
| IMPORTING | ||
| Y_COMMIT | = lv_y_commit | |
| EXCEPTIONS | ||
| NO_DB_UPD = 1 | ||
| NO_NEWKEY = 2 | ||
| NO_OLDKEY = 3 | ||
| NO_KSV_UPD = 4 | ||
| WMODE_ERROR = 5 | ||
| . " ISU_M_KSV_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_M_KSV_UPDATE
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 EMG_CHECK FROM TEMFD INTO @DATA(ld_y_commit). | ||||
| "SELECT single WMODE FROM TEMOB INTO @DATA(ld_x_wmode). | ||||
| "SELECT single DB_UPDATE FROM EMGGEN INTO @DATA(ld_x_update). | ||||
Search for further information about these or an SAP related objects