SAP K_PLAN_CUA_KPP2_SET Function Module for









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

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



Function K_PLAN_CUA_KPP2_SET 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_CUA_KPP2_SET'"
EXPORTING
I_BILDTYP = "

TABLES
* T_KPP0I = "
.



IMPORTING Parameters details for K_PLAN_CUA_KPP2_SET

I_BILDTYP -

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

TABLES Parameters details for K_PLAN_CUA_KPP2_SET

T_KPP0I -

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

Copy and paste ABAP code example for K_PLAN_CUA_KPP2_SET 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:
lt_t_kpp0i  TYPE STANDARD TABLE OF KPP0I, "   
lv_i_bildtyp  TYPE KPP2D-BILDTYP. "   

  CALL FUNCTION 'K_PLAN_CUA_KPP2_SET'  "
    EXPORTING
         I_BILDTYP = lv_i_bildtyp
    TABLES
         T_KPP0I = lt_t_kpp0i
. " K_PLAN_CUA_KPP2_SET




ABAP code using 7.40 inline data declarations to call FM K_PLAN_CUA_KPP2_SET

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 BILDTYP FROM KPP2D INTO @DATA(ld_i_bildtyp).
 


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!