SAP CK37_COSTING_LOG_SET_OBJECT Function Module for









CK37_COSTING_LOG_SET_OBJECT is a standard ck37 costing log set object 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 ck37 costing log set object FM, simply by entering the name CK37_COSTING_LOG_SET_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function CK37_COSTING_LOG_SET_OBJECT 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 'CK37_COSTING_LOG_SET_OBJECT'"
  EXPORTING
*  DISPO = ' ' "
*  KALNR_BAL = ' ' "
*  PROCUREMENT_ALT = ' ' "
*  TYPE = ' ' "
*  EXTNR = ' ' "
*  POSNR = ' ' "
*  I_KALNR = ' ' "
*  I_CUOBJID = ' ' "
*  EKGRP = ' ' "
*  FEVOR = ' ' "
*  KOKRS = ' ' "
*  KOSTL = ' ' "
*  LABOR = ' ' "
*  PLANR = ' ' "
*  WERKS = ' ' "
*  MATNR = ' ' "

 IMPORTING
   OBJECT =  "
.



IMPORTING Parameters details for CK37_COSTING_LOG_SET_OBJECT

DISPO -

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

KALNR_BAL -

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

PROCUREMENT_ALT -

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

TYPE -

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

EXTNR -

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

POSNR -

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

I_KALNR -

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

I_CUOBJID -

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

EKGRP -

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

FEVOR -

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

KOKRS -

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

KOSTL -

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

LABOR -

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

PLANR -

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

WERKS -

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

MATNR -

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

EXPORTING Parameters details for CK37_COSTING_LOG_SET_OBJECT

OBJECT -

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

Copy and paste ABAP code example for CK37_COSTING_LOG_SET_OBJECT 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_dispo  TYPE T024D-DISPO, "   SPACE
lv_object  TYPE T024D, "   
lv_kalnr_bal  TYPE CMIOBJCK2-KALNR_BAL, "   SPACE
lv_procurement_alt  TYPE CKKVMK-SELKZ, "   SPACE
lv_type  TYPE CMIOBJCK3-TYPE, "   SPACE
lv_extnr  TYPE CKBS-EXTNR, "   SPACE
lv_posnr  TYPE CMISUBOBJCK-POSNR, "   SPACE
lv_i_kalnr  TYPE CK_KALNR1, "   SPACE
lv_i_cuobjid  TYPE CK_CUOBJID, "   SPACE
lv_ekgrp  TYPE T024-EKGRP, "   SPACE
lv_fevor  TYPE T024A-FEVOR, "   SPACE
lv_kokrs  TYPE TKA01-KOKRS, "   SPACE
lv_kostl  TYPE CSKS-KOSTL, "   SPACE
lv_labor  TYPE T024L-LABOR, "   SPACE
lv_planr  TYPE TC27-PLANR, "   SPACE
lv_werks  TYPE T001W-WERKS, "   SPACE
lv_matnr  TYPE CMIOBJCK1-MATNR. "   SPACE

  CALL FUNCTION 'CK37_COSTING_LOG_SET_OBJECT'  "
    EXPORTING
         DISPO = lv_dispo
         KALNR_BAL = lv_kalnr_bal
         PROCUREMENT_ALT = lv_procurement_alt
         TYPE = lv_type
         EXTNR = lv_extnr
         POSNR = lv_posnr
         I_KALNR = lv_i_kalnr
         I_CUOBJID = lv_i_cuobjid
         EKGRP = lv_ekgrp
         FEVOR = lv_fevor
         KOKRS = lv_kokrs
         KOSTL = lv_kostl
         LABOR = lv_labor
         PLANR = lv_planr
         WERKS = lv_werks
         MATNR = lv_matnr
    IMPORTING
         OBJECT = lv_object
. " CK37_COSTING_LOG_SET_OBJECT




ABAP code using 7.40 inline data declarations to call FM CK37_COSTING_LOG_SET_OBJECT

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 DISPO FROM T024D INTO @DATA(ld_dispo).
DATA(ld_dispo) = ' '.
 
 
"SELECT single KALNR_BAL FROM CMIOBJCK2 INTO @DATA(ld_kalnr_bal).
DATA(ld_kalnr_bal) = ' '.
 
"SELECT single SELKZ FROM CKKVMK INTO @DATA(ld_procurement_alt).
DATA(ld_procurement_alt) = ' '.
 
"SELECT single TYPE FROM CMIOBJCK3 INTO @DATA(ld_type).
DATA(ld_type) = ' '.
 
"SELECT single EXTNR FROM CKBS INTO @DATA(ld_extnr).
DATA(ld_extnr) = ' '.
 
"SELECT single POSNR FROM CMISUBOBJCK INTO @DATA(ld_posnr).
DATA(ld_posnr) = ' '.
 
DATA(ld_i_kalnr) = ' '.
 
DATA(ld_i_cuobjid) = ' '.
 
"SELECT single EKGRP FROM T024 INTO @DATA(ld_ekgrp).
DATA(ld_ekgrp) = ' '.
 
"SELECT single FEVOR FROM T024A INTO @DATA(ld_fevor).
DATA(ld_fevor) = ' '.
 
"SELECT single KOKRS FROM TKA01 INTO @DATA(ld_kokrs).
DATA(ld_kokrs) = ' '.
 
"SELECT single KOSTL FROM CSKS INTO @DATA(ld_kostl).
DATA(ld_kostl) = ' '.
 
"SELECT single LABOR FROM T024L INTO @DATA(ld_labor).
DATA(ld_labor) = ' '.
 
"SELECT single PLANR FROM TC27 INTO @DATA(ld_planr).
DATA(ld_planr) = ' '.
 
"SELECT single WERKS FROM T001W INTO @DATA(ld_werks).
DATA(ld_werks) = ' '.
 
"SELECT single MATNR FROM CMIOBJCK1 INTO @DATA(ld_matnr).
DATA(ld_matnr) = ' '.
 


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!