SAP SLIM_GET_SDCC_CLIENT Function Module for
SLIM_GET_SDCC_CLIENT is a standard slim get sdcc client 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 slim get sdcc client FM, simply by entering the name SLIM_GET_SDCC_CLIENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLIM_IF_TO_SDCC
Program Name: SAPLSLIM_IF_TO_SDCC
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SLIM_GET_SDCC_CLIENT 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 'SLIM_GET_SDCC_CLIENT'".
EXPORTING
SDCC_SESSION_ID = "
IMPORTING
SDCC_SESSION_CLIENT = "Client
EXCEPTIONS
NO_VALID_SESSION_FOR_CLIENT = 1 NO_SESSION_FOUND = 2
IMPORTING Parameters details for SLIM_GET_SDCC_CLIENT
SDCC_SESSION_ID -
Data type: SLIM_SDCC_SESSION_IDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SLIM_GET_SDCC_CLIENT
SDCC_SESSION_CLIENT - Client
Data type: MANDTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_VALID_SESSION_FOR_CLIENT -
Data type:Optional: No
Call by Reference: Yes
NO_SESSION_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SLIM_GET_SDCC_CLIENT 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_sdcc_session_id | TYPE SLIM_SDCC_SESSION_ID, " | |||
| lv_sdcc_session_client | TYPE MANDT, " | |||
| lv_no_valid_session_for_client | TYPE MANDT, " | |||
| lv_no_session_found | TYPE MANDT. " |
|   CALL FUNCTION 'SLIM_GET_SDCC_CLIENT' " |
| EXPORTING | ||
| SDCC_SESSION_ID | = lv_sdcc_session_id | |
| IMPORTING | ||
| SDCC_SESSION_CLIENT | = lv_sdcc_session_client | |
| EXCEPTIONS | ||
| NO_VALID_SESSION_FOR_CLIENT = 1 | ||
| NO_SESSION_FOUND = 2 | ||
| . " SLIM_GET_SDCC_CLIENT | ||
ABAP code using 7.40 inline data declarations to call FM SLIM_GET_SDCC_CLIENT
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