SAP Knowledge Base Article - Preview

2203318 - KRI frequency is not considered by the background job

Symptom

When KRI instance is created with timeframe daily or monthly still after triggering of background job GRRM_KRI_RUNTIME, the KRIs are updated on daily basis and the last execution date is not saved.


Read more...

Environment

Risk Management 10.0 Risk Management 10.1, Risk Management 12.0

Product

SAP Risk Management 10.0 ; SAP Risk Management 10.1 ; SAP Risk Management 12.0

Keywords

KRI, KRI Instance, Key Risk Indicator, Next Execution, Timeframe, Frequency, Offset , KBA , features and functionality , best practices , GRC-RM , GRC Risk Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.