SAP BKK_PER_TASK_AUTHORITY_CHECK Function Module for Authorization Check for Periodic Tasks
BKK_PER_TASK_AUTHORITY_CHECK is a standard bkk per task authority check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Authorization Check for Periodic Tasks 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 per task authority check FM, simply by entering the name BKK_PER_TASK_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB0AUREP
Program Name: SAPLFB0AUREP
Main Program: SAPLFB0AUREP
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_PER_TASK_AUTHORITY_CHECK 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_PER_TASK_AUTHORITY_CHECK'"Authorization Check for Periodic Tasks.
EXPORTING
I_OBJECT = "Object
I_METHOD = "Method
I_ACTVT = "16: Execute, 48: Simulate
* I_BKKRS = "Either 1 Bank Area
* I_FLG_MSG_HANDLER = 'X' "
IMPORTING
E_METHOD_ALLOWED = "0: Yes/ 1: No/ 2: Method Not Checked
E_STR_MESSAGE = "Application Log: Message Data
TABLES
* R_BKKRS = "Or Range of Bank Areas
IMPORTING Parameters details for BKK_PER_TASK_AUTHORITY_CHECK
I_OBJECT - Object
Data type: TBKK_EMP_OBJMTH-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
I_METHOD - Method
Data type: TBKK_EMP_OBJMTH-METHODOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTVT - 16: Execute, 48: Simulate
Data type: TACT-ACTVTOptional: No
Call by Reference: No ( called with pass by value option)
I_BKKRS - Either 1 Bank Area
Data type: TBKK01-BKKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_MSG_HANDLER -
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_PER_TASK_AUTHORITY_CHECK
E_METHOD_ALLOWED - 0: Yes/ 1: No/ 2: Method Not Checked
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
E_STR_MESSAGE - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
TABLES Parameters details for BKK_PER_TASK_AUTHORITY_CHECK
R_BKKRS - Or Range of Bank Areas
Data type: BKK_R_BKKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_PER_TASK_AUTHORITY_CHECK 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: | ||||
| lt_r_bkkrs | TYPE STANDARD TABLE OF BKK_R_BKKRS, " | |||
| lv_i_object | TYPE TBKK_EMP_OBJMTH-OBJECT, " | |||
| lv_e_method_allowed | TYPE SY-SUBRC, " | |||
| lv_i_method | TYPE TBKK_EMP_OBJMTH-METHOD, " | |||
| lv_e_str_message | TYPE BAL_S_MSG, " | |||
| lv_i_actvt | TYPE TACT-ACTVT, " | |||
| lv_i_bkkrs | TYPE TBKK01-BKKRS, " | |||
| lv_i_flg_msg_handler | TYPE BOOLE-BOOLE. " 'X' |
|   CALL FUNCTION 'BKK_PER_TASK_AUTHORITY_CHECK' "Authorization Check for Periodic Tasks |
| EXPORTING | ||
| I_OBJECT | = lv_i_object | |
| I_METHOD | = lv_i_method | |
| I_ACTVT | = lv_i_actvt | |
| I_BKKRS | = lv_i_bkkrs | |
| I_FLG_MSG_HANDLER | = lv_i_flg_msg_handler | |
| IMPORTING | ||
| E_METHOD_ALLOWED | = lv_e_method_allowed | |
| E_STR_MESSAGE | = lv_e_str_message | |
| TABLES | ||
| R_BKKRS | = lt_r_bkkrs | |
| . " BKK_PER_TASK_AUTHORITY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BKK_PER_TASK_AUTHORITY_CHECK
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 OBJECT FROM TBKK_EMP_OBJMTH INTO @DATA(ld_i_object). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_method_allowed). | ||||
| "SELECT single METHOD FROM TBKK_EMP_OBJMTH INTO @DATA(ld_i_method). | ||||
| "SELECT single ACTVT FROM TACT INTO @DATA(ld_i_actvt). | ||||
| "SELECT single BKKRS FROM TBKK01 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_msg_handler). | ||||
| DATA(ld_i_flg_msg_handler) | = 'X'. | |||
Search for further information about these or an SAP related objects