SAP RSHI_NODE_RELATION_GET Function Module for Nodes: supply relation
RSHI_NODE_RELATION_GET is a standard rshi node relation 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 Nodes: supply relation 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 rshi node relation get FM, simply by entering the name RSHI_NODE_RELATION_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSHI
Program Name: SAPLRSHI
Main Program: SAPLRSHI
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSHI_NODE_RELATION_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 'RSHI_NODE_RELATION_GET'"Nodes: supply relation.
EXPORTING
I_NODE_ID = "
IMPORTING
E_RELATION = "
ET_CHILD_ID = "
E_PARENT_NODE_ID = "
E_LEFT_NODE_ID = "
E_RIGHT_NODE_ID = "
E_FIRST_CHILD_NODE_ID = "
E_LAST_CHILD_NODE_ID = "
EXCEPTIONS
INVALID_NODE_ID = 1 NODE_IS_FREE = 2
IMPORTING Parameters details for RSHI_NODE_RELATION_GET
I_NODE_ID -
Data type: RSATD_KEYTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSHI_NODE_RELATION_GET
E_RELATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ET_CHILD_ID -
Data type: RSATD_IT_KEYTYPEOptional: No
Call by Reference: No ( called with pass by value option)
E_PARENT_NODE_ID -
Data type: RSATD_NODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
E_LEFT_NODE_ID -
Data type: RSATD_NODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
E_RIGHT_NODE_ID -
Data type: RSATD_NODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
E_FIRST_CHILD_NODE_ID -
Data type: RSATD_NODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
E_LAST_CHILD_NODE_ID -
Data type: RSATD_NODE-IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_NODE_ID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NODE_IS_FREE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSHI_NODE_RELATION_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: | ||||
| lv_i_node_id | TYPE RSATD_KEYTYPE, " | |||
| lv_e_relation | TYPE RSATD_KEYTYPE, " | |||
| lv_invalid_node_id | TYPE RSATD_KEYTYPE, " | |||
| lv_et_child_id | TYPE RSATD_IT_KEYTYPE, " | |||
| lv_node_is_free | TYPE RSATD_IT_KEYTYPE, " | |||
| lv_e_parent_node_id | TYPE RSATD_NODE-ID, " | |||
| lv_e_left_node_id | TYPE RSATD_NODE-ID, " | |||
| lv_e_right_node_id | TYPE RSATD_NODE-ID, " | |||
| lv_e_first_child_node_id | TYPE RSATD_NODE-ID, " | |||
| lv_e_last_child_node_id | TYPE RSATD_NODE-ID. " |
|   CALL FUNCTION 'RSHI_NODE_RELATION_GET' "Nodes: supply relation |
| EXPORTING | ||
| I_NODE_ID | = lv_i_node_id | |
| IMPORTING | ||
| E_RELATION | = lv_e_relation | |
| ET_CHILD_ID | = lv_et_child_id | |
| E_PARENT_NODE_ID | = lv_e_parent_node_id | |
| E_LEFT_NODE_ID | = lv_e_left_node_id | |
| E_RIGHT_NODE_ID | = lv_e_right_node_id | |
| E_FIRST_CHILD_NODE_ID | = lv_e_first_child_node_id | |
| E_LAST_CHILD_NODE_ID | = lv_e_last_child_node_id | |
| EXCEPTIONS | ||
| INVALID_NODE_ID = 1 | ||
| NODE_IS_FREE = 2 | ||
| . " RSHI_NODE_RELATION_GET | ||
ABAP code using 7.40 inline data declarations to call FM RSHI_NODE_RELATION_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 ID FROM RSATD_NODE INTO @DATA(ld_e_parent_node_id). | ||||
| "SELECT single ID FROM RSATD_NODE INTO @DATA(ld_e_left_node_id). | ||||
| "SELECT single ID FROM RSATD_NODE INTO @DATA(ld_e_right_node_id). | ||||
| "SELECT single ID FROM RSATD_NODE INTO @DATA(ld_e_first_child_node_id). | ||||
| "SELECT single ID FROM RSATD_NODE INTO @DATA(ld_e_last_child_node_id). | ||||
Search for further information about these or an SAP related objects