SAP STC_CONT_SCOPE_EDITOR Function Module for Technical Configuration Scope Editor

Search SAP Function Modules

STC_CONT_SCOPE_EDITOR is a standard stc cont scope editor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Technical Configuration Scope Editor 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 stc cont scope editor FM, simply by entering the name STC_CONT_SCOPE_EDITOR into the relevant SAP transaction such as SE37 or SE38.

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

Function STC_CONT_SCOPE_EDITOR 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 'STC_CONT_SCOPE_EDITOR'"Technical Configuration Scope Editor
  EXPORTING
   I_DISPLAY_ONLY =  "Display only flag
   I_SCENARIO =  "
   I_VERSION =  "
*  I_SCOPEVARIANT =  "
   I_TASKLIST_NAME =  "
*  I_TASKLIST_RUN = '' "
*  I_SCOPEVARIANT_CHECK = ABAP_FALSE "

CHANGING
*  C_SCOPEVARIANT_DEFAULT = '' "
   CT_SCOPE_ITEMS =  "

.

IMPORTING Parameters details for STC_CONT_SCOPE_EDITOR

I_DISPLAY_ONLY - Display only flag

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

I_SCENARIO -

Data type: IF_STCS_SCOPE=>TY_TC_SCENARIO
Optional: No
Call by Reference: Yes

I_VERSION -

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

I_SCOPEVARIANT -

Data type: IF_STCS_SCOPE=>TT_CONFIG_SCOPE_VARIANTS
Optional: Yes
Call by Reference: Yes

I_TASKLIST_NAME -

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

I_TASKLIST_RUN -

Data type: STC_SESSION_ID
Default: ''
Optional: Yes
Call by Reference: Yes

I_SCOPEVARIANT_CHECK -

Data type: BOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for STC_CONT_SCOPE_EDITOR

C_SCOPEVARIANT_DEFAULT -

Data type: IF_STCS_SCOPE=>TY_TC_SCOPE_ID
Default: ''
Optional: Yes
Call by Reference: Yes

CT_SCOPE_ITEMS -

Data type: IF_STCS_SCOPE=>TT_CONFIG_SCOPE_ITEMS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for STC_CONT_SCOPE_EDITOR 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.

ABAP code using 7.40 inline data declarations to call FM STC_CONT_SCOPE_EDITOR

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.

Search for further information about these or an SAP related objects