SAP PK_CHECK_STATUS Function Module for NOTRANSL: Prüfen des Feolgestatus eines Kanbans
PK_CHECK_STATUS is a standard pk check 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 NOTRANSL: Prüfen des Feolgestatus eines Kanbans 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 pk check status FM, simply by entering the name PK_CHECK_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: MPKA
Program Name: SAPLMPKA
Main Program: SAPLMPKA
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PK_CHECK_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 'PK_CHECK_STATUS'"NOTRANSL: Prüfen des Feolgestatus eines Kanbans.
EXPORTING
PKSAE_IV = "
PKHD_IS = "
PKPS_IS = "
TPK00_IS = "
* KBB_VIEW_IV = "View of the Kanban Board
* NO_STATUS_RESTR_IV = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
CHANGING
NEXTSTATUS = "
* ET_WAITING_KANBANS = "Tables of Waiting Kanbans in Trigger Groups
IMPORTING Parameters details for PK_CHECK_STATUS
PKSAE_IV -
Data type: TPK01-PKSAEOptional: No
Call by Reference: Yes
PKHD_IS -
Data type: PKHDOptional: No
Call by Reference: Yes
PKPS_IS -
Data type: PKPSOptional: No
Call by Reference: Yes
TPK00_IS -
Data type: TPK00Optional: No
Call by Reference: Yes
KBB_VIEW_IV - View of the Kanban Board
Data type: KBB_VIEWOptional: Yes
Call by Reference: Yes
NO_STATUS_RESTR_IV - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: SPACE
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for PK_CHECK_STATUS
NEXTSTATUS -
Data type: PKPS-PKBSTOptional: No
Call by Reference: Yes
ET_WAITING_KANBANS - Tables of Waiting Kanbans in Trigger Groups
Data type: PKWAITING_KANBAN_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PK_CHECK_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_pksae_iv | TYPE TPK01-PKSAE, " | |||
| lv_nextstatus | TYPE PKPS-PKBST, " | |||
| lv_pkhd_is | TYPE PKHD, " | |||
| lv_et_waiting_kanbans | TYPE PKWAITING_KANBAN_T, " | |||
| lv_pkps_is | TYPE PKPS, " | |||
| lv_tpk00_is | TYPE TPK00, " | |||
| lv_kbb_view_iv | TYPE KBB_VIEW, " | |||
| lv_no_status_restr_iv | TYPE BOOLE_D. " SPACE |
|   CALL FUNCTION 'PK_CHECK_STATUS' "NOTRANSL: Prüfen des Feolgestatus eines Kanbans |
| EXPORTING | ||
| PKSAE_IV | = lv_pksae_iv | |
| PKHD_IS | = lv_pkhd_is | |
| PKPS_IS | = lv_pkps_is | |
| TPK00_IS | = lv_tpk00_is | |
| KBB_VIEW_IV | = lv_kbb_view_iv | |
| NO_STATUS_RESTR_IV | = lv_no_status_restr_iv | |
| CHANGING | ||
| NEXTSTATUS | = lv_nextstatus | |
| ET_WAITING_KANBANS | = lv_et_waiting_kanbans | |
| . " PK_CHECK_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM PK_CHECK_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 PKSAE FROM TPK01 INTO @DATA(ld_pksae_iv). | ||||
| "SELECT single PKBST FROM PKPS INTO @DATA(ld_nextstatus). | ||||
| DATA(ld_no_status_restr_iv) | = ' '. | |||
Search for further information about these or an SAP related objects