SAP PPEUIREP_EXAMPLE Function Module for NOTRANSL: Beispiel für die Schnittstelle iPPE-Workbench - Berichte









PPEUIREP_EXAMPLE is a standard ppeuirep example 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: Beispiel für die Schnittstelle iPPE-Workbench - Berichte 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 ppeuirep example FM, simply by entering the name PPEUIREP_EXAMPLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PPEUIREP
Program Name: SAPLPPEUIREP
Main Program: SAPLPPEUIREP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PPEUIREP_EXAMPLE 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 'PPEUIREP_EXAMPLE'"NOTRANSL: Beispiel für die Schnittstelle iPPE-Workbench - Berichte
EXPORTING
* IS_DATA = "Dialog Structure for Navigation Tree - Core Elements
* IS_EXPL_STATUS = "Explosion Parameter
* IS_GUI_STATUS = "GUI Status

IMPORTING
ES_BALMI = "Application Log: APPL_LOG_WRITE_MESSAGES interface
.



IMPORTING Parameters details for PPEUIREP_EXAMPLE

IS_DATA - Dialog Structure for Navigation Tree - Core Elements

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

IS_EXPL_STATUS - Explosion Parameter

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

IS_GUI_STATUS - GUI Status

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

EXPORTING Parameters details for PPEUIREP_EXAMPLE

ES_BALMI - Application Log: APPL_LOG_WRITE_MESSAGES interface

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

Copy and paste ABAP code example for PPEUIREP_EXAMPLE 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_is_data  TYPE PPEGIMAP_CORE, "   
lv_es_balmi  TYPE BALMI, "   
lv_is_expl_status  TYPE PPET0_EXPL_STATUS, "   
lv_is_gui_status  TYPE PPET0_GUI_STATUS. "   

  CALL FUNCTION 'PPEUIREP_EXAMPLE'  "NOTRANSL: Beispiel für die Schnittstelle iPPE-Workbench - Berichte
    EXPORTING
         IS_DATA = lv_is_data
         IS_EXPL_STATUS = lv_is_expl_status
         IS_GUI_STATUS = lv_is_gui_status
    IMPORTING
         ES_BALMI = lv_es_balmi
. " PPEUIREP_EXAMPLE




ABAP code using 7.40 inline data declarations to call FM PPEUIREP_EXAMPLE

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!