KMC_WF_SUBSTITUTE and HRUS_D2 relation: Issues in "Take Over"

Question

Hello All,
User B  is getting an error while taking over tasks for a "Fill in for me" from User A,A1,A2.
The end users A,A1,A2 has set user B to be the "Fill in for me" using the RMPS_SET_SUBSTITUTE report in ECC.
When the user B navidates to Portal UWL --> Manage Substitution Rules" and tries to  "Take Over" the tasks, he gets an error of "Duplicate key exception, Error returned from Provider".
If i look at the HRUS_D2 table, the 4 entries are as below for User B
HRUS_D2 Table Starts,
MANDT US_NAME      REP_NAME     BEGDA       ENDDA        REPPR          ACTIVE
100       User A           User B            01.07.2011 31.12.9999       
100       User A1         User B            01.07.2011 31.12.9999       
100       User A2         User B            01.07.2011 31.12.9999       
The above 3 entries indicate a "Fill in for me " from Users A,A1,A2 to User B
100       User B           User A3         01.07.2011 31.12.9999       
The above entry indicates that User B has set User A3 as "fill in for me"
HRUS_D2 Table Ends
KMC_WF_SUBSTITUTE Table starts  for User B
AUSER  SUBSTITUTE   PROFILE                         START_DATE      END_DATE       MODE ASTATE
User B  User A4           DEFAULT_ALL_TASKS 2011-06-01                                   S        0
KMC_WF_SUBSTITUTE Table ends
Appreciate if any one can provide insights in to this issue.
-PN

Answer 1

Hello Karri,
Thanks for the reply. I did check for the circumstances in which this error occurs. It occurs for all tasks which are substituted to this user B. Even when the assignor tries to assign task ( Fill in for me) through "Manage Substitution Rules" in UWL for "All Tasks" to this user id , it does not allow the rule to be set . It however does  allow for some other user id for "All Tasks"
It however does allow substitute assignment from RMPS_SET_SUBSTITUTE for the same user id and can see the "Take Over" in UWL.But when the user B tries to "take Over" , it throws the same error.
There seems to be no errors in default trace other than the "Duplicate Key exception" for this user B.
Looks to me like some data problem in tables KMC_WF_SUSBTITUTE/HRUS_D2 for this specific user id.
-PN