SAP ISM_CONTRACT_KNVP_CHANGE Function Module for IS-M: Change Partner Roles for a Business Partner
ISM_CONTRACT_KNVP_CHANGE is a standard ism contract knvp change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M: Change Partner Roles for a Business Partner 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 ism contract knvp change FM, simply by entering the name ISM_CONTRACT_KNVP_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDCONTRACT_PARTNERFUNC
Program Name: SAPLJKSDCONTRACT_PARTNERFUNC
Main Program: SAPLJKSDCONTRACT_PARTNERFUNC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_CONTRACT_KNVP_CHANGE 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 'ISM_CONTRACT_KNVP_CHANGE'"IS-M: Change Partner Roles for a Business Partner.
EXPORTING
I_RJKSD_KNVP_KEY = "
* I_TESTRUN = 'X' "'X' = Test Run, ' ' = Update Run
IMPORTING
E_RETURN_TAB = "Return Parameter(s)
IMPORTING Parameters details for ISM_CONTRACT_KNVP_CHANGE
I_RJKSD_KNVP_KEY -
Data type: RJKSD_KNVP_KEYOptional: No
Call by Reference: No ( called with pass by value option)
I_TESTRUN - 'X' = Test Run, ' ' = Update Run
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISM_CONTRACT_KNVP_CHANGE
E_RETURN_TAB - Return Parameter(s)
Data type: BAPIRET2TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_CONTRACT_KNVP_CHANGE 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_return_tab | TYPE BAPIRET2TAB, " | |||
| lv_i_rjksd_knvp_key | TYPE RJKSD_KNVP_KEY, " | |||
| lv_i_testrun | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'ISM_CONTRACT_KNVP_CHANGE' "IS-M: Change Partner Roles for a Business Partner |
| EXPORTING | ||
| I_RJKSD_KNVP_KEY | = lv_i_rjksd_knvp_key | |
| I_TESTRUN | = lv_i_testrun | |
| IMPORTING | ||
| E_RETURN_TAB | = lv_e_return_tab | |
| . " ISM_CONTRACT_KNVP_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM ISM_CONTRACT_KNVP_CHANGE
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_i_testrun) | = 'X'. | |||
Search for further information about these or an SAP related objects