SAP EPM_KPI_DEFINITION_GET Function Module for NOTRANSL: Lesen Kennzahl aus Kennzahlenkatalog









EPM_KPI_DEFINITION_GET is a standard epm kpi definition get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen Kennzahl aus Kennzahlenkatalog 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 epm kpi definition get FM, simply by entering the name EPM_KPI_DEFINITION_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: EPM_KPI
Program Name: SAPLEPM_KPI
Main Program: SAPLEPM_KPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function EPM_KPI_DEFINITION_GET 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 'EPM_KPI_DEFINITION_GET'"NOTRANSL: Lesen Kennzahl aus Kennzahlenkatalog
EXPORTING
* I_KPI_ID = "Technical Name of KPI
* I_EPM_PROGRAM = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_EPM_VARIANT = "Variant for R/3 Program that Determines KPIs
* I_BW_AN_PROCESS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_KPI_SOURCE_TYPE = "Type of Source System for KPI
* I_KPI_SOURCE = "KPI Source System
* I_LANGU = "SAP System, Current Language
* I_UNAME = "User Name in User Master Record

IMPORTING
ES_KPI = "KPI with Text

EXCEPTIONS
MISSING_IMPORT_PARAMETER = 1 NO_KPI_FOUND = 2
.



IMPORTING Parameters details for EPM_KPI_DEFINITION_GET

I_KPI_ID - Technical Name of KPI

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

I_EPM_PROGRAM - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_EPM_VARIANT - Variant for R/3 Program that Determines KPIs

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

I_BW_AN_PROCESS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_KPI_SOURCE_TYPE - Type of Source System for KPI

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

I_KPI_SOURCE - KPI Source System

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

I_LANGU - SAP System, Current Language

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

I_UNAME - User Name in User Master Record

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

EXPORTING Parameters details for EPM_KPI_DEFINITION_GET

ES_KPI - KPI with Text

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

EXCEPTIONS details

MISSING_IMPORT_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

NO_KPI_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for EPM_KPI_DEFINITION_GET 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_es_kpi  TYPE EPM_TS_KPI, "   
lv_i_kpi_id  TYPE EPM_KPI_ID, "   
lv_missing_import_parameter  TYPE EPM_KPI_ID, "   
lv_no_kpi_found  TYPE EPM_KPI_ID, "   
lv_i_epm_program  TYPE EPM_PROGRAM, "   
lv_i_epm_variant  TYPE EPM_VARIANT, "   
lv_i_bw_an_process  TYPE EPM_AN_PROCESS, "   
lv_i_kpi_source_type  TYPE EPM_KPI_SOURCE_TYPE, "   
lv_i_kpi_source  TYPE EPM_KPI_SOURCE, "   
lv_i_langu  TYPE SY-LANGU, "   
lv_i_uname  TYPE XUBNAME. "   

  CALL FUNCTION 'EPM_KPI_DEFINITION_GET'  "NOTRANSL: Lesen Kennzahl aus Kennzahlenkatalog
    EXPORTING
         I_KPI_ID = lv_i_kpi_id
         I_EPM_PROGRAM = lv_i_epm_program
         I_EPM_VARIANT = lv_i_epm_variant
         I_BW_AN_PROCESS = lv_i_bw_an_process
         I_KPI_SOURCE_TYPE = lv_i_kpi_source_type
         I_KPI_SOURCE = lv_i_kpi_source
         I_LANGU = lv_i_langu
         I_UNAME = lv_i_uname
    IMPORTING
         ES_KPI = lv_es_kpi
    EXCEPTIONS
        MISSING_IMPORT_PARAMETER = 1
        NO_KPI_FOUND = 2
. " EPM_KPI_DEFINITION_GET




ABAP code using 7.40 inline data declarations to call FM EPM_KPI_DEFINITION_GET

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 LANGU FROM SY INTO @DATA(ld_i_langu).
 
 


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!