SAP PK_GET_STATUS Function Module for NOTRANSL: Kanban Folgestatus ermitteln

Search SAP Function Modules

PK_GET_STATUS is a standard pk 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 NOTRANSL: Kanban Folgestatus ermitteln 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 get status FM, simply by entering the name PK_GET_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_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 'PK_GET_STATUS'"NOTRANSL: Kanban Folgestatus ermitteln
  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 (=' ')

 IMPORTING
   NEXTSTATUS_EV =  "
   TEMP_NEXTSTATUS_EV =  "

CHANGING
*  ET_WAITING_KANBANS =  "Tables of Waiting Kanbans in Trigger Groups

.

IMPORTING Parameters details for PK_GET_STATUS

PKSAE_IV -

Data type: TPK01-PKSAE
Optional: No
Call by Reference: No ( called with pass by value option)

PKHD_IS -

Data type: PKHD
Optional: No
Call by Reference: Yes

PKPS_IS -

Data type: PKPS
Optional: No
Call by Reference: Yes

TPK00_IS -

Data type: TPK00
Optional: No
Call by Reference: No ( called with pass by value option)

KBB_VIEW_IV - View of the Kanban Board

Data type: KBB_VIEW
Optional: Yes
Call by Reference: Yes

NO_STATUS_RESTR_IV - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PK_GET_STATUS

NEXTSTATUS_EV -

Data type: PKPS-PKBST
Optional: No
Call by Reference: Yes

TEMP_NEXTSTATUS_EV -

Data type: PKBST
Optional: No
Call by Reference: Yes

CHANGING Parameters details for PK_GET_STATUS

ET_WAITING_KANBANS - Tables of Waiting Kanbans in Trigger Groups

Data type: PKWAITING_KANBAN_T
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for PK_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.

ABAP code using 7.40 inline data declarations to call FM PK_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.

Search for further information about these or an SAP related objects