SAP UPX_KPI_API_SAVE Function Module for to save the BPS data on the CRM demand









UPX_KPI_API_SAVE is a standard upx kpi api save 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 save the BPS data on the CRM demand 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 save FM, simply by entering the name UPX_KPI_API_SAVE 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_SAVE 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_SAVE'"to save the BPS data on the CRM demand
EXPORTING
* I_APP = "CRM Planning Application

TABLES
* ET_RETURN = "Return Parameter
.



IMPORTING Parameters details for UPX_KPI_API_SAVE

I_APP - CRM Planning Application

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

TABLES Parameters details for UPX_KPI_API_SAVE

ET_RETURN - Return Parameter

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

Copy and paste ABAP code example for UPX_KPI_API_SAVE 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_et_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'UPX_KPI_API_SAVE'  "to save the BPS data on the CRM demand
    EXPORTING
         I_APP = lv_i_app
    TABLES
         ET_RETURN = lt_et_return
. " UPX_KPI_API_SAVE




ABAP code using 7.40 inline data declarations to call FM UPX_KPI_API_SAVE

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!