on 05-15-2008 5:15 PM
Dear all,
I am encountering a problem in Leave Workflow. Here the Workflow is 3 level .
If any Employee applies leave form ESS Leave request task will go1st leave of Approver .If he/ she approves the Leave it ill updated in IT2001 else if this 1st leave of approver has not taken any on action for 2 working days that leave request will move to 2nd level of approver once he/she approves it will update in IT2001 else if this 2nd leave of approver has not taken any on action for 2 working days that leave request will move to HR and Hr should Updated.
Here the Problem is the Leave request task is moving from 1st level approver Inbox to 2nd level approver Inbox after 2 working days but, when we check the Pending leave requests with 1st leave approver using the Report "RPTARQAPP" still the request is laying with him.
Please help me solve these issues.
Hi Sai
I am new to ESS, can you please let me knw. how can we restrict leave approving authority to not to approve leave if its pending from more than 30 days.
Regards,
Aman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
are you using deadline monitoring to move the request to second approver if the first approver doesn't take any action for 2 days?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i am deleting the worktiem form the 1st approver once deadline is reached in mean time when any other employee raise a leave request
if it send to same approver when that approver is trying to approve new request when he click the worktem in UWL new request a window will open with list of leave request pending with him in that list the request which is allready moved form his inbox is also appearing.
you are using an application that shows you the request that is there in the application table.
The problem you are facing is that your first workitem is not getting deleted logically and because of that this reference is there in the leave approval application.
Canyou please confirm if you are using deadline monitoring only.
Could you please explain how have you created the steps in the workflow please for mutlitple approvals.
I need to know the sequencing of steps to analyse the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am encountering a problem in Leave Workflow. Here the Workflow is 3 levels.
1. Employee Applies for Leave in ESS
2. Leave request goes to 1st leave approver
3. If it is approved it will update Infotype 2001
4. If the Approver did not act on the request for 2 working days, request will be forwarded to the 2nd approver
5. If it is approved it will update Infotype 2001
6. If the Approver did not act on the request for 2 working days, request will be forwarded to the HR
7. HR should update Infotype 2001
we made a copy of the standard leave workflow
made changes in the workflow so that the work item to send to 2nd approver if 1st level of approver has not acted for 2 working days .
Basically we have added a rule in the approval process step which calculates the 2nd level approver also.
Now the work item goes to the next approver and the new approver is able to see the work item in his inbox.
Here the Problem is
the Leave request task is moving from 1st level approver Inbox to 2nd level approver Inbox after 2 working days
but, when we check the Pending leave requests with 1st leave approver and 2nd level approver using the Report "RPTARQAPP" for both of them
it is showing pending with them.
This is becoz, when i see the workflow container log from the sender's outbox,
the table REQ->N_PROCESSOR still shows the 1st manager details(instead of the 2nd approver details).
So the work item details are stored in the PTREQ_HEADER table with the actor id of the old line manager details.
That is why even though the new approver is getting the work item, same request is also showing for 1st level approver.
When 1st level approver click an other leave work item a screen with list request pending with him will apiaries in that request which is moved to next level also appearing. (as it tries to search the PTREQ_HEADER table with the pending actor id with him .
How can we solve this, Please give your valuable inputs on this...
Please help me solve these issues.
Kindly advice
You need to check the agent or check the tables of the leave request ie starting with Ptreq*
PTREQ_ATTABSDATA
PTRQ_ITEMS
PTREQ_ITEMS and PTREQ_HEADER
Also check the WF log in swia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Here the Problem is the Leave request task is moving from 1st level approver Inbox to 2nd level approver Inbox after 2 working days but, when we check the Pending leave requests using the Report "RPTARQAPP" this report is showing pending with both the approvers, but i want we the task is moving from one level to next leave along with that request should move , but it`s not happening ,can you help me in these..
Hi Sai kumar,
I gone through your question regarding second level approver is getting the leave request but leave request is still lying with first level manager.
We are also facing the same problem. In our case the leave request gone to first Manager and after his approval it has gone for HOD approval but the same request shows up in first Manager's leave request iview. The moment HOD approves the request it get disappeared from Manager's leave iview too. On the other hand if first level Manager approves the request which is still lying in his iview then it gets approved without going to HOD.
Can you please share the solution with us.
Thanks
Venkat
When you move the leave request, Are you also updating the approver field of the Leave request in tables so that the new approver is reflected everywhere?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
104 | |
9 | |
6 | |
6 | |
5 | |
5 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.