KFM_KF_DB_VALUE_INSERT_LIGHT SAP Function module

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

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

Pattern for FM KFM_KF_DB_VALUE_INSERT_LIGHT - KFM KF DB VALUE INSERT LIGHT

CALL FUNCTION 'KFM_KF_DB_VALUE_INSERT_LIGHT' "
  EXPORTING
*   iv_kf_id =                  " kfm_kf_id
*   iv_kf_adm_var =             " kfm_adm_var
    iv_kf_value =               " kfm_value
*   iv_kf_val_creation =        " kfm_timestamp
*   iv_kf_run_time =            " kfm_runtime
    iv_user_id =                " xubname
    iv_perform_on_commit =      " xflag
  EXCEPTIONS
    KEY_FIGURE_NOT_FOUND = 1    "
    UPDATE_IMPOSSIBLE = 2       "
    ALERT_CREATE_ERROR = 3      "
    .  "  KFM_KF_DB_VALUE_INSERT_LIGHT

ABAP code example for Function Module KFM_KF_DB_VALUE_INSERT_LIGHT

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

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

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

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

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

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

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

CALL FUNCTION 'KFM_KF_DB_VALUE_INSERT_LIGHT'
  EXPORTING
*   iv_kf_id =                   ld_iv_kf_id
*   iv_kf_adm_var =              ld_iv_kf_adm_var
    iv_kf_value =                ld_iv_kf_value
*   iv_kf_val_creation =         ld_iv_kf_val_creation
*   iv_kf_run_time =             ld_iv_kf_run_time
    iv_user_id =                 ld_iv_user_id
    iv_perform_on_commit =       ld_iv_perform_on_commit
  EXCEPTIONS
    KEY_FIGURE_NOT_FOUND =       1
    UPDATE_IMPOSSIBLE =          2
    ALERT_CREATE_ERROR =         3
    .  "  KFM_KF_DB_VALUE_INSERT_LIGHT

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
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_iv_kf_id
 
 TYPE KFM_KF_ID ,
ld_iv_kf_adm_var
 
 TYPE KFM_ADM_VAR ,
ld_iv_kf_value
 
 TYPE KFM_VALUE ,
ld_iv_kf_val_creation
 
 TYPE KFM_TIMESTAMP ,
ld_iv_kf_run_time
 
 TYPE KFM_RUNTIME ,
ld_iv_user_id
 
 TYPE XUBNAME ,
ld_iv_perform_on_commit
 
 TYPE XFLAG .


ld_iv_kf_id = 'Check type of data required'.
ld_iv_kf_adm_var = 'Check type of data required'.
ld_iv_kf_value = 'Check type of data required'.
ld_iv_kf_val_creation = 'Check type of data required'.
ld_iv_kf_run_time = 'Check type of data required'.
ld_iv_user_id = 'Check type of data required'.
ld_iv_perform_on_commit = 'Check type of data required'.