SAP K_PLANBK_CHECK Function Module for









K_PLANBK_CHECK is a standard k planbk check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 k planbk check FM, simply by entering the name K_PLANBK_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: KIPL
Program Name: SAPLKIPL
Main Program: SAPLKIPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K_PLANBK_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 'K_PLANBK_CHECK'"
EXPORTING
IRKBKPL = "
* IRKU01_CUR = ' ' "
* IRKU02_CUR = ' ' "

IMPORTING
BKPL_NOT_VALID = "
KOKRS = "
KTOPL = "
ITKA00 = "
ITKA01 = "
ITKA07 = "
ITKA09 = "

TABLES
* IT_COIOB = "Conversion of Object Number and Object Data

EXCEPTIONS
BLOCKED_VERSION = 1 VERSN_NOT_FOUND = 10 VRGNG_NOT_FOUND = 11 VRGNG_BLOCKED = 12 RWIN_ERROR = 13 KOKRS_NOT_FOUND = 2 NO_NUMKR = 3 NO_PARAMETER = 4 NO_PLANNING = 5 NO_PLAN_ACTIVITY = 6 NO_VERSION_IN_GJAHR = 7 PERBI_TO_HIGH = 8 PERIV_NOT_FOUND = 9
.



IMPORTING Parameters details for K_PLANBK_CHECK

IRKBKPL -

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

IRKU01_CUR -

Data type: RKU01_CUR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IRKU02_CUR -

Data type: RKU02_CUR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for K_PLANBK_CHECK

BKPL_NOT_VALID -

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

KOKRS -

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

KTOPL -

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

ITKA00 -

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

ITKA01 -

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

ITKA07 -

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

ITKA09 -

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

TABLES Parameters details for K_PLANBK_CHECK

IT_COIOB - Conversion of Object Number and Object Data

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

EXCEPTIONS details

BLOCKED_VERSION - Version is locked

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

VERSN_NOT_FOUND - Version not defined

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

VRGNG_NOT_FOUND - Transaction/Event not Defined

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

VRGNG_BLOCKED - Period Is Locked

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

RWIN_ERROR -

Data type:
Optional: No
Call by Reference: Yes

KOKRS_NOT_FOUND - Controlling area does not exist

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

NO_NUMKR - No number range defined

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

NO_PARAMETER - Plan parameter not available

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

NO_PLANNING - Version without plan data

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

NO_PLAN_ACTIVITY - Transaction not from manual planning

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

NO_VERSION_IN_GJAHR - Version in fiscal year not defined

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

PERBI_TO_HIGH - To plan period too large

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

PERIV_NOT_FOUND - Fiscal year version not available

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

Copy and paste ABAP code example for K_PLANBK_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:
lv_irkbkpl  TYPE RKBKPL, "   
lt_it_coiob  TYPE STANDARD TABLE OF COIOB, "   
lv_bkpl_not_valid  TYPE COIOB, "   
lv_blocked_version  TYPE COIOB, "   
lv_versn_not_found  TYPE COIOB, "   
lv_vrgng_not_found  TYPE COIOB, "   
lv_vrgng_blocked  TYPE COIOB, "   
lv_rwin_error  TYPE COIOB, "   
lv_kokrs  TYPE TKA01-KOKRS, "   
lv_irku01_cur  TYPE RKU01_CUR, "   SPACE
lv_kokrs_not_found  TYPE RKU01_CUR, "   
lv_ktopl  TYPE T004-KTOPL, "   
lv_no_numkr  TYPE T004, "   
lv_irku02_cur  TYPE RKU02_CUR, "   SPACE
lv_itka00  TYPE TKA00, "   
lv_no_parameter  TYPE TKA00, "   
lv_itka01  TYPE TKA01, "   
lv_no_planning  TYPE TKA01, "   
lv_itka07  TYPE TKA07, "   
lv_no_plan_activity  TYPE TKA07, "   
lv_itka09  TYPE TKA09, "   
lv_no_version_in_gjahr  TYPE TKA09, "   
lv_perbi_to_high  TYPE TKA09, "   
lv_periv_not_found  TYPE TKA09. "   

  CALL FUNCTION 'K_PLANBK_CHECK'  "
    EXPORTING
         IRKBKPL = lv_irkbkpl
         IRKU01_CUR = lv_irku01_cur
         IRKU02_CUR = lv_irku02_cur
    IMPORTING
         BKPL_NOT_VALID = lv_bkpl_not_valid
         KOKRS = lv_kokrs
         KTOPL = lv_ktopl
         ITKA00 = lv_itka00
         ITKA01 = lv_itka01
         ITKA07 = lv_itka07
         ITKA09 = lv_itka09
    TABLES
         IT_COIOB = lt_it_coiob
    EXCEPTIONS
        BLOCKED_VERSION = 1
        VERSN_NOT_FOUND = 10
        VRGNG_NOT_FOUND = 11
        VRGNG_BLOCKED = 12
        RWIN_ERROR = 13
        KOKRS_NOT_FOUND = 2
        NO_NUMKR = 3
        NO_PARAMETER = 4
        NO_PLANNING = 5
        NO_PLAN_ACTIVITY = 6
        NO_VERSION_IN_GJAHR = 7
        PERBI_TO_HIGH = 8
        PERIV_NOT_FOUND = 9
. " K_PLANBK_CHECK




ABAP code using 7.40 inline data declarations to call FM K_PLANBK_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 KOKRS FROM TKA01 INTO @DATA(ld_kokrs).
 
DATA(ld_irku01_cur) = ' '.
 
 
"SELECT single KTOPL FROM T004 INTO @DATA(ld_ktopl).
 
 
DATA(ld_irku02_cur) = ' '.
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!