Setting work item as obsolete

[Former Member]

Hi Experts,

We are using modeled deadline monitoring. We are setting the " Workitem to obsolete" in the process control step.

Does this imply that the approver will not be able to execute the work item once it crosses it deadline.

In case of repeated deadline monitoring, what do we need to do.

Could you kindly guide us on the same.

Cheers,

Belinda Clarke

[Former Member]

Hi,

"Workitem to obsolete" means technically the work item cannot be processed again and will be unusable...

however you can create a new workitem similar to the old(deleted) one to the same/different user by using your logic in workflow...

What is your exact scenario here ?

Regards

Gautam

Edited by: gautam maini on Oct 18, 2011 11:49 AM

[Former Member]

Hi Gautam,

Thanks for your response.

We are basically using a leave request wf using WS12300111.

In the Approval Process step TS12300097, we are using this deadline monitoring step. They want the Approver to get the email in his outlook every 30 minutes if he has not taken an action on it.

We had set up the deadline monitoring process by seeing this document : [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00e47216-ce95-2e10-cf8f-f861e9a25aa2?quicklink=index&overridelayout=true]

In this they had set the same to obsolete.

Now i want to know that the user should be getting the mail notification in his outlook every 30 mins. What should be the status be displayed as instead of obsolete.

In case of having repeated messages coming every 30 mins, what do we need to do.

Kindly guide us.

Cheers,

Belinda Clarke

[Former Member]

Hi,

That sounds strange "notifications every 30 mins"...

You can use a fork having 2 branches... 1 having the approval step and the other having a loop using status change and a mail step for your reminder mails... you will have to implement 30 mins logc as well here...

I think this should help...

Regards

Gautam

[Former Member]

Hi Gautam,

Thanks for your response.

You have specified Loop using status change in the second branch.....what i wanted to know whether is it necessary to validate whether the work item was processed in the second branch.

Correct me if i am wrong....the concept of using a FORK is to have 2 activities running in parallel. Let us say that we have the first branch having the approval process and the second branch is having the loop using status change.

In the second branch, if we create a DUMMY method and set a deadline to it as 1 day. Let us set a container variable say lv_deadline as 'X' in the DUMMY method. Below that we put in a send mail step that sends the mail to the approver. This happens inside a loop in which we set the condition as Loop until lv_deadline = X.

Now in the case of FORK, these two activities will be running in parallel. The second branch will run after 1 day. If the work item is processed in the first branch, the control will go to the step after the FORK.

Is my understanding correct....do we need to validate in the second branch whether the work item was processed.

Kindly advice.

Regards,

Belinda Clarke

[Former Member]

Hi,

Assign the dead line monitor approval task inside loop, the logic given below

loop var = '20/30/40'

check approve = 'X'.

True

set var = '20/20/40'

False

Repeat the approval task

endloop

Hope This Helps,

Srini.