SAP UPP_PP_KERNEL_GET_META_INFO Function Module for Planning Processor features, attributes, DDIC
UPP_PP_KERNEL_GET_META_INFO is a standard upp pp kernel get meta info 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 features, attributes, DDIC 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 meta info FM, simply by entering the name UPP_PP_KERNEL_GET_META_INFO 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_META_INFO 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_META_INFO'"Planning Processor features, attributes, DDIC.
EXPORTING
I_HNDL = "Planningprocessor: Handle for context
IMPORTING
ETO_KD = "Planning processor: table type of dimension table
ETO_KDA = "Planning processor: table type of dim. dependency info
ETH_KDD = "Planning processor: table type of data dict. infos
ET_KU = "Planning processor: table type of user attributes
EXCEPTIONS
INVALID_HANDLE = 1
IMPORTING Parameters details for UPP_PP_KERNEL_GET_META_INFO
I_HNDL - Planningprocessor: Handle for context
Data type: UPP_Y_PP_HNDLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UPP_PP_KERNEL_GET_META_INFO
ETO_KD - Planning processor: table type of dimension table
Data type: UPP_YTO_KDOptional: No
Call by Reference: Yes
ETO_KDA - Planning processor: table type of dim. dependency info
Data type: UPP_YTO_KDAOptional: No
Call by Reference: Yes
ETH_KDD - Planning processor: table type of data dict. infos
Data type: UPP_YTH_KDDOptional: No
Call by Reference: Yes
ET_KU - Planning processor: table type of user attributes
Data type: UPP_YT_KUOptional: 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_META_INFO 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_eto_kd | TYPE UPP_YTO_KD, " | |||
| lv_i_hndl | TYPE UPP_Y_PP_HNDL, " | |||
| lv_invalid_handle | TYPE UPP_Y_PP_HNDL, " | |||
| lv_eto_kda | TYPE UPP_YTO_KDA, " | |||
| lv_eth_kdd | TYPE UPP_YTH_KDD, " | |||
| lv_et_ku | TYPE UPP_YT_KU. " |
|   CALL FUNCTION 'UPP_PP_KERNEL_GET_META_INFO' "Planning Processor features, attributes, DDIC |
| EXPORTING | ||
| I_HNDL | = lv_i_hndl | |
| IMPORTING | ||
| ETO_KD | = lv_eto_kd | |
| ETO_KDA | = lv_eto_kda | |
| ETH_KDD | = lv_eth_kdd | |
| ET_KU | = lv_et_ku | |
| EXCEPTIONS | ||
| INVALID_HANDLE = 1 | ||
| . " UPP_PP_KERNEL_GET_META_INFO | ||
ABAP code using 7.40 inline data declarations to call FM UPP_PP_KERNEL_GET_META_INFO
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