SAP BKK_API_ACNT_CLOSURE Function Module for API Function Module for Account Closure
BKK_API_ACNT_CLOSURE is a standard bkk api acnt closure SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API Function Module for Account Closure 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 api acnt closure FM, simply by entering the name BKK_API_ACNT_CLOSURE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBKS
Program Name: SAPLFBKS
Main Program: SAPLFBKS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_API_ACNT_CLOSURE 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_API_ACNT_CLOSURE'"API Function Module for Account Closure.
EXPORTING
I_BKKRS = "
* I_ACNUM_INT = "
* I_ACNUM_EXT = "
* I_BKK43 = "
* I_TESTRUN = "Do Test Run ('X' = Yes, ' '= No)
* I_NO_BTE = "Skip BTE Event of Bank Statement ('X' = Yes)
IMPORTING
E_STATUS_ADD = "
E_RC = "
E_BKST_HEADER = "
TABLES
* TE_BKST_ADDR = "
* TE_BKST_AD_BINT = "
* TE_BKST_CLOS = "
* TE_BKST_ITEMS = "
* TE_BKST_PAYMN = "
* TE_BKKIT = "
IMPORTING Parameters details for BKK_API_ACNT_CLOSURE
I_BKKRS -
Data type: BKK40-BKKRSOptional: No
Call by Reference: Yes
I_ACNUM_INT -
Data type: BKK40-ACNUM_INTOptional: Yes
Call by Reference: Yes
I_ACNUM_EXT -
Data type: BKK42-ACNUM_EXTOptional: Yes
Call by Reference: Yes
I_BKK43 -
Data type: BKK43Optional: Yes
Call by Reference: Yes
I_TESTRUN - Do Test Run ('X' = Yes, ' '= No)
Data type: BAPI_BKK_DTE_TESTRUNOptional: Yes
Call by Reference: Yes
I_NO_BTE - Skip BTE Event of Bank Statement ('X' = Yes)
Data type: BAPI_BKK_DTE_NOBTEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BKK_API_ACNT_CLOSURE
E_STATUS_ADD -
Data type: BKK40-STATUS_ADDOptional: No
Call by Reference: Yes
E_RC -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
E_BKST_HEADER -
Data type: IBKKBKSTHDOptional: No
Call by Reference: Yes
TABLES Parameters details for BKK_API_ACNT_CLOSURE
TE_BKST_ADDR -
Data type: IBKKBKSTADOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_BKST_AD_BINT -
Data type: IBKKBKSTAD_BINTOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_BKST_CLOS -
Data type: IBKKBKSTCLOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_BKST_ITEMS -
Data type: IBKKBKSTITOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_BKST_PAYMN -
Data type: IBKKBKSTNTOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_BKKIT -
Data type: BKKITOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_API_ACNT_CLOSURE 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_i_bkkrs | TYPE BKK40-BKKRS, " | |||
| lv_e_status_add | TYPE BKK40-STATUS_ADD, " | |||
| lt_te_bkst_addr | TYPE STANDARD TABLE OF IBKKBKSTAD, " | |||
| lv_e_rc | TYPE SY-SUBRC, " | |||
| lv_i_acnum_int | TYPE BKK40-ACNUM_INT, " | |||
| lt_te_bkst_ad_bint | TYPE STANDARD TABLE OF IBKKBKSTAD_BINT, " | |||
| lv_i_acnum_ext | TYPE BKK42-ACNUM_EXT, " | |||
| lt_te_bkst_clos | TYPE STANDARD TABLE OF IBKKBKSTCL, " | |||
| lv_e_bkst_header | TYPE IBKKBKSTHD, " | |||
| lv_i_bkk43 | TYPE BKK43, " | |||
| lt_te_bkst_items | TYPE STANDARD TABLE OF IBKKBKSTIT, " | |||
| lv_i_testrun | TYPE BAPI_BKK_DTE_TESTRUN, " | |||
| lt_te_bkst_paymn | TYPE STANDARD TABLE OF IBKKBKSTNT, " | |||
| lv_i_no_bte | TYPE BAPI_BKK_DTE_NOBTE, " | |||
| lt_te_bkkit | TYPE STANDARD TABLE OF BKKIT. " |
|   CALL FUNCTION 'BKK_API_ACNT_CLOSURE' "API Function Module for Account Closure |
| EXPORTING | ||
| I_BKKRS | = lv_i_bkkrs | |
| I_ACNUM_INT | = lv_i_acnum_int | |
| I_ACNUM_EXT | = lv_i_acnum_ext | |
| I_BKK43 | = lv_i_bkk43 | |
| I_TESTRUN | = lv_i_testrun | |
| I_NO_BTE | = lv_i_no_bte | |
| IMPORTING | ||
| E_STATUS_ADD | = lv_e_status_add | |
| E_RC | = lv_e_rc | |
| E_BKST_HEADER | = lv_e_bkst_header | |
| TABLES | ||
| TE_BKST_ADDR | = lt_te_bkst_addr | |
| TE_BKST_AD_BINT | = lt_te_bkst_ad_bint | |
| TE_BKST_CLOS | = lt_te_bkst_clos | |
| TE_BKST_ITEMS | = lt_te_bkst_items | |
| TE_BKST_PAYMN | = lt_te_bkst_paymn | |
| TE_BKKIT | = lt_te_bkkit | |
| . " BKK_API_ACNT_CLOSURE | ||
ABAP code using 7.40 inline data declarations to call FM BKK_API_ACNT_CLOSURE
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 BKKRS FROM BKK40 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single STATUS_ADD FROM BKK40 INTO @DATA(ld_e_status_add). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_rc). | ||||
| "SELECT single ACNUM_INT FROM BKK40 INTO @DATA(ld_i_acnum_int). | ||||
| "SELECT single ACNUM_EXT FROM BKK42 INTO @DATA(ld_i_acnum_ext). | ||||
Search for further information about these or an SAP related objects