SAP STREE_SAVE_CHANGED_NODES_GENER Function Module for
STREE_SAVE_CHANGED_NODES_GENER is a standard stree save changed nodes gener SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 stree save changed nodes gener FM, simply by entering the name STREE_SAVE_CHANGED_NODES_GENER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SHI3
Program Name: SAPLSHI3
Main Program: SAPLSHI3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STREE_SAVE_CHANGED_NODES_GENER 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 'STREE_SAVE_CHANGED_NODES_GENER'".
EXPORTING
STRUCTURE_ID = "
* EXTENSION = ' ' "
TABLE_NAME = "
NODE_TRANSPORT_OBJECT = "
* NO_COMMIT_WORK = 'X' "
* TRANSPORT_ORDER = ' ' "
* DEVELOPMENT_CLASS = ' ' "
IMPORTING
MESSAGE = "
TABLES
LIST_OF_ALL_NODES = "
INSERT_NODES = "
DELETE_NODES = "
INSERT_REFERENCES = "
INSERT_TEXTS = "
* OLD_LIST_OF_NODES = "
* OLD_LIST_OF_TEXTS = "
IMPORTING Parameters details for STREE_SAVE_CHANGED_NODES_GENER
STRUCTURE_ID -
Data type: TTREE-IDOptional: No
Call by Reference: No ( called with pass by value option)
EXTENSION -
Data type: TTREE_EXT-EXTENSIONDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLE_NAME -
Data type: TTREETYPE-DB_TABLEOptional: No
Call by Reference: No ( called with pass by value option)
NODE_TRANSPORT_OBJECT -
Data type: TTREETYPE-TRANS_OBJOptional: No
Call by Reference: No ( called with pass by value option)
NO_COMMIT_WORK -
Data type: HIER_TYPES-CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRANSPORT_ORDER -
Data type: KO200-TRKORRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEVELOPMENT_CLASS -
Data type: KO200-DEVCLASSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STREE_SAVE_CHANGED_NODES_GENER
MESSAGE -
Data type: HIER_MESSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for STREE_SAVE_CHANGED_NODES_GENER
LIST_OF_ALL_NODES -
Data type: HIER_IFACEOptional: No
Call by Reference: No ( called with pass by value option)
INSERT_NODES -
Data type: HIER_IFACEOptional: No
Call by Reference: No ( called with pass by value option)
DELETE_NODES -
Data type: HIER_IFACEOptional: No
Call by Reference: No ( called with pass by value option)
INSERT_REFERENCES -
Data type: HIER_REFOptional: No
Call by Reference: No ( called with pass by value option)
INSERT_TEXTS -
Data type: HIER_TEXTSOptional: No
Call by Reference: No ( called with pass by value option)
OLD_LIST_OF_NODES -
Data type: HIER_IFACEOptional: Yes
Call by Reference: No ( called with pass by value option)
OLD_LIST_OF_TEXTS -
Data type: HIER_TEXTSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STREE_SAVE_CHANGED_NODES_GENER 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_message | TYPE HIER_MESS, " | |||
| lv_structure_id | TYPE TTREE-ID, " | |||
| lt_list_of_all_nodes | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lv_extension | TYPE TTREE_EXT-EXTENSION, " SPACE | |||
| lt_insert_nodes | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lv_table_name | TYPE TTREETYPE-DB_TABLE, " | |||
| lt_delete_nodes | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lt_insert_references | TYPE STANDARD TABLE OF HIER_REF, " | |||
| lv_node_transport_object | TYPE TTREETYPE-TRANS_OBJ, " | |||
| lt_insert_texts | TYPE STANDARD TABLE OF HIER_TEXTS, " | |||
| lv_no_commit_work | TYPE HIER_TYPES-CHAR1, " 'X' | |||
| lv_transport_order | TYPE KO200-TRKORR, " SPACE | |||
| lt_old_list_of_nodes | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lv_development_class | TYPE KO200-DEVCLASS, " SPACE | |||
| lt_old_list_of_texts | TYPE STANDARD TABLE OF HIER_TEXTS. " |
|   CALL FUNCTION 'STREE_SAVE_CHANGED_NODES_GENER' " |
| EXPORTING | ||
| STRUCTURE_ID | = lv_structure_id | |
| EXTENSION | = lv_extension | |
| TABLE_NAME | = lv_table_name | |
| NODE_TRANSPORT_OBJECT | = lv_node_transport_object | |
| NO_COMMIT_WORK | = lv_no_commit_work | |
| TRANSPORT_ORDER | = lv_transport_order | |
| DEVELOPMENT_CLASS | = lv_development_class | |
| IMPORTING | ||
| MESSAGE | = lv_message | |
| TABLES | ||
| LIST_OF_ALL_NODES | = lt_list_of_all_nodes | |
| INSERT_NODES | = lt_insert_nodes | |
| DELETE_NODES | = lt_delete_nodes | |
| INSERT_REFERENCES | = lt_insert_references | |
| INSERT_TEXTS | = lt_insert_texts | |
| OLD_LIST_OF_NODES | = lt_old_list_of_nodes | |
| OLD_LIST_OF_TEXTS | = lt_old_list_of_texts | |
| . " STREE_SAVE_CHANGED_NODES_GENER | ||
ABAP code using 7.40 inline data declarations to call FM STREE_SAVE_CHANGED_NODES_GENER
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 TTREE INTO @DATA(ld_structure_id). | ||||
| "SELECT single EXTENSION FROM TTREE_EXT INTO @DATA(ld_extension). | ||||
| DATA(ld_extension) | = ' '. | |||
| "SELECT single DB_TABLE FROM TTREETYPE INTO @DATA(ld_table_name). | ||||
| "SELECT single TRANS_OBJ FROM TTREETYPE INTO @DATA(ld_node_transport_object). | ||||
| "SELECT single CHAR1 FROM HIER_TYPES INTO @DATA(ld_no_commit_work). | ||||
| DATA(ld_no_commit_work) | = 'X'. | |||
| "SELECT single TRKORR FROM KO200 INTO @DATA(ld_transport_order). | ||||
| DATA(ld_transport_order) | = ' '. | |||
| "SELECT single DEVCLASS FROM KO200 INTO @DATA(ld_development_class). | ||||
| DATA(ld_development_class) | = ' '. | |||
Search for further information about these or an SAP related objects