SAP BTFR_DELETE Function Module for Delete

Search SAP Function Modules

BTFR_DELETE is a standard btfr delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete 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 btfr delete FM, simply by entering the name BTFR_DELETE 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_DELETE 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'"Delete
  EXPORTING
*  FLAG_STRING =  "
*  HEADER =  "Structure for Header Fields

CHANGING
*  HEADER_TAB =  "Header Data
*  TEXT_TAB =  "Short Texts (fields from SOTR_TEXT that are used)
*  STRING_TAB =  "Long Texts (fields from SOTR_TEXTU that are used)

EXCEPTIONS
   NOT_ALL_CONCEPTS_DELETED = 1    NOT_ALL_ENTRIES_DELETED = 2    ERROR_TADIR_ENTRY = 3 

.

IMPORTING Parameters details for BTFR_DELETE

FLAG_STRING -

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

HEADER - Structure for Header Fields

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

CHANGING Parameters details for BTFR_DELETE

HEADER_TAB - Header Data

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

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

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

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

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

EXCEPTIONS details

NOT_ALL_CONCEPTS_DELETED -

Data type:
Optional: No
Call by Reference: Yes

NOT_ALL_ENTRIES_DELETED -

Data type:
Optional: No
Call by Reference: Yes

ERROR_TADIR_ENTRY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BTFR_DELETE 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.

ABAP code using 7.40 inline data declarations to call FM BTFR_DELETE

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.

Search for further information about these or an SAP related objects