Deadline Monitoring Scenario

[Maue, Thomas]

Tom,

 

That is correct although annoying.  UWL is designed to work only with
the workitems in the folder "Workplace - Inbox".  Items in other
sub-folders (deadlines) are not displayed in the UWL.  Solution is to
create modeled deadlines but then you have a different workitem (same
task).  Another workitem means a delay in seeing it on the Portal side
even with the refresh functionality.  I am doing the same thing right
now and obsolete the original workitem.

 

My next step is to try the special Workflow header level event
"Reevaluate rules on active work items".

 

Thanks,

Thomas

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Simon, Tom
Sent: Wednesday, November 05, 2008 7:32 AM
To: sap-wug at mit.edu
Subject: Re: Deadline Monitoring Scenario

 

Thomas,

             I am using the UWL in the Portal.  After testing the
deadline with a text only option, these deadline messages do not show up
in the UWL. They do show up in R3.   A modeled deadline is the only way
to execute a step that would create a workitem for an agent and get
pulled into the UWL.  I am trying to find a way to send the same
workitem that has a deadline executed to the superior of the agent who
was supposed to execute the original workitem.   

 

 

Tom,

 

There are multiple ways to handle this.  One simple way is to choose the
deadline tab of your choice, do not model the deadline and you will see
a 'Recipient of message when latest end missed'.  You can put a rule in
here to find the 2nd level or use an expression if the approval agents
are captured already.

 

In this case you are correct that once one selects, the workitem is
removed from the other's work list.

 

Regards,

Thomas Maue

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Simon, Tom
Sent: Tuesday, November 04, 2008 7:39 AM
To: sap-wug at mit.edu
Subject: Re: Deadline Monitoring Scenario

 

Shai,

        Thank you for the help with the determining the next level agent
for a deadline monitoring scenario.  I created a rule as you suggested ,
using a "z" version of function module SWX_GET_MANAGER.  I modifed the
source code to repeat getting the immediate superior, first for the
initiator, then for the initators superior.

This rule  works in obtaining the next level manager. 

 I have another question on the deadline scenario.  The requirements are
that the 2nd level approver receives the approval task if the 1st level
approver does not complete the workitem.  Is it possible to send the
same workitem to this 2nd level approver when the deadline has passed
or do I have to execute a new approver step using the same task senario
that was used for the 1st level approver.  The reason I am asking is
that if I there is a way to send the same workitem to the second level
approver after the deadline has passed I assume that when either
approver selects the workitem it should be removed from the other
approvers worklist.  Otherwise,  I am creating a new workitem for the
second approver and must decide to obsolete the original workitem in the
1st approvers worklist.  If I didn't obsolete the original workitem it
appears to me that I would then have two different workitems out there
waiting to be completed by two different agents?  What do you think? 

 Tom 

 




-----------------------------------------
This transmission is intended only for use by the intended
recipient(s). If you are not an intended recipient you should not
read, disclose, copy, circulate or in any other way use the
information contained in this transmission. The information
contained in this transmission may be confidential and/or
privileged. If you have received this transmission in error, please
notify the sender immediately and delete this transmission
including any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20081105/75ecce5b/attachment.htm