Workitem is not completed in portal Manager inbox - URGENT

[Former Member]

Hi Gurus,

I copied the standard workflow template i.e. WS12300111.I assigned manager to APPROVAL PROCESS.

in Portal I applied the leave from the j2ee_admin it is coming into manager level we are able to approve the leave but it is not moving from manager inbox and we are not able to open it in second time, it is throughing the below java error. After that I checked in SWIA the green line upto manager it is not completing leave process.

Please can any one give me the solution it is urgent.

Thanks,

Chava Sunil

Java portal error in manager inbox.txt.zip

[paul_bakker2]

Hi,

This (standard SAP) workflow has an interesting design.

The 'Approval' step only shows you a text, asking you to go to your leave request worklist and approve the request.

The workflow then waits until it receives an event, notifiying it that the request has been processed... and that event can be POSTED, ERROR, WITHDRAWN, etc

So processing the approval workitem is not enough - you also need to go into the worklist and do the approval yourself.

Note that standard SAP workflows are usually not very good - I guess they are meant to just serve as 'inspiration' for your own workflow developments.

cheers

Paul

[Former Member]

Hi Paul,

Thanks for your reply.

we almost solved the issue by rescheduling the jobs in the clients and the background jobs are running some other client also.

Now the background job SWWERRE is running everry 20 mins but it is deleting the workitems logically.

with status is finished the job.

we are able to get the leave request into manager inbox and approve also but workflow is not completed in SWIA after approving request in portal manager inbox.

Error follows:

Job started                                                          00           516          S

Step 001 started (program RSWWERRE, variant , user ID WF-BATCH)      00           550          S

Starting Background Steps in Status "Being Processed"                00           001          S

==> 0 background steps started                                     SWF_RUN        613          S

==> 0 error(s) occurred (  > see application log)                  SWF_RUN        614          S

Starting Work Items in Status "Ready"                                00           001          S

==> 0 background steps started                                     SWF_RUN        613          S

==> 0 error(s) occurred (  > see application log)                  SWF_RUN        614          S

Logically Delete Work Items                                          00           001          S

==> 0 work items logically deleted (0 with errors)                 SWF_RUN        615          S

Repeat Callbacks                                                     00           001          S

==> 0 instances of result processing executed (0 with errors)      SWF_RUN        616          S

Repeat Callbacks                                                     00           001          S

==> 0 instances of result processing executed (0 with errors)      SWF_RUN        616          S

Repeat Callbacks                                                     00           001          S

==> 0 instances of result processing executed (0 with errors)      SWF_RUN        616          S

Repeat Callbacks                                                     00           001          S

==> 0 instances of result processing executed (0 with errors)      SWF_RUN        616          S

'0' entries have been edited                                         WL           010          S

Job finished                                                         00           517          S

Experts Any help on this ?

Thanks,

Chava

[Jocelyn_Dart]

Hi Sunil/Paul,

No that's not correct Paul - it's nothing to do with the design of the workflow, and not a reflection on the quality of this workflow, this is about the design of the overall leave request solution, which uses workflow as a delivery mechanism only.

What happens with this is you do your approval in the inbox first.  Then there is a job that should be scheduled as a regular (at least daily) background job, RPTARQPOST that actually handles the posting of the leave into the database. As the posting could be successful or could fail - e.g. there could be a clash of leave dates or personnel infotypes for those leave dates - the background job then triggers the POSTED or ERROR events.  (BTW the WITHDRAWN is only used if the employee decides to cancel the leave.)

The workflow waits until it knows if it is posted - in which case it completes - or errors - in which case it sends a work item to a HR administrator to correct the clashing infotypes manually. 

So the logical deletion of the approval work item is correct, and is nothing to do with SWWERRE - that is behaving correctly.  I suspect what you need to look at the following:

a) How and with what frequency is RPTARQPOST scheduled?

b) When you copied WS12300111 did you also copy the entries in transaction SWFVISU for the task visualizations of all the underlying TS tasks?

c) Have you made sure your copy is managing the ERROR handling process correctly - i.e. finding an administrator to send the "correct the errors" work item to.

d) Did you make sure your copied WS workflow and TS tasks are correctly listening to the relevant terminating events sent out by the RPTARQPOST job (and other parts of the leave request application)?

BTW I notice at many sites that when people copy workflows that are new to them they tend to leave out bits they don't understand. That is usually a counter-productive approach - much better to keep them in until you know exactly what they do.

Regards,

Jocelyn

[hugo_amo]

Hi Chava,

Increase the value of environment variable CPIC_MAX_CONV in ALL the servers servers of your portal system and performed a reboot of the servers after the change.

Hope this helps.

Regards,

Hugo

[Former Member]

Hi Hugo,

Thanks for your reply. We did as you said but no use still we are facing same problem.

If we execute manually in SWIA transaction the workflow is completing but still the request is in manager inbox.

I have gone through some of sap links, I came to know that we have to configure the DELTA PULL mechanism. Do you have any idea !

1) . If I see in swia transaction -> workflow log ->it is showing manager inbox after approving the request in manager inbox from portal.

2) . If execute manually the workitem then it is completing the leave request in SWIA>

Helpful answers rewarded.

Thanks,

Chava Sunil

[Former Member]

Hugo,

When I check in ST22 the run time error analysis is ::: -

Error analysis

    Short text of error message:

    Request ID   does not exist

    Long text of error message:

    Technical information about the message:

    Message class....... "HRTIM_ABS_REQ"

    Number.............. 038

    Variable 1.......... " "

    Variable 2.......... " "

    Variable 3.......... " "

    Variable 4.......... " "

Thanks,

Chava Sunil