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

Function RKE_CLIENT_STATE 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 'RKE_CLIENT_STATE'".
IMPORTING
E_SYST_TYPE = "
E_CURR_SETTINGS = "
E_SUBRC = "
E_TRANSP_STATE = "
EXCEPTIONS
INTERNAL_ERROR = 1
EXPORTING Parameters details for RKE_CLIENT_STATE
E_SYST_TYPE -
Data type: CGSPAR-SYSTPOptional: No
Call by Reference: No ( called with pass by value option)
E_CURR_SETTINGS -
Data type: RKEA1_FLAGOptional: No
Call by Reference: Yes
E_SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
E_TRANSP_STATE -
Data type: T000-CCCORACTIVOptional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKE_CLIENT_STATE 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_e_syst_type | TYPE CGSPAR-SYSTP, " | |||
| lv_internal_error | TYPE CGSPAR, " | |||
| lv_e_curr_settings | TYPE RKEA1_FLAG, " | |||
| lv_e_subrc | TYPE SY-SUBRC, " | |||
| lv_e_transp_state | TYPE T000-CCCORACTIV. " |
|   CALL FUNCTION 'RKE_CLIENT_STATE' " |
| IMPORTING | ||
| E_SYST_TYPE | = lv_e_syst_type | |
| E_CURR_SETTINGS | = lv_e_curr_settings | |
| E_SUBRC | = lv_e_subrc | |
| E_TRANSP_STATE | = lv_e_transp_state | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| . " RKE_CLIENT_STATE | ||
ABAP code using 7.40 inline data declarations to call FM RKE_CLIENT_STATE
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 SYSTP FROM CGSPAR INTO @DATA(ld_e_syst_type). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
| "SELECT single CCCORACTIV FROM T000 INTO @DATA(ld_e_transp_state). | ||||
Search for further information about these or an SAP related objects