SAP UPP_PP_KERNEL_PROCESS_EVENT Function Module for Planning Processor: PAI event handling









UPP_PP_KERNEL_PROCESS_EVENT is a standard upp pp kernel process event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Planning Processor: PAI event handling processing and below is the pattern details for this FM, 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 upp pp kernel process event FM, simply by entering the name UPP_PP_KERNEL_PROCESS_EVENT into the relevant SAP transaction such as SE37 or SE38.

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



Function UPP_PP_KERNEL_PROCESS_EVENT 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 'UPP_PP_KERNEL_PROCESS_EVENT'"Planning Processor: PAI event handling
  EXPORTING
   I_OK_CODE =  "Screens, Function Code Triggered by PAI
   I_DATAR =  "Single-Character Flag
   IS_LL_KEY =  "Planinng processor: key of logical screen
   I_HNDL =  "Planningprocessor: Handle for context
*  IS_FUNC =  "Executing a Planning Function with Commit in FW

 IMPORTING
   ET_ERR_MESG =  "Planinng processor: table of messages
   E_OK_CODE_PROCESSED =  "Single-Character Flag
   E_ERROR_MODE =  "Single-Character Flag
   E_DATA_CHANGED =  "Data changed

CHANGING
   XT_LL =  "Planning: logical screen

EXCEPTIONS
   ERROR_IN_PAI = 1    INVALID_HANDLE = 2
.



IMPORTING Parameters details for UPP_PP_KERNEL_PROCESS_EVENT

I_OK_CODE - Screens, Function Code Triggered by PAI

Data type: SYUCOMM
Optional: No
Call by Reference: Yes

I_DATAR - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

IS_LL_KEY - Planinng processor: key of logical screen

Data type: UPP_YS_LL_KEY
Optional: No
Call by Reference: Yes

I_HNDL - Planningprocessor: Handle for context

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

IS_FUNC - Executing a Planning Function with Commit in FW

Data type: UPC_YS_COMMIT_EXEC
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for UPP_PP_KERNEL_PROCESS_EVENT

ET_ERR_MESG - Planinng processor: table of messages

Data type: UPP_YT_MESG
Optional: No
Call by Reference: Yes

E_OK_CODE_PROCESSED - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_ERROR_MODE - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_DATA_CHANGED - Data changed

Data type: CHAR1
Optional: No
Call by Reference: Yes

CHANGING Parameters details for UPP_PP_KERNEL_PROCESS_EVENT

XT_LL - Planning: logical screen

Data type: UPP_YT_LL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_IN_PAI - Error in PAI processing

Data type:
Optional: No
Call by Reference: Yes

INVALID_HANDLE - Invalid handle

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPP_PP_KERNEL_PROCESS_EVENT 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_xt_ll  TYPE UPP_YT_LL, "   
lv_i_ok_code  TYPE SYUCOMM, "   
lv_et_err_mesg  TYPE UPP_YT_MESG, "   
lv_error_in_pai  TYPE UPP_YT_MESG, "   
lv_i_datar  TYPE CHAR1, "   
lv_invalid_handle  TYPE CHAR1, "   
lv_e_ok_code_processed  TYPE CHAR1, "   
lv_is_ll_key  TYPE UPP_YS_LL_KEY, "   
lv_e_error_mode  TYPE CHAR1, "   
lv_i_hndl  TYPE UPP_Y_PP_HNDL, "   
lv_e_data_changed  TYPE CHAR1, "   
lv_is_func  TYPE UPC_YS_COMMIT_EXEC. "   

  CALL FUNCTION 'UPP_PP_KERNEL_PROCESS_EVENT'  "Planning Processor: PAI event handling
    EXPORTING
         I_OK_CODE = lv_i_ok_code
         I_DATAR = lv_i_datar
         IS_LL_KEY = lv_is_ll_key
         I_HNDL = lv_i_hndl
         IS_FUNC = lv_is_func
    IMPORTING
         ET_ERR_MESG = lv_et_err_mesg
         E_OK_CODE_PROCESSED = lv_e_ok_code_processed
         E_ERROR_MODE = lv_e_error_mode
         E_DATA_CHANGED = lv_e_data_changed
    CHANGING
         XT_LL = lv_xt_ll
    EXCEPTIONS
        ERROR_IN_PAI = 1
        INVALID_HANDLE = 2
. " UPP_PP_KERNEL_PROCESS_EVENT




ABAP code using 7.40 inline data declarations to call FM UPP_PP_KERNEL_PROCESS_EVENT

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



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!