SAP UPP_PP_KERNEL_GET_LOG_SCREEN Function Module for Planning Processor: get logical screen

Search SAP Function Modules

UPP_PP_KERNEL_GET_LOG_SCREEN is a standard upp pp kernel get log screen 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: get logical screen 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 get log screen FM, simply by entering the name UPP_PP_KERNEL_GET_LOG_SCREEN 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_GET_LOG_SCREEN 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_GET_LOG_SCREEN'"Planning Processor: get logical screen
  EXPORTING
   I_HNDL =  "Planningprocessor: Handle for context

 IMPORTING
   ET_LL =  "Planning: Logical screen
   ETO_PARENT_CHILD =  "Planning: Parent - Child relation on logical screen
   ETO_PARENT_CHILD_COL =  "Planning: Parent - Child relation on logical screen
   ES_HIE_ATTR =  "Hierarchy attributes
   E_ERROR_MODE =  "Single-Character Flag
   E_SHOW_DOC =  "Single-Character Flag

EXCEPTIONS
   INVALID_HANDLE = 1 

.

IMPORTING Parameters details for UPP_PP_KERNEL_GET_LOG_SCREEN

I_HNDL - Planningprocessor: Handle for context

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

EXPORTING Parameters details for UPP_PP_KERNEL_GET_LOG_SCREEN

ET_LL - Planning: Logical screen

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

ETO_PARENT_CHILD - Planning: Parent - Child relation on logical screen

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

ETO_PARENT_CHILD_COL - Planning: Parent - Child relation on logical screen

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

ES_HIE_ATTR - Hierarchy attributes

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

E_ERROR_MODE - Single-Character Flag

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

E_SHOW_DOC - Single-Character Flag

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

EXCEPTIONS details

INVALID_HANDLE - Invalid handle

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPP_PP_KERNEL_GET_LOG_SCREEN 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.

ABAP code using 7.40 inline data declarations to call FM UPP_PP_KERNEL_GET_LOG_SCREEN

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