SAP UPDATE_CONFIGURATION_DATA Function Module for NOTRANSL: Aktualisiert Daten aus einer Konfiguration aufgrund von Merkmals

Search SAP Function Modules

UPDATE_CONFIGURATION_DATA is a standard update configuration data 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: Aktualisiert Daten aus einer Konfiguration aufgrund von Merkmals 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 update configuration data FM, simply by entering the name UPDATE_CONFIGURATION_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function UPDATE_CONFIGURATION_DATA 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 'UPDATE_CONFIGURATION_DATA'"NOTRANSL: Aktualisiert Daten aus einer Konfiguration aufgrund von Merkmals
  EXPORTING
   SOURCE_CUOBJ =  "Configuration (internal object number)
   SOURCE_OBJECT_ID =  "Name of database table for object
   SOURCE_OBJECT =  "Key of configurable object
   DEST_CUOBJ =  "Configuration (internal object number)
   DEST_OBJECT_ID =  "Name of database table for object
   DEST_OBJECT =  "Key of configurable object
*  CHECK_ONLY = ' ' "ABAP System Field: Batch Input Processing Active

 IMPORTING
   NR_VALUES =  "ABAP System Field: Loop Index

EXCEPTIONS
   NO_CHANGES = 1    NO_CONFIGURATION_DATA_FOUND = 2    INTERNAL_CONFIGURATION_ERROR = 3    INCONSISTENT_CONFIGURATION = 4    UPDATE_ALREADY_PERFORMED = 5 

.

IMPORTING Parameters details for UPDATE_CONFIGURATION_DATA

SOURCE_CUOBJ - Configuration (internal object number)

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

SOURCE_OBJECT_ID - Name of database table for object

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

SOURCE_OBJECT - Key of configurable object

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

DEST_CUOBJ - Configuration (internal object number)

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

DEST_OBJECT_ID - Name of database table for object

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

DEST_OBJECT - Key of configurable object

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

CHECK_ONLY - ABAP System Field: Batch Input Processing Active

Data type: SY-BINPT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UPDATE_CONFIGURATION_DATA

NR_VALUES - ABAP System Field: Loop Index

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

EXCEPTIONS details

NO_CHANGES -

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

NO_CONFIGURATION_DATA_FOUND -

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

INTERNAL_CONFIGURATION_ERROR -

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

INCONSISTENT_CONFIGURATION -

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

UPDATE_ALREADY_PERFORMED -

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

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

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