SAP RS_EDTR_SEARCH Function Module for Global search in programs, components, screens, function modules etc.









RS_EDTR_SEARCH is a standard rs edtr search SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Global search in programs, components, screens, function modules etc. 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 search FM, simply by entering the name RS_EDTR_SEARCH 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_SEARCH 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_SEARCH'"Global search in programs, components, screens, function modules etc.
  EXPORTING
*  ACTUAL_INCLUDE = ' ' "
*  ACTUAL_LINE = '000000' "
*  DYNPRO_PART = 'B' "'L'-flow logic / 'F'-field list / B-both
*  EXACT_SPELLING = ' ' "Search for exact spelling
*  FINDSTRING = ' ' "Search string
*  METHOD = ' ' "
   OBJECTTYPE =  "Object category: R/M/O/U/E/Y/T/F/G
*  DDICTABLE = ' ' "

 IMPORTING
   O_FCODE =  "

TABLES
   OBJECTTAB =  "Table of objects to be scanned
*  ACTUAL_SOURCE =  "

EXCEPTIONS
   NOT_EXECUTED = 1    NOT_FOUND = 2
.



IMPORTING Parameters details for RS_EDTR_SEARCH

ACTUAL_INCLUDE -

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

ACTUAL_LINE -

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

DYNPRO_PART - 'L'-flow logic / 'F'-field list / B-both

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

EXACT_SPELLING - Search for exact spelling

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

FINDSTRING - Search string

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

METHOD -

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

OBJECTTYPE - Object category: R/M/O/U/E/Y/T/F/G

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

DDICTABLE -

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

EXPORTING Parameters details for RS_EDTR_SEARCH

O_FCODE -

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

TABLES Parameters details for RS_EDTR_SEARCH

OBJECTTAB - Table of objects to be scanned

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

ACTUAL_SOURCE -

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

EXCEPTIONS details

NOT_EXECUTED -

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

NOT_FOUND - Search unsuccessful

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

Copy and paste ABAP code example for RS_EDTR_SEARCH 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_o_fcode  TYPE STRING, "   
lt_objecttab  TYPE STANDARD TABLE OF STRING, "   
lv_not_executed  TYPE STRING, "   
lv_actual_include  TYPE STRING, "   SPACE
lv_not_found  TYPE STRING, "   
lv_actual_line  TYPE STRING, "   '000000'
lt_actual_source  TYPE STANDARD TABLE OF STRING, "   
lv_dynpro_part  TYPE STRING, "   'B'
lv_exact_spelling  TYPE STRING, "   SPACE
lv_findstring  TYPE STRING, "   SPACE
lv_method  TYPE STRING, "   SPACE
lv_objecttype  TYPE STRING, "   
lv_ddictable  TYPE DD02L-TABNAME. "   SPACE

  CALL FUNCTION 'RS_EDTR_SEARCH'  "Global search in programs, components, screens, function modules etc.
    EXPORTING
         ACTUAL_INCLUDE = lv_actual_include
         ACTUAL_LINE = lv_actual_line
         DYNPRO_PART = lv_dynpro_part
         EXACT_SPELLING = lv_exact_spelling
         FINDSTRING = lv_findstring
         METHOD = lv_method
         OBJECTTYPE = lv_objecttype
         DDICTABLE = lv_ddictable
    IMPORTING
         O_FCODE = lv_o_fcode
    TABLES
         OBJECTTAB = lt_objecttab
         ACTUAL_SOURCE = lt_actual_source
    EXCEPTIONS
        NOT_EXECUTED = 1
        NOT_FOUND = 2
. " RS_EDTR_SEARCH




ABAP code using 7.40 inline data declarations to call FM RS_EDTR_SEARCH

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_actual_include) = ' '.
 
 
DATA(ld_actual_line) = '000000'.
 
 
DATA(ld_dynpro_part) = 'B'.
 
DATA(ld_exact_spelling) = ' '.
 
DATA(ld_findstring) = ' '.
 
DATA(ld_method) = ' '.
 
 
"SELECT single TABNAME FROM DD02L INTO @DATA(ld_ddictable).
DATA(ld_ddictable) = ' '.
 


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!