SAP STREE_EXTERNAL_DISPLAY Function Module for Display Structure
STREE_EXTERNAL_DISPLAY is a standard stree external display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Structure 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 stree external display FM, simply by entering the name STREE_EXTERNAL_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SHI21
Program Name: SAPLSHI21
Main Program: SAPLSHI21
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function STREE_EXTERNAL_DISPLAY 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_EXTERNAL_DISPLAY'"Display Structure.
EXPORTING
STRUCTURE_ID = "
* LANGUAGE = SY-LANGU "
* DISPLAY_STRUCTURE = 'X' "
* NO_COMMIT_WORK = 'X' "
* USE_REMOTE_CONNECTION = ' ' "
* RFC_DESTINATION = 'NONE' "
* POSITION_ON_NODE = ' ' "
* POSITION_ON_NODES = "Hierarchy tool node IDs
* ID_FOR_USE_AS_FILTER = ' ' "
IMPORTING
MESSAGE = "
TOGGLE = "
TABLES
* USER_PARAMETERS = "
* POSITION_HIERARCHY = "Hierarchy Maintenance Tool Node Passing Interface
IMPORTING Parameters details for STREE_EXTERNAL_DISPLAY
STRUCTURE_ID -
Data type: TTREE-IDOptional: No
Call by Reference: No ( called with pass by value option)
LANGUAGE -
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_STRUCTURE -
Data type: HIER_TYPES-CHAR1Default: 'X'
Optional: Yes
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)
USE_REMOTE_CONNECTION -
Data type: HIER_TYPES-CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
RFC_DESTINATION -
Data type: RFCDES-RFCDESTDefault: 'NONE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
POSITION_ON_NODE -
Data type: HIER_IFACE-NODE_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
POSITION_ON_NODES - Hierarchy tool node IDs
Data type: HIER_NODE_IDSOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_FOR_USE_AS_FILTER -
Data type: TTREE-IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STREE_EXTERNAL_DISPLAY
MESSAGE -
Data type: HIER_MESSOptional: No
Call by Reference: No ( called with pass by value option)
TOGGLE -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for STREE_EXTERNAL_DISPLAY
USER_PARAMETERS -
Data type: STREEPROPOptional: Yes
Call by Reference: No ( called with pass by value option)
POSITION_HIERARCHY - Hierarchy Maintenance Tool Node Passing Interface
Data type: HIER_IFACEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for STREE_EXTERNAL_DISPLAY 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_user_parameters | TYPE STANDARD TABLE OF STREEPROP, " | |||
| lv_toggle | TYPE CHAR1, " | |||
| lv_language | TYPE SY-LANGU, " SY-LANGU | |||
| lt_position_hierarchy | TYPE STANDARD TABLE OF HIER_IFACE, " | |||
| lv_display_structure | TYPE HIER_TYPES-CHAR1, " 'X' | |||
| lv_no_commit_work | TYPE HIER_TYPES-CHAR1, " 'X' | |||
| lv_use_remote_connection | TYPE HIER_TYPES-CHAR1, " ' ' | |||
| lv_rfc_destination | TYPE RFCDES-RFCDEST, " 'NONE' | |||
| lv_position_on_node | TYPE HIER_IFACE-NODE_ID, " SPACE | |||
| lv_position_on_nodes | TYPE HIER_NODE_IDS, " | |||
| lv_id_for_use_as_filter | TYPE TTREE-ID. " SPACE |
|   CALL FUNCTION 'STREE_EXTERNAL_DISPLAY' "Display Structure |
| EXPORTING | ||
| STRUCTURE_ID | = lv_structure_id | |
| LANGUAGE | = lv_language | |
| DISPLAY_STRUCTURE | = lv_display_structure | |
| NO_COMMIT_WORK | = lv_no_commit_work | |
| USE_REMOTE_CONNECTION | = lv_use_remote_connection | |
| RFC_DESTINATION | = lv_rfc_destination | |
| POSITION_ON_NODE | = lv_position_on_node | |
| POSITION_ON_NODES | = lv_position_on_nodes | |
| ID_FOR_USE_AS_FILTER | = lv_id_for_use_as_filter | |
| IMPORTING | ||
| MESSAGE | = lv_message | |
| TOGGLE | = lv_toggle | |
| TABLES | ||
| USER_PARAMETERS | = lt_user_parameters | |
| POSITION_HIERARCHY | = lt_position_hierarchy | |
| . " STREE_EXTERNAL_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM STREE_EXTERNAL_DISPLAY
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 LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| "SELECT single CHAR1 FROM HIER_TYPES INTO @DATA(ld_display_structure). | ||||
| DATA(ld_display_structure) | = 'X'. | |||
| "SELECT single CHAR1 FROM HIER_TYPES INTO @DATA(ld_no_commit_work). | ||||
| DATA(ld_no_commit_work) | = 'X'. | |||
| "SELECT single CHAR1 FROM HIER_TYPES INTO @DATA(ld_use_remote_connection). | ||||
| DATA(ld_use_remote_connection) | = ' '. | |||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfc_destination). | ||||
| DATA(ld_rfc_destination) | = 'NONE'. | |||
| "SELECT single NODE_ID FROM HIER_IFACE INTO @DATA(ld_position_on_node). | ||||
| DATA(ld_position_on_node) | = ' '. | |||
| "SELECT single ID FROM TTREE INTO @DATA(ld_id_for_use_as_filter). | ||||
| DATA(ld_id_for_use_as_filter) | = ' '. | |||
Search for further information about these or an SAP related objects