SAP K_PROCESS_CHANGE_DB_UPDATE Function Module for

Search SAP Function Modules

K_PROCESS_CHANGE_DB_UPDATE is a standard k process change db update 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 process change db update FM, simply by entering the name K_PROCESS_CHANGE_DB_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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

Function K_PROCESS_CHANGE_DB_UPDATE 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_PROCESS_CHANGE_DB_UPDATE'"
  EXPORTING
   KOKRS =  "Controlling Area
   PRZNR =  "Business Process
   DATAB =  "From Date
   DATBI =  "To-Date

 IMPORTING
   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_SAPLKWM3_001 Flow Logic PBO
EXIT_SAPLKWM3_002 Flow Logic PAI

IMPORTING Parameters details for K_PROCESS_CHANGE_DB_UPDATE

KOKRS - Controlling Area

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

PRZNR - Business Process

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

DATAB - From Date

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

DATBI - To-Date

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

EXPORTING Parameters details for K_PROCESS_CHANGE_DB_UPDATE

KTEXT - Name

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

LTEXT - Description

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

Copy and paste ABAP code example for K_PROCESS_CHANGE_DB_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM K_PROCESS_CHANGE_DB_UPDATE

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