We are currently struggling with the Leave Request Workflow on our project, and especially with what we want to do: enable the user to do a mass approval of leave requests directly from the Universal Worklist.

Let me explain the problem in separated steps:

1. For the leave request process, we use WF12300111 with the task TS12300097. When I approve a leave request via the UWL in the standard way, the portal tells me that it's approved and send.

2. I check in the employee's leave requests and the status stays at "sent" and it's not approved like it should be.

3. I check in the backend to see where the workflow goes and here is what I observe:
The workflow goes to step step 158 (request approved?) which has this condition: "&REQ.STATUS& = POSTED or &REQ.STATUS& = APPROVED or &REQ.STATUS& = ERROR". If this condition is ok, the workflow goes to the "approve" path.
I check in the container of the task and the parameter "REQ.STATUS" is well updated to "APPROVED" so it should go the 'approve' path in the workflow, but it's not the case.
The workflow follows the 'rejected' path and it seems it's coming from the agent. In fact, in the WF graphical view, it's mentionned "no agent" just beside this step 158, even though the parameter in TS12300097 for the agent is set to "&Agent_0001.Agents&" (so it should take the hierarchical chief in OM)
So, my questions are:

- Does anyone have an idea of a possible solution for that problem ?
- Do you think I should use another workflow for that leave request ? If yes, which one ?
- Is it possible to enable a mass approval for the leave request with this WF12300111, or with another one ?

And I would of course appreciate any tips and tricks on that topic !

Thanks in advance,

KR

David Fraiture

Hi,
Use this report program RPTARQPOST to update the Approved leave requests,

You have to run this report program periodically to update the Approved leave requests.

Kind Regards

Hari Sankar M

Thanks mate but actually I have already tried to run this report.

It does not work, and the "pending" leave request approved by the manager BUT not approved in the ESS are not taken in account when I run the report.

I get the result of it, and no trace about my pending leave requests....

Any other idea ?

Thanks in advance,

David

Can you check if the Workitem status remains SENT even
in the WF log using SWIA or SWI1.

It should have the changed the status if it is approved
Make sure you have not done any changes to Transition table can be accessed via PTARQ.

Make sure you have activated jobs in SWU3 for background
evaluation, this can have affect

Also For mass approval like timesheet this is not possible as Leave requests are grouped togather and individually Approved

FOr this you need to be using a Modification to the WF!

About the Agents, Please read the Note 779075.

This is the only Standard WF available for leave request

Guys,

First thanks for your comments. Actually I found a part of my problem : why the process did not reach the manager. It was a setting problem in my UWL that disturbed .

Now, I still would like to enable the universal worklist to mass approve leave requests but actually I don't know if it's feasible.

What I've done and tested:

In the container of the workitem, when a leave request is approved, the attribute "STATUS" contained in the _Wi_Object_ID is updated to "APPROVED".

To enable the mass approval, in my XML file, I've added two additional columns: one with an approve checkbox and the other one with a reject checkbox.

Behind those checkbox button, I've defined "actions" that try to update the parameter "STATUS" of the attribute "_Wi_Object_ID".

The fact is, when I approve for example with my custom view, it sends and adds a parameter in the back end but actually it does not reach the good one. The "_Wi_Object_ID STATUS" parameter is equal to "SEND" and I've a new parameter in my container

Examples:












With this value as "property name", when I approve, the container get a new line with "STATUS = APPROVE". And on the other hand, my ""_Wi_Object_ID STATUS" is equal to send.

If I put the value "_Wi_Object_ID.STATUS" in my XML file as "Property name", I get a new line in my container with ""_Wi_Object_ID.STATUS" = approved, but the right parameter I have to update stays to "SEND" !

To summarize, I need to find the way to update the good parameter in the container, via my XML configuration file of the UWL.

I hope it's clear because, actually, the problem is not easy to explain :-)

Thanks in advance for your help,

David

David, how did you resolve the issue with UWL not sending the work item to the manager?

Thanks,
Tiberiu

Hi,

It's not resolved yet actually.

David

Mass approval of these leave workitems is very much possible

Please have a look at report RPTARQAPP .
This report will give u a list of pending approvals for a manager.
U can copy the code and use it in a BAPI, Create a new simple
WD application to list out all the pending requests..
Then whats left ... approve... Thats very simple..call following code..

CALL METHOD cl_pt_req_badi=>initiate_state_transition
EXPORTING
im_request = request
im_event = event
IM_RET_VALUE = 0
IMPORTING
ex_new_status = me->status.

where status = 'APPROVED'.

U can develop a simple web dynpro application using this code..
its easy and u can give multiple approvals option also called as MASS APPROVAL.
create a select all button and select All and approve dats it.

U should be ready for development for this... its simple and easy ...
no JDI no importing of ESS MSS business package.. easy to maintain code!!

Cheers!!
SJ

David:

I have the same issue. Did you resolve this?

I am implementing UWL mass approval for leave requests.

After pressing "Submit Decisions", the tasks drop off the manager's Inbox. a success message appears and the workflow completes with the Workflow Container displaying my updated values -- _WI_RESULT = "A" and _RESULT = "A". This is accomplished in the XML using handler="UpdatingContainerHandler". When I log on as the employee, the leave request has a status of "SENT" (which I see in the container also) and the quota total does not reflect the approved leave request.

In addition, updating the parameter _Wi_Object_Id-Status = "Approved" had no effect on the issue.

For the "Submit Decisions" to work properly, are more container parameters\values required in addition
to _WI_RESULT and _RESULT? Or does this require changes to the backend WF?

Can you share your solution with us?

Thanks,
john