SAP CK_COSTINGRUN_GET_VALUES Function Module for









CK_COSTINGRUN_GET_VALUES is a standard ck costingrun get values 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 costingrun get values FM, simply by entering the name CK_COSTINGRUN_GET_VALUES into the relevant SAP transaction such as SE37 or SE38.

Function Group: CKCC03
Program Name: SAPLCKCC03
Main Program: SAPLCKCC03
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CK_COSTINGRUN_GET_VALUES 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_COSTINGRUN_GET_VALUES'"
EXPORTING
I_KALAID = "Name of costing run
I_KALADAT = "Costing run date
* I_REFRESH = "Read database data

IMPORTING
E_KALA = "Costing Run: General Data/Parameters
E_KLVAR = "Costing Variant
E_KALASUM = "
E_REFKALAID = "Name of costing run
E_REFKALADAT = "Costing run date

TABLES
* ET_KALST = "Costing Levels
* ET_KALF = "Error Log

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for CK_COSTINGRUN_GET_VALUES

I_KALAID - Name of costing run

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

I_KALADAT - Costing run date

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

I_REFRESH - Read database data

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

EXPORTING Parameters details for CK_COSTINGRUN_GET_VALUES

E_KALA - Costing Run: General Data/Parameters

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

E_KLVAR - Costing Variant

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

E_KALASUM -

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

E_REFKALAID - Name of costing run

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

E_REFKALADAT - Costing run date

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

TABLES Parameters details for CK_COSTINGRUN_GET_VALUES

ET_KALST - Costing Levels

Data type: CKIKALST
Optional: Yes
Call by Reference: Yes

ET_KALF - Error Log

Data type: KALF
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CK_COSTINGRUN_GET_VALUES 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_e_kala  TYPE KALA, "   
lt_et_kalst  TYPE STANDARD TABLE OF CKIKALST, "   
lv_i_kalaid  TYPE KALA-KALAID, "   
lv_not_found  TYPE KALA, "   
lt_et_kalf  TYPE STANDARD TABLE OF KALF, "   
lv_e_klvar  TYPE KALV-KLVAR, "   
lv_i_kaladat  TYPE KALA-KALADAT, "   
lv_e_kalasum  TYPE CKCC_KALA_SUM, "   
lv_i_refresh  TYPE CKCC_KALA_STATE-NOT_FOUND, "   
lv_e_refkalaid  TYPE KALA-KALAID, "   
lv_e_refkaladat  TYPE KALA-KALADAT. "   

  CALL FUNCTION 'CK_COSTINGRUN_GET_VALUES'  "
    EXPORTING
         I_KALAID = lv_i_kalaid
         I_KALADAT = lv_i_kaladat
         I_REFRESH = lv_i_refresh
    IMPORTING
         E_KALA = lv_e_kala
         E_KLVAR = lv_e_klvar
         E_KALASUM = lv_e_kalasum
         E_REFKALAID = lv_e_refkalaid
         E_REFKALADAT = lv_e_refkaladat
    TABLES
         ET_KALST = lt_et_kalst
         ET_KALF = lt_et_kalf
    EXCEPTIONS
        NOT_FOUND = 1
. " CK_COSTINGRUN_GET_VALUES




ABAP code using 7.40 inline data declarations to call FM CK_COSTINGRUN_GET_VALUES

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 KALAID FROM KALA INTO @DATA(ld_i_kalaid).
 
 
 
"SELECT single KLVAR FROM KALV INTO @DATA(ld_e_klvar).
 
"SELECT single KALADAT FROM KALA INTO @DATA(ld_i_kaladat).
 
 
"SELECT single NOT_FOUND FROM CKCC_KALA_STATE INTO @DATA(ld_i_refresh).
 
"SELECT single KALAID FROM KALA INTO @DATA(ld_e_refkalaid).
 
"SELECT single KALADAT FROM KALA INTO @DATA(ld_e_refkaladat).
 


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!