I have a tough one for you experts out there....
We are implementing the ESS leave request iview com.sap.pct.erp.ess.leaverequestapprover in an EP7.0 system without enhancement packs. The backend system is ECC6.0. We are NOT using the UWL. The approver is using the "worklist" in the iView com.sap.pct.erp.ess.leaverequestapprover as their list to approver/reject.
Here is the scenario:
1) Leave Request Approver logs into ESS for the 1st time for the day
2) The approver opens the Leave Request: Approval iView (com.sap.pct.erp.ess.leaverequestapprover)
3) The approver is presented the "worklist" on the Leave Request: Approval iView
4) The approver sees the requests waiting for his approval
5) The hours in the USED column of the worklist are DOUBLE what they should be
6) The approver logs off and logs back into the ESS system
7) The approver opens the Leave Request: Approval iView again
8) The hours in the USED column of the worklist are now NORMAL
9) They can repeat this process multiple times during the day and the hours will be normal until the next day
I have sent an OSS message to SAP but they have not been helpful with this issue.
Has anyone seen this behavior before? Any ideas about what the root cause might be?
Some of the analysis I have done leads me to the class CA_PT_ARQ_DEDUCTION in method GET_PERSISTENT_FOR_REQUESTID. It looks like this method may be doubling the amounts due to some "persistence" data, which I am not sure how this actually works.
Any help would be appreciated,
Brian Snyder