SAP BTFR_SELECT Function Module for









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

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



Function BTFR_SELECT 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 'BTFR_SELECT'"
EXPORTING
* FLAG_STRING = "
* OBJECT_TYPE = "Object Type
* OBJECT_NAME = "
* FLAG_FUZZY_SEARCH = "
* FLAG_GET_ALL_CONTEXTS = "
* FLAG_SYSTEM_CONTEXT = 'X' "
* LANGU = SY-LANGU "Language Key
* BTFR_TEXT = "
* BTFR_STRING = "
* PACKAGE = "Package
* ALIAS = "Unique Alias Name for OTR Concept

IMPORTING
TEXT_TAB = "Short Texts (fields from SOTR_TEXT that are used)
STRING_TAB = "Long Texts (fields from SOTR_TEXTU that are used)
HELP_TAB = "F4 Help/Browser (Fields from Head Table and Text Table)

EXCEPTIONS
INVALID_PARAMETERS = 1 ERROR_READ_DB = 2
.



IMPORTING Parameters details for BTFR_SELECT

FLAG_STRING -

Data type: BTFR_F_STRING
Optional: Yes
Call by Reference: Yes

OBJECT_TYPE - Object Type

Data type: TROBJTYPE
Optional: Yes
Call by Reference: Yes

OBJECT_NAME -

Data type: TROBJ_NAME
Optional: Yes
Call by Reference: Yes

FLAG_FUZZY_SEARCH -

Data type: BTFR_FLAG
Optional: Yes
Call by Reference: Yes

FLAG_GET_ALL_CONTEXTS -

Data type: BTFR_FLAG
Optional: Yes
Call by Reference: Yes

FLAG_SYSTEM_CONTEXT -

Data type: BTFR_FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

LANGU - Language Key

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

BTFR_TEXT -

Data type: BTFR_TEXT
Optional: Yes
Call by Reference: Yes

BTFR_STRING -

Data type: BTFR_STRING
Optional: Yes
Call by Reference: Yes

PACKAGE - Package

Data type: DEVCLASS
Optional: Yes
Call by Reference: Yes

ALIAS - Unique Alias Name for OTR Concept

Data type: SOTR_ALIAS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BTFR_SELECT

TEXT_TAB - Short Texts (fields from SOTR_TEXT that are used)

Data type: BTFR_TEXT_TT
Optional: No
Call by Reference: Yes

STRING_TAB - Long Texts (fields from SOTR_TEXTU that are used)

Data type: BTFR_STRING_TT
Optional: No
Call by Reference: Yes

HELP_TAB - F4 Help/Browser (Fields from Head Table and Text Table)

Data type: BTFR_HELP_TT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

ERROR_READ_DB -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BTFR_SELECT 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_text_tab  TYPE BTFR_TEXT_TT, "   
lv_flag_string  TYPE BTFR_F_STRING, "   
lv_invalid_parameters  TYPE BTFR_F_STRING, "   
lv_object_type  TYPE TROBJTYPE, "   
lv_object_name  TYPE TROBJ_NAME, "   
lv_string_tab  TYPE BTFR_STRING_TT, "   
lv_error_read_db  TYPE BTFR_STRING_TT, "   
lv_flag_fuzzy_search  TYPE BTFR_FLAG, "   
lv_help_tab  TYPE BTFR_HELP_TT, "   
lv_flag_get_all_contexts  TYPE BTFR_FLAG, "   
lv_flag_system_context  TYPE BTFR_FLAG, "   'X'
lv_langu  TYPE SPRAS, "   SY-LANGU
lv_btfr_text  TYPE BTFR_TEXT, "   
lv_btfr_string  TYPE BTFR_STRING, "   
lv_package  TYPE DEVCLASS, "   
lv_alias  TYPE SOTR_ALIAS. "   

  CALL FUNCTION 'BTFR_SELECT'  "
    EXPORTING
         FLAG_STRING = lv_flag_string
         OBJECT_TYPE = lv_object_type
         OBJECT_NAME = lv_object_name
         FLAG_FUZZY_SEARCH = lv_flag_fuzzy_search
         FLAG_GET_ALL_CONTEXTS = lv_flag_get_all_contexts
         FLAG_SYSTEM_CONTEXT = lv_flag_system_context
         LANGU = lv_langu
         BTFR_TEXT = lv_btfr_text
         BTFR_STRING = lv_btfr_string
         PACKAGE = lv_package
         ALIAS = lv_alias
    IMPORTING
         TEXT_TAB = lv_text_tab
         STRING_TAB = lv_string_tab
         HELP_TAB = lv_help_tab
    EXCEPTIONS
        INVALID_PARAMETERS = 1
        ERROR_READ_DB = 2
. " BTFR_SELECT




ABAP code using 7.40 inline data declarations to call FM BTFR_SELECT

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_flag_system_context) = 'X'.
 
DATA(ld_langu) = SY-LANGU.
 
 
 
 
 


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!