SAP GRPC_API_TIMEFRAME_RETRIEVE Function Module for to get the list of the users from the system
GRPC_API_TIMEFRAME_RETRIEVE is a standard grpc api timeframe retrieve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for to get the list of the users from the system 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 grpc api timeframe retrieve FM, simply by entering the name GRPC_API_TIMEFRAME_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_TIMEFRAME
Program Name: SAPLGRPC_API_TIMEFRAME
Main Program: SAPLGRPC_API_TIMEFRAME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_API_TIMEFRAME_RETRIEVE 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 'GRPC_API_TIMEFRAME_RETRIEVE'"to get the list of the users from the system.
EXPORTING
I_TIMEFRAME = "GRPC Entity API: Timeframe of the session
I_TF_YEAR = "The year of the GRPC entity API session
* I_LANGUAGE = SY-LANGU "Language Key of Current Text Environment
IMPORTING
ES_TIMEFRAME = "The timeframe data
E_RETURN_CODE = "Natural number
TABLES
* ET_MESSAGE = "Error Messages
IMPORTING Parameters details for GRPC_API_TIMEFRAME_RETRIEVE
I_TIMEFRAME - GRPC Entity API: Timeframe of the session
Data type: GRPC_API_SESSION_TIMEFRAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TF_YEAR - The year of the GRPC entity API session
Data type: GRPC_API_SESSION_TF_YEAROptional: No
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - Language Key of Current Text Environment
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_TIMEFRAME_RETRIEVE
ES_TIMEFRAME - The timeframe data
Data type: GRPC_S_API_TIMEFRAME_DETAILOptional: No
Call by Reference: No ( called with pass by value option)
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRPC_API_TIMEFRAME_RETRIEVE
ET_MESSAGE - Error Messages
Data type: BAPIRET2_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_API_TIMEFRAME_RETRIEVE 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_et_message | TYPE STANDARD TABLE OF BAPIRET2_TAB, " | |||
| lv_i_timeframe | TYPE GRPC_API_SESSION_TIMEFRAME, " | |||
| lv_es_timeframe | TYPE GRPC_S_API_TIMEFRAME_DETAIL, " | |||
| lv_i_tf_year | TYPE GRPC_API_SESSION_TF_YEAR, " | |||
| lv_e_return_code | TYPE INT4, " | |||
| lv_i_language | TYPE SY-LANGU. " SY-LANGU |
|   CALL FUNCTION 'GRPC_API_TIMEFRAME_RETRIEVE' "to get the list of the users from the system |
| EXPORTING | ||
| I_TIMEFRAME | = lv_i_timeframe | |
| I_TF_YEAR | = lv_i_tf_year | |
| I_LANGUAGE | = lv_i_language | |
| IMPORTING | ||
| ES_TIMEFRAME | = lv_es_timeframe | |
| E_RETURN_CODE | = lv_e_return_code | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_TIMEFRAME_RETRIEVE | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_TIMEFRAME_RETRIEVE
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 LANGU FROM SY INTO @DATA(ld_i_language). | ||||
| DATA(ld_i_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects