SAP TREEV_MOVE_NODE Function Module for Move Node in Tree
TREEV_MOVE_NODE is a standard treev move node SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Move Node in Tree 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 treev move node FM, simply by entering the name TREEV_MOVE_NODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNT4
Program Name: SAPLCNT4
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TREEV_MOVE_NODE 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 'TREEV_MOVE_NODE'"Move Node in Tree.
EXPORTING
HANDLE = "Handle for Tree Control
NODE_KEY = "Node Key
RELATKEY = "Dest.point
RELATSHIP = "Relationship Between Source and Target
* NO_FLUSH = "
EXCEPTIONS
FAILED = 1 CNTL_SYSTEM_ERROR = 2 NODE_NOT_FOUND = 3 MOVE_ERROR = 4 RELATIVE_NOT_FOUND = 5 ILLEGAL_RELATSHIP = 6 PARENT_IS_LEAF = 7
IMPORTING Parameters details for TREEV_MOVE_NODE
HANDLE - Handle for Tree Control
Data type: CNTL_HANDLEOptional: No
Call by Reference: Yes
NODE_KEY - Node Key
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
RELATKEY - Dest.point
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
RELATSHIP - Relationship Between Source and Target
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
NO_FLUSH -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FAILED - General Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CNTL_SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NODE_NOT_FOUND - Node With Key NODE_KEY Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MOVE_ERROR - Incorrect Target
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RELATIVE_NOT_FOUND - Unable To Find Node With Key RELAT_KEY
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_RELATSHIP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARENT_IS_LEAF - Target Parent Node is a Leaf
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TREEV_MOVE_NODE 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_failed | TYPE STRING, " | |||
| lv_handle | TYPE CNTL_HANDLE, " | |||
| lv_node_key | TYPE C, " | |||
| lv_cntl_system_error | TYPE C, " | |||
| lv_relatkey | TYPE C, " | |||
| lv_node_not_found | TYPE C, " | |||
| lv_relatship | TYPE I, " | |||
| lv_move_error | TYPE I, " | |||
| lv_no_flush | TYPE C, " | |||
| lv_relative_not_found | TYPE C, " | |||
| lv_illegal_relatship | TYPE C, " | |||
| lv_parent_is_leaf | TYPE C. " |
|   CALL FUNCTION 'TREEV_MOVE_NODE' "Move Node in Tree |
| EXPORTING | ||
| HANDLE | = lv_handle | |
| NODE_KEY | = lv_node_key | |
| RELATKEY | = lv_relatkey | |
| RELATSHIP | = lv_relatship | |
| NO_FLUSH | = lv_no_flush | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| CNTL_SYSTEM_ERROR = 2 | ||
| NODE_NOT_FOUND = 3 | ||
| MOVE_ERROR = 4 | ||
| RELATIVE_NOT_FOUND = 5 | ||
| ILLEGAL_RELATSHIP = 6 | ||
| PARENT_IS_LEAF = 7 | ||
| . " TREEV_MOVE_NODE | ||
ABAP code using 7.40 inline data declarations to call FM TREEV_MOVE_NODE
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