SAP RDB_RESULTS_READ_FOR_REP_PH_GV Function Module for RDB Summensätze lesen: GuV
RDB_RESULTS_READ_FOR_REP_PH_GV is a standard rdb results read for rep ph gv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RDB Summensätze lesen: GuV 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 rdb results read for rep ph gv FM, simply by entering the name RDB_RESULTS_READ_FOR_REP_PH_GV into the relevant SAP transaction such as SE37 or SE38.
Function Group: RDB_RESULTS_READ_FOR_REP
Program Name: SAPLRDB_RESULTS_READ_FOR_REP
Main Program: SAPLRDB_RESULTS_READ_FOR_REP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RDB_RESULTS_READ_FOR_REP_PH_GV 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 'RDB_RESULTS_READ_FOR_REP_PH_GV'"RDB Summensätze lesen: GuV.
EXPORTING
I_KEYDATE_TAB = "Stichtage
I_SUMSTATE_TAB = "Stati Endergebnissätze in Ergebnisdatenbanken
I_KEYFIGURE_TAB = "Kennzahlen
I_PHIERA = "Portfoliohierarchie
I_PHNODE = "Portfoliohierarchieknoten
I_RKNOTEN_TAB = "Knoten der Risikohierarchie
IMPORTING
E_SPECIFIC_RESULTS_GUV = "Gewinn & Verlust
CHANGING
* C_LOG_TAB = "Tabellentyp für Fehlerbehandlung
EXCEPTIONS
INIT_ERROR = 1 INTERNAL_ERROR = 2 UNKNOWN_KEYFIGURE = 3
IMPORTING Parameters details for RDB_RESULTS_READ_FOR_REP_PH_GV
I_KEYDATE_TAB - Stichtage
Data type: RDBIF_KEYDATES_TOptional: No
Call by Reference: No ( called with pass by value option)
I_SUMSTATE_TAB - Stati Endergebnissätze in Ergebnisdatenbanken
Data type: RDBIF_SUMSTATES_TOptional: No
Call by Reference: No ( called with pass by value option)
I_KEYFIGURE_TAB - Kennzahlen
Data type: AFWKF_DEFINITION_TOptional: No
Call by Reference: No ( called with pass by value option)
I_PHIERA - Portfoliohierarchie
Data type: AFW_PHIERAOptional: No
Call by Reference: No ( called with pass by value option)
I_PHNODE - Portfoliohierarchieknoten
Data type: AFW_PHNODEOptional: No
Call by Reference: No ( called with pass by value option)
I_RKNOTEN_TAB - Knoten der Risikohierarchie
Data type: RDBIF_RKNOTEN_TOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RDB_RESULTS_READ_FOR_REP_PH_GV
E_SPECIFIC_RESULTS_GUV - Gewinn & Verlust
Data type: RDBIF_RAG1_EX_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for RDB_RESULTS_READ_FOR_REP_PH_GV
C_LOG_TAB - Tabellentyp für Fehlerbehandlung
Data type: BAPIERR_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INIT_ERROR - Keine oder fehlerhafte Initialisierung
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Fehler in der Verarbeitung
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_KEYFIGURE - Unbekannte Kennzahl
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RDB_RESULTS_READ_FOR_REP_PH_GV 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_c_log_tab | TYPE BAPIERR_T, " | |||
| lv_init_error | TYPE BAPIERR_T, " | |||
| lv_i_keydate_tab | TYPE RDBIF_KEYDATES_T, " | |||
| lv_e_specific_results_guv | TYPE RDBIF_RAG1_EX_TAB, " | |||
| lv_internal_error | TYPE RDBIF_RAG1_EX_TAB, " | |||
| lv_i_sumstate_tab | TYPE RDBIF_SUMSTATES_T, " | |||
| lv_i_keyfigure_tab | TYPE AFWKF_DEFINITION_T, " | |||
| lv_unknown_keyfigure | TYPE AFWKF_DEFINITION_T, " | |||
| lv_i_phiera | TYPE AFW_PHIERA, " | |||
| lv_i_phnode | TYPE AFW_PHNODE, " | |||
| lv_i_rknoten_tab | TYPE RDBIF_RKNOTEN_T. " |
|   CALL FUNCTION 'RDB_RESULTS_READ_FOR_REP_PH_GV' "RDB Summensätze lesen: GuV |
| EXPORTING | ||
| I_KEYDATE_TAB | = lv_i_keydate_tab | |
| I_SUMSTATE_TAB | = lv_i_sumstate_tab | |
| I_KEYFIGURE_TAB | = lv_i_keyfigure_tab | |
| I_PHIERA | = lv_i_phiera | |
| I_PHNODE | = lv_i_phnode | |
| I_RKNOTEN_TAB | = lv_i_rknoten_tab | |
| IMPORTING | ||
| E_SPECIFIC_RESULTS_GUV | = lv_e_specific_results_guv | |
| CHANGING | ||
| C_LOG_TAB | = lv_c_log_tab | |
| EXCEPTIONS | ||
| INIT_ERROR = 1 | ||
| INTERNAL_ERROR = 2 | ||
| UNKNOWN_KEYFIGURE = 3 | ||
| . " RDB_RESULTS_READ_FOR_REP_PH_GV | ||
ABAP code using 7.40 inline data declarations to call FM RDB_RESULTS_READ_FOR_REP_PH_GV
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