SAP CK_F_ORDER_COSTING Function Module for









CK_F_ORDER_COSTING is a standard ck f order costing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ck f order costing FM, simply by entering the name CK_F_ORDER_COSTING into the relevant SAP transaction such as SE37 or SE38.

Function Group: CK00
Program Name: SAPLCK00
Main Program: SAPLCK00
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CK_F_ORDER_COSTING pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'CK_F_ORDER_COSTING'"
  EXPORTING
   CAUFVD_IMP =  "
*  FLG_ECONOMY = ' ' "
*  FLG_CALCUL = ' ' "
*  NO_CO_REFRESH = 0 "
*  VBKZ = ' ' "
*  NO_INFO_MESSAGE = ' ' "
*  LOG_INITIALIZE = 'X' "Initializes the Message Collector
*  NO_STATUS_CHECK = ' ' "
*  PLANNED_ORDER = ' ' "

 IMPORTING
   CAUFVD_EXP =  "

EXCEPTIONS
   NO_COSTING = 1
.



IMPORTING Parameters details for CK_F_ORDER_COSTING

CAUFVD_IMP -

Data type: CAUFVD
Optional: No
Call by Reference: No ( called with pass by value option)

FLG_ECONOMY -

Data type: CKI64A-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FLG_CALCUL -

Data type: CKI64A-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_CO_REFRESH -

Data type: SY-INDEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

VBKZ -

Data type: AFVGB-VBKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_INFO_MESSAGE -

Data type: CKI64A-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOG_INITIALIZE - Initializes the Message Collector

Data type: CKI64A-SELKZ
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_STATUS_CHECK -

Data type: CKI64A-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLANNED_ORDER -

Data type: CKI64A-SELKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CK_F_ORDER_COSTING

CAUFVD_EXP -

Data type: CAUFVD
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_COSTING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CK_F_ORDER_COSTING Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_caufvd_exp  TYPE CAUFVD, "   
lv_caufvd_imp  TYPE CAUFVD, "   
lv_no_costing  TYPE CAUFVD, "   
lv_flg_economy  TYPE CKI64A-SELKZ, "   SPACE
lv_flg_calcul  TYPE CKI64A-SELKZ, "   SPACE
lv_no_co_refresh  TYPE SY-INDEX, "   0
lv_vbkz  TYPE AFVGB-VBKZ, "   SPACE
lv_no_info_message  TYPE CKI64A-SELKZ, "   SPACE
lv_log_initialize  TYPE CKI64A-SELKZ, "   'X'
lv_no_status_check  TYPE CKI64A-SELKZ, "   SPACE
lv_planned_order  TYPE CKI64A-SELKZ. "   SPACE

  CALL FUNCTION 'CK_F_ORDER_COSTING'  "
    EXPORTING
         CAUFVD_IMP = lv_caufvd_imp
         FLG_ECONOMY = lv_flg_economy
         FLG_CALCUL = lv_flg_calcul
         NO_CO_REFRESH = lv_no_co_refresh
         VBKZ = lv_vbkz
         NO_INFO_MESSAGE = lv_no_info_message
         LOG_INITIALIZE = lv_log_initialize
         NO_STATUS_CHECK = lv_no_status_check
         PLANNED_ORDER = lv_planned_order
    IMPORTING
         CAUFVD_EXP = lv_caufvd_exp
    EXCEPTIONS
        NO_COSTING = 1
. " CK_F_ORDER_COSTING




ABAP code using 7.40 inline data declarations to call FM CK_F_ORDER_COSTING

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_flg_economy).
DATA(ld_flg_economy) = ' '.
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_flg_calcul).
DATA(ld_flg_calcul) = ' '.
 
"SELECT single INDEX FROM SY INTO @DATA(ld_no_co_refresh).
 
"SELECT single VBKZ FROM AFVGB INTO @DATA(ld_vbkz).
DATA(ld_vbkz) = ' '.
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_no_info_message).
DATA(ld_no_info_message) = ' '.
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_log_initialize).
DATA(ld_log_initialize) = 'X'.
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_no_status_check).
DATA(ld_no_status_check) = ' '.
 
"SELECT single SELKZ FROM CKI64A INTO @DATA(ld_planned_order).
DATA(ld_planned_order) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!