SAP SAL_WS_TOOLSET_STARTER Function Module for Alert: Monitoring Type: write general customization data









SAL_WS_TOOLSET_STARTER is a standard sal ws toolset starter SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Alert: Monitoring Type: write general customization 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 sal ws toolset starter FM, simply by entering the name SAL_WS_TOOLSET_STARTER into the relevant SAP transaction such as SE37 or SE38.

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



Function SAL_WS_TOOLSET_STARTER 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 'SAL_WS_TOOLSET_STARTER'"Alert: Monitoring Type: write general customization data
EXPORTING
DESTINATION = "Logical Destination (Specified When Function Is Called)
* MAX_TOOLSTARTER_RUNTIME = 0 "Alert: Maximum runtime of a tool dispatcher
TOOL_DISPATCHER_NAME = "Alert: Name of a tool dispatcher

IMPORTING
ERROR_TEXT = "

TABLES
TOOL_SET = "Alert: Description of a tool instance to be executed

EXCEPTIONS
C_CALL_FAILED = 1 INTERNAL_ERROR = 2 NOT_PRIMARY_CEN = 3 WS_PROXY_FAILURE = 4 NOT_CONNECTED_TO_SEGMENT = 5
.



IMPORTING Parameters details for SAL_WS_TOOLSET_STARTER

DESTINATION - Logical Destination (Specified When Function Is Called)

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

MAX_TOOLSTARTER_RUNTIME - Alert: Maximum runtime of a tool dispatcher

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

TOOL_DISPATCHER_NAME - Alert: Name of a tool dispatcher

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

EXPORTING Parameters details for SAL_WS_TOOLSET_STARTER

ERROR_TEXT -

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

TABLES Parameters details for SAL_WS_TOOLSET_STARTER

TOOL_SET - Alert: Description of a tool instance to be executed

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

EXCEPTIONS details

C_CALL_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_PRIMARY_CEN -

Data type:
Optional: No
Call by Reference: Yes

WS_PROXY_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

NOT_CONNECTED_TO_SEGMENT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SAL_WS_TOOLSET_STARTER 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:
lt_tool_set  TYPE STANDARD TABLE OF ALTLEXDESC, "   
lv_error_text  TYPE STRING, "   
lv_destination  TYPE RFCDEST, "   
lv_c_call_failed  TYPE RFCDEST, "   
lv_internal_error  TYPE RFCDEST, "   
lv_max_toolstarter_runtime  TYPE ALTOOLDP-DPMAXRUNT, "   0
lv_not_primary_cen  TYPE ALTOOLDP, "   
lv_tool_dispatcher_name  TYPE ALTLDPNM, "   
lv_ws_proxy_failure  TYPE ALTLDPNM, "   
lv_not_connected_to_segment  TYPE ALTLDPNM. "   

  CALL FUNCTION 'SAL_WS_TOOLSET_STARTER'  "Alert: Monitoring Type: write general customization data
    EXPORTING
         DESTINATION = lv_destination
         MAX_TOOLSTARTER_RUNTIME = lv_max_toolstarter_runtime
         TOOL_DISPATCHER_NAME = lv_tool_dispatcher_name
    IMPORTING
         ERROR_TEXT = lv_error_text
    TABLES
         TOOL_SET = lt_tool_set
    EXCEPTIONS
        C_CALL_FAILED = 1
        INTERNAL_ERROR = 2
        NOT_PRIMARY_CEN = 3
        WS_PROXY_FAILURE = 4
        NOT_CONNECTED_TO_SEGMENT = 5
. " SAL_WS_TOOLSET_STARTER




ABAP code using 7.40 inline data declarations to call FM SAL_WS_TOOLSET_STARTER

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 DPMAXRUNT FROM ALTOOLDP INTO @DATA(ld_max_toolstarter_runtime).
 
 
 
 
 


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!