SAP BKK_CLOSING_DB_GET_DATA Function Module for Get Periodic Settings for Accounts
BKK_CLOSING_DB_GET_DATA is a standard bkk closing db get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Periodic Settings for Accounts 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 closing db get data FM, simply by entering the name BKK_CLOSING_DB_GET_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBM3
Program Name: SAPLFBM3
Main Program: SAPLFBM3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_CLOSING_DB_GET_DATA 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_CLOSING_DB_GET_DATA'"Get Periodic Settings for Accounts.
EXPORTING
I_TAB_KEYS = "
* I_XFORCE_DB_READ = "
TABLES
* E_T_PERIODICAL_DATA = "
IMPORTING Parameters details for BKK_CLOSING_DB_GET_DATA
I_TAB_KEYS -
Data type: BKKD_TAB_PERIODDATA_KEYOptional: No
Call by Reference: Yes
I_XFORCE_DB_READ -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
TABLES Parameters details for BKK_CLOSING_DB_GET_DATA
E_T_PERIODICAL_DATA -
Data type: BKKM2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BKK_CLOSING_DB_GET_DATA 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_tab_keys | TYPE BKKD_TAB_PERIODDATA_KEY, " | |||
| lt_e_t_periodical_data | TYPE STANDARD TABLE OF BKKM2, " | |||
| lv_i_xforce_db_read | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'BKK_CLOSING_DB_GET_DATA' "Get Periodic Settings for Accounts |
| EXPORTING | ||
| I_TAB_KEYS | = lv_i_tab_keys | |
| I_XFORCE_DB_READ | = lv_i_xforce_db_read | |
| TABLES | ||
| E_T_PERIODICAL_DATA | = lt_e_t_periodical_data | |
| . " BKK_CLOSING_DB_GET_DATA | ||
ABAP code using 7.40 inline data declarations to call FM BKK_CLOSING_DB_GET_DATA
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 BOOLE FROM BOOLE INTO @DATA(ld_i_xforce_db_read). | ||||
Search for further information about these or an SAP related objects