SAP CK30_COSTINGLEVEL_STAT_FILL Function Module for









CK30_COSTINGLEVEL_STAT_FILL is a standard ck30 costinglevel stat fill 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 ck30 costinglevel stat fill FM, simply by entering the name CK30_COSTINGLEVEL_STAT_FILL into the relevant SAP transaction such as SE37 or SE38.

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



Function CK30_COSTINGLEVEL_STAT_FILL 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 'CK30_COSTINGLEVEL_STAT_FILL'"
EXPORTING
STEP = "
KVMK = "
MAXMSGTYP = "

CHANGING
* CL_OBJCOUNTER = "
* CL_ERROR_OBJCOUNTER = "
CL_MAXMSGTYP = "
* CL_STATUS = "
* CL_NEXTSTEPCOUNTER = "
.



IMPORTING Parameters details for CK30_COSTINGLEVEL_STAT_FILL

STEP -

Data type: CK_KALASTEP
Optional: No
Call by Reference: Yes

KVMK -

Data type: CKKVMK
Optional: No
Call by Reference: Yes

MAXMSGTYP -

Data type: CK_MAXMSGTYP
Optional: No
Call by Reference: Yes

CHANGING Parameters details for CK30_COSTINGLEVEL_STAT_FILL

CL_OBJCOUNTER -

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

CL_ERROR_OBJCOUNTER -

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

CL_MAXMSGTYP -

Data type: CK_MAXMSGTYP
Optional: No
Call by Reference: Yes

CL_STATUS -

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

CL_NEXTSTEPCOUNTER -

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

Copy and paste ABAP code example for CK30_COSTINGLEVEL_STAT_FILL 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_step  TYPE CK_KALASTEP, "   
lv_cl_objcounter  TYPE CK_ANZAHL, "   
lv_kvmk  TYPE CKKVMK, "   
lv_cl_error_objcounter  TYPE CK_ANZOBJ_FEH, "   
lv_maxmsgtyp  TYPE CK_MAXMSGTYP, "   
lv_cl_maxmsgtyp  TYPE CK_MAXMSGTYP, "   
lv_cl_status  TYPE CK_FEH_STA, "   
lv_cl_nextstepcounter  TYPE CK_AVANZ. "   

  CALL FUNCTION 'CK30_COSTINGLEVEL_STAT_FILL'  "
    EXPORTING
         STEP = lv_step
         KVMK = lv_kvmk
         MAXMSGTYP = lv_maxmsgtyp
    CHANGING
         CL_OBJCOUNTER = lv_cl_objcounter
         CL_ERROR_OBJCOUNTER = lv_cl_error_objcounter
         CL_MAXMSGTYP = lv_cl_maxmsgtyp
         CL_STATUS = lv_cl_status
         CL_NEXTSTEPCOUNTER = lv_cl_nextstepcounter
. " CK30_COSTINGLEVEL_STAT_FILL




ABAP code using 7.40 inline data declarations to call FM CK30_COSTINGLEVEL_STAT_FILL

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.

 
 
 
 
 
 
 
 


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!