SAP STREE_STRUCTURE_READ_MULTIPLE Function Module for Read structure data









STREE_STRUCTURE_READ_MULTIPLE is a standard stree structure read multiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read structure data 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 structure read multiple FM, simply by entering the name STREE_STRUCTURE_READ_MULTIPLE 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_READ_MULTIPLE 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_READ_MULTIPLE'"Read structure data
EXPORTING
* GET_ALSO_TEXTS = ' ' "

IMPORTING
MESSAGE = "

TABLES
I_STRUCTURE_IDS = "
* E_STRUCTURE_HEADER = "
* E_STRUCTURE_TEXTS = "
.



IMPORTING Parameters details for STREE_STRUCTURE_READ_MULTIPLE

GET_ALSO_TEXTS -

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

EXPORTING Parameters details for STREE_STRUCTURE_READ_MULTIPLE

MESSAGE -

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

TABLES Parameters details for STREE_STRUCTURE_READ_MULTIPLE

I_STRUCTURE_IDS -

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

E_STRUCTURE_HEADER -

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

E_STRUCTURE_TEXTS -

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

Copy and paste ABAP code example for STREE_STRUCTURE_READ_MULTIPLE 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_get_also_texts  TYPE CHAR1, "   ' '
lt_i_structure_ids  TYPE STANDARD TABLE OF TTREE, "   
lt_e_structure_header  TYPE STANDARD TABLE OF TTREE, "   
lt_e_structure_texts  TYPE STANDARD TABLE OF TTREET. "   

  CALL FUNCTION 'STREE_STRUCTURE_READ_MULTIPLE'  "Read structure data
    EXPORTING
         GET_ALSO_TEXTS = lv_get_also_texts
    IMPORTING
         MESSAGE = lv_message
    TABLES
         I_STRUCTURE_IDS = lt_i_structure_ids
         E_STRUCTURE_HEADER = lt_e_structure_header
         E_STRUCTURE_TEXTS = lt_e_structure_texts
. " STREE_STRUCTURE_READ_MULTIPLE




ABAP code using 7.40 inline data declarations to call FM STREE_STRUCTURE_READ_MULTIPLE

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_get_also_texts) = ' '.
 
 
 
 


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!