SAP GRPC_API_CONTROL_RETRIEVE Function Module for Load the list of the orgunits









GRPC_API_CONTROL_RETRIEVE is a standard grpc api control 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 control retrieve FM, simply by entering the name GRPC_API_CONTROL_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_CONTROL
Program Name: SAPLGRPC_API_CONTROL
Main Program: SAPLGRPC_API_CONTROL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GRPC_API_CONTROL_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_CONTROL_RETRIEVE'"Load the list of the orgunits
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
   I_CONTROL_ID =  "GRPC ID of the individual object
*  I_REGULATION_ID =  "GRPC ID of the individual object
*  I_EDITABLE =  "Boolean Variable (X=True, -=False, Space=Unknown)
*  I_PARENT_ID =  "Authorization by Parent object ID

 IMPORTING
   ES_CONTROL_BDATA =  "Control data for API service - basic fields
   ES_CONTROL_CDATA =  "Control data for API service - control fields
   ES_CONTROL_TDATA =  "Control data for API service - testing fields
   ET_SUBGROUP =  "Control Subgroup
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_RELEVANCE =  "Relevance
*  ET_CONTROL_COR =  "Obsolete. See ET_SUBPROCESS_RISK
*  ET_CONTROL_ACCGROUP =  "table type for account group
*  ET_CONTROL_RULE =  "Control Rule Assigment Linking Table
*  ET_MESSAGE =  "Table with BAPI Return Information
*  ET_SUBPROCESS_RISK =  "Assigned risks
*  ET_REGULATION =  "Regulation
*  ET_REGULATION_REQ =  "Regulation requirements
.



IMPORTING Parameters details for GRPC_API_CONTROL_RETRIEVE

I_SESSION_ID - GRPC unique session ID

Data type: GRPC_API_SESSION_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CONTROL_ID - GRPC ID of the individual object

Data type: GRPC_API_OBJECT_ID
Optional: No
Call by Reference: No ( called with pass by value option)

I_REGULATION_ID - GRPC ID of the individual object

Data type: GRPC_API_OBJECT_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EDITABLE - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARENT_ID - Authorization by Parent object ID

Data type: GRPC_API_OBJECT_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GRPC_API_CONTROL_RETRIEVE

ES_CONTROL_BDATA - Control data for API service - basic fields

Data type: GRPC_S_API_CONTROL_BDATA
Optional: No
Call by Reference: No ( called with pass by value option)

ES_CONTROL_CDATA - Control data for API service - control fields

Data type: GRPC_S_API_CONTROL_CDATA
Optional: No
Call by Reference: No ( called with pass by value option)

ES_CONTROL_TDATA - Control data for API service - testing fields

Data type: GRPC_S_API_CONTROL_TDATA
Optional: No
Call by Reference: No ( called with pass by value option)

ET_SUBGROUP - Control Subgroup

Data type: GRPC_T_API_CNTR_SUBGROUP
Optional: No
Call by Reference: No ( called with pass by value option)

E_RETURN_CODE - Natural number

Data type: INT4
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GRPC_API_CONTROL_RETRIEVE

ET_RELEVANCE - Relevance

Data type: GRPC_T_API_CNTR_RELEVANCE
Optional: Yes
Call by Reference: Yes

ET_CONTROL_COR - Obsolete. See ET_SUBPROCESS_RISK

Data type: GRPC_T_API_CONTROL_COR
Optional: Yes
Call by Reference: Yes

ET_CONTROL_ACCGROUP - table type for account group

Data type: GRPC_T_API_CONTROL_ACCGROUP
Optional: Yes
Call by Reference: Yes

ET_CONTROL_RULE - Control Rule Assigment Linking Table

Data type: GRPC_T_API_CONTROL_RULE
Optional: Yes
Call by Reference: Yes

ET_MESSAGE - Table with BAPI Return Information

Data type: BAPIRETTAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

ET_SUBPROCESS_RISK - Assigned risks

Data type: GRPC_T_API_RISK_COVERAGE
Optional: Yes
Call by Reference: Yes

ET_REGULATION - Regulation

Data type: GRFN_T_API_REGULATION
Optional: Yes
Call by Reference: Yes

ET_REGULATION_REQ - Regulation requirements

Data type: GRFN_T_API_REGULATION_REQ
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for GRPC_API_CONTROL_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_relevance  TYPE STANDARD TABLE OF GRPC_T_API_CNTR_RELEVANCE, "   
lv_i_session_id  TYPE GRPC_API_SESSION_ID, "   
lv_es_control_bdata  TYPE GRPC_S_API_CONTROL_BDATA, "   
lv_i_control_id  TYPE GRPC_API_OBJECT_ID, "   
lt_et_control_cor  TYPE STANDARD TABLE OF GRPC_T_API_CONTROL_COR, "   
lv_es_control_cdata  TYPE GRPC_S_API_CONTROL_CDATA, "   
lv_i_regulation_id  TYPE GRPC_API_OBJECT_ID, "   
lv_es_control_tdata  TYPE GRPC_S_API_CONTROL_TDATA, "   
lt_et_control_accgroup  TYPE STANDARD TABLE OF GRPC_T_API_CONTROL_ACCGROUP, "   
lv_i_editable  TYPE BOOLEAN, "   
lv_et_subgroup  TYPE GRPC_T_API_CNTR_SUBGROUP, "   
lt_et_control_rule  TYPE STANDARD TABLE OF GRPC_T_API_CONTROL_RULE, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_parent_id  TYPE GRPC_API_OBJECT_ID, "   
lv_e_return_code  TYPE INT4, "   
lt_et_subprocess_risk  TYPE STANDARD TABLE OF GRPC_T_API_RISK_COVERAGE, "   
lt_et_regulation  TYPE STANDARD TABLE OF GRFN_T_API_REGULATION, "   
lt_et_regulation_req  TYPE STANDARD TABLE OF GRFN_T_API_REGULATION_REQ. "   

  CALL FUNCTION 'GRPC_API_CONTROL_RETRIEVE'  "Load the list of the orgunits
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_CONTROL_ID = lv_i_control_id
         I_REGULATION_ID = lv_i_regulation_id
         I_EDITABLE = lv_i_editable
         I_PARENT_ID = lv_i_parent_id
    IMPORTING
         ES_CONTROL_BDATA = lv_es_control_bdata
         ES_CONTROL_CDATA = lv_es_control_cdata
         ES_CONTROL_TDATA = lv_es_control_tdata
         ET_SUBGROUP = lv_et_subgroup
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_RELEVANCE = lt_et_relevance
         ET_CONTROL_COR = lt_et_control_cor
         ET_CONTROL_ACCGROUP = lt_et_control_accgroup
         ET_CONTROL_RULE = lt_et_control_rule
         ET_MESSAGE = lt_et_message
         ET_SUBPROCESS_RISK = lt_et_subprocess_risk
         ET_REGULATION = lt_et_regulation
         ET_REGULATION_REQ = lt_et_regulation_req
. " GRPC_API_CONTROL_RETRIEVE




ABAP code using 7.40 inline data declarations to call FM GRPC_API_CONTROL_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!