SAP GRPC_API_XECGROUP_GET_LOCAL Function Module for Get all local xecgroup by a central ELC
GRPC_API_XECGROUP_GET_LOCAL is a standard grpc api xecgroup get local SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get all local xecgroup by a central ELC 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 xecgroup get local FM, simply by entering the name GRPC_API_XECGROUP_GET_LOCAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_XECGROUP
Program Name: SAPLGRPC_API_XECGROUP
Main Program: SAPLGRPC_API_XECGROUP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_API_XECGROUP_GET_LOCAL 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_XECGROUP_GET_LOCAL'"Get all local xecgroup by a central ELC.
EXPORTING
I_OBJECT_ID = "GRPC ID of the individual object
I_REGULATION_ID = "GRPC ID of the individual object
TABLES
ET_REL_OBJECTS = "Econtrol key list
IMPORTING Parameters details for GRPC_API_XECGROUP_GET_LOCAL
I_OBJECT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: Yes
I_REGULATION_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: Yes
TABLES Parameters details for GRPC_API_XECGROUP_GET_LOCAL
ET_REL_OBJECTS - Econtrol key list
Data type: GRPC_T_API_ECONTROLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_XECGROUP_GET_LOCAL 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_object_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lt_et_rel_objects | TYPE STANDARD TABLE OF GRPC_T_API_ECONTROL, " | |||
| lv_i_regulation_id | TYPE GRPC_API_OBJECT_ID. " |
|   CALL FUNCTION 'GRPC_API_XECGROUP_GET_LOCAL' "Get all local xecgroup by a central ELC |
| EXPORTING | ||
| I_OBJECT_ID | = lv_i_object_id | |
| I_REGULATION_ID | = lv_i_regulation_id | |
| TABLES | ||
| ET_REL_OBJECTS | = lt_et_rel_objects | |
| . " GRPC_API_XECGROUP_GET_LOCAL | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_XECGROUP_GET_LOCAL
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