SAP CKML_RUN_PERIOD_GET Function Module for









CKML_RUN_PERIOD_GET is a standard ckml run period get 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 ckml run period get FM, simply by entering the name CKML_RUN_PERIOD_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function CKML_RUN_PERIOD_GET 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 'CKML_RUN_PERIOD_GET'"
EXPORTING
* I_RUN_ID = "Number of Costing Runs for Material Ledger
* I_RUN_TYPE = "Costing Run in Actual Costing
* I_LAST_DAY = "Last Day of Period
* I_LANGU = SY-LANGU "Current Language
* I_POPER = "Posting Period
* I_GJAHR = "Fiscal Year
* I_APPL = CKRU0_CO_APPL_ACT "Material ledger costing run application

IMPORTING
ES_RUNPERIOD = "

EXCEPTIONS
RUN_NOT_EXISTENT = 1
.



IMPORTING Parameters details for CKML_RUN_PERIOD_GET

I_RUN_ID - Number of Costing Runs for Material Ledger

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

I_RUN_TYPE - Costing Run in Actual Costing

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

I_LAST_DAY - Last Day of Period

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

I_LANGU - Current Language

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

I_POPER - Posting Period

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

I_GJAHR - Fiscal Year

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

I_APPL - Material ledger costing run application

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

EXPORTING Parameters details for CKML_RUN_PERIOD_GET

ES_RUNPERIOD -

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

EXCEPTIONS details

RUN_NOT_EXISTENT -

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

Copy and paste ABAP code example for CKML_RUN_PERIOD_GET 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_i_run_id  TYPE CKML_RUN_ID, "   
lv_es_runperiod  TYPE CKML_RUN_PERIOD_DATA, "   
lv_run_not_existent  TYPE CKML_RUN_PERIOD_DATA, "   
lv_i_run_type  TYPE CKML_RUN_TYPE, "   
lv_i_last_day  TYPE CKML_RUN_LAST_DAY_OF_PERIOD, "   
lv_i_langu  TYPE SY-LANGU, "   SY-LANGU
lv_i_poper  TYPE POPER, "   
lv_i_gjahr  TYPE GJAHR, "   
lv_i_appl  TYPE CKML_RUN_APPL. "   CKRU0_CO_APPL_ACT

  CALL FUNCTION 'CKML_RUN_PERIOD_GET'  "
    EXPORTING
         I_RUN_ID = lv_i_run_id
         I_RUN_TYPE = lv_i_run_type
         I_LAST_DAY = lv_i_last_day
         I_LANGU = lv_i_langu
         I_POPER = lv_i_poper
         I_GJAHR = lv_i_gjahr
         I_APPL = lv_i_appl
    IMPORTING
         ES_RUNPERIOD = lv_es_runperiod
    EXCEPTIONS
        RUN_NOT_EXISTENT = 1
. " CKML_RUN_PERIOD_GET




ABAP code using 7.40 inline data declarations to call FM CKML_RUN_PERIOD_GET

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 LANGU FROM SY INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
 
 
DATA(ld_i_appl) = CKRU0_CO_APPL_ACT.
 


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!