SAP STREE_GET_GLOBAL Function Module for









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

Function Group: SHI0
Program Name: SAPLSHI0
Main Program: SAPLSHI0
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function STREE_GET_GLOBAL 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_GET_GLOBAL'"
IMPORTING
STRUCTURE_ID = "
LANGUAGE = "
EXTENSION = "
NO_COMMIT_WORK = "
RFC_DESTINATION = "
MSGID = "
.



EXPORTING Parameters details for STREE_GET_GLOBAL

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
Optional: No
Call by Reference: No ( called with pass by value option)

EXTENSION -

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

NO_COMMIT_WORK -

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

RFC_DESTINATION -

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

MSGID -

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

Copy and paste ABAP code example for STREE_GET_GLOBAL 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_structure_id  TYPE HIER_IFACE-TREE_ID, "   
lv_language  TYPE SY-LANGU, "   
lv_extension  TYPE TTREE_EXT-EXTENSION, "   
lv_no_commit_work  TYPE CHAR1, "   
lv_rfc_destination  TYPE RFCDES-RFCDEST, "   
lv_msgid  TYPE HIER_MESS-MSGID. "   

  CALL FUNCTION 'STREE_GET_GLOBAL'  "
    IMPORTING
         STRUCTURE_ID = lv_structure_id
         LANGUAGE = lv_language
         EXTENSION = lv_extension
         NO_COMMIT_WORK = lv_no_commit_work
         RFC_DESTINATION = lv_rfc_destination
         MSGID = lv_msgid
. " STREE_GET_GLOBAL




ABAP code using 7.40 inline data declarations to call FM STREE_GET_GLOBAL

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).
 
"SELECT single EXTENSION FROM TTREE_EXT INTO @DATA(ld_extension).
 
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_rfc_destination).
 
"SELECT single MSGID FROM HIER_MESS INTO @DATA(ld_msgid).
 


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!