SAP K_PLAN_CHECK_ACTIVITY_RECORD_C Function Module for









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

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



Function K_PLAN_CHECK_ACTIVITY_RECORD_C 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_ACTIVITY_RECORD_C'"
EXPORTING
I_CSSL_KEY = "
I_CHECK_COKL = "
I_VERSN = "
I_CHECK_VKSTA = "
I_VKSTA = "
I_KATYP = "
* I_EMPFWDL = "
I_VIEW = "
I_PGEBIET = "

IMPORTING
E_LATYPI = "

TABLES
T_PERIODS = "
T_MESG = "
T_KSTAR = "
.



IMPORTING Parameters details for K_PLAN_CHECK_ACTIVITY_RECORD_C

I_CSSL_KEY -

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

I_CHECK_COKL -

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

I_VERSN -

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

I_CHECK_VKSTA -

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

I_VKSTA -

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

I_KATYP -

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

I_EMPFWDL -

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

I_VIEW -

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

I_PGEBIET -

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

EXPORTING Parameters details for K_PLAN_CHECK_ACTIVITY_RECORD_C

E_LATYPI -

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

TABLES Parameters details for K_PLAN_CHECK_ACTIVITY_RECORD_C

T_PERIODS -

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

T_MESG -

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

T_KSTAR -

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

Copy and paste ABAP code example for K_PLAN_CHECK_ACTIVITY_RECORD_C 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_latypi  TYPE COKL-LATYPI, "   
lt_t_periods  TYPE STANDARD TABLE OF PERIODS, "   
lv_i_cssl_key  TYPE CSSL_KEY, "   
lt_t_mesg  TYPE STANDARD TABLE OF MESG, "   
lv_i_check_cokl  TYPE MESG, "   
lv_i_versn  TYPE COKL-VERSN, "   
lt_t_kstar  TYPE STANDARD TABLE OF COO_KSTAR, "   
lv_i_check_vksta  TYPE COO_KSTAR, "   
lv_i_vksta  TYPE COKL-VKSTA, "   
lv_i_katyp  TYPE CSKB-KATYP, "   
lv_i_empfwdl  TYPE COO0S-EMPFWDL, "   
lv_i_view  TYPE COO0S, "   
lv_i_pgebiet  TYPE KPPT-PGEBIET. "   

  CALL FUNCTION 'K_PLAN_CHECK_ACTIVITY_RECORD_C'  "
    EXPORTING
         I_CSSL_KEY = lv_i_cssl_key
         I_CHECK_COKL = lv_i_check_cokl
         I_VERSN = lv_i_versn
         I_CHECK_VKSTA = lv_i_check_vksta
         I_VKSTA = lv_i_vksta
         I_KATYP = lv_i_katyp
         I_EMPFWDL = lv_i_empfwdl
         I_VIEW = lv_i_view
         I_PGEBIET = lv_i_pgebiet
    IMPORTING
         E_LATYPI = lv_e_latypi
    TABLES
         T_PERIODS = lt_t_periods
         T_MESG = lt_t_mesg
         T_KSTAR = lt_t_kstar
. " K_PLAN_CHECK_ACTIVITY_RECORD_C




ABAP code using 7.40 inline data declarations to call FM K_PLAN_CHECK_ACTIVITY_RECORD_C

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 LATYPI FROM COKL INTO @DATA(ld_e_latypi).
 
 
 
 
 
"SELECT single VERSN FROM COKL INTO @DATA(ld_i_versn).
 
 
 
"SELECT single VKSTA FROM COKL INTO @DATA(ld_i_vksta).
 
"SELECT single KATYP FROM CSKB INTO @DATA(ld_i_katyp).
 
"SELECT single EMPFWDL FROM COO0S INTO @DATA(ld_i_empfwdl).
 
 
"SELECT single PGEBIET FROM KPPT INTO @DATA(ld_i_pgebiet).
 


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!