GRC-AC 5.3 RAR Management view error - Expired users not cleaned-up.

Question

Hello Gurus,
I have a problem in RAR Management View:  Users who was valid have been analyzed and their conflicts considered in statistics, but when they become expired, their conflicts remain in the statistics forever, because they are not re-analyzed neither in Full nor in Incremental sync.    Even if all roles are removed from the user in backend, the conflicts remain in Management View.
I think the Full Batch Risk Analysis should clean-up all users violations from current period statistics before recording the new analysis results. 
Did you have this problem too?  Am I missing something? 
I appreciate your thoughts about it.
Vaner

Answer 1

Hello Nuno,
Thanks for your comments.
My release is 5.3 SP 16.2.
I also think the full sync should be enough but I already find about 20 users with problems, in 4 different backend and in 2 GRC (Tests and Production)
I think that depending on some procedures done in the back-end the full sync do neither re-analyze the user nor clean-up previuos statistics, for example:
1. A user was delete and recreated again with option to maintain old data, and he already had expiration date.
2. A sand-box environment was created as copy of production, users were created valid but already with expiration date.
I observed that for these scenarios, there was no Change Document for field "valid to", my guess is that Full Sync process relies on Change Documents to do its job.
I already opened a message in SAP for this, first level could not solve it, It is in Development Team now.
Vaner