RKE_GENERATE_SCENARIO_CODE SAP Function module

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

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

Pattern for FM RKE_GENERATE_SCENARIO_CODE - RKE GENERATE SCENARIO CODE

CALL FUNCTION 'RKE_GENERATE_SCENARIO_CODE' "
  EXPORTING
    i_repnam_gen =              " rs38m-programm
    i_repnam_source =           " rs38m-programm
    i_tabname =                 " tkepszk-tabname
    it_obj_fieldtab =           " keps_t_fieldtab
    it_val_fieldtab =           " keps_t_fieldtab
    it_perio_fnams =            " keps_t_perio_fnams
  EXCEPTIONS
    GENERATION_ERROR = 1        "
    .  "  RKE_GENERATE_SCENARIO_CODE

ABAP code example for Function Module RKE_GENERATE_SCENARIO_CODE

The ABAP code below is a full code listing to execute function module RKE_GENERATE_SCENARIO_CODE 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_repnam_gen) = some text here


DATA(ld_i_repnam_source) = some text here
 

SELECT single TABNAME 
  FROM TKEPSZK 
  INTO @DATA(ld_i_tabname).


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

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

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

CALL FUNCTION 'RKE_GENERATE_SCENARIO_CODE'
  EXPORTING
    i_repnam_gen =               ld_i_repnam_gen
    i_repnam_source =            ld_i_repnam_source
    i_tabname =                  ld_i_tabname
    it_obj_fieldtab =            ld_it_obj_fieldtab
    it_val_fieldtab =            ld_it_val_fieldtab
    it_perio_fnams =             ld_it_perio_fnams
  EXCEPTIONS
    GENERATION_ERROR =           1
    .  "  RKE_GENERATE_SCENARIO_CODE

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_repnam_gen
 
 TYPE RS38M-PROGRAMM ,
ld_i_repnam_source
 
 TYPE RS38M-PROGRAMM ,
ld_i_tabname
 
 TYPE TKEPSZK-TABNAME ,
ld_it_obj_fieldtab
 
 TYPE KEPS_T_FIELDTAB ,
ld_it_val_fieldtab
 
 TYPE KEPS_T_FIELDTAB ,
ld_it_perio_fnams
 
 TYPE KEPS_T_PERIO_FNAMS .



ld_i_repnam_gen = some text here

ld_i_repnam_source = some text here

SELECT single TABNAME 
  FROM TKEPSZK 
  INTO ld_i_tabname.

ld_it_obj_fieldtab = 'Check type of data required'.
ld_it_val_fieldtab = 'Check type of data required'.
ld_it_perio_fnams = 'Check type of data required'.