SAP CK_F_KEKOS_SELECTION Function Module for









CK_F_KEKOS_SELECTION is a standard ck f kekos selection 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 kekos selection FM, simply by entering the name CK_F_KEKOS_SELECTION into the relevant SAP transaction such as SE37 or SE38.

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



Function CK_F_KEKOS_SELECTION 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_KEKOS_SELECTION'"
  EXPORTING
   MASCHIN =  "
   MANUELL =  "
   MIMEGER =  "
   OHMEGER =  "
   USED_FOR_ARCHIVE_REL =  "
*  P_KALAID =  "
*  P_KALADAT =  "
*  BAPI_CALL =  "
*  F_KEKOKEY =  "

TABLES
   T_KEKO =  "
*  T_KALAID =  "
*  T_KALADAT =  "
*  P_KLVAR =  "
*  P_TVERS =  "
*  P_KADAT =  "
*  P_BIDAT =  "
*  P_MATNR =  "
*  P_WERKS =  "
*  P_BUKRS =  "
*  P_FEH_STA =  "
.



IMPORTING Parameters details for CK_F_KEKOS_SELECTION

MASCHIN -

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

MANUELL -

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

MIMEGER -

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

OHMEGER -

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

USED_FOR_ARCHIVE_REL -

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

P_KALAID -

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

P_KALADAT -

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

BAPI_CALL -

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

F_KEKOKEY -

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

TABLES Parameters details for CK_F_KEKOS_SELECTION

T_KEKO -

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

T_KALAID -

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

T_KALADAT -

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

P_KLVAR -

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

P_TVERS -

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

P_KADAT -

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

P_BIDAT -

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

P_MATNR -

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

P_WERKS -

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

P_BUKRS -

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

P_FEH_STA -

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

Copy and paste ABAP code example for CK_F_KEKOS_SELECTION 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:
lt_t_keko  TYPE STANDARD TABLE OF COST_KEKO_ITAB, "   
lv_maschin  TYPE XFELD, "   
lt_t_kalaid  TYPE STANDARD TABLE OF BAPICOSTINGRUN, "   
lt_t_kaladat  TYPE STANDARD TABLE OF BAPICOSTINGRUN_DATE, "   
lv_manuell  TYPE XFELD, "   
lt_p_klvar  TYPE STANDARD TABLE OF RSKLVAR, "   
lv_mimeger  TYPE XFELD, "   
lt_p_tvers  TYPE STANDARD TABLE OF RSTVERS, "   
lv_ohmeger  TYPE XFELD, "   
lt_p_kadat  TYPE STANDARD TABLE OF RSKADAT, "   
lt_p_bidat  TYPE STANDARD TABLE OF RSBIDAT, "   
lv_used_for_archive_rel  TYPE XFELD, "   
lt_p_matnr  TYPE STANDARD TABLE OF RSMATNR, "   
lv_p_kalaid  TYPE CK_KALAID, "   
lt_p_werks  TYPE STANDARD TABLE OF RSWERKS, "   
lv_p_kaladat  TYPE CK_KALADAT, "   
lt_p_bukrs  TYPE STANDARD TABLE OF RSBUKRS, "   
lv_bapi_call  TYPE XFELD, "   
lv_f_kekokey  TYPE CKIKEKOKEY, "   
lt_p_feh_sta  TYPE STANDARD TABLE OF RSFEHSTA. "   

  CALL FUNCTION 'CK_F_KEKOS_SELECTION'  "
    EXPORTING
         MASCHIN = lv_maschin
         MANUELL = lv_manuell
         MIMEGER = lv_mimeger
         OHMEGER = lv_ohmeger
         USED_FOR_ARCHIVE_REL = lv_used_for_archive_rel
         P_KALAID = lv_p_kalaid
         P_KALADAT = lv_p_kaladat
         BAPI_CALL = lv_bapi_call
         F_KEKOKEY = lv_f_kekokey
    TABLES
         T_KEKO = lt_t_keko
         T_KALAID = lt_t_kalaid
         T_KALADAT = lt_t_kaladat
         P_KLVAR = lt_p_kltar
         P_TVERS = lt_p_tvers
         P_KADAT = lt_p_kadat
         P_BIDAT = lt_p_bidat
         P_MATNR = lt_p_matnr
         P_WERKS = lt_p_werks
         P_BUKRS = lt_p_bukrs
         P_FEH_STA = lt_p_feh_sta
. " CK_F_KEKOS_SELECTION




ABAP code using 7.40 inline data declarations to call FM CK_F_KEKOS_SELECTION

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!