CK_F_F4_COSTING_MODEL SAP Function module

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

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

Pattern for FM CK_F_F4_COSTING_MODEL - CK F F4 COSTING MODEL

CALL FUNCTION 'CK_F_F4_COSTING_MODEL' "
  EXPORTING
*   i_bzobj = SPACE             " bzobj
*   i_tplclass = SPACE          " abc_class
    i_kokrs =                   " kokrs
*   i_multiple_choice = SPACE   " xflag
*   i_dynp_program_name =       " d020s-prog
*   i_dynp_field_name_model_id =   " dynfnam
*   i_dynp_field_name_model_descr =   " dynfnam
  IMPORTING
    f_costmodel =               " cki_s_costmodel
    et_costing_model =          " cki_t_costmodel
    .  "  CK_F_F4_COSTING_MODEL

ABAP code example for Function Module CK_F_F4_COSTING_MODEL

The ABAP code below is a full code listing to execute function module CK_F_F4_COSTING_MODEL 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_f_costmodel  
 
 TYPE CKI_S_COSTMODEL
,
ld_et_costing_model  
 
 TYPE CKI_T_COSTMODEL
.


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

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

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

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

SELECT single PROG 
  FROM D020S 
  INTO @DATA(ld_i_dynp_program_name).


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

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

CALL FUNCTION 'CK_F_F4_COSTING_MODEL'
  EXPORTING
*   i_bzobj =                    ld_i_bzobj
*   i_tplclass =                 ld_i_tplclass
    i_kokrs =                    ld_i_kokrs
*   i_multiple_choice =          ld_i_multiple_choice
*   i_dynp_program_name =        ld_i_dynp_program_name
*   i_dynp_field_name_model_id =    ld_i_dynp_field_name_model_id
*   i_dynp_field_name_model_descr =    ld_i_dynp_field_name_model_descr
  IMPORTING
    f_costmodel =                ld_f_costmodel
    et_costing_model =           ld_et_costing_model
    .  "  CK_F_F4_COSTING_MODEL

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_f_costmodel
 
 TYPE CKI_S_COSTMODEL ,
ld_i_bzobj
 
 TYPE BZOBJ ,
ld_et_costing_model
 
 TYPE CKI_T_COSTMODEL ,
ld_i_tplclass
 
 TYPE ABC_CLASS ,
ld_i_kokrs
 
 TYPE KOKRS ,
ld_i_multiple_choice
 
 TYPE XFLAG ,
ld_i_dynp_program_name
 
 TYPE D020S-PROG ,
ld_i_dynp_field_name_model_id
 
 TYPE DYNFNAM ,
ld_i_dynp_field_name_model_descr
 
 TYPE DYNFNAM .


ld_i_bzobj = 'Check type of data required'.
ld_i_tplclass = 'Check type of data required'.
ld_i_kokrs = 'Check type of data required'.
ld_i_multiple_choice = 'Check type of data required'.

SELECT single PROG 
  FROM D020S 
  INTO ld_i_dynp_program_name.

ld_i_dynp_field_name_model_id = 'Check type of data required'.
ld_i_dynp_field_name_model_descr = 'Check type of data required'.