SAP PPC1RP_RP_READ Function Module for NOTRANSL: Lesen Daten zu den ZP-e









PPC1RP_RP_READ is a standard ppc1rp rp read 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 Daten zu den ZP-e 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 ppc1rp rp read FM, simply by entering the name PPC1RP_RP_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function PPC1RP_RP_READ 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 'PPC1RP_RP_READ'"NOTRANSL: Lesen Daten zu den ZP-e
EXPORTING
IF_NODEID = "Header for line identification (Line Design)
IF_COUNTER = "Version of the line/reporting point structure
* IT_REPPOINT = "List of Reporting Points (GUIDs)
* IF_REPPOINT = "Internal reporting point (GIUD 16 Byte)

IMPORTING
IT_REPPOINT_INFO = "Reporting Point Info
.



IMPORTING Parameters details for PPC1RP_RP_READ

IF_NODEID - Header for line identification (Line Design)

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

IF_COUNTER - Version of the line/reporting point structure

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

IT_REPPOINT - List of Reporting Points (GUIDs)

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

IF_REPPOINT - Internal reporting point (GIUD 16 Byte)

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

EXPORTING Parameters details for PPC1RP_RP_READ

IT_REPPOINT_INFO - Reporting Point Info

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

Copy and paste ABAP code example for PPC1RP_RP_READ 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_if_nodeid  TYPE PPC_IPPE_HEADER_INT, "   
lv_it_reppoint_info  TYPE PPC_T_REPPOINT_INFO, "   
lv_if_counter  TYPE PPC_LINE_VERSION, "   
lv_it_reppoint  TYPE PPC_T_REPPOINT, "   
lv_if_reppoint  TYPE PPC_REPPOINT_INT. "   

  CALL FUNCTION 'PPC1RP_RP_READ'  "NOTRANSL: Lesen Daten zu den ZP-e
    EXPORTING
         IF_NODEID = lv_if_nodeid
         IF_COUNTER = lv_if_counter
         IT_REPPOINT = lv_it_reppoint
         IF_REPPOINT = lv_if_reppoint
    IMPORTING
         IT_REPPOINT_INFO = lv_it_reppoint_info
. " PPC1RP_RP_READ




ABAP code using 7.40 inline data declarations to call FM PPC1RP_RP_READ

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!