SAP BKK_COND_CLOSE_DELETE_T Function Module for Deletion of Entries
BKK_COND_CLOSE_DELETE_T is a standard bkk cond close delete t SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deletion of Entries 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 bkk cond close delete t FM, simply by entering the name BKK_COND_CLOSE_DELETE_T into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB96
Program Name: SAPLFB96
Main Program: SAPLFB96
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_COND_CLOSE_DELETE_T 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 'BKK_COND_CLOSE_DELETE_T'"Deletion of Entries.
IMPORTING
E_NUM_DELETED = "
TABLES
T_BKK92 = "
EXCEPTIONS
DELETE_UNSUCCESSFUL = 1
EXPORTING Parameters details for BKK_COND_CLOSE_DELETE_T
E_NUM_DELETED -
Data type: SY-DBCNTOptional: No
Call by Reference: Yes
TABLES Parameters details for BKK_COND_CLOSE_DELETE_T
T_BKK92 -
Data type: BKK92Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DELETE_UNSUCCESSFUL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_COND_CLOSE_DELETE_T 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: | ||||
| lt_t_bkk92 | TYPE STANDARD TABLE OF BKK92, " | |||
| lv_e_num_deleted | TYPE SY-DBCNT, " | |||
| lv_delete_unsuccessful | TYPE SY. " |
|   CALL FUNCTION 'BKK_COND_CLOSE_DELETE_T' "Deletion of Entries |
| IMPORTING | ||
| E_NUM_DELETED | = lv_e_num_deleted | |
| TABLES | ||
| T_BKK92 | = lt_t_bkk92 | |
| EXCEPTIONS | ||
| DELETE_UNSUCCESSFUL = 1 | ||
| . " BKK_COND_CLOSE_DELETE_T | ||
ABAP code using 7.40 inline data declarations to call FM BKK_COND_CLOSE_DELETE_T
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.| "SELECT single DBCNT FROM SY INTO @DATA(ld_e_num_deleted). | ||||
Search for further information about these or an SAP related objects