SAP RS_DIALOG_EDIT Function Module for









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

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



Function RS_DIALOG_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 'RS_DIALOG_EDIT'"
EXPORTING
OBJECTNAME = "
* WB_REFERENCE = "

EXCEPTIONS
OBJECT_NOT_FOUND = 1 PERMISSION_FAILURE = 2
.



IMPORTING Parameters details for RS_DIALOG_EDIT

OBJECTNAME -

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

WB_REFERENCE -

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

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

PERMISSION_FAILURE -

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

Copy and paste ABAP code example for RS_DIALOG_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_objectname  TYPE TDCT-DNAM, "   
lv_object_not_found  TYPE TDCT, "   
lv_wb_reference  TYPE CL_WB_DIALOG_MODULE, "   
lv_permission_failure  TYPE CL_WB_DIALOG_MODULE. "   

  CALL FUNCTION 'RS_DIALOG_EDIT'  "
    EXPORTING
         OBJECTNAME = lv_objectname
         WB_REFERENCE = lv_wb_reference
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        PERMISSION_FAILURE = 2
. " RS_DIALOG_EDIT




ABAP code using 7.40 inline data declarations to call FM RS_DIALOG_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 DNAM FROM TDCT INTO @DATA(ld_objectname).
 
 
 
 


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!