K_UNITCOSTING_DIALOG_INIT SAP Function module

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

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

Pattern for FM K_UNITCOSTING_DIALOG_INIT - K UNITCOSTING DIALOG INIT

CALL FUNCTION 'K_UNITCOSTING_DIALOG_INIT' "
  EXPORTING
    rk70k_imp =                 " rk70k
    gs_bzobj_pointer_imp =      " kkek1_bzobj_pointer
    uc_imp =                    " kkek0_uc
    ref_uc_imp =                " kkek0_uc
    is_subscreen_imp =          " c
*   i_no_functiongroup_clear = SPACE  " xflag
  IMPORTING
    rc_exp =                    " rk70k-rc
    .  "  K_UNITCOSTING_DIALOG_INIT

ABAP code example for Function Module K_UNITCOSTING_DIALOG_INIT

The ABAP code below is a full code listing to execute function module K_UNITCOSTING_DIALOG_INIT 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_rc_exp  
 
 TYPE RK70K-RC
.


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

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

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

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

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

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

CALL FUNCTION 'K_UNITCOSTING_DIALOG_INIT'
  EXPORTING
    rk70k_imp =                  ld_rk70k_imp
    gs_bzobj_pointer_imp =       ld_gs_bzobj_pointer_imp
    uc_imp =                     ld_uc_imp
    ref_uc_imp =                 ld_ref_uc_imp
    is_subscreen_imp =           ld_is_subscreen_imp
*   i_no_functiongroup_clear =    ld_i_no_functiongroup_clear
  IMPORTING
    rc_exp =                     ld_rc_exp
    .  "  K_UNITCOSTING_DIALOG_INIT

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_rc_exp
 
 TYPE RK70K-RC ,
ld_rk70k_imp
 
 TYPE RK70K ,
ld_gs_bzobj_pointer_imp
 
 TYPE KKEK1_BZOBJ_POINTER ,
ld_uc_imp
 
 TYPE KKEK0_UC ,
ld_ref_uc_imp
 
 TYPE KKEK0_UC ,
ld_is_subscreen_imp
 
 TYPE C ,
ld_i_no_functiongroup_clear
 
 TYPE XFLAG .


ld_rk70k_imp = 'Check type of data required'.
ld_gs_bzobj_pointer_imp = 'Check type of data required'.
ld_uc_imp = 'Check type of data required'.
ld_ref_uc_imp = 'Check type of data required'.
ld_is_subscreen_imp = 'Check type of data required'.
ld_i_no_functiongroup_clear = 'Check type of data required'.