SAP MEMGMT_NODE_GETDETAIL Function Module for Retrieving details of the node









MEMGMT_NODE_GETDETAIL is a standard memgmt node getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieving details of the node 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 memgmt node getdetail FM, simply by entering the name MEMGMT_NODE_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: MEMGMT_HIERARCHY
Program Name: SAPLMEMGMT_HIERARCHY
Main Program: SAPLMEMGMT_HIERARCHY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MEMGMT_NODE_GETDETAIL 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 'MEMGMT_NODE_GETDETAIL'"Retrieving details of the node
  EXPORTING
   NODE_ID =  "Unique hierarchy node ID
   LANG =  "Language Key

 IMPORTING
   ENODE_ID =  "Unique hierarchy node ID
   NODE_DESCRIPTION =  "ME: Hierarchy node description
   FATHER_NODE_ID =  "Unique hierarchy node ID
   FATHER_NODE_DESCRIPTION =  "ME: Hierarchy node description

TABLES
   DEVICETEMPLATES =  "ME: Table type for objects assigned to the node
   DEVICES =  "ME: Table type for objects assigned to the node
   USERS =  "ME: Table type for objects assigned to the node
   CHILDREN_LIST =  "ME: Table type for children node IDs
   RETURN =  "Return Parameter
.



IMPORTING Parameters details for MEMGMT_NODE_GETDETAIL

NODE_ID - Unique hierarchy node ID

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

LANG - Language Key

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

EXPORTING Parameters details for MEMGMT_NODE_GETDETAIL

ENODE_ID - Unique hierarchy node ID

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

NODE_DESCRIPTION - ME: Hierarchy node description

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

FATHER_NODE_ID - Unique hierarchy node ID

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

FATHER_NODE_DESCRIPTION - ME: Hierarchy node description

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

TABLES Parameters details for MEMGMT_NODE_GETDETAIL

DEVICETEMPLATES - ME: Table type for objects assigned to the node

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

DEVICES - ME: Table type for objects assigned to the node

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

USERS - ME: Table type for objects assigned to the node

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

CHILDREN_LIST - ME: Table type for children node IDs

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for MEMGMT_NODE_GETDETAIL 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_node_id  TYPE MENODEGUID, "   
lv_enode_id  TYPE MENODEGUID, "   
lt_devicetemplates  TYPE STANDARD TABLE OF MEMGMT_NODE_OBJ_TT, "   
lv_lang  TYPE LANGU, "   
lt_devices  TYPE STANDARD TABLE OF MEMGMT_NODE_OBJ_TT, "   
lv_node_description  TYPE MENODE_TEXT, "   
lt_users  TYPE STANDARD TABLE OF MEMGMT_NODE_OBJ_TT, "   
lv_father_node_id  TYPE MENODEGUID, "   
lt_children_list  TYPE STANDARD TABLE OF MEMGMT_NODE_CHILDREN_LIST_TT, "   
lv_father_node_description  TYPE MENODE_TEXT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'MEMGMT_NODE_GETDETAIL'  "Retrieving details of the node
    EXPORTING
         NODE_ID = lv_node_id
         LANG = lv_lang
    IMPORTING
         ENODE_ID = lv_enode_id
         NODE_DESCRIPTION = lv_node_description
         FATHER_NODE_ID = lv_father_node_id
         FATHER_NODE_DESCRIPTION = lv_father_node_description
    TABLES
         DEVICETEMPLATES = lt_devicetemplates
         DEVICES = lt_devices
         USERS = lt_users
         CHILDREN_LIST = lt_children_list
         RETURN = lt_return
. " MEMGMT_NODE_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM MEMGMT_NODE_GETDETAIL

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



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!