Inline Risk Analysis

ActiveControl includes functionality – via its ShiftLeft: Risk Guard analyser – to warn users when doing an Approval or Test signoff, if the transports contain ‘risky’ objects.

This functionality also exists in the form of an ‘Inline Risk Analysis’ that can be presented to users in the SAPGUI. The functionality has several main current use cases:

1) to warn Developers if the objects they are changing have been deemed risky, earlier in the process than the Approval/Test sign-off process.
2) to facilitate a white-listing/blacklisting scenario – whereby certain objects cannot be touched in certain Development systems.
3) to facilitate transport splitting scenario – where certain objects cannot be mixed in the same transport.

Example of Inline Risk screen presented to Developers:

Configuration Steps

To use Inline Risk Analysis in its simplest form of warning Developers/Functional teams that the objects they are changing have been deemed risky objects, the following configuration is required in the ActiveControl Domain Controller. Most of the configuration steps are similar to that used by the ShiftLeft: Risk Guard analyser.

1. Risk Group should be configured in /BTI/TE_RISKG.

2. The set of objects should be added to /BTI/TE_RISKGOB.

3. Each Development system is then configured for the appropriate risk object groups along with a risk level that if exceeded with trigger the error/warning, in table /BTI/TE_RISK_INL.

System ID: Enter the SID of the development system for which you are switching on Inline Risk Analysis
Risk Group: Enter the Risk Group (from /BTI/TE_RISKG) that contains the risky objects that you want to highlight to the developer
Risk Level: Enter the minimum risk level that you want to report on
Error Mode: Choose here whether you want to present a Warning to the developer (allowing them to continue) or an Error (which will stop them from adding the object)