RSKPI_GET_INFO_VARIANT_DESIGN SAP Function module - Read the infos of the Parameterisation of a KPI

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

Associated Function Group: RSKPI_VARIANT
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RSKPI_GET_INFO_VARIANT_DESIGN - RSKPI GET INFO VARIANT DESIGN

CALL FUNCTION 'RSKPI_GET_INFO_VARIANT_DESIGN' "Read the infos of the Parameterisation of a KPI
  EXPORTING
    i_kpi_id =                  " rskpi_kpi_id  Technical Name of KPI
  IMPORTING
    e_s_kpi_header =            " rskpi_s_kpi_header  Header Information for KPI
    e_t_threshold =             " rskpi_t_threshold  KPI definition: Thresholds
    e_tx_input_def =            " rskpi_tx_input_def  Definition of the input parameters of a KPI
    e_t_value_help_meta =       " rsdas_t_value_help_meta  Metadata for Input Help for Input Parameters
    e_t_message =               " rsdas_t_message  Structure for Messages
    e_subrc =                   " sysubrc       Return Value from ABAP Statements
    .  "  RSKPI_GET_INFO_VARIANT_DESIGN

ABAP code example for Function Module RSKPI_GET_INFO_VARIANT_DESIGN

The ABAP code below is a full code listing to execute function module RSKPI_GET_INFO_VARIANT_DESIGN 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_s_kpi_header  
 
 TYPE RSKPI_S_KPI_HEADER
,
ld_e_t_threshold  
 
 TYPE RSKPI_T_THRESHOLD
,
ld_e_tx_input_def  
 
 TYPE RSKPI_TX_INPUT_DEF
,
ld_e_t_value_help_meta  
 
 TYPE RSDAS_T_VALUE_HELP_META
,
ld_e_t_message  
 
 TYPE RSDAS_T_MESSAGE
,
ld_e_subrc  
 
 TYPE SYSUBRC
.


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

CALL FUNCTION 'RSKPI_GET_INFO_VARIANT_DESIGN'
  EXPORTING
    i_kpi_id =                   ld_i_kpi_id
  IMPORTING
    e_s_kpi_header =             ld_e_s_kpi_header
    e_t_threshold =              ld_e_t_threshold
    e_tx_input_def =             ld_e_tx_input_def
    e_t_value_help_meta =        ld_e_t_value_help_meta
    e_t_message =                ld_e_t_message
    e_subrc =                    ld_e_subrc
    .  "  RSKPI_GET_INFO_VARIANT_DESIGN

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_s_kpi_header
 
 TYPE RSKPI_S_KPI_HEADER ,
ld_i_kpi_id
 
 TYPE RSKPI_KPI_ID ,
ld_e_t_threshold
 
 TYPE RSKPI_T_THRESHOLD ,
ld_e_tx_input_def
 
 TYPE RSKPI_TX_INPUT_DEF ,
ld_e_t_value_help_meta
 
 TYPE RSDAS_T_VALUE_HELP_META ,
ld_e_t_message
 
 TYPE RSDAS_T_MESSAGE ,
ld_e_subrc
 
 TYPE SYSUBRC .


ld_i_kpi_id = 'Check type of data required'.