ISM_CONTRACT_KNVP_CREATE_CHECK SAP Function module - IS-M: Checks When Creating Control Record for New Partner Roles

ISM_CONTRACT_KNVP_CREATE_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISM_CONTRACT_KNVP_CREATE_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JKSDCONTRACT_PARTNERFUNC
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISM_CONTRACT_KNVP_CREATE_CHECK - ISM CONTRACT KNVP CREATE CHECK

CALL FUNCTION 'ISM_CONTRACT_KNVP_CREATE_CHECK' "IS-M: Checks When Creating Control Record for New Partner Roles
  EXPORTING
    i_kunnr_pos =               " kunnr_pos
    i_parvw_pos =               " parvw_pos
    i_vkorg =                   " vkorg         Sales Organization
    i_vtweg =                   " vtweg         Distribution Channel
    i_spart =                   " spart         Division
    i_validfrom =               " gueltigvon
  EXCEPTIONS
    INPUT_ERROR = 1             "               Incorrect Input
    .  "  ISM_CONTRACT_KNVP_CREATE_CHECK

ABAP code example for Function Module ISM_CONTRACT_KNVP_CREATE_CHECK

The ABAP code below is a full code listing to execute function module ISM_CONTRACT_KNVP_CREATE_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_i_kunnr_pos) = 'Check type of data required'.

DATA(ld_i_parvw_pos) = 'Check type of data required'.

DATA(ld_i_vkorg) = 'Check type of data required'.

DATA(ld_i_vtweg) = 'Check type of data required'.

DATA(ld_i_spart) = 'Check type of data required'.

DATA(ld_i_validfrom) = 'Check type of data required'.
.

CALL FUNCTION 'ISM_CONTRACT_KNVP_CREATE_CHECK'
  EXPORTING
    i_kunnr_pos =                ld_i_kunnr_pos
    i_parvw_pos =                ld_i_parvw_pos
    i_vkorg =                    ld_i_vkorg
    i_vtweg =                    ld_i_vtweg
    i_spart =                    ld_i_spart
    i_validfrom =                ld_i_validfrom
  EXCEPTIONS
    INPUT_ERROR =                1
    .  "  ISM_CONTRACT_KNVP_CREATE_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_kunnr_pos
 
 TYPE KUNNR_POS ,
ld_i_parvw_pos
 
 TYPE PARVW_POS ,
ld_i_vkorg
 
 TYPE VKORG ,
ld_i_vtweg
 
 TYPE VTWEG ,
ld_i_spart
 
 TYPE SPART ,
ld_i_validfrom
 
 TYPE GUELTIGVON .


ld_i_kunnr_pos = 'Check type of data required'.
ld_i_parvw_pos = 'Check type of data required'.
ld_i_vkorg = 'Check type of data required'.
ld_i_vtweg = 'Check type of data required'.
ld_i_spart = 'Check type of data required'.
ld_i_validfrom = 'Check type of data required'.