SAP DSYS_EDIT Function Module for









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

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



Function DSYS_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 'DSYS_EDIT'"
EXPORTING
DOKCLASS = "Class of the object to be edited
* DOKLANGU = SY-LANGU "Editing language
DOKNAME = "Name of the object to be edited
* DOKSHORTTEXT = ' ' "
* TEMPLATE_ID = "
* TEMPLATE_OBJECT = "
* TEMPLATE_TYP = "
* USE_NOTE_TEMPLATE = ' ' "

IMPORTING
CHANGED = "whether something was changed in t

EXCEPTIONS
NOT_HYPERTEXT_CLASS = 1 NO_EDITOR = 2
.



IMPORTING Parameters details for DSYS_EDIT

DOKCLASS - Class of the object to be edited

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

DOKLANGU - Editing language

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

DOKNAME - Name of the object to be edited

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

DOKSHORTTEXT -

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

TEMPLATE_ID -

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

TEMPLATE_OBJECT -

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

TEMPLATE_TYP -

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

USE_NOTE_TEMPLATE -

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

EXPORTING Parameters details for DSYS_EDIT

CHANGED - whether something was changed in t

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

EXCEPTIONS details

NOT_HYPERTEXT_CLASS - Class not defined for hypertext

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

NO_EDITOR - No editor available for this class

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

Copy and paste ABAP code example for DSYS_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_changed  TYPE STRING, "   
lv_dokclass  TYPE DSYSH-DOKCLASS, "   
lv_not_hypertext_class  TYPE DSYSH, "   
lv_doklangu  TYPE SY-LANGU, "   SY-LANGU
lv_no_editor  TYPE SY, "   
lv_dokname  TYPE SY, "   
lv_dokshorttext  TYPE SY, "   SPACE
lv_template_id  TYPE DOKHL-ID, "   
lv_template_object  TYPE DOKHL-OBJECT, "   
lv_template_typ  TYPE DOKHL-TYP, "   
lv_use_note_template  TYPE CHAR1. "   SPACE

  CALL FUNCTION 'DSYS_EDIT'  "
    EXPORTING
         DOKCLASS = lv_dokclass
         DOKLANGU = lv_doklangu
         DOKNAME = lv_dokname
         DOKSHORTTEXT = lv_dokshorttext
         TEMPLATE_ID = lv_template_id
         TEMPLATE_OBJECT = lv_template_object
         TEMPLATE_TYP = lv_template_typ
         USE_NOTE_TEMPLATE = lv_use_note_template
    IMPORTING
         CHANGED = lv_changed
    EXCEPTIONS
        NOT_HYPERTEXT_CLASS = 1
        NO_EDITOR = 2
. " DSYS_EDIT




ABAP code using 7.40 inline data declarations to call FM DSYS_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 DOKCLASS FROM DSYSH INTO @DATA(ld_dokclass).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_doklangu).
DATA(ld_doklangu) = SY-LANGU.
 
 
 
DATA(ld_dokshorttext) = ' '.
 
"SELECT single ID FROM DOKHL INTO @DATA(ld_template_id).
 
"SELECT single OBJECT FROM DOKHL INTO @DATA(ld_template_object).
 
"SELECT single TYP FROM DOKHL INTO @DATA(ld_template_typ).
 
DATA(ld_use_note_template) = ' '.
 


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!