ISM_MAP_CONTRACT_GP_ROLE SAP Function module - IS-M: Determine Contracts for Same Business Partner Roles

ISM_MAP_CONTRACT_GP_ROLE 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_MAP_CONTRACT_GP_ROLE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISM_MAP_CONTRACT_GP_ROLE - ISM MAP CONTRACT GP ROLE

CALL FUNCTION 'ISM_MAP_CONTRACT_GP_ROLE' "IS-M: Determine Contracts for Same Business Partner Roles
  EXPORTING
    in_t_contract_source =      " rjksdcontracttab  IS-M: Contract Items
    in_t_contract_target =      " rjksdcontracttab  IS-M: Contract Items
    in_t_role_range =           " rjksd_parvw_range_tab  IS-M: Range Table for PARVW
*   in_no_lines_check =         " xfeld         Checkbox Field
  IMPORTING
    out_t_mapcontract =         " rjksdmapcontracttab  IS-M: Table for Similar Contracts
    out_t_protocol =            " bapiret2_tab  Error Messages
    .  "  ISM_MAP_CONTRACT_GP_ROLE

ABAP code example for Function Module ISM_MAP_CONTRACT_GP_ROLE

The ABAP code below is a full code listing to execute function module ISM_MAP_CONTRACT_GP_ROLE 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_out_t_mapcontract  
 
 TYPE RJKSDMAPCONTRACTTAB
,
ld_out_t_protocol  
 
 TYPE BAPIRET2_TAB
.


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

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

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

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

CALL FUNCTION 'ISM_MAP_CONTRACT_GP_ROLE'
  EXPORTING
    in_t_contract_source =       ld_in_t_contract_source
    in_t_contract_target =       ld_in_t_contract_target
    in_t_role_range =            ld_in_t_role_range
*   in_no_lines_check =          ld_in_no_lines_check
  IMPORTING
    out_t_mapcontract =          ld_out_t_mapcontract
    out_t_protocol =             ld_out_t_protocol
    .  "  ISM_MAP_CONTRACT_GP_ROLE

IF SY-SUBRC EQ 0.
  "All OK
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_out_t_mapcontract
 
 TYPE RJKSDMAPCONTRACTTAB ,
ld_in_t_contract_source
 
 TYPE RJKSDCONTRACTTAB ,
ld_out_t_protocol
 
 TYPE BAPIRET2_TAB ,
ld_in_t_contract_target
 
 TYPE RJKSDCONTRACTTAB ,
ld_in_t_role_range
 
 TYPE RJKSD_PARVW_RANGE_TAB ,
ld_in_no_lines_check
 
 TYPE XFELD .


ld_in_t_contract_source = 'Check type of data required'.
ld_in_t_contract_target = 'Check type of data required'.
ld_in_t_role_range = 'Check type of data required'.
ld_in_no_lines_check = 'Check type of data required'.