SAP SDU_MODEL_ADD Function Module for UDM Create data model









SDU_MODEL_ADD is a standard sdu model add 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 Create 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 add FM, simply by entering the name SDU_MODEL_ADD 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_ADD 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_ADD'"UDM Create data model
EXPORTING
OBJECTNAME = "Data model name
* POPUP = ' ' "Flag: 'X' Enter name in dialog box
* SHORTTEXT = ' ' "Short description (optional)

IMPORTING
MODEL_INFOS = "Data model information
OK_CODE = "OK Code which can not be handled itself

EXCEPTIONS
ALREADY_EXISTS = 1 NAME_NOT_VALID = 2 NOT_EXECUTED = 3 NOT_SPECIFIED = 4 PERMISSION_FAILURE = 5
.



IMPORTING Parameters details for SDU_MODEL_ADD

OBJECTNAME - Data model name

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

POPUP - Flag: 'X' Enter name in dialog box

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

SHORTTEXT - Short description (optional)

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

EXPORTING Parameters details for SDU_MODEL_ADD

MODEL_INFOS - Data model information

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

OK_CODE - OK Code which can not be handled itself

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

EXCEPTIONS details

ALREADY_EXISTS - Object already exists

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

NAME_NOT_VALID - Name does not follow naming convention

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

NOT_EXECUTED - Action was cancelled without saving

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_ADD 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_objectname  TYPE DM40L-DMOID, "   
lv_model_infos  TYPE DM40V, "   
lv_already_exists  TYPE DM40V, "   
lv_popup  TYPE DM40V, "   SPACE
lv_ok_code  TYPE DMCTL-FLG_RETURN, "   
lv_name_not_valid  TYPE DMCTL, "   
lv_shorttext  TYPE DM40T-LANGBEZ, "   SPACE
lv_not_executed  TYPE DM40T, "   
lv_not_specified  TYPE DM40T, "   
lv_permission_failure  TYPE DM40T. "   

  CALL FUNCTION 'SDU_MODEL_ADD'  "UDM Create data model
    EXPORTING
         OBJECTNAME = lv_objectname
         POPUP = lv_popup
         SHORTTEXT = lv_shorttext
    IMPORTING
         MODEL_INFOS = lv_model_infos
         OK_CODE = lv_ok_code
    EXCEPTIONS
        ALREADY_EXISTS = 1
        NAME_NOT_VALID = 2
        NOT_EXECUTED = 3
        NOT_SPECIFIED = 4
        PERMISSION_FAILURE = 5
. " SDU_MODEL_ADD




ABAP code using 7.40 inline data declarations to call FM SDU_MODEL_ADD

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).
 
 
 
DATA(ld_popup) = ' '.
 
"SELECT single FLG_RETURN FROM DMCTL INTO @DATA(ld_ok_code).
 
 
"SELECT single LANGBEZ FROM DM40T INTO @DATA(ld_shorttext).
DATA(ld_shorttext) = ' '.
 
 
 
 


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!