SAP FPP_UI_GET_RUN Function Module for NOTRANSL: Übergibt das Objekt Lauf
FPP_UI_GET_RUN is a standard fpp ui get run 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: Übergibt das Objekt Lauf 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 fpp ui get run FM, simply by entering the name FPP_UI_GET_RUN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPP_UI_APPLICATION
Program Name: SAPLFPP_UI_APPLICATION
Main Program: SAPLFPP_UI_APPLICATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FPP_UI_GET_RUN 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 'FPP_UI_GET_RUN'"NOTRANSL: Übergibt das Objekt Lauf.
IMPORTING
E_RUN = "FPP Services
E_ACTIVITY = "Component of Version Number
EXPORTING Parameters details for FPP_UI_GET_RUN
E_RUN - FPP Services
Data type: CL_FPP_RUNSOptional: No
Call by Reference: Yes
E_ACTIVITY - Component of Version Number
Data type: CHAR2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPP_UI_GET_RUN 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_e_run | TYPE CL_FPP_RUNS, " | |||
| lv_e_activity | TYPE CHAR2. " |
|   CALL FUNCTION 'FPP_UI_GET_RUN' "NOTRANSL: Übergibt das Objekt Lauf |
| IMPORTING | ||
| E_RUN | = lv_e_run | |
| E_ACTIVITY | = lv_e_activity | |
| . " FPP_UI_GET_RUN | ||
ABAP code using 7.40 inline data declarations to call FM FPP_UI_GET_RUN
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