FKK_GET_CHALL_STRATEGY SAP Function module

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

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

Pattern for FM FKK_GET_CHALL_STRATEGY - FKK GET CHALL STRATEGY

CALL FUNCTION 'FKK_GET_CHALL_STRATEGY' "
  EXPORTING
    i_strat =                   " strat_cm_kk   Collection Strategy
    i_gpart =                   " gpart_kk      Business Partner Number
*   i_vkont =                   " vkont_kk      Contract Account Number
*   i_vtref =                   " vtref_kk      Reference Specifications from Contract
    i_cmgrp =                   " cmgrp_cm_kk   Collection Management: Master Data Group
*   i_grplvl =                  " grplvl_cm_kk  Master Data Grouping Level
  IMPORTING
    e_strat_chall =             " strat_chall_cm_kk  Challenger Collection Strategy
    e_fromdate =                " fromdate      Valid-from Date
    e_todate =                  " todate        Valid to Date
    .  "  FKK_GET_CHALL_STRATEGY

ABAP code example for Function Module FKK_GET_CHALL_STRATEGY

The ABAP code below is a full code listing to execute function module FKK_GET_CHALL_STRATEGY 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_e_strat_chall  
 
 TYPE STRAT_CHALL_CM_KK
,
ld_e_fromdate  
 
 TYPE FROMDATE
,
ld_e_todate  
 
 TYPE TODATE
.


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

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

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

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

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

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

CALL FUNCTION 'FKK_GET_CHALL_STRATEGY'
  EXPORTING
    i_strat =                    ld_i_strat
    i_gpart =                    ld_i_gpart
*   i_vkont =                    ld_i_vkont
*   i_vtref =                    ld_i_vtref
    i_cmgrp =                    ld_i_cmgrp
*   i_grplvl =                   ld_i_grplvl
  IMPORTING
    e_strat_chall =              ld_e_strat_chall
    e_fromdate =                 ld_e_fromdate
    e_todate =                   ld_e_todate
    .  "  FKK_GET_CHALL_STRATEGY

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_e_strat_chall
 
 TYPE STRAT_CHALL_CM_KK ,
ld_i_strat
 
 TYPE STRAT_CM_KK ,
ld_e_fromdate
 
 TYPE FROMDATE ,
ld_i_gpart
 
 TYPE GPART_KK ,
ld_e_todate
 
 TYPE TODATE ,
ld_i_vkont
 
 TYPE VKONT_KK ,
ld_i_vtref
 
 TYPE VTREF_KK ,
ld_i_cmgrp
 
 TYPE CMGRP_CM_KK ,
ld_i_grplvl
 
 TYPE GRPLVL_CM_KK .


ld_i_strat = 'Check type of data required'.
ld_i_gpart = 'Check type of data required'.
ld_i_vkont = 'Check type of data required'.
ld_i_vtref = 'Check type of data required'.
ld_i_cmgrp = 'Check type of data required'.
ld_i_grplvl = 'Check type of data required'.