SAP K_PLAN_CHECK_PLANVALUES Function Module for









K_PLAN_CHECK_PLANVALUES is a standard k plan check planvalues 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 plan check planvalues FM, simply by entering the name K_PLAN_CHECK_PLANVALUES into the relevant SAP transaction such as SE37 or SE38.

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



Function K_PLAN_CHECK_PLANVALUES 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_PLAN_CHECK_PLANVALUES'"
  EXPORTING
   I_KOKRS =  "Controlling Area
   I_VERSN =  "Version
   I_GJAHR =  "Fiscal Year
*  I_CHECK_CCA = 'X' "
*  I_CHECK_ORDERS = 'X' "Indicator: Test Plan Data for Orders
*  I_CHECK_PROJECTS = 'X' "Indicator: Test Plan Data for Projects
*  I_CHECK_BPS = 'X' "Indicator: Test Plan Data for Business Processes
*  I_PLINT_ONLY = 'X' "

 IMPORTING
   E_VALUES_FOUND =  "Indicator: Plan Data Exists

EXCEPTIONS
   WRONG_INPUT = 1
.



IMPORTING Parameters details for K_PLAN_CHECK_PLANVALUES

I_KOKRS - Controlling Area

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

I_VERSN - Version

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

I_GJAHR - Fiscal Year

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

I_CHECK_CCA -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHECK_ORDERS - Indicator: Test Plan Data for Orders

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHECK_PROJECTS - Indicator: Test Plan Data for Projects

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHECK_BPS - Indicator: Test Plan Data for Business Processes

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLINT_ONLY -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for K_PLAN_CHECK_PLANVALUES

E_VALUES_FOUND - Indicator: Plan Data Exists

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

EXCEPTIONS details

WRONG_INPUT -

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

Copy and paste ABAP code example for K_PLAN_CHECK_PLANVALUES 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_kokrs  TYPE CCSS-KOKRS, "   
lv_wrong_input  TYPE CCSS, "   
lv_e_values_found  TYPE BOOLE-BOOLE, "   
lv_i_versn  TYPE CCSS-VERSN, "   
lv_i_gjahr  TYPE CCSS-GJAHR, "   
lv_i_check_cca  TYPE BOOLE-BOOLE, "   'X'
lv_i_check_orders  TYPE BOOLE-BOOLE, "   'X'
lv_i_check_projects  TYPE BOOLE-BOOLE, "   'X'
lv_i_check_bps  TYPE BOOLE-BOOLE, "   'X'
lv_i_plint_only  TYPE BOOLE-BOOLE. "   'X'

  CALL FUNCTION 'K_PLAN_CHECK_PLANVALUES'  "
    EXPORTING
         I_KOKRS = lv_i_kokrs
         I_VERSN = lv_i_versn
         I_GJAHR = lv_i_gjahr
         I_CHECK_CCA = lv_i_check_cca
         I_CHECK_ORDERS = lv_i_check_orders
         I_CHECK_PROJECTS = lv_i_check_projects
         I_CHECK_BPS = lv_i_check_bps
         I_PLINT_ONLY = lv_i_plint_only
    IMPORTING
         E_VALUES_FOUND = lv_e_values_found
    EXCEPTIONS
        WRONG_INPUT = 1
. " K_PLAN_CHECK_PLANVALUES




ABAP code using 7.40 inline data declarations to call FM K_PLAN_CHECK_PLANVALUES

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 CCSS INTO @DATA(ld_i_kokrs).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_values_found).
 
"SELECT single VERSN FROM CCSS INTO @DATA(ld_i_versn).
 
"SELECT single GJAHR FROM CCSS INTO @DATA(ld_i_gjahr).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check_cca).
DATA(ld_i_check_cca) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check_orders).
DATA(ld_i_check_orders) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check_projects).
DATA(ld_i_check_projects) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check_bps).
DATA(ld_i_check_bps) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_plint_only).
DATA(ld_i_plint_only) = 'X'.
 


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!