SAP Knowledge Base Article - Preview

2908656 - After releasing a request that was on hold, the escalation no longer works.

Symptom

Escalation is working correctly for all MSMP workflow Process IDs, however if customer puts a given request on hold, and later releases it, that request will no longer escalate once the escalation time defined at stage level is reached.

This behavior is noted for any request in the MSMP regardless of Process ID.


Read more...

Environment

SAP GRC Access Control 10.0
SAP GRC Access Control 10.1
SAP GRC Access Control 12.0

Product

SAP Access Control 10.0 ; SAP Access Control 10.1 ; SAP Access Control 12.0

Keywords

HANDLE_ESCALATION_FORWARD _RELEASE_INSTANCE_FOR_ESCALATE EVALUATE_ROUTING_RULES HANDLE_ESCAPE_ROUTING P_HANDLE_ESCALATION HANDLE_MOVE_TO_NEXT_STAGE GET_ESCALATION_SETTINGS RESOLVE_ROUTING _EVALUATE_ROUTING_RULES cl_grfn_msmp_instance_model update_instance_escalated
cl_grfn_msmp_instance_model check_instance_on_hold cl_grfn_msmp_instance_model update_instance_release_hold hold_by grfnmwrtinst released deadline reached date deleted enable escalation , KBA , GRC-SAC-WF , Workflow , GRC-SAC-ARQ , Access Request , How To

About this page

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

Search for additional results

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