SAP K_EO_CCTR_APPL_CREATE Function Module for









K_EO_CCTR_APPL_CREATE is a standard k eo cctr appl create 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 k eo cctr appl create FM, simply by entering the name K_EO_CCTR_APPL_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function K_EO_CCTR_APPL_CREATE 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 'K_EO_CCTR_APPL_CREATE'"
  EXPORTING
   SCENARIO =  "
*  CLASS_KEY =  "
   DATE =  "Key Date
   PLVAR =  "Plan Variant
   FUZZY_BEGDA =  "
   FUZZY_ENDDA =  "
   CHANGEMODE =  "
*  OTYPE =  "
*  TABTYPE =  "

 IMPORTING
   SUCCESS =  "
   ETKA01 =  "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKMA1_001 Flow Logic PBO
EXIT_SAPLKMA1_002 Flow Logic PAI
EXIT_SAPLKMA1_003 Checks for Saving

IMPORTING Parameters details for K_EO_CCTR_APPL_CREATE

SCENARIO -

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

CLASS_KEY -

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

DATE - Key Date

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

PLVAR - Plan Variant

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

FUZZY_BEGDA -

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

FUZZY_ENDDA -

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

CHANGEMODE -

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

OTYPE -

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

TABTYPE -

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

EXPORTING Parameters details for K_EO_CCTR_APPL_CREATE

SUCCESS -

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

ETKA01 -

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

Copy and paste ABAP code example for K_EO_CCTR_APPL_CREATE 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_success  TYPE BOOLE_D, "   
lv_scenario  TYPE HROMSCEN, "   
lv_etka01  TYPE TKA01, "   
lv_class_key  TYPE OMCLASSKEY, "   
lv_date  TYPE SY-DATUM, "   
lv_plvar  TYPE PLVAR, "   
lv_fuzzy_begda  TYPE SY-DATUM, "   
lv_fuzzy_endda  TYPE SY-DATUM, "   
lv_changemode  TYPE OMACTMODE, "   
lv_otype  TYPE OTYPE, "   
lv_tabtype  TYPE HRTABTYPE. "   

  CALL FUNCTION 'K_EO_CCTR_APPL_CREATE'  "
    EXPORTING
         SCENARIO = lv_scenario
         CLASS_KEY = lv_class_key
         DATE = lv_date
         PLVAR = lv_plvar
         FUZZY_BEGDA = lv_fuzzy_begda
         FUZZY_ENDDA = lv_fuzzy_endda
         CHANGEMODE = lv_changemode
         OTYPE = lv_otype
         TABTYPE = lv_tabtype
    IMPORTING
         SUCCESS = lv_success
         ETKA01 = lv_etka01
. " K_EO_CCTR_APPL_CREATE




ABAP code using 7.40 inline data declarations to call FM K_EO_CCTR_APPL_CREATE

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 DATUM FROM SY INTO @DATA(ld_date).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_begda).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_endda).
 
 
 
 


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!