SAP RM_PH_NODE_CHAR_GET Function Module for RM: ermittelt Merkmale und Ausprägungen zu einem PH-Knoten (opt. mit Text)
RM_PH_NODE_CHAR_GET is a standard rm ph node char get 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: ermittelt Merkmale und Ausprägungen zu einem PH-Knoten (opt. mit Text) 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 node char get FM, simply by entering the name RM_PH_NODE_CHAR_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBRJ
Program Name: SAPLJBRJ
Main Program: SAPLJBRJ
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_PH_NODE_CHAR_GET 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_NODE_CHAR_GET'"RM: ermittelt Merkmale und Ausprägungen zu einem PH-Knoten (opt. mit Text).
EXPORTING
P_SICHT = "Sicht
P_PHID = "Portfoliohierarchie
P_NAME = "Knotenname (permanente ID)
* WITH_TEXT = "Kennzeichen: auch Texte ermitteln
TABLES
* E_CHAR = "Tabelle der Merkmale und Ausprägungen
EXCEPTIONS
HIERARCHY_NOT_FOUND = 1 NODE_NOT_FOUND = 2 INCONSISTENT_HIERARCHY = 3 ENQUEUE_ERROR = 4
IMPORTING Parameters details for RM_PH_NODE_CHAR_GET
P_SICHT - Sicht
Data type: JBRSI-SICHTIDOptional: No
Call by Reference: No ( called with pass by value option)
P_PHID - Portfoliohierarchie
Data type: JBRPH-PHIDOptional: No
Call by Reference: No ( called with pass by value option)
P_NAME - Knotenname (permanente ID)
Data type: JBRPHBAUM-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
WITH_TEXT - Kennzeichen: auch Texte ermitteln
Data type: JBRFLDDOCU-XFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RM_PH_NODE_CHAR_GET
E_CHAR - Tabelle der Merkmale und Ausprägungen
Data type: JBRPHKNTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
HIERARCHY_NOT_FOUND - Hierarchiestruktur wurde nicht gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NODE_NOT_FOUND - Gesuchter Knoten wurde in der Hier. nicht gef.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCONSISTENT_HIERARCHY - Fehlerhafte Hierarchie (keine Wurzel)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_ERROR - Sperrproblem
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_PH_NODE_CHAR_GET 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: | ||||
| lt_e_char | TYPE STANDARD TABLE OF JBRPHKNTXT, " | |||
| lv_p_sicht | TYPE JBRSI-SICHTID, " | |||
| lv_hierarchy_not_found | TYPE JBRSI, " | |||
| lv_p_phid | TYPE JBRPH-PHID, " | |||
| lv_node_not_found | TYPE JBRPH, " | |||
| lv_p_name | TYPE JBRPHBAUM-NAME, " | |||
| lv_inconsistent_hierarchy | TYPE JBRPHBAUM, " | |||
| lv_with_text | TYPE JBRFLDDOCU-XFIELD, " | |||
| lv_enqueue_error | TYPE JBRFLDDOCU. " |
|   CALL FUNCTION 'RM_PH_NODE_CHAR_GET' "RM: ermittelt Merkmale und Ausprägungen zu einem PH-Knoten (opt. mit Text) |
| EXPORTING | ||
| P_SICHT | = lv_p_sicht | |
| P_PHID | = lv_p_phid | |
| P_NAME | = lv_p_name | |
| WITH_TEXT | = lv_with_text | |
| TABLES | ||
| E_CHAR | = lt_e_char | |
| EXCEPTIONS | ||
| HIERARCHY_NOT_FOUND = 1 | ||
| NODE_NOT_FOUND = 2 | ||
| INCONSISTENT_HIERARCHY = 3 | ||
| ENQUEUE_ERROR = 4 | ||
| . " RM_PH_NODE_CHAR_GET | ||
ABAP code using 7.40 inline data declarations to call FM RM_PH_NODE_CHAR_GET
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.| "SELECT single SICHTID FROM JBRSI INTO @DATA(ld_p_sicht). | ||||
| "SELECT single PHID FROM JBRPH INTO @DATA(ld_p_phid). | ||||
| "SELECT single NAME FROM JBRPHBAUM INTO @DATA(ld_p_name). | ||||
| "SELECT single XFIELD FROM JBRFLDDOCU INTO @DATA(ld_with_text). | ||||
Search for further information about these or an SAP related objects