SAP EASYDMS_GET_RFC_CACHE_TIME Function Module for Abfrage der Aktualität der RFC-Schnittstelle
EASYDMS_GET_RFC_CACHE_TIME is a standard easydms get rfc cache time SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Abfrage der Aktualität der RFC-Schnittstelle processing and below is the pattern details for this FM, 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 easydms get rfc cache time FM, simply by entering the name EASYDMS_GET_RFC_CACHE_TIME into the relevant SAP transaction such as SE37 or SE38.
Function Group: EASYDMS
Program Name: SAPLEASYDMS
Main Program: SAPLEASYDMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EASYDMS_GET_RFC_CACHE_TIME 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 'EASYDMS_GET_RFC_CACHE_TIME'"Abfrage der Aktualität der RFC-Schnittstelle.
IMPORTING
DATETIME = "Änderungszeitpunkt (UTC)
EXPORTING Parameters details for EASYDMS_GET_RFC_CACHE_TIME
DATETIME - Änderungszeitpunkt (UTC)
Data type: BAPI_DOC_FILES2-CHANGED_ATOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EASYDMS_GET_RFC_CACHE_TIME 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_datetime | TYPE BAPI_DOC_FILES2-CHANGED_AT. " |
|   CALL FUNCTION 'EASYDMS_GET_RFC_CACHE_TIME' "Abfrage der Aktualität der RFC-Schnittstelle |
| IMPORTING | ||
| DATETIME | = lv_datetime | |
| . " EASYDMS_GET_RFC_CACHE_TIME | ||
ABAP code using 7.40 inline data declarations to call FM EASYDMS_GET_RFC_CACHE_TIME
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 CHANGED_AT FROM BAPI_DOC_FILES2 INTO @DATA(ld_datetime). | ||||
Search for further information about these or an SAP related objects