SAP ISM_CONTRACT_KNVP Function Module for IS-M: Check New Partner Roles

Search SAP Function Modules

ISM_CONTRACT_KNVP is a standard ism contract knvp 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: Check New Partner Roles 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 FM, simply by entering the name ISM_CONTRACT_KNVP 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 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'"IS-M: Check New Partner Roles
  EXPORTING
   I_RJKSD_KNVP_KEY =  "
   I_KUNNR_POS =  "
   I_PARVW_POS =  "
*  I_NEW_PARTNER_FUNCTION_TAB =  "Table Type for Partner Data
   I_VKORG =  "Sales Organization
   I_VTWEG =  "Distribution Channel
   I_SPART =  "Division
*  I_TESTRUN = 'X' "'X' = Test Run, ' ' = Update Run
*  I_CHECK_PARTNERROLE = ' ' "

EXCEPTIONS
   KUNNR_NOT_FOUND = 1    WRONG_PARVW = 2    KNVP_NOT_FOUND = 3    PARVW_CHANGE_NOT_POSSIBLE = 4    KNVP_LOCKED = 5    NO_DIFFERENCE_IN_PARTNERROLE = 6    MULTIPLE_RECORDS = 7 

.

IMPORTING Parameters details for ISM_CONTRACT_KNVP

I_RJKSD_KNVP_KEY -

Data type: RJKSD_KNVP_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

I_KUNNR_POS -

Data type: KUNNR_POS
Optional: No
Call by Reference: No ( called with pass by value option)

I_PARVW_POS -

Data type: PARVW_POS
Optional: No
Call by Reference: No ( called with pass by value option)

I_NEW_PARTNER_FUNCTION_TAB - Table Type for Partner Data

Data type: RJKSDPARTNER_TAB
Optional: Yes
Call by Reference: Yes

I_VKORG - Sales Organization

Data type: VKORG
Optional: No
Call by Reference: No ( called with pass by value option)

I_VTWEG - Distribution Channel

Data type: VTWEG
Optional: No
Call by Reference: No ( called with pass by value option)

I_SPART - Division

Data type: SPART
Optional: No
Call by Reference: No ( called with pass by value option)

I_TESTRUN - 'X' = Test Run, ' ' = Update Run

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHECK_PARTNERROLE -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

KUNNR_NOT_FOUND - Customer does not exist

Data type:
Optional: No
Call by Reference: Yes

WRONG_PARVW -

Data type:
Optional: No
Call by Reference: Yes

KNVP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PARVW_CHANGE_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

KNVP_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

NO_DIFFERENCE_IN_PARTNERROLE -

Data type:
Optional: No
Call by Reference: Yes

MULTIPLE_RECORDS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_CONTRACT_KNVP 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.

ABAP code using 7.40 inline data declarations to call FM ISM_CONTRACT_KNVP

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