SAP BTFR_DELETE_SINGLE_TEXT Function Module for
BTFR_DELETE_SINGLE_TEXT is a standard btfr delete single text 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 delete single text FM, simply by entering the name BTFR_DELETE_SINGLE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BTFR_API_MAINTENANCE
Program Name: SAPLBTFR_API_MAINTENANCE
Main Program: SAPLBTFR_API_MAINTENANCE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BTFR_DELETE_SINGLE_TEXT 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_DELETE_SINGLE_TEXT'".
EXPORTING
CONCEPT = "Key for Logical Object in the OTR
* LANGU = SY-LANGU "Language Key
* FLAG_STRING = "Indicator: 'X': Long Text (String), ' ': Short Text
* CONTEXT = "Kontext for the OTR
* FLAG_CORRECTION_ENTRY = 'X' "
* CORR_NUM = "
* USE_KORRNUM_IMMEDIATEDLY = "
EXCEPTIONS
TEXT_NOT_FOUND = 1 INVALID_PACKAGE = 2 TEXT_NOT_CHANGEABLE = 3 TEXT_ENQUEUED = 4 NO_CORRECTION = 5 PARAMETER_ERROR = 6
IMPORTING Parameters details for BTFR_DELETE_SINGLE_TEXT
CONCEPT - Key for Logical Object in the OTR
Data type: SOTR_CONCOptional: No
Call by Reference: Yes
LANGU - Language Key
Data type: SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
FLAG_STRING - Indicator: 'X': Long Text (String), ' ': Short Text
Data type: BTFR_F_STRINGOptional: Yes
Call by Reference: Yes
CONTEXT - Kontext for the OTR
Data type: SOTR_CNTXTOptional: Yes
Call by Reference: Yes
FLAG_CORRECTION_ENTRY -
Data type: BTFR_FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
CORR_NUM -
Data type: TRKORROptional: Yes
Call by Reference: Yes
USE_KORRNUM_IMMEDIATEDLY -
Data type: BTFR_FLAGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
TEXT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PACKAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TEXT_NOT_CHANGEABLE -
Data type:Optional: No
Call by Reference: Yes
TEXT_ENQUEUED -
Data type:Optional: No
Call by Reference: Yes
NO_CORRECTION -
Data type:Optional: No
Call by Reference: Yes
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BTFR_DELETE_SINGLE_TEXT 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_concept | TYPE SOTR_CONC, " | |||
| lv_text_not_found | TYPE SOTR_CONC, " | |||
| lv_langu | TYPE SPRAS, " SY-LANGU | |||
| lv_invalid_package | TYPE SPRAS, " | |||
| lv_flag_string | TYPE BTFR_F_STRING, " | |||
| lv_text_not_changeable | TYPE BTFR_F_STRING, " | |||
| lv_context | TYPE SOTR_CNTXT, " | |||
| lv_text_enqueued | TYPE SOTR_CNTXT, " | |||
| lv_no_correction | TYPE SOTR_CNTXT, " | |||
| lv_flag_correction_entry | TYPE BTFR_FLAG, " 'X' | |||
| lv_corr_num | TYPE TRKORR, " | |||
| lv_parameter_error | TYPE TRKORR, " | |||
| lv_use_korrnum_immediatedly | TYPE BTFR_FLAG. " |
|   CALL FUNCTION 'BTFR_DELETE_SINGLE_TEXT' " |
| EXPORTING | ||
| CONCEPT | = lv_concept | |
| LANGU | = lv_langu | |
| FLAG_STRING | = lv_flag_string | |
| CONTEXT | = lv_context | |
| FLAG_CORRECTION_ENTRY | = lv_flag_correction_entry | |
| CORR_NUM | = lv_corr_num | |
| USE_KORRNUM_IMMEDIATEDLY | = lv_use_korrnum_immediatedly | |
| EXCEPTIONS | ||
| TEXT_NOT_FOUND = 1 | ||
| INVALID_PACKAGE = 2 | ||
| TEXT_NOT_CHANGEABLE = 3 | ||
| TEXT_ENQUEUED = 4 | ||
| NO_CORRECTION = 5 | ||
| PARAMETER_ERROR = 6 | ||
| . " BTFR_DELETE_SINGLE_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM BTFR_DELETE_SINGLE_TEXT
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_langu) | = SY-LANGU. | |||
| DATA(ld_flag_correction_entry) | = 'X'. | |||
Search for further information about these or an SAP related objects