SAP STREE_STRUCTURE_SAVE_NODES Function Module for









STREE_STRUCTURE_SAVE_NODES is a standard stree structure save nodes 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 structure save nodes FM, simply by entering the name STREE_STRUCTURE_SAVE_NODES into the relevant SAP transaction such as SE37 or SE38.

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



Function STREE_STRUCTURE_SAVE_NODES 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_STRUCTURE_SAVE_NODES'"
EXPORTING
STRUCTURE_ID = "
* LANGUAGE = SY-LANGU "
* EXTENSION = ' ' "
* NO_COMMIT_WORK = 'X' "
* TRANSPORT_ORDER = ' ' "
* DEVELOPMENT_CLASS = ' ' "

IMPORTING
MESSAGE = "

TABLES
LIST_OF_ALL_NODES = "
INSERT_NODES = "
INSERT_REFERENCES = "
INSERT_TEXTS = "
DELETE_NODES = "
.



IMPORTING Parameters details for STREE_STRUCTURE_SAVE_NODES

STRUCTURE_ID -

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

LANGUAGE -

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

EXTENSION -

Data type: TTREE_EXT-EXTENSION
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_COMMIT_WORK -

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

TRANSPORT_ORDER -

Data type: KO200-TRKORR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEVELOPMENT_CLASS -

Data type: KO200-DEVCLASS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for STREE_STRUCTURE_SAVE_NODES

MESSAGE -

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

TABLES Parameters details for STREE_STRUCTURE_SAVE_NODES

LIST_OF_ALL_NODES -

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

INSERT_NODES -

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

INSERT_REFERENCES -

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

INSERT_TEXTS -

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

DELETE_NODES -

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

Copy and paste ABAP code example for STREE_STRUCTURE_SAVE_NODES 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 HIER_IFACE-TREE_ID, "   
lt_list_of_all_nodes  TYPE STANDARD TABLE OF HIER_IFACE, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lt_insert_nodes  TYPE STANDARD TABLE OF HIER_IFACE, "   
lv_extension  TYPE TTREE_EXT-EXTENSION, "   SPACE
lt_insert_references  TYPE STANDARD TABLE OF HIER_REF, "   
lt_insert_texts  TYPE STANDARD TABLE OF HIER_TEXTS, "   
lv_no_commit_work  TYPE HIER_TYPES-CHAR1, "   'X'
lt_delete_nodes  TYPE STANDARD TABLE OF HIER_IFACE, "   
lv_transport_order  TYPE KO200-TRKORR, "   SPACE
lv_development_class  TYPE KO200-DEVCLASS. "   SPACE

  CALL FUNCTION 'STREE_STRUCTURE_SAVE_NODES'  "
    EXPORTING
         STRUCTURE_ID = lv_structure_id
         LANGUAGE = lv_language
         EXTENSION = lv_extension
         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
         INSERT_REFERENCES = lt_insert_references
         INSERT_TEXTS = lt_insert_texts
         DELETE_NODES = lt_delete_nodes
. " STREE_STRUCTURE_SAVE_NODES




ABAP code using 7.40 inline data declarations to call FM STREE_STRUCTURE_SAVE_NODES

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 TREE_ID FROM HIER_IFACE INTO @DATA(ld_structure_id).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
"SELECT single EXTENSION FROM TTREE_EXT INTO @DATA(ld_extension).
DATA(ld_extension) = ' '.
 
 
 
"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



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!