SAP BKK_CLOSCTRL_CHECK_ACC_IN_PROC Function Module for Check Whether Account in Processing by Mass Runs
BKK_CLOSCTRL_CHECK_ACC_IN_PROC is a standard bkk closctrl check acc in proc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Account in Processing by Mass Runs 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 closctrl check acc in proc FM, simply by entering the name BKK_CLOSCTRL_CHECK_ACC_IN_PROC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBMJ
Program Name: SAPLFBMJ
Main Program: SAPLFBMJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_CLOSCTRL_CHECK_ACC_IN_PROC 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_CLOSCTRL_CHECK_ACC_IN_PROC'"Check Whether Account in Processing by Mass Runs.
EXPORTING
I_BKKRS = "Bank Area
I_ACCNOINT = "Internal Account Number
* I_XSETDIALOGLOCK = 'X' "Indicator: Dialog Lock if in Processing
* I_XACTIVE_ONLY = 'X' "Indicator: Only Check for Current Processing
* I_EXCL_PROGN = "Exclude Program from check
IMPORTING
E_XINPROCESS = "Indicator 'In Processing'
E_XPROCESS_ACTIVE = "
E_XDIALOGLOCKSET = "Indicator: Dialog Lock Set
E_APPLCATG = "
IMPORTING Parameters details for BKK_CLOSCTRL_CHECK_ACC_IN_PROC
I_BKKRS - Bank Area
Data type: TBKK01-BKKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_ACCNOINT - Internal Account Number
Data type: BKK40-ACNUM_INTOptional: No
Call by Reference: No ( called with pass by value option)
I_XSETDIALOGLOCK - Indicator: Dialog Lock if in Processing
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XACTIVE_ONLY - Indicator: Only Check for Current Processing
Data type: BOOLE-BOOLEDefault: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)
I_EXCL_PROGN - Exclude Program from check
Data type: BKK_PROGNOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BKK_CLOSCTRL_CHECK_ACC_IN_PROC
E_XINPROCESS - Indicator 'In Processing'
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_XPROCESS_ACTIVE -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_XDIALOGLOCKSET - Indicator: Dialog Lock Set
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
E_APPLCATG -
Data type: BKKD_APPLCATGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_CLOSCTRL_CHECK_ACC_IN_PROC 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 TBKK01-BKKRS, " | |||
| lv_e_xinprocess | TYPE BOOLE-BOOLE, " | |||
| lv_i_accnoint | TYPE BKK40-ACNUM_INT, " | |||
| lv_e_xprocess_active | TYPE BOOLE-BOOLE, " | |||
| lv_e_xdialoglockset | TYPE BOOLE-BOOLE, " | |||
| lv_i_xsetdialoglock | TYPE BOOLE-BOOLE, " 'X' | |||
| lv_e_applcatg | TYPE BKKD_APPLCATG, " | |||
| lv_i_xactive_only | TYPE BOOLE-BOOLE, " 'X' | |||
| lv_i_excl_progn | TYPE BKK_PROGN. " |
|   CALL FUNCTION 'BKK_CLOSCTRL_CHECK_ACC_IN_PROC' "Check Whether Account in Processing by Mass Runs |
| EXPORTING | ||
| I_BKKRS | = lv_i_bkkrs | |
| I_ACCNOINT | = lv_i_accnoint | |
| I_XSETDIALOGLOCK | = lv_i_xsetdialoglock | |
| I_XACTIVE_ONLY | = lv_i_xactive_only | |
| I_EXCL_PROGN | = lv_i_excl_progn | |
| IMPORTING | ||
| E_XINPROCESS | = lv_e_xinprocess | |
| E_XPROCESS_ACTIVE | = lv_e_xprocess_active | |
| E_XDIALOGLOCKSET | = lv_e_xdialoglockset | |
| E_APPLCATG | = lv_e_applcatg | |
| . " BKK_CLOSCTRL_CHECK_ACC_IN_PROC | ||
ABAP code using 7.40 inline data declarations to call FM BKK_CLOSCTRL_CHECK_ACC_IN_PROC
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 TBKK01 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_xinprocess). | ||||
| "SELECT single ACNUM_INT FROM BKK40 INTO @DATA(ld_i_accnoint). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_xprocess_active). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_xdialoglockset). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xsetdialoglock). | ||||
| DATA(ld_i_xsetdialoglock) | = 'X'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xactive_only). | ||||
| DATA(ld_i_xactive_only) | = 'X'. | |||
Search for further information about these or an SAP related objects