User Unable to Cancel/Delete GRC Access Request? Here’s How to Handle It Like a Pro! 💡
Ever faced a situation where a user says —
“I can’t cancel or delete my GRC access request!” 😩
No worries — let’s fix it step by step 👇
⚙️ Why It Happens:
🔸 Request is already in progress in the approval workflow.
🔸 The user doesn’t have proper action rights.
🔸 Or the workflow path doesn’t allow cancellation.
🧭 How to Use – Step-by-Step Fix:
✅ 1️⃣ Check Request Path and Status
🔍 Go to table GRFNMWRTINST or use Tcode: GRFNMW_DBGMONITOR
→ Verify the workflow path, stage, and request status.
✅ 2️⃣ Use “Request Abort” Option
💥 If the request is stuck or user unable to cancel →
Use the “Abort Request” feature from GRFNMW_DBGMONITOR to stop it safely (avoids inconsistencies).
✅ 3️⃣ Validate MSMP Configuration
🛠️ Check if “Requester can cancel” is enabled in MSMP configuration under workflow path setup.
✅ 4️⃣ Update GRC Roles (if needed)
🔐 Ensure the requester’s role includes action CANCEL_REQUEST or ABORT_REQUEST in GRAC_ACTIONS.
💡 Pro Tip:
Always abort requests from the backend (not by deletion) — this keeps workflow logs clean and ensures audit traceability ✅