SAP STREE_EXTERNAL_EDIT_EXTENSION Function Module for









STREE_EXTERNAL_EDIT_EXTENSION is a standard stree external edit extension 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 external edit extension FM, simply by entering the name STREE_EXTERNAL_EDIT_EXTENSION 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): Normal Function Module
Update:



Function STREE_EXTERNAL_EDIT_EXTENSION 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_EDIT_EXTENSION'"
  EXPORTING
   STRUCTURE_ID =  "
   EXTENSION_ID =  "
*  LANGUAGE = SY-LANGU "
*  EDIT_STRUCTURE = 'X' "
*  NO_COMMIT_WORK = 'X' "
*  USE_REMOTE_CONNECTION = ' ' "
*  RFC_DESTINATION = 'NONE' "
*  POSITION_ON_NODE = ' ' "Unique ID - 32 Characters

 IMPORTING
   MESSAGE =  "
   TOGGLE =  "

TABLES
*  USER_PARAMETERS =  "
.



IMPORTING Parameters details for STREE_EXTERNAL_EDIT_EXTENSION

STRUCTURE_ID -

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

EXTENSION_ID -

Data type: TTREE_EXT-EXTENSION
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)

EDIT_STRUCTURE -

Data type: HIER_TYPES-CHAR1
Default: 'X'
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)

USE_REMOTE_CONNECTION -

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

RFC_DESTINATION -

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

POSITION_ON_NODE - Unique ID - 32 Characters

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

EXPORTING Parameters details for STREE_EXTERNAL_EDIT_EXTENSION

MESSAGE -

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

TOGGLE -

Data type: CHAR1
Optional: No
Call by Reference: Yes

TABLES Parameters details for STREE_EXTERNAL_EDIT_EXTENSION

USER_PARAMETERS -

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

Copy and paste ABAP code example for STREE_EXTERNAL_EDIT_EXTENSION 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_extension_id  TYPE TTREE_EXT-EXTENSION, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_edit_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

  CALL FUNCTION 'STREE_EXTERNAL_EDIT_EXTENSION'  "
    EXPORTING
         STRUCTURE_ID = lv_structure_id
         EXTENSION_ID = lv_extension_id
         LANGUAGE = lv_language
         EDIT_STRUCTURE = lv_edit_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
    IMPORTING
         MESSAGE = lv_message
         TOGGLE = lv_toggle
    TABLES
         USER_PARAMETERS = lt_user_parameters
. " STREE_EXTERNAL_EDIT_EXTENSION




ABAP code using 7.40 inline data declarations to call FM STREE_EXTERNAL_EDIT_EXTENSION

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_id).
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
"SELECT single CHAR1 FROM HIER_TYPES INTO @DATA(ld_edit_structure).
DATA(ld_edit_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) = ' '.
 


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!