SAP GRPC_API_RISK_RETRIEVE Function Module for Retrieve Local Risk Data

Search SAP Function Modules

GRPC_API_RISK_RETRIEVE is a standard grpc api risk 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 Retrieve Local Risk Data 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 risk retrieve FM, simply by entering the name GRPC_API_RISK_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_RISK
Program Name: SAPLGRPC_API_RISK
Main Program: SAPLGRPC_API_RISK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_API_RISK_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_RISK_RETRIEVE'"Retrieve Local Risk Data
  EXPORTING
   I_SESSION_ID =  "GRPC unique session ID
   I_RISK_ID =  "GRPC ID of the individual object
*  I_EDITABLE =  "Boolean Variable (X=True, -=False, Space=Unknown)
   I_REGULATION_ID =  "GRPC ID of the individual object

 IMPORTING
   E_RETURN_CODE =  "Natural number
   ES_LOCAL_RISK_DATA =  "Local Risk Data Structure
   ES_LOCAL_RISK_ATTR =  "Additional Risk Attributes
   ET_LOCAL_RISK_DRIVER =  "Driver
   ET_LOCAL_RISK_IMPACT =  "Impact

TABLES
*  ET_MESSAGE =  "Obsolete: Table with BAPI Return Information
*  ET_CONTROL_TYPE =  "Obsolete: Control Types
*  ET_RISK_ASSERTION =  "Account Assertions on Risk

.

IMPORTING Parameters details for GRPC_API_RISK_RETRIEVE

I_SESSION_ID - GRPC unique session ID

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

I_RISK_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_EDITABLE - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: 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_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GRPC_API_RISK_RETRIEVE

E_RETURN_CODE - Natural number

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

ES_LOCAL_RISK_DATA - Local Risk Data Structure

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

ES_LOCAL_RISK_ATTR - Additional Risk Attributes

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

ET_LOCAL_RISK_DRIVER - Driver

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

ET_LOCAL_RISK_IMPACT - Impact

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

TABLES Parameters details for GRPC_API_RISK_RETRIEVE

ET_MESSAGE - Obsolete: Table with BAPI Return Information

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

ET_CONTROL_TYPE - Obsolete: Control Types

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

ET_RISK_ASSERTION - Account Assertions on Risk

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

Copy and paste ABAP code example for GRPC_API_RISK_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.

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