SAP GRAC_RISK_VIO_LOG Function Module for Risk violation log









GRAC_RISK_VIO_LOG is a standard grac risk vio log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Risk violation log 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 grac risk vio log FM, simply by entering the name GRAC_RISK_VIO_LOG into the relevant SAP transaction such as SE37 or SE38.

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



Function GRAC_RISK_VIO_LOG 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 'GRAC_RISK_VIO_LOG'"Risk violation log
EXPORTING
IT_RTROLELOG = "Log of user reason for profile gen with conflicts

IMPORTING
EV_UP_FLAG = "Single-Character Flag
.



IMPORTING Parameters details for GRAC_RISK_VIO_LOG

IT_RTROLELOG - Log of user reason for profile gen with conflicts

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

EXPORTING Parameters details for GRAC_RISK_VIO_LOG

EV_UP_FLAG - Single-Character Flag

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

Copy and paste ABAP code example for GRAC_RISK_VIO_LOG 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_ev_up_flag  TYPE CHAR1, "   
lv_it_rtrolelog  TYPE GRAC_T_RTROLELOG. "   

  CALL FUNCTION 'GRAC_RISK_VIO_LOG'  "Risk violation log
    EXPORTING
         IT_RTROLELOG = lv_it_rtrolelog
    IMPORTING
         EV_UP_FLAG = lv_ev_up_flag
. " GRAC_RISK_VIO_LOG




ABAP code using 7.40 inline data declarations to call FM GRAC_RISK_VIO_LOG

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!