SAP PPEDBHDR_READ_OBJ Function Module for NOTRANSL: Lesen der PPEOBJ-Objekte von der Datenbank
PPEDBHDR_READ_OBJ is a standard ppedbhdr read obj 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 der PPEOBJ-Objekte von der Datenbank 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 ppedbhdr read obj FM, simply by entering the name PPEDBHDR_READ_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: PPEDBHDR
Program Name: SAPLPPEDBHDR
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPEDBHDR_READ_OBJ 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 'PPEDBHDR_READ_OBJ'"NOTRANSL: Lesen der PPEOBJ-Objekte von der Datenbank.
EXPORTING
IT_OBJID = "Internal Identification for PVS Objects
IMPORTING
ET_PPEOBJ = "Object Table
IMPORTING Parameters details for PPEDBHDR_READ_OBJ
IT_OBJID - Internal Identification for PVS Objects
Data type: PPET4_OBJID_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PPEDBHDR_READ_OBJ
ET_PPEOBJ - Object Table
Data type: PPET4_PPEOBJ_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPEDBHDR_READ_OBJ 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_it_objid | TYPE PPET4_OBJID_TAB, " | |||
| lv_et_ppeobj | TYPE PPET4_PPEOBJ_TAB. " |
|   CALL FUNCTION 'PPEDBHDR_READ_OBJ' "NOTRANSL: Lesen der PPEOBJ-Objekte von der Datenbank |
| EXPORTING | ||
| IT_OBJID | = lv_it_objid | |
| IMPORTING | ||
| ET_PPEOBJ | = lv_et_ppeobj | |
| . " PPEDBHDR_READ_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM PPEDBHDR_READ_OBJ
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