SAP PPEDBRCP_POSV_GET2 Function Module for NOTRANSL: RMS-RCP: Lesen Anwendungsobjektdaten von der DB
PPEDBRCP_POSV_GET2 is a standard ppedbrcp posv get2 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: RMS-RCP: Lesen Anwendungsobjektdaten von der DB 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 ppedbrcp posv get2 FM, simply by entering the name PPEDBRCP_POSV_GET2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSDBRCP
Program Name: SAPLPVSDBRCP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPEDBRCP_POSV_GET2 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 'PPEDBRCP_POSV_GET2'"NOTRANSL: RMS-RCP: Lesen Anwendungsobjektdaten von der DB.
EXPORTING
IT_POSVID_LI = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
ET_PVRCPD_LI = "Application Object Data of Recipe
IMPORTING Parameters details for PPEDBRCP_POSV_GET2
IT_POSVID_LI - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: PPET_POSVID_LI_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PPEDBRCP_POSV_GET2
ET_PVRCPD_LI - Application Object Data of Recipe
Data type: PPET7_PVRCPD_LI_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPEDBRCP_POSV_GET2 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_et_pvrcpd_li | TYPE PPET7_PVRCPD_LI_TAB, " | |||
| lv_it_posvid_li | TYPE PPET_POSVID_LI_TAB. " |
|   CALL FUNCTION 'PPEDBRCP_POSV_GET2' "NOTRANSL: RMS-RCP: Lesen Anwendungsobjektdaten von der DB |
| EXPORTING | ||
| IT_POSVID_LI | = lv_it_posvid_li | |
| IMPORTING | ||
| ET_PVRCPD_LI | = lv_et_pvrcpd_li | |
| . " PPEDBRCP_POSV_GET2 | ||
ABAP code using 7.40 inline data declarations to call FM PPEDBRCP_POSV_GET2
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