SAP SALT_TOOL_EXECUTE Function Module for
SALT_TOOL_EXECUTE is a standard salt tool execute 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 salt tool execute FM, simply by entering the name SALT_TOOL_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALT
Program Name: SAPLSALT
Main Program: SAPLSALT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALT_TOOL_EXECUTE 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 'SALT_TOOL_EXECUTE'".
EXPORTING
DIALOG_MODE = "
TOOL_TO_EXECUTE = "
TOOL_CALL_TYPE = "
CHANGING
SELFMONI_MSC_TID = "Alert: Global Monitoring Type Identifier
TABLES
MT_TOOL_INFO = "
EXCEPTIONS
INVALID_DIALOG_MODE = 1 MT_TOOL_INFO_MISSING = 2 INVALID_TOOL_CALL_TYPE = 3 NO_TCODE_EXECUTE_AUTHORITY = 4 TOOL_WAS_ABORTED = 5 TOOL_START_FAILED = 6
IMPORTING Parameters details for SALT_TOOL_EXECUTE
DIALOG_MODE -
Data type: ALTYPES-CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TOOL_TO_EXECUTE -
Data type: ALTLEXDESC-TOOLEXECOptional: No
Call by Reference: No ( called with pass by value option)
TOOL_CALL_TYPE -
Data type: ALTLEXDESC-CALLTYPEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SALT_TOOL_EXECUTE
SELFMONI_MSC_TID - Alert: Global Monitoring Type Identifier
Data type: ALGLOBTIDOptional: No
Call by Reference: Yes
TABLES Parameters details for SALT_TOOL_EXECUTE
MT_TOOL_INFO -
Data type: ALTLEXDESCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_DIALOG_MODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MT_TOOL_INFO_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TOOL_CALL_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_TCODE_EXECUTE_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOOL_WAS_ABORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOOL_START_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALT_TOOL_EXECUTE 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_dialog_mode | TYPE ALTYPES-CHAR1, " | |||
| lt_mt_tool_info | TYPE STANDARD TABLE OF ALTLEXDESC, " | |||
| lv_selfmoni_msc_tid | TYPE ALGLOBTID, " | |||
| lv_invalid_dialog_mode | TYPE ALGLOBTID, " | |||
| lv_tool_to_execute | TYPE ALTLEXDESC-TOOLEXEC, " | |||
| lv_mt_tool_info_missing | TYPE ALTLEXDESC, " | |||
| lv_tool_call_type | TYPE ALTLEXDESC-CALLTYPE, " | |||
| lv_invalid_tool_call_type | TYPE ALTLEXDESC, " | |||
| lv_no_tcode_execute_authority | TYPE ALTLEXDESC, " | |||
| lv_tool_was_aborted | TYPE ALTLEXDESC, " | |||
| lv_tool_start_failed | TYPE ALTLEXDESC. " |
|   CALL FUNCTION 'SALT_TOOL_EXECUTE' " |
| EXPORTING | ||
| DIALOG_MODE | = lv_dialog_mode | |
| TOOL_TO_EXECUTE | = lv_tool_to_execute | |
| TOOL_CALL_TYPE | = lv_tool_call_type | |
| CHANGING | ||
| SELFMONI_MSC_TID | = lv_selfmoni_msc_tid | |
| TABLES | ||
| MT_TOOL_INFO | = lt_mt_tool_info | |
| EXCEPTIONS | ||
| INVALID_DIALOG_MODE = 1 | ||
| MT_TOOL_INFO_MISSING = 2 | ||
| INVALID_TOOL_CALL_TYPE = 3 | ||
| NO_TCODE_EXECUTE_AUTHORITY = 4 | ||
| TOOL_WAS_ABORTED = 5 | ||
| TOOL_START_FAILED = 6 | ||
| . " SALT_TOOL_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM SALT_TOOL_EXECUTE
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 CHAR1 FROM ALTYPES INTO @DATA(ld_dialog_mode). | ||||
| "SELECT single TOOLEXEC FROM ALTLEXDESC INTO @DATA(ld_tool_to_execute). | ||||
| "SELECT single CALLTYPE FROM ALTLEXDESC INTO @DATA(ld_tool_call_type). | ||||
Search for further information about these or an SAP related objects