SAP BKK_IC_CHECK_SUB_ACCNT Function Module for Checks for sub-accounts
BKK_IC_CHECK_SUB_ACCNT is a standard bkk ic check sub accnt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks for sub-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 ic check sub accnt FM, simply by entering the name BKK_IC_CHECK_SUB_ACCNT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBHQ
Program Name: SAPLFBHQ
Main Program: SAPLFBHQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_IC_CHECK_SUB_ACCNT 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_IC_CHECK_SUB_ACCNT'"Checks for sub-accounts.
EXPORTING
I_HYTYPE = "Account Hierarchy: Hierarchy Type
* I_FATHER_BKKRS = "Bank Area
* I_FATHER_ACNUM_INT = "Internal Account Number for Current Account
I_POOL_METH = "Interest Compensation Method
* I_TREENR = "Bank Account Relationship Number
I_BKKRS = "Bank Area
* I_BANKS = "Bank country key
* I_BANKL = "Bank Keys
* I_ACNUM_INT = "Internal Account Number for Current Account
* I_ACNUM_EXT = "Account number for current account
I_DATE_FROM = "Valid from date
I_DATE_TO = "Validity Date (Valid To)
IMPORTING
E_RC = "Return Value of ABAP Statements
IMPORTING Parameters details for BKK_IC_CHECK_SUB_ACCNT
I_HYTYPE - Account Hierarchy: Hierarchy Type
Data type: BKK610-HYTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_FATHER_BKKRS - Bank Area
Data type: BKK40-BKKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FATHER_ACNUM_INT - Internal Account Number for Current Account
Data type: BKK40-ACNUM_INTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_POOL_METH - Interest Compensation Method
Data type: TBKK92-POOL_METHOptional: No
Call by Reference: No ( called with pass by value option)
I_TREENR - Bank Account Relationship Number
Data type: BKK610-TREENROptional: Yes
Call by Reference: Yes
I_BKKRS - Bank Area
Data type: BKK40-BKKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_BANKS - Bank country key
Data type: BKK610-BANKSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BANKL - Bank Keys
Data type: BKK610-BANKLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACNUM_INT - Internal Account Number for Current Account
Data type: BKK40-ACNUM_INTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACNUM_EXT - Account number for current account
Data type: BKK42-ACNUM_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_FROM - Valid from date
Data type: BKK610-DATE_FROMOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_TO - Validity Date (Valid To)
Data type: BKK610-DATE_TOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_IC_CHECK_SUB_ACCNT
E_RC - Return Value of ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_IC_CHECK_SUB_ACCNT 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_e_rc | TYPE SY-SUBRC, " | |||
| lv_i_hytype | TYPE BKK610-HYTYPE, " | |||
| lv_i_father_bkkrs | TYPE BKK40-BKKRS, " | |||
| lv_i_father_acnum_int | TYPE BKK40-ACNUM_INT, " | |||
| lv_i_pool_meth | TYPE TBKK92-POOL_METH, " | |||
| lv_i_treenr | TYPE BKK610-TREENR, " | |||
| lv_i_bkkrs | TYPE BKK40-BKKRS, " | |||
| lv_i_banks | TYPE BKK610-BANKS, " | |||
| lv_i_bankl | TYPE BKK610-BANKL, " | |||
| lv_i_acnum_int | TYPE BKK40-ACNUM_INT, " | |||
| lv_i_acnum_ext | TYPE BKK42-ACNUM_EXT, " | |||
| lv_i_date_from | TYPE BKK610-DATE_FROM, " | |||
| lv_i_date_to | TYPE BKK610-DATE_TO. " |
|   CALL FUNCTION 'BKK_IC_CHECK_SUB_ACCNT' "Checks for sub-accounts |
| EXPORTING | ||
| I_HYTYPE | = lv_i_hytype | |
| I_FATHER_BKKRS | = lv_i_father_bkkrs | |
| I_FATHER_ACNUM_INT | = lv_i_father_acnum_int | |
| I_POOL_METH | = lv_i_pool_meth | |
| I_TREENR | = lv_i_treenr | |
| I_BKKRS | = lv_i_bkkrs | |
| I_BANKS | = lv_i_banks | |
| I_BANKL | = lv_i_bankl | |
| I_ACNUM_INT | = lv_i_acnum_int | |
| I_ACNUM_EXT | = lv_i_acnum_ext | |
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| IMPORTING | ||
| E_RC | = lv_e_rc | |
| . " BKK_IC_CHECK_SUB_ACCNT | ||
ABAP code using 7.40 inline data declarations to call FM BKK_IC_CHECK_SUB_ACCNT
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 SUBRC FROM SY INTO @DATA(ld_e_rc). | ||||
| "SELECT single HYTYPE FROM BKK610 INTO @DATA(ld_i_hytype). | ||||
| "SELECT single BKKRS FROM BKK40 INTO @DATA(ld_i_father_bkkrs). | ||||
| "SELECT single ACNUM_INT FROM BKK40 INTO @DATA(ld_i_father_acnum_int). | ||||
| "SELECT single POOL_METH FROM TBKK92 INTO @DATA(ld_i_pool_meth). | ||||
| "SELECT single TREENR FROM BKK610 INTO @DATA(ld_i_treenr). | ||||
| "SELECT single BKKRS FROM BKK40 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single BANKS FROM BKK610 INTO @DATA(ld_i_banks). | ||||
| "SELECT single BANKL FROM BKK610 INTO @DATA(ld_i_bankl). | ||||
| "SELECT single ACNUM_INT FROM BKK40 INTO @DATA(ld_i_acnum_int). | ||||
| "SELECT single ACNUM_EXT FROM BKK42 INTO @DATA(ld_i_acnum_ext). | ||||
| "SELECT single DATE_FROM FROM BKK610 INTO @DATA(ld_i_date_from). | ||||
| "SELECT single DATE_TO FROM BKK610 INTO @DATA(ld_i_date_to). | ||||
Search for further information about these or an SAP related objects