SAP GRPC_BTC_REPORT_CHECK Function Module for
GRPC_BTC_REPORT_CHECK is a standard grpc btc report check 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 grpc btc report check FM, simply by entering the name GRPC_BTC_REPORT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_BTC_REPORT
Program Name: SAPLGRPC_BTC_REPORT
Main Program: SAPLGRPC_BTC_REPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_BTC_REPORT_CHECK 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_BTC_REPORT_CHECK'".
EXPORTING
I_GUID = "
IMPORTING
E_DONE = "
E_PROGRESS = "
ET_DATA = "
ET_TEXT = "
ES_ATTR = "
E_STATUS_UPDATED = "
IMPORTING Parameters details for GRPC_BTC_REPORT_CHECK
I_GUID -
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_BTC_REPORT_CHECK
E_DONE -
Data type: ABAP_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
E_PROGRESS -
Data type: FOptional: No
Call by Reference: No ( called with pass by value option)
ET_DATA -
Data type: GRPCR_T_REPORT_LINEOptional: No
Call by Reference: Yes
ET_TEXT -
Data type: GRPCR_T_TEXTPOOLOptional: No
Call by Reference: Yes
ES_ATTR -
Data type: GRPCR_S_ATTR_POOLOptional: No
Call by Reference: Yes
E_STATUS_UPDATED -
Data type: ABAP_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_BTC_REPORT_CHECK 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_done | TYPE ABAP_BOOL, " | |||
| lv_i_guid | TYPE GUID_32, " | |||
| lv_e_progress | TYPE F, " | |||
| lv_et_data | TYPE GRPCR_T_REPORT_LINE, " | |||
| lv_et_text | TYPE GRPCR_T_TEXTPOOL, " | |||
| lv_es_attr | TYPE GRPCR_S_ATTR_POOL, " | |||
| lv_e_status_updated | TYPE ABAP_BOOL. " |
|   CALL FUNCTION 'GRPC_BTC_REPORT_CHECK' " |
| EXPORTING | ||
| I_GUID | = lv_i_guid | |
| IMPORTING | ||
| E_DONE | = lv_e_done | |
| E_PROGRESS | = lv_e_progress | |
| ET_DATA | = lv_et_data | |
| ET_TEXT | = lv_et_text | |
| ES_ATTR | = lv_es_attr | |
| E_STATUS_UPDATED | = lv_e_status_updated | |
| . " GRPC_BTC_REPORT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_BTC_REPORT_CHECK
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