SAP BKK_PA_PROCESS_GET_STATUS Function Module for Retrieve Status of Current Application Processes
BKK_PA_PROCESS_GET_STATUS is a standard bkk pa process get status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve Status of Current Application Processes 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 pa process get status FM, simply by entering the name BKK_PA_PROCESS_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBMH
Program Name: SAPLFBMH
Main Program: SAPLFBMH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_PA_PROCESS_GET_STATUS 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_PA_PROCESS_GET_STATUS'"Retrieve Status of Current Application Processes.
EXPORTING
* I_PROGN = "
* I_PROGDATE = "
* I_PROGNO = "
* I_TAB_RUNKEY = "
* I_APPLCATG = "
* I_R_APPLCATG = "
* I_XFORCE_DB_READ = "
IMPORTING
E_CURRSTATUS = "
E_REALSTATUS = "
E_TAB_RUNSTAT = "
TABLES
* I_T_WHERE = "
IMPORTING Parameters details for BKK_PA_PROCESS_GET_STATUS
I_PROGN -
Data type: BKKD_PROGNOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGDATE -
Data type: BKKD_PROGDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGNO -
Data type: BKKD_PROGNOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_RUNKEY -
Data type: BKKD_TAB_RUNKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_APPLCATG -
Data type: BKKD_APPLCATGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_R_APPLCATG -
Data type: BKKD_R_APPLCATGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XFORCE_DB_READ -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_PA_PROCESS_GET_STATUS
E_CURRSTATUS -
Data type: BKKD_RUNSTATUSOptional: No
Call by Reference: No ( called with pass by value option)
E_REALSTATUS -
Data type: BKKD_RUNSTATUSOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_RUNSTAT -
Data type: BKKD_TAB_RUNKEY_STATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BKK_PA_PROCESS_GET_STATUS
I_T_WHERE -
Data type: RSDSWHEREOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_PA_PROCESS_GET_STATUS 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_progn | TYPE BKKD_PROGN, " | |||
| lt_i_t_where | TYPE STANDARD TABLE OF RSDSWHERE, " | |||
| lv_e_currstatus | TYPE BKKD_RUNSTATUS, " | |||
| lv_i_progdate | TYPE BKKD_PROGDATE, " | |||
| lv_e_realstatus | TYPE BKKD_RUNSTATUS, " | |||
| lv_i_progno | TYPE BKKD_PROGNO, " | |||
| lv_e_tab_runstat | TYPE BKKD_TAB_RUNKEY_STAT, " | |||
| lv_i_tab_runkey | TYPE BKKD_TAB_RUNKEY, " | |||
| lv_i_applcatg | TYPE BKKD_APPLCATG, " | |||
| lv_i_r_applcatg | TYPE BKKD_R_APPLCATG, " | |||
| lv_i_xforce_db_read | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'BKK_PA_PROCESS_GET_STATUS' "Retrieve Status of Current Application Processes |
| EXPORTING | ||
| I_PROGN | = lv_i_progn | |
| I_PROGDATE | = lv_i_progdate | |
| I_PROGNO | = lv_i_progno | |
| I_TAB_RUNKEY | = lv_i_tab_runkey | |
| I_APPLCATG | = lv_i_applcatg | |
| I_R_APPLCATG | = lv_i_r_applcatg | |
| I_XFORCE_DB_READ | = lv_i_xforce_db_read | |
| IMPORTING | ||
| E_CURRSTATUS | = lv_e_currstatus | |
| E_REALSTATUS | = lv_e_realstatus | |
| E_TAB_RUNSTAT | = lv_e_tab_runstat | |
| TABLES | ||
| I_T_WHERE | = lt_i_t_where | |
| . " BKK_PA_PROCESS_GET_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM BKK_PA_PROCESS_GET_STATUS
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