KFM_KF_DB_VALUE_INSERT SAP Function module

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

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

Pattern for FM KFM_KF_DB_VALUE_INSERT - KFM KF DB VALUE INSERT

CALL FUNCTION 'KFM_KF_DB_VALUE_INSERT' "
  EXPORTING
*   i_kf_id =                   " kfm_kf_id
*   i_kf_adm_var =              " kfm_adm_var
    i_kf_value =                " kfm_value
*   i_kf_val_creation =         " kfm_timestamp
*   i_kf_run_time =             " kfm_runtime
    i_user_id =                 " xubname
  EXCEPTIONS
    KEY_FIGURE_NOT_FOUND = 1    "
    UPDATE_IMPOSSIBLE = 2       "
    DB_ERROR = 3                "
    ALERT_CREATE_ERROR = 4      "
    .  "  KFM_KF_DB_VALUE_INSERT

ABAP code example for Function Module KFM_KF_DB_VALUE_INSERT

The ABAP code below is a full code listing to execute function module KFM_KF_DB_VALUE_INSERT 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_kf_id) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'KFM_KF_DB_VALUE_INSERT'
  EXPORTING
*   i_kf_id =                    ld_i_kf_id
*   i_kf_adm_var =               ld_i_kf_adm_var
    i_kf_value =                 ld_i_kf_value
*   i_kf_val_creation =          ld_i_kf_val_creation
*   i_kf_run_time =              ld_i_kf_run_time
    i_user_id =                  ld_i_user_id
  EXCEPTIONS
    KEY_FIGURE_NOT_FOUND =       1
    UPDATE_IMPOSSIBLE =          2
    DB_ERROR =                   3
    ALERT_CREATE_ERROR =         4
    .  "  KFM_KF_DB_VALUE_INSERT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_kf_id
 
 TYPE KFM_KF_ID ,
ld_i_kf_adm_var
 
 TYPE KFM_ADM_VAR ,
ld_i_kf_value
 
 TYPE KFM_VALUE ,
ld_i_kf_val_creation
 
 TYPE KFM_TIMESTAMP ,
ld_i_kf_run_time
 
 TYPE KFM_RUNTIME ,
ld_i_user_id
 
 TYPE XUBNAME .


ld_i_kf_id = 'Check type of data required'.
ld_i_kf_adm_var = 'Check type of data required'.
ld_i_kf_value = 'Check type of data required'.
ld_i_kf_val_creation = 'Check type of data required'.
ld_i_kf_run_time = 'Check type of data required'.
ld_i_user_id = 'Check type of data required'.