SAP K_PLAN_CREATE_SYSTEM_VARIANT Function Module for
K_PLAN_CREATE_SYSTEM_VARIANT is a standard k plan create system variant 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 create system variant FM, simply by entering the name K_PLAN_CREATE_SYSTEM_VARIANT into the relevant SAP transaction such as SE37 or SE38.
Function Group: KPP2
Program Name: SAPLKPP2
Main Program: SAPLKPP2
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_PLAN_CREATE_SYSTEM_VARIANT 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_CREATE_SYSTEM_VARIANT'".
EXPORTING
I_TKES1 = "
IMPORTING
E_MESG = "
TABLES
ITKPP1LG = "
IMPORTING Parameters details for K_PLAN_CREATE_SYSTEM_VARIANT
I_TKES1 -
Data type: TKES1Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for K_PLAN_CREATE_SYSTEM_VARIANT
E_MESG -
Data type: MESGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for K_PLAN_CREATE_SYSTEM_VARIANT
ITKPP1LG -
Data type: KPP1LGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for K_PLAN_CREATE_SYSTEM_VARIANT 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_e_mesg | TYPE MESG, " | |||
| lv_i_tkes1 | TYPE TKES1, " | |||
| lt_itkpp1lg | TYPE STANDARD TABLE OF KPP1LG. " |
|   CALL FUNCTION 'K_PLAN_CREATE_SYSTEM_VARIANT' " |
| EXPORTING | ||
| I_TKES1 | = lv_i_tkes1 | |
| IMPORTING | ||
| E_MESG | = lv_e_mesg | |
| TABLES | ||
| ITKPP1LG | = lt_itkpp1lg | |
| . " K_PLAN_CREATE_SYSTEM_VARIANT | ||
ABAP code using 7.40 inline data declarations to call FM K_PLAN_CREATE_SYSTEM_VARIANT
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