SAP K_ACTIVITYTYPE_CREATE_DB_UPD Function Module for









K_ACTIVITYTYPE_CREATE_DB_UPD is a standard k activitytype create db upd 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 activitytype create db upd FM, simply by entering the name K_ACTIVITYTYPE_CREATE_DB_UPD into the relevant SAP transaction such as SE37 or SE38.

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



Function K_ACTIVITYTYPE_CREATE_DB_UPD 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_ACTIVITYTYPE_CREATE_DB_UPD'"
EXPORTING
KOKRS = "Controlling Area
* LSTAR = "
* DATAB = "From Date
* DATBI = "To-Date

IMPORTING
CANCELED = "Terminated
E_KOKRS = "Controlling Area
LSTAR = "
KTEXT = "Name
LTEXT = "Description
.




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_SAPLKMA6_001 Flow Logic PBO
EXIT_SAPLKMA6_002 Flow Logic PAI

IMPORTING Parameters details for K_ACTIVITYTYPE_CREATE_DB_UPD

KOKRS - Controlling Area

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

LSTAR -

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

DATAB - From Date

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

DATBI - To-Date

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

EXPORTING Parameters details for K_ACTIVITYTYPE_CREATE_DB_UPD

CANCELED - Terminated

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

E_KOKRS - Controlling Area

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

LSTAR -

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

KTEXT - Name

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

LTEXT - Description

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

Copy and paste ABAP code example for K_ACTIVITYTYPE_CREATE_DB_UPD 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_kokrs  TYPE CSLA-KOKRS, "   
lv_canceled  TYPE C, "   
lv_lstar  TYPE CSLA-LSTAR, "   
lv_e_kokrs  TYPE CSLA-KOKRS, "   
lv_datab  TYPE CSLA-DATAB, "   
lv_lstar  TYPE CSLA-LSTAR, "   
lv_datbi  TYPE CSLA-DATBI, "   
lv_ktext  TYPE CSLT-KTEXT, "   
lv_ltext  TYPE CSLT-LTEXT. "   

  CALL FUNCTION 'K_ACTIVITYTYPE_CREATE_DB_UPD'  "
    EXPORTING
         KOKRS = lv_kokrs
         LSTAR = lv_lstar
         DATAB = lv_datab
         DATBI = lv_datbi
    IMPORTING
         CANCELED = lv_canceled
         E_KOKRS = lv_e_kokrs
         LSTAR = lv_lstar
         KTEXT = lv_ktext
         LTEXT = lv_ltext
. " K_ACTIVITYTYPE_CREATE_DB_UPD




ABAP code using 7.40 inline data declarations to call FM K_ACTIVITYTYPE_CREATE_DB_UPD

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 KOKRS FROM CSLA INTO @DATA(ld_kokrs).
 
 
"SELECT single LSTAR FROM CSLA INTO @DATA(ld_lstar).
 
"SELECT single KOKRS FROM CSLA INTO @DATA(ld_e_kokrs).
 
"SELECT single DATAB FROM CSLA INTO @DATA(ld_datab).
 
"SELECT single LSTAR FROM CSLA INTO @DATA(ld_lstar).
 
"SELECT single DATBI FROM CSLA INTO @DATA(ld_datbi).
 
"SELECT single KTEXT FROM CSLT INTO @DATA(ld_ktext).
 
"SELECT single LTEXT FROM CSLT INTO @DATA(ld_ltext).
 


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!