You are on page 1of 1

7/9/2019 Debugging HR Trigger - Simulation - Governance, Risk and Compliance - SCN Wiki

Getting Started Store

Community WIKI SAP Community Welcome, Guest Login Register Search the Community

Governance, Risk and Compliance / … / Access Request (ARQ)

Debugging HR Trigger - Simulation


Created by Luciana Ullmann, last modified on Jun 18, 2015

Purpose
This WIKI is intended to assist customers in getting their HR trigger scenarios working.

This document should be reviewed by programmers or technical people. This document is not meant to functional people without technical knowledge, as it explains how to set up breakpoints, and how to
fill out the HR trigger function module in the GRC foundation system to debug possible root causes.

Overview
Below will be detailed most important code points that should be analysed during debug.

The whole scenario of building HR triggers is not the goal here. I assume the scenario is in place, butthe simulation is not resolving the correct Action ID.

Simulating at Function level


A single, top-level expression can be processed and its result will be returned in the result data object. Upon simulating it, it is possible to see if the BRF rule is working as designed.

In the BRFplus Workbench, a simulation tool exists that allows you to analyze the processing and outcome of an active function with test values. The tool can be invoked either for a currently displayed
function with the button "Start Simulation", or for any function via the menu entry "Tools • Simulation".

When a function is executed, BRFplus will try to execute the ABAP code that was automatically generated when the function was executed the first time.

To debug this code, when the function is being simulated, please set breakpoints in the following:

To debug the simulation at function level (not a decision table level), set the following breakpoints:

Transaction: SE80

WebDynpro component: FDT_WD_SIMULATION

Method: RUN_SIMULATION

Other points, that will be executed from the above breakpoint, are also useful, if you want to go directly to them, here they are:

Transaction: SE24

Class: CL_FDT_FUNCTION

Method: IF_FDT_FUNCTION~PROCESS

Class: CL_FDT_DECISION_TABLE

Method: IF_FDT_EXPRESSION~PROCESS

Class: CL_FDT_COMPARISON

Method: COMPARE_ELEMENTS

Class: CL_FDT_EXPR_SV

Method: PROCESS_RANGE

Hope this helps!

Related Content
Check out this blog, if HR Triggers BRF+ rule getting too complex?

Related Documents

https://wiki.scn.sap.com/wiki/display/GRC/Debugging+HR+Trigger+-+Simulation 1/2

You might also like