SAP RM_PH_EVAL_DATA_CHECK Function Module for RM: prüft PH auf abhängige Auswertungsdaten
RM_PH_EVAL_DATA_CHECK is a standard rm ph eval data check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: prüft PH auf abhängige Auswertungsdaten 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 rm ph eval data check FM, simply by entering the name RM_PH_EVAL_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBRJ
Program Name: SAPLJBRJ
Main Program: SAPLJBRJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_PH_EVAL_DATA_CHECK 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 'RM_PH_EVAL_DATA_CHECK'"RM: prüft PH auf abhängige Auswertungsdaten.
EXPORTING
I_VIEW = "Sicht
I_PH = "Portfoliohierarchie
* I_MODE = ' ' "'I': exp. Info-Flags ; 'G' Generierungsprüfung
* I_PHCHECK = '8' "Status Check PH-Definition
* I_MHCHECK = '8' "Status Check MH-Definition
* I_DEF_FLID = "Filter: Name
* I_GEN_FLID = "Filter: Name
IMPORTING
E_BDS = "'X' = BDS-Läufe zur PH vorhanden
E_RDB = "'X' = RDB-Kennzahlen zur PH vorhanden
E_ALM = "'X' = ALM Planungsvarianten
E_PHDEF = "'X' = PH-Definition anweichend
E_MHDEF = "'X' = MH-Definition anweichend
E_FLID_GEN = "ursprüngliche Filterzuordnung
TABLES
* I_JBRPHDEF = "Definitionen, aus denen sich die PortfHier ableitet
EXCEPTIONS
EVAL_DATA_EXIST = 1 EVAL_DATA_ADAPT = 2 NO_PHDEF = 3
IMPORTING Parameters details for RM_PH_EVAL_DATA_CHECK
I_VIEW - Sicht
Data type: JBRSICHTIDOptional: No
Call by Reference: Yes
I_PH - Portfoliohierarchie
Data type: JBRPHIDOptional: No
Call by Reference: Yes
I_MODE - 'I': exp. Info-Flags ; 'G' Generierungsprüfung
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PHCHECK - Status Check PH-Definition
Data type: RMPHSTATEDefault: '8'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MHCHECK - Status Check MH-Definition
Data type: RMPHSTATEDefault: '8'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DEF_FLID - Filter: Name
Data type: AFWCH_FLIDOptional: Yes
Call by Reference: Yes
I_GEN_FLID - Filter: Name
Data type: AFWCH_FLIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RM_PH_EVAL_DATA_CHECK
E_BDS - 'X' = BDS-Läufe zur PH vorhanden
Data type: XFELDOptional: No
Call by Reference: Yes
E_RDB - 'X' = RDB-Kennzahlen zur PH vorhanden
Data type: XFELDOptional: No
Call by Reference: Yes
E_ALM - 'X' = ALM Planungsvarianten
Data type: XFELDOptional: No
Call by Reference: Yes
E_PHDEF - 'X' = PH-Definition anweichend
Data type: XFELDOptional: No
Call by Reference: Yes
E_MHDEF - 'X' = MH-Definition anweichend
Data type: XFELDOptional: No
Call by Reference: Yes
E_FLID_GEN - ursprüngliche Filterzuordnung
Data type: AFWCH_FLIDOptional: No
Call by Reference: Yes
TABLES Parameters details for RM_PH_EVAL_DATA_CHECK
I_JBRPHDEF - Definitionen, aus denen sich die PortfHier ableitet
Data type: JBRPHDEFOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
EVAL_DATA_EXIST - Auswertungsdaten vorhanden
Data type:Optional: No
Call by Reference: Yes
EVAL_DATA_ADAPT - trotz Auswertungsdaten, Anpassung erlaubt
Data type:Optional: No
Call by Reference: Yes
NO_PHDEF - keine Definitionen vorhanden
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_PH_EVAL_DATA_CHECK 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_e_bds | TYPE XFELD, " | |||
| lv_i_view | TYPE JBRSICHTID, " | |||
| lt_i_jbrphdef | TYPE STANDARD TABLE OF JBRPHDEF, " | |||
| lv_eval_data_exist | TYPE JBRPHDEF, " | |||
| lv_i_ph | TYPE JBRPHID, " | |||
| lv_e_rdb | TYPE XFELD, " | |||
| lv_eval_data_adapt | TYPE XFELD, " | |||
| lv_e_alm | TYPE XFELD, " | |||
| lv_i_mode | TYPE XFELD, " ' ' | |||
| lv_no_phdef | TYPE XFELD, " | |||
| lv_e_phdef | TYPE XFELD, " | |||
| lv_i_phcheck | TYPE RMPHSTATE, " '8' | |||
| lv_e_mhdef | TYPE XFELD, " | |||
| lv_i_mhcheck | TYPE RMPHSTATE, " '8' | |||
| lv_e_flid_gen | TYPE AFWCH_FLID, " | |||
| lv_i_def_flid | TYPE AFWCH_FLID, " | |||
| lv_i_gen_flid | TYPE AFWCH_FLID. " |
|   CALL FUNCTION 'RM_PH_EVAL_DATA_CHECK' "RM: prüft PH auf abhängige Auswertungsdaten |
| EXPORTING | ||
| I_VIEW | = lv_i_view | |
| I_PH | = lv_i_ph | |
| I_MODE | = lv_i_mode | |
| I_PHCHECK | = lv_i_phcheck | |
| I_MHCHECK | = lv_i_mhcheck | |
| I_DEF_FLID | = lv_i_def_flid | |
| I_GEN_FLID | = lv_i_gen_flid | |
| IMPORTING | ||
| E_BDS | = lv_e_bds | |
| E_RDB | = lv_e_rdb | |
| E_ALM | = lv_e_alm | |
| E_PHDEF | = lv_e_phdef | |
| E_MHDEF | = lv_e_mhdef | |
| E_FLID_GEN | = lv_e_flid_gen | |
| TABLES | ||
| I_JBRPHDEF | = lt_i_jbrphdef | |
| EXCEPTIONS | ||
| EVAL_DATA_EXIST = 1 | ||
| EVAL_DATA_ADAPT = 2 | ||
| NO_PHDEF = 3 | ||
| . " RM_PH_EVAL_DATA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RM_PH_EVAL_DATA_CHECK
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.| DATA(ld_i_mode) | = ' '. | |||
| DATA(ld_i_phcheck) | = '8'. | |||
| DATA(ld_i_mhcheck) | = '8'. | |||
Search for further information about these or an SAP related objects