SAP K_PLAN_CHECK_PAGING_FUNCTION Function Module for









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

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



Function K_PLAN_CHECK_PAGING_FUNCTION 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_PAGING_FUNCTION'"
EXPORTING
I_OKCODE = "

EXCEPTIONS
NO_PAGING_FUNCTION = 1
.



IMPORTING Parameters details for K_PLAN_CHECK_PAGING_FUNCTION

I_OKCODE -

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

EXCEPTIONS details

NO_PAGING_FUNCTION -

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

Copy and paste ABAP code example for K_PLAN_CHECK_PAGING_FUNCTION 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_okcode  TYPE RSEU1-FUNC_1, "   
lv_no_paging_function  TYPE RSEU1. "   

  CALL FUNCTION 'K_PLAN_CHECK_PAGING_FUNCTION'  "
    EXPORTING
         I_OKCODE = lv_i_okcode
    EXCEPTIONS
        NO_PAGING_FUNCTION = 1
. " K_PLAN_CHECK_PAGING_FUNCTION




ABAP code using 7.40 inline data declarations to call FM K_PLAN_CHECK_PAGING_FUNCTION

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 FUNC_1 FROM RSEU1 INTO @DATA(ld_i_okcode).
 
 


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!