SAP SDU_MODEL_CHANGE Function Module for UDM Change data model









SDU_MODEL_CHANGE is a standard sdu model change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for UDM Change data model 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 sdu model change FM, simply by entering the name SDU_MODEL_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function SDU_MODEL_CHANGE 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 'SDU_MODEL_CHANGE'"UDM Change data model
EXPORTING
OBJECTNAME = "Data model name

IMPORTING
MODEL_INFOS = "
OK_CODE = "OK code which cannot be processed

EXCEPTIONS
NOT_FOUND = 1 NOT_SPECIFIED = 2 PERMISSION_FAILURE = 3
.



IMPORTING Parameters details for SDU_MODEL_CHANGE

OBJECTNAME - Data model name

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

EXPORTING Parameters details for SDU_MODEL_CHANGE

MODEL_INFOS -

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

OK_CODE - OK code which cannot be processed

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

EXCEPTIONS details

NOT_FOUND - Object not found

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

NOT_SPECIFIED - Name missing

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

PERMISSION_FAILURE - Access not possible

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

Copy and paste ABAP code example for SDU_MODEL_CHANGE 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_not_found  TYPE STRING, "   
lv_objectname  TYPE DM40L-DMOID, "   
lv_model_infos  TYPE DM40V, "   
lv_ok_code  TYPE DMCTL-FLG_RETURN, "   
lv_not_specified  TYPE DMCTL, "   
lv_permission_failure  TYPE DMCTL. "   

  CALL FUNCTION 'SDU_MODEL_CHANGE'  "UDM Change data model
    EXPORTING
         OBJECTNAME = lv_objectname
    IMPORTING
         MODEL_INFOS = lv_model_infos
         OK_CODE = lv_ok_code
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_SPECIFIED = 2
        PERMISSION_FAILURE = 3
. " SDU_MODEL_CHANGE




ABAP code using 7.40 inline data declarations to call FM SDU_MODEL_CHANGE

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 DMOID FROM DM40L INTO @DATA(ld_objectname).
 
 
"SELECT single FLG_RETURN FROM DMCTL INTO @DATA(ld_ok_code).
 
 
 


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!