SAP RSDM_F4_GET_NODE_FROM_KEY Function Module for Properties of a Node in Hierarchy Node F4









RSDM_F4_GET_NODE_FROM_KEY is a standard rsdm f4 get node from key SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Properties of a Node in Hierarchy Node F4 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 rsdm f4 get node from key FM, simply by entering the name RSDM_F4_GET_NODE_FROM_KEY into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSDM_F4
Program Name: SAPLRSDM_F4
Main Program: SAPLRSDM_F4
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSDM_F4_GET_NODE_FROM_KEY 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 'RSDM_F4_GET_NODE_FROM_KEY'"Properties of a Node in Hierarchy Node F4
EXPORTING
I_NODEKEY = "Node Key
* I_READ_TEXT = RS_C_TRUE "Read Node Text Additionally
* I_VALUE_EXT = RS_C_TRUE "Generate External Key

IMPORTING
E_SID = "
E_S_NODET = "Selected Node
E_T_DEP = "Dependent Information

EXCEPTIONS
INVALID_HIERARCHY = 1 ILLEGAL_INFOOBJECT = 2 NO_TREE_ACTIVE = 3 TREE_ACTIVE = 4 NO_VALUES_AVAILABLE = 5 DIALOGUE_CANCELED = 6 X_MESSAGE = 7
.



IMPORTING Parameters details for RSDM_F4_GET_NODE_FROM_KEY

I_NODEKEY - Node Key

Data type: RSDM4_NODEKEY
Optional: No
Call by Reference: No ( called with pass by value option)

I_READ_TEXT - Read Node Text Additionally

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALUE_EXT - Generate External Key

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RSDM_F4_GET_NODE_FROM_KEY

E_SID -

Data type: RSD_SID
Optional: No
Call by Reference: No ( called with pass by value option)

E_S_NODET - Selected Node

Data type: RSDM_S_NODET
Optional: No
Call by Reference: No ( called with pass by value option)

E_T_DEP - Dependent Information

Data type: RRSV_T_DEP
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_HIERARCHY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ILLEGAL_INFOOBJECT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_TREE_ACTIVE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TREE_ACTIVE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_VALUES_AVAILABLE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DIALOGUE_CANCELED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

X_MESSAGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RSDM_F4_GET_NODE_FROM_KEY 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_sid  TYPE RSD_SID, "   
lv_i_nodekey  TYPE RSDM4_NODEKEY, "   
lv_invalid_hierarchy  TYPE RSDM4_NODEKEY, "   
lv_e_s_nodet  TYPE RSDM_S_NODET, "   
lv_i_read_text  TYPE RS_BOOL, "   RS_C_TRUE
lv_illegal_infoobject  TYPE RS_BOOL, "   
lv_e_t_dep  TYPE RRSV_T_DEP, "   
lv_i_value_ext  TYPE RS_BOOL, "   RS_C_TRUE
lv_no_tree_active  TYPE RS_BOOL, "   
lv_tree_active  TYPE RS_BOOL, "   
lv_no_values_available  TYPE RS_BOOL, "   
lv_dialogue_canceled  TYPE RS_BOOL, "   
lv_x_message  TYPE RS_BOOL. "   

  CALL FUNCTION 'RSDM_F4_GET_NODE_FROM_KEY'  "Properties of a Node in Hierarchy Node F4
    EXPORTING
         I_NODEKEY = lv_i_nodekey
         I_READ_TEXT = lv_i_read_text
         I_VALUE_EXT = lv_i_value_ext
    IMPORTING
         E_SID = lv_e_sid
         E_S_NODET = lv_e_s_nodet
         E_T_DEP = lv_e_t_dep
    EXCEPTIONS
        INVALID_HIERARCHY = 1
        ILLEGAL_INFOOBJECT = 2
        NO_TREE_ACTIVE = 3
        TREE_ACTIVE = 4
        NO_VALUES_AVAILABLE = 5
        DIALOGUE_CANCELED = 6
        X_MESSAGE = 7
. " RSDM_F4_GET_NODE_FROM_KEY




ABAP code using 7.40 inline data declarations to call FM RSDM_F4_GET_NODE_FROM_KEY

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_read_text) = RS_C_TRUE.
 
 
 
DATA(ld_i_value_ext) = RS_C_TRUE.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!