SAP BKK_FIKEY_CHECK_TRANSFER Function Module for FI Key: Check if Transfer to General Ledger Possible
BKK_FIKEY_CHECK_TRANSFER is a standard bkk fikey check transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FI Key: Check if Transfer to General Ledger Possible 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 fikey check transfer FM, simply by entering the name BKK_FIKEY_CHECK_TRANSFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBC7
Program Name: SAPLFBC7
Main Program: SAPLFBC7
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_FIKEY_CHECK_TRANSFER 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_FIKEY_CHECK_TRANSFER'"FI Key: Check if Transfer to General Ledger Possible.
EXPORTING
I_BKKRS = "Bank Area
I_FIKEY = "FI Key
I_BUKRS = "Company Code for FI Key (or Bank Area)
* I_DATE_TO = 99991231 "To-Date
I_X_DATA_TRANSF = "
* I_POSTING_DATE = "Posting date
IMPORTING
E_XTRANSFER = "X = Transfer FI OK
MAX_SEVERITY = "Error
TABLES
T_BKKC02 = "FI Key Records Compressed Using FIKeyC
T_BKKC02_GL_SUMSZ = "GL_SUMSZ for Update BKKC02 (Ref. in FI Doc.)
IMPORTING Parameters details for BKK_FIKEY_CHECK_TRANSFER
I_BKKRS - Bank Area
Data type: BKKC01-BKKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_FIKEY - FI Key
Data type: BKKC01-FIKEYOptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS - Company Code for FI Key (or Bank Area)
Data type: BKKC01-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_TO - To-Date
Data type: IBKKGL_DNP_REP_TRF-T_DATEDefault: 99991231
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_X_DATA_TRANSF -
Data type: BKK_XFELDOptional: No
Call by Reference: No ( called with pass by value option)
I_POSTING_DATE - Posting date
Data type: BKK_PSTDATOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BKK_FIKEY_CHECK_TRANSFER
E_XTRANSFER - X = Transfer FI OK
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
MAX_SEVERITY - Error
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BKK_FIKEY_CHECK_TRANSFER
T_BKKC02 - FI Key Records Compressed Using FIKeyC
Data type: IBKKC02Optional: No
Call by Reference: No ( called with pass by value option)
T_BKKC02_GL_SUMSZ - GL_SUMSZ for Update BKKC02 (Ref. in FI Doc.)
Data type: BKKH_T_BKKC02_GL_SUMSZOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_FIKEY_CHECK_TRANSFER 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 BKKC01-BKKRS, " | |||
| lt_t_bkkc02 | TYPE STANDARD TABLE OF IBKKC02, " | |||
| lv_e_xtransfer | TYPE BOOLE-BOOLE, " | |||
| lv_i_fikey | TYPE BKKC01-FIKEY, " | |||
| lv_max_severity | TYPE SY-SUBRC, " | |||
| lt_t_bkkc02_gl_sumsz | TYPE STANDARD TABLE OF BKKH_T_BKKC02_GL_SUMSZ, " | |||
| lv_i_bukrs | TYPE BKKC01-BUKRS, " | |||
| lv_i_date_to | TYPE IBKKGL_DNP_REP_TRF-T_DATE, " 99991231 | |||
| lv_i_x_data_transf | TYPE BKK_XFELD, " | |||
| lv_i_posting_date | TYPE BKK_PSTDAT. " |
|   CALL FUNCTION 'BKK_FIKEY_CHECK_TRANSFER' "FI Key: Check if Transfer to General Ledger Possible |
| EXPORTING | ||
| I_BKKRS | = lv_i_bkkrs | |
| I_FIKEY | = lv_i_fikey | |
| I_BUKRS | = lv_i_bukrs | |
| I_DATE_TO | = lv_i_date_to | |
| I_X_DATA_TRANSF | = lv_i_x_data_transf | |
| I_POSTING_DATE | = lv_i_posting_date | |
| IMPORTING | ||
| E_XTRANSFER | = lv_e_xtransfer | |
| MAX_SEVERITY | = lv_max_severity | |
| TABLES | ||
| T_BKKC02 | = lt_t_bkkc02 | |
| T_BKKC02_GL_SUMSZ | = lt_t_bkkc02_gl_sumsz | |
| . " BKK_FIKEY_CHECK_TRANSFER | ||
ABAP code using 7.40 inline data declarations to call FM BKK_FIKEY_CHECK_TRANSFER
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 BKKC01 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_xtransfer). | ||||
| "SELECT single FIKEY FROM BKKC01 INTO @DATA(ld_i_fikey). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_max_severity). | ||||
| "SELECT single BUKRS FROM BKKC01 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single T_DATE FROM IBKKGL_DNP_REP_TRF INTO @DATA(ld_i_date_to). | ||||
| DATA(ld_i_date_to) | = 99991231. | |||
Search for further information about these or an SAP related objects