SAP UPX_KPI_API_DATA_GET Function Module for to get the data from SEM to CRM









UPX_KPI_API_DATA_GET is a standard upx kpi api data 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 to get the data from SEM to CRM 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 upx kpi api data get FM, simply by entering the name UPX_KPI_API_DATA_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function UPX_KPI_API_DATA_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 'UPX_KPI_API_DATA_GET'"to get the data from SEM to CRM
  EXPORTING
   I_APP =  "CRM Planning Application
   I_OBJECTID =  "Field for any characteristic value
   I_PROFILE =  "Planning Profile
*  I_DETAIL =  "level of detail - 0..3
*  I_VERSION =  "Object Version
*  I_OBJECTNM =  "Object element - 0CRM_MTKELM etc...

TABLES
   IT_ATTRIBUTE =  "Known Selection within Synchronization Profile
*  ET_DATA_CHAVL =  "Known Selection within Synchronization Profile
*  ET_DATA_KYFVL =  "Known Selection within Synchronization Profile
*  ET_RETURN =  "Return Parameter
.



IMPORTING Parameters details for UPX_KPI_API_DATA_GET

I_APP - CRM Planning Application

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

I_OBJECTID - Field for any characteristic value

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

I_PROFILE - Planning Profile

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

I_DETAIL - level of detail - 0..3

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

I_VERSION - Object Version

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

I_OBJECTNM - Object element - 0CRM_MTKELM etc...

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

TABLES Parameters details for UPX_KPI_API_DATA_GET

IT_ATTRIBUTE - Known Selection within Synchronization Profile

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

ET_DATA_CHAVL - Known Selection within Synchronization Profile

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

ET_DATA_KYFVL - Known Selection within Synchronization Profile

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

ET_RETURN - Return Parameter

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

Copy and paste ABAP code example for UPX_KPI_API_DATA_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_i_app  TYPE UPX_Y_KPI_APP, "   
lt_it_attribute  TYPE STANDARD TABLE OF UPX_YS_KPI_ATTR_CHAVL, "   
lv_i_objectid  TYPE UPC_Y_CHAVLINT, "   
lt_et_data_chavl  TYPE STANDARD TABLE OF UPX_YS_KPI_DATA_CHAVL, "   
lv_i_profile  TYPE UPC_Y_PROFILE, "   
lt_et_data_kyfvl  TYPE STANDARD TABLE OF UPX_YS_KPI_DATA_KYFVL, "   
lv_i_detail  TYPE CHAR1, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_version  TYPE UPC_Y_CHAVLINT, "   
lv_i_objectnm  TYPE UPC_Y_CHANM. "   

  CALL FUNCTION 'UPX_KPI_API_DATA_GET'  "to get the data from SEM to CRM
    EXPORTING
         I_APP = lv_i_app
         I_OBJECTID = lv_i_objectid
         I_PROFILE = lv_i_profile
         I_DETAIL = lv_i_detail
         I_VERSION = lv_i_version
         I_OBJECTNM = lv_i_objectnm
    TABLES
         IT_ATTRIBUTE = lt_it_attribute
         ET_DATA_CHAVL = lt_et_data_chavl
         ET_DATA_KYFVL = lt_et_data_kyfvl
         ET_RETURN = lt_et_return
. " UPX_KPI_API_DATA_GET




ABAP code using 7.40 inline data declarations to call FM UPX_KPI_API_DATA_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.

 
 
 
 
 
 
 
 
 
 


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!