Why Workitem is lying in SWI1 instead of SBWP??

Tue Jan 12 00:46:44 EST 2010

Hi Friends,

I am also facing the same issue in our sandbox system. When WF is tested
manually, I can verify that agent is determined properly - from SWI1,
however the same is not available in user's Inbox.

Can anybody pls suggest what might be the issue?

Regards,

Akshay Bhagwat

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Gambier
Sent: Wednesday, January 06, 2010 4:48 PM
To: sap-wug at mit.edu
Subject: RE: Why Workitem is lying in SWI1 instead of SBWP??

Hi,

Work Items don't 'move' from SWI1 to SBWP per se, so I think maybe
you've confused yourself here. 

The status of the Work Item can sometimes 'hide' it from users Inboxes,
e.g. WAITING (Deadline), but typically there's a good reason why an
agent can't see a particular WI. And often it's something obvious if you
go look...

By the sounds of it you're more concerned about the visibility and
routing of the Work Item to any agents or perhaps to the specific agents
you expected it to be routed to.

There are lots of ways to ascertain whether a Work Item should be
visible to agents. Indeed, SWI1 gives you menu options to do this. I'd
probably start there if I were you.

The underlying tables can also be helpful if you have the WI ID to hand
(SWWORGTASK and SWWUSERWI).

If the Task is a General one it is probable that you've employed an
Agent Determination Rule (PFAC) or some kind of restriction somehwere,
perhaps at the node level in the WF Template, so that it isn't sent to
everyone.

If you're trying to test the routing of a Work Item and want to 'see' it
in your own SBWP session make sure you are listed as a possible agent
yourself, i.e. ensure your HR Org Assignments or Task assignments are
valid for the WI.

Mike GT

________________________________

Subject: RE: Why Workitem is lying in SWI1 instead of SBWP??
Date: Wed, 6 Jan 2010 16:26:15 +0530
From: venkat.prasad at wipro.com
To: sap-wug at mit.edu; sap-wug at mit.edu

Hello Srinivas,

                           There could be scenarios where a Work Item is
stuck in "STARTED" Status in SWI1 due to system issues. What you can do
is, check the Workflow Definition and try to Complete the Work Item
manually from SWI1.

Thanks,

Venkat Phani Prasad K

________________________________

From: sap-wug-bounces at mit.edu on behalf of srinivas
Sent: Wed 1/6/2010 2:39 PM
To: SAP Workflow Users' Group
Subject: Re: Why Workitem is lying in SWI1 instead of SBWP??

Hi Akshay,

It is general task.

On Wed, Jan 6, 2010 at 2:25 PM, <akshay.bhagwat at wipro.com> wrote:

Pls check your agent assignments to task.

Regards,

Akshay Bhagwat

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of srinivas
Sent: Wednesday, January 06, 2010 2:06 PM
To: SAP Workflow Users' Group
Subject: Why Workitem is lying in SWI1 instead of SBWP??

Hi Experts

Firstly a very happy new year 2010 to all of you and your families.

I have created a workflow template which will be triggered from an event
material create.After the material is created as per the business
process a workitem need to be generated to the level up manager.The
probelm is the workitem getting generated but it is lying in SWI1 not
moving to SBWP.Please let me know what needs to be done to move the
workitem to SBWP??Thanks in advance.

-- 
SRINIVAS REDDY OOTA
SAP Technical Consultant
srinivas.oota at hp.com
+919246647077

Please do not print this email unless it is absolutely necessary. 
The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email. 
www.wipro.com <http://www.wipro.com/>  

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-- 
SRINIVAS REDDY OOTA
SAP Technical Consultant
GDAS
srinivas.oota at eds.com
srinivas.oota at hp.com
+919246647077

Please do not print this email unless it is absolutely necessary. 
The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email. 
www.wipro.com 

________________________________

Add other email accounts to Hotmail in 3 easy steps. Find out how.
<http://clk.atdmt.com/UKM/go/186394593/direct/01/%20> 

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100112/c24e50ab/attachment.htm