SAP MEMGMT_NODE_CHANGE Function Module for ME: Node change









MEMGMT_NODE_CHANGE is a standard memgmt node change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ME: Node change 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 change FM, simply by entering the name MEMGMT_NODE_CHANGE 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_CHANGE 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_CHANGE'"ME: Node change
  EXPORTING
   NODE_ID =  "Unique hierarchy node ID
*  LANG =  "Language Key
*  NEW_NODE_DESCR =  "ME: Hierarchy node description
*  CHANGE_NODE_DESCR = ' ' "Single-Character Flag
*  NEW_FATHER_NODE_ID =  "Unique hierarchy node ID
*  INHERIT = ' ' "Single-Character Flag

TABLES
   RETURN =  "Return Parameter
.



IMPORTING Parameters details for MEMGMT_NODE_CHANGE

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: Yes
Call by Reference: No ( called with pass by value option)

NEW_NODE_DESCR - ME: Hierarchy node description

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

CHANGE_NODE_DESCR - Single-Character Flag

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

NEW_FATHER_NODE_ID - Unique hierarchy node ID

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

INHERIT - Single-Character Flag

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

TABLES Parameters details for MEMGMT_NODE_CHANGE

RETURN - Return Parameter

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

Copy and paste ABAP code example for MEMGMT_NODE_CHANGE 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_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_node_id  TYPE MENODEGUID, "   
lv_lang  TYPE LANGU, "   
lv_new_node_descr  TYPE MENODE_TEXT, "   
lv_change_node_descr  TYPE CHAR1, "   ' '
lv_new_father_node_id  TYPE MENODEGUID, "   
lv_inherit  TYPE CHAR1. "   ' '

  CALL FUNCTION 'MEMGMT_NODE_CHANGE'  "ME: Node change
    EXPORTING
         NODE_ID = lv_node_id
         LANG = lv_lang
         NEW_NODE_DESCR = lv_new_node_descr
         CHANGE_NODE_DESCR = lv_change_node_descr
         NEW_FATHER_NODE_ID = lv_new_father_node_id
         INHERIT = lv_inherit
    TABLES
         RETURN = lt_return
. " MEMGMT_NODE_CHANGE




ABAP code using 7.40 inline data declarations to call FM MEMGMT_NODE_CHANGE

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_change_node_descr) = ' '.
 
 
DATA(ld_inherit) = ' '.
 


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!