SAP SDU_DMO_ENT_EDIT Function Module for









SDU_DMO_ENT_EDIT is a standard sdu dmo ent edit 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 sdu dmo ent edit FM, simply by entering the name SDU_DMO_ENT_EDIT into the relevant SAP transaction such as SE37 or SE38.

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



Function SDU_DMO_ENT_EDIT 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_DMO_ENT_EDIT'"
  EXPORTING
*  AS4LOCAL = 'A' "Validity
*  DMOID = ' ' "Data model name
*  ENTITY = 'UDM0009501' "Entity name
*  KORRNUM = ' ' "Correction Number
*  MODE = '    ' "Editing Mode
*  MODE_ENQ = 'Y' "Lock Mode

 IMPORTING
   DMO_ENTITY =  "
   OK_CODE =  "

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for SDU_DMO_ENT_EDIT

AS4LOCAL - Validity

Data type: DM41S-AS4LOCAL
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DMOID - Data model name

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

ENTITY - Entity name

Data type: DM41S-OBJID
Default: 'UDM0009501'
Optional: Yes
Call by Reference: No ( called with pass by value option)

KORRNUM - Correction Number

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

MODE - Editing Mode

Data type: DMINF-FLG_ENTRY
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODE_ENQ - Lock Mode

Data type: DMCTL-FLG_ENQOBJ
Default: 'Y'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SDU_DMO_ENT_EDIT

DMO_ENTITY -

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

OK_CODE -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for SDU_DMO_ENT_EDIT 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_as4local  TYPE DM41S-AS4LOCAL, "   'A'
lv_not_found  TYPE DM41S, "   
lv_dmo_entity  TYPE DM41S, "   
lv_dmoid  TYPE DM41S-DMOID, "   SPACE
lv_ok_code  TYPE DMINF-FLG_ENTRY, "   
lv_entity  TYPE DM41S-OBJID, "   'UDM0009501'
lv_korrnum  TYPE E070-TRKORR, "   SPACE
lv_mode  TYPE DMINF-FLG_ENTRY, "   ' '
lv_mode_enq  TYPE DMCTL-FLG_ENQOBJ. "   'Y'

  CALL FUNCTION 'SDU_DMO_ENT_EDIT'  "
    EXPORTING
         AS4LOCAL = lv_as4local
         DMOID = lv_dmoid
         ENTITY = lv_entity
         KORRNUM = lv_korrnum
         MODE = lv_mode
         MODE_ENQ = lv_mode_enq
    IMPORTING
         DMO_ENTITY = lv_dmo_entity
         OK_CODE = lv_ok_code
    EXCEPTIONS
        NOT_FOUND = 1
. " SDU_DMO_ENT_EDIT




ABAP code using 7.40 inline data declarations to call FM SDU_DMO_ENT_EDIT

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 AS4LOCAL FROM DM41S INTO @DATA(ld_as4local).
DATA(ld_as4local) = 'A'.
 
 
 
"SELECT single DMOID FROM DM41S INTO @DATA(ld_dmoid).
DATA(ld_dmoid) = ' '.
 
"SELECT single FLG_ENTRY FROM DMINF INTO @DATA(ld_ok_code).
 
"SELECT single OBJID FROM DM41S INTO @DATA(ld_entity).
DATA(ld_entity) = 'UDM0009501'.
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_korrnum).
DATA(ld_korrnum) = ' '.
 
"SELECT single FLG_ENTRY FROM DMINF INTO @DATA(ld_mode).
DATA(ld_mode) = ' '.
 
"SELECT single FLG_ENQOBJ FROM DMCTL INTO @DATA(ld_mode_enq).
DATA(ld_mode_enq) = 'Y'.
 


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!