FM_STRATEGY_FROM_KOKRS SAP Function module - Get Strategy ID assigned to Controlling Area

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

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

Pattern for FM FM_STRATEGY_FROM_KOKRS - FM STRATEGY FROM KOKRS

CALL FUNCTION 'FM_STRATEGY_FROM_KOKRS' "Get Strategy ID assigned to Controlling Area
  EXPORTING
*   i_applclass = 'FM'          " applclass     Application class for DD objects (not used)
*   i_subclass = '01'           " subclass      Subgroup by application class
*   i_abadrstratid = 'FMOA'     " abadrstratid  Strategy ID
    i_kokrs =                   " kokrs         Controlling Area
    i_catsappl =                " fmsp_catsappl  Target Component for CATS
  IMPORTING
    e_abadrenv =                " abadrenv      Environment for strategy
    .  "  FM_STRATEGY_FROM_KOKRS

ABAP code example for Function Module FM_STRATEGY_FROM_KOKRS

The ABAP code below is a full code listing to execute function module FM_STRATEGY_FROM_KOKRS 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_abadrenv  
 
 TYPE ABADRENV
.


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

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

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

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

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

CALL FUNCTION 'FM_STRATEGY_FROM_KOKRS'
  EXPORTING
*   i_applclass =                ld_i_applclass
*   i_subclass =                 ld_i_subclass
*   i_abadrstratid =             ld_i_abadrstratid
    i_kokrs =                    ld_i_kokrs
    i_catsappl =                 ld_i_catsappl
  IMPORTING
    e_abadrenv =                 ld_e_abadrenv
    .  "  FM_STRATEGY_FROM_KOKRS

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_abadrenv
 
 TYPE ABADRENV ,
ld_i_applclass
 
 TYPE APPLCLASS ,
ld_i_subclass
 
 TYPE SUBCLASS ,
ld_i_abadrstratid
 
 TYPE ABADRSTRATID ,
ld_i_kokrs
 
 TYPE KOKRS ,
ld_i_catsappl
 
 TYPE FMSP_CATSAPPL .


ld_i_applclass = 'Check type of data required'.
ld_i_subclass = 'Check type of data required'.
ld_i_abadrstratid = 'Check type of data required'.
ld_i_kokrs = 'Check type of data required'.
ld_i_catsappl = 'Check type of data required'.