SAP GRPC_API_ECONTROL_RETRIEVE Function Module for Load the list of the orgunits
GRPC_API_ECONTROL_RETRIEVE is a standard grpc api econtrol 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 Load the list of the orgunits 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 econtrol retrieve FM, simply by entering the name GRPC_API_ECONTROL_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_ECONTROL
Program Name: SAPLGRPC_API_ECONTROL
Main Program: SAPLGRPC_API_ECONTROL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function GRPC_API_ECONTROL_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_ECONTROL_RETRIEVE'"Load the list of the orgunits.
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
I_ECONTROL_ID = "GRPC ID of the individual object
* I_EDITABLE = "Boolean Variable (X=True, -=False, Space=Unknown)
* I_PARENT_ID = "Authorization by Parent object ID
I_REGULATION_ID = "GRPC ID of the individual object
IMPORTING
ES_ECONTROL_LOCAL_DATA = "The detail of entity-level control
E_RETURN_CODE = "Natural number
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_ECONTROL_RETRIEVE
I_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ECONTROL_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_EDITABLE - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARENT_ID - Authorization by Parent object ID
Data type: GRPC_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REGULATION_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_ECONTROL_RETRIEVE
ES_ECONTROL_LOCAL_DATA - The detail of entity-level control
Data type: GRPC_S_API_ECONTROL_DATAOptional: 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_ECONTROL_RETRIEVE
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_API_ECONTROL_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 BAPIRETTAB, " | |||
lv_i_session_id | TYPE GRPC_API_SESSION_ID, " | |||
lv_es_econtrol_local_data | TYPE GRPC_S_API_ECONTROL_DATA, " | |||
lv_e_return_code | TYPE INT4, " | |||
lv_i_econtrol_id | TYPE GRPC_API_OBJECT_ID, " | |||
lv_i_editable | TYPE BOOLEAN, " | |||
lv_i_parent_id | TYPE GRPC_API_OBJECT_ID, " | |||
lv_i_regulation_id | TYPE GRPC_API_OBJECT_ID. " |
  CALL FUNCTION 'GRPC_API_ECONTROL_RETRIEVE' "Load the list of the orgunits |
EXPORTING | ||
I_SESSION_ID | = lv_i_session_id | |
I_ECONTROL_ID | = lv_i_econtrol_id | |
I_EDITABLE | = lv_i_editable | |
I_PARENT_ID | = lv_i_parent_id | |
I_REGULATION_ID | = lv_i_regulation_id | |
IMPORTING | ||
ES_ECONTROL_LOCAL_DATA | = lv_es_econtrol_local_data | |
E_RETURN_CODE | = lv_e_return_code | |
TABLES | ||
ET_MESSAGE | = lt_et_message | |
. " GRPC_API_ECONTROL_RETRIEVE |
ABAP code using 7.40 inline data declarations to call FM GRPC_API_ECONTROL_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.Search for further information about these or an SAP related objects