Risk Guard (0001) checks all objects on the selected transport requests and highlights any that contain objects identified as critical or risky, for example Company Code changes, Plant changes or changes to Number Ranges. If there are any changes to these types of objects then a message will be issued notifying the user of the level of risk for that request.
Parameters
| Parameter | Description |
|---|---|
| MINIMUMRISKLEVEL | Minimum Risk Level from table/BTI/TE_RISKL |
| RISKGROUP | Risk Group from table /BTI/TE_RISKG |
Prerequisite Configuration
There are 4 tables that must first be configured in the ActiveControl domain controller before Risk Guard will work:
| Table | Description |
|---|---|
| /BTI/TE_RISKL | Risk Levels |
| /BTI/TE_RISKG | Risk Groups |
| /BTI/TE_RISKGOB | Risk Group Objects |
| /BTI/TE_RISKGOBT | Risk Group Object Texts |
Some sample entries are delivered in these tables but it recommended to create local customer specific entries so they won’t be overwritten during any upgrades. The tables can be configured using via SE16 or SM31. It is also possible to download whatever has already been maintained in Risk Group Objects and texts using /BTI/TE_RUDOWNLOAD_RISK_DATA, and also to do an enmasse upload of this data using /BTI/TE_RUUPLOAD_RISK_DATA.
Risk Levels
Risk levels are configured in backend table /BTI/TE_RISKL.
| Field | Details |
|---|---|
| RISKLEVELID | 10 character field for the Risk Level Identifier. |
| RISKLEVEL | 10 digit numerical field used to indicate the risk level. The higher the value of this field, the higher the risk. |
| TITLE | 50 character comment field. This can be used to indicate the risk level in words. For example, “Low risk”, “Moderate risk”, “High risk” etc. |
Below are some example entries for this table:
| Risk Level Identifier | Risk Level | Comment |
|---|---|---|
| BT0001 | 1 | Risk level 1 |
| BT0002 | 2 | Risk level 2 |
| BT0003 | 3 | Risk level 3 |
| BT0004 | 4 | Risk level 4 |
| BT0005 | 5 | Risk level 5 |
| BT0006 | 6 | Risk level 6 |
| BT0007 | 7 | Risk level 7 |
| BT0008 | 8 | Risk level 8 |
| BT0009 | 9 | Risk level 9 |
| BT0010 | 10 | Risk level 10 |
When setting up Risk Guard, you can specify a risk level value. If that is set, the Risk Analysis will only report on objects that have a risk level greater than the specified value.
Risk Groups
Risk groups provide ActiveControl with a way of varying how risks are identified for different systems or control points. For example, a program called ZZ_TEST may be a moderate risk when going into a QA system but a high risk when moving into a Production system. Risk Groups are configured in backend table /BTI/TE_RISKG.
There are 2 fields in this table. Field GROUPID is the group identifier and the field TITLE is the description of the group.
Below are some example entries for this table:
| GROUPID | TITLE |
|---|---|
| BT0001 | Basis Technologies Risk Group 0001 |
Risk Group Objects
Risk Groups Objects are configured in backend table /BTI/TE_RISKGOB.
| Field | Description |
|---|---|
| GROUPID | Links the object to the group specified in table /BTI/TE_RISKG. |
| PGMID , OBJECT, OBJ_NAME | Relate to the same fields in the object list for a transport. For example, to highlight the transports of any number range objects as risks, there needs to be 2 entries in this table, one for R3TR NROB and one for R3TR TABU NRIV. Note that * can be used as a wildcard value. E.g. T0* |
| RISKLEVELID | References the risk level table /BTI/TE_RISKL. |
| APPENDFLAG | Checking this will include direct includes (eg. adding MARA with this flag set also adds EMARA and IST_MAT_FIELDS) |
| INVERSEFLAG | Currently does not do anything. |
| DELETEFLAG | Can be used if you want the Risk Guard analysis to indicate if a transport contains a deletion to the object) |
| URL | Can be used if you want the Risk Guard analyser output to include a URL to further information. |
Below are some example entries for the /BTI/TE_RISKGOB table:
| GROUPID | PGMID | OBJECT | OBJ_NAME | RISKLEVELID | TEXT | APPENDFLAG | INVERSEFLAG | DELETEFLAG | URL |
|---|---|---|---|---|---|---|---|---|---|
| BT0001 | LIMU | INDX | * | BT0009 | Database indexes require rebuilding – take care importing into production | ||||
| BT0001 | LIMU | TABD | * | BT0007 | Table definition changes may have an effect on production data | ||||
| BT0001 | R3TR | NROB | * | BT0008 | Be careful when transporting number range objects | ||||
| BT0001 | R3TR | TABL | * | BT0008 | Table definition changes may have an effect on production data | ||||
| BT0001 | R3TR | TABU | NRIV | BT0010 | Number range intervals should not be transported unless during setup | https://blogs.sap.com/2015/05/29/number-ranges-things-to-keep-in-mind/ | |||
| BT0001 | R3TR | TABU | PATH | BT0007 | Be careful when transporting logical filenames and directories | ||||
| BT0001 | R3TR | TABU | T000 | BT0008 | The client table should never be transported | ||||
| BT0001 | R3TR | TABU | T001 | BT0008 | Be careful when changing the critical Company Code table | ||||
| BT0001 | R3TR | TABU | T012 | BT0007 | Be careful when transporting the House Banks table | ||||
| BT0001 | R3TR | TABU | T030 | BT0007 | Be careful when transporting the critical General Ledger table | ||||
| BT0001 | R3TR | TABU | TBDLS | BT0008 | Be careful when transporting Logical Systems | ||||
| BT0001 | R3TR | XINX | * | BT0009 | Database indexes changes should be carefully applied to production | ||||
| BT0001 | R3TR | XPRA | * | BT0006 | Take care as this change will be executing program(s) after import |
Risk Groups Object Texts
Risk Groups Object Texts are configured in backend table /BTI/TE_RISKGOBT. This table contains the text to be displayed when the Risk Guard finds any risks.
Post your comment on this topic.