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

Function RKE_BIW_DATA_TIMESTMP_GET 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_BIW_DATA_TIMESTMP_GET'".
EXPORTING
* I_T_SEL = "
IMPORTING
E_TO_TIMESTMP = "
EXCEPTIONS
FOREIGN_LOCK = 1
IMPORTING Parameters details for RKE_BIW_DATA_TIMESTMP_GET
I_T_SEL -
Data type: KERR_T_SELOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RKE_BIW_DATA_TIMESTMP_GET
E_TO_TIMESTMP -
Data type: CEDDB-TIMESTMPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKE_BIW_DATA_TIMESTMP_GET 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_i_t_sel | TYPE KERR_T_SEL, " | |||
| lv_foreign_lock | TYPE KERR_T_SEL, " | |||
| lv_e_to_timestmp | TYPE CEDDB-TIMESTMP. " |
|   CALL FUNCTION 'RKE_BIW_DATA_TIMESTMP_GET' " |
| EXPORTING | ||
| I_T_SEL | = lv_i_t_sel | |
| IMPORTING | ||
| E_TO_TIMESTMP | = lv_e_to_timestmp | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| . " RKE_BIW_DATA_TIMESTMP_GET | ||
ABAP code using 7.40 inline data declarations to call FM RKE_BIW_DATA_TIMESTMP_GET
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 TIMESTMP FROM CEDDB INTO @DATA(ld_e_to_timestmp). | ||||
Search for further information about these or an SAP related objects