SAP K_CMPERS_UP_DB_WRITE Function Module for NOTRANSL: Personalisierung (intern!): Benutzereinstellungen speichern

Search SAP Function Modules

K_CMPERS_UP_DB_WRITE is a standard k cmpers up db write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Personalisierung (intern!): Benutzereinstellungen speichern processing and below is the pattern details for this FM, 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 cmpers up db write FM, simply by entering the name K_CMPERS_UP_DB_WRITE into the relevant SAP transaction such as SE37 or SE38.

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

Function K_CMPERS_UP_DB_WRITE 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_CMPERS_UP_DB_WRITE'"NOTRANSL: Personalisierung (intern!): Benutzereinstellungen speichern
  EXPORTING
*  P_PERSKEY_TYPE = KCMPE_KEYTYPE_USER "DE-EN-LANG-SWITCH-NO-TRANSLATION
   P_PERSKEY =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

TABLES
   P_CMPERSPARM =  "Personalization: User Settings
   P_CMPERSINDX =  "Personalization: Field Catalog
*  P_CMPERSAPPL =  "Personalization: Application Hierarchy

EXCEPTIONS
   PERSKEY_NOT_UNIQUE = 1    INVALID_FIELD = 2 

.

IMPORTING Parameters details for K_CMPERS_UP_DB_WRITE

P_PERSKEY_TYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: CMPERSPARM-PERSKEYTP
Default: KCMPE_KEYTYPE_USER
Optional: Yes
Call by Reference: Yes

P_PERSKEY - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: CMPERSPARM-PERSKEY
Optional: No
Call by Reference: Yes

TABLES Parameters details for K_CMPERS_UP_DB_WRITE

P_CMPERSPARM - Personalization: User Settings

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

P_CMPERSINDX - Personalization: Field Catalog

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

P_CMPERSAPPL - Personalization: Application Hierarchy

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

EXCEPTIONS details

PERSKEY_NOT_UNIQUE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

INVALID_FIELD - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for K_CMPERS_UP_DB_WRITE 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_CMPERS_UP_DB_WRITE

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