SAP SALK_CLIENT_INFO Function Module for
SALK_CLIENT_INFO is a standard salk client info 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 salk client info FM, simply by entering the name SALK_CLIENT_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALK
Program Name: SAPLSALK
Main Program: SAPLSALK
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SALK_CLIENT_INFO 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 'SALK_CLIENT_INFO'".
TABLES
MT_TOOL_INFO = "Alert: Description of a tool instance to be executed
EXCEPTIONS
INVALID_DIALOG_MODE = 1 MT_TOOL_INFO_MISSING = 2 TOOL_INTENTIONALLY_ABORTED = 3 INTERNAL_ERROR = 4
TABLES Parameters details for SALK_CLIENT_INFO
MT_TOOL_INFO - Alert: Description of a tool instance to be executed
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)
TOOL_INTENTIONALLY_ABORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SALK_CLIENT_INFO 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_mt_tool_info | TYPE STANDARD TABLE OF ALTLEXDESC, " | |||
| lv_invalid_dialog_mode | TYPE ALTLEXDESC, " | |||
| lv_mt_tool_info_missing | TYPE ALTLEXDESC, " | |||
| lv_tool_intentionally_aborted | TYPE ALTLEXDESC, " | |||
| lv_internal_error | TYPE ALTLEXDESC. " |
| CALL FUNCTION 'SALK_CLIENT_INFO' " |
| TABLES | ||
| MT_TOOL_INFO | = lt_mt_tool_info | |
| EXCEPTIONS | ||
| INVALID_DIALOG_MODE = 1 | ||
| MT_TOOL_INFO_MISSING = 2 | ||
| TOOL_INTENTIONALLY_ABORTED = 3 | ||
| INTERNAL_ERROR = 4 | ||
| . " SALK_CLIENT_INFO | ||
ABAP code using 7.40 inline data declarations to call FM SALK_CLIENT_INFO
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