SAP RS_EDTR_ADD Function Module for Development environment: Add a module
RS_EDTR_ADD is a standard rs edtr 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 Development environment: Add a module 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 rs edtr add FM, simply by entering the name RS_EDTR_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEUR
Program Name: SAPLSEUR
Main Program: SAPLSEUR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RS_EDTR_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 'RS_EDTR_ADD'"Development environment: Add a module.
EXPORTING
* NAME = "
* SUBNAME = "Component Name (Module/FORM)
* PROGRAM = ' ' "
* I_TYPE = 'R' "Component Type
* INCLUDE = ' ' "
* MODE = "
* SUPPRESS_DIALOG = ABAP_FALSE "
IMPORTING
NAME_O = "Name of component to be added
NEW_INCLUDE_NAME = "Include name if new include also created
NEW_MASTER_INCLUDE = "
CHANGING
* INSERT_STATEMENT = "
EXCEPTIONS
EXISTS_ALREADY = 1 NOT_EXECUTED = 2 PROGRAM_ENQUEUED = 3
IMPORTING Parameters details for RS_EDTR_ADD
NAME -
Data type: EDOBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
SUBNAME - Component Name (Module/FORM)
Data type: SEU_OBJKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
PROGRAM -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TYPE - Component Type
Data type:Default: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)
INCLUDE -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MODE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
SUPPRESS_DIALOG -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RS_EDTR_ADD
NAME_O - Name of component to be added
Data type: EDOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
NEW_INCLUDE_NAME - Include name if new include also created
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NEW_MASTER_INCLUDE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RS_EDTR_ADD
INSERT_STATEMENT -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EXISTS_ALREADY - The component already exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_EXECUTED - Program or include does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_ENQUEUED - Program /Include blocked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_EDTR_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_name | TYPE EDOBJECT, " | |||
| lv_name_o | TYPE EDOBJECT, " | |||
| lv_exists_already | TYPE EDOBJECT, " | |||
| lv_insert_statement | TYPE CHAR1, " | |||
| lv_subname | TYPE SEU_OBJKEY, " | |||
| lv_not_executed | TYPE SEU_OBJKEY, " | |||
| lv_new_include_name | TYPE SEU_OBJKEY, " | |||
| lv_program | TYPE SEU_OBJKEY, " SPACE | |||
| lv_program_enqueued | TYPE SEU_OBJKEY, " | |||
| lv_new_master_include | TYPE SEU_OBJKEY, " | |||
| lv_i_type | TYPE SEU_OBJKEY, " 'R' | |||
| lv_include | TYPE SEU_OBJKEY, " SPACE | |||
| lv_mode | TYPE SEU_OBJKEY, " | |||
| lv_suppress_dialog | TYPE ABAP_BOOL. " ABAP_FALSE |
|   CALL FUNCTION 'RS_EDTR_ADD' "Development environment: Add a module |
| EXPORTING | ||
| NAME | = lv_name | |
| SUBNAME | = lv_subname | |
| PROGRAM | = lv_program | |
| I_TYPE | = lv_i_type | |
| INCLUDE | = lv_include | |
| MODE | = lv_mode | |
| SUPPRESS_DIALOG | = lv_suppress_dialog | |
| IMPORTING | ||
| NAME_O | = lv_name_o | |
| NEW_INCLUDE_NAME | = lv_new_include_name | |
| NEW_MASTER_INCLUDE | = lv_new_master_include | |
| CHANGING | ||
| INSERT_STATEMENT | = lv_insert_statement | |
| EXCEPTIONS | ||
| EXISTS_ALREADY = 1 | ||
| NOT_EXECUTED = 2 | ||
| PROGRAM_ENQUEUED = 3 | ||
| . " RS_EDTR_ADD | ||
ABAP code using 7.40 inline data declarations to call FM RS_EDTR_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.| DATA(ld_program) | = ' '. | |||
| DATA(ld_i_type) | = 'R'. | |||
| DATA(ld_include) | = ' '. | |||
| DATA(ld_suppress_dialog) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects