<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body><BR >Hi All, <BR><FONT face=Arial size=3 >
Hi, <BR>
In workflow the loop never stops. The condition for ending the loop are the standard one CurrentAgents NX AND Approval status = 0 OR Approval status <> 0 .<BR>
When there is a rejection this is working fine the workflow stops<BR>
After the final approver of the workflow has approved , in the step called Determine next approver, the actualAgents table is not updated and the <FONT class="">No_further_<FONT class="">approval</FONT>_needed</FONT> is not updated either.<BR>
Behind this step is task TS14007989, BUS4101 with method NEXTDYNAMICAPPROVERGET. All the binding seems correct.<BR>
When testing the Method directly the result is the same as within the workflow ( ActualAgent is not correct and No_further_<FONT class="">approval</FONT> is not set)<BR>
It seems to be coming from Function BBP_WFL_DIN_APPR_CONTAINER_<FONT class="">GET</FONT> where the approvallist-state = 2 for the last approver.<BR>
(Code: * get the list of dynamic approvers from wi-container<BR>
swf_<FONT class="">get_element</FONT> ev_wi_container_handle c_wf_appr_list lt_cont_<FONT class="">approver</FONT>.)<BR>
While testing the BADI function directly the no_further_<FONT class="">approval</FONT> flag is present<BR>
<BR>
Can someone help me to determine why this method is not returning the right value or why the approval state of my last approver is set at 2 ?<BR>
</FONT> <BR>
Our version is SRM 4.0 with support package applied is SAPKIBKS08<BR>
<BR ><BR >Thanks for your help <BR>
Stephane Bailleul<BR ><BR ><BR>
<HR id=stopSpelling>
<BR>
> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 18, Issue 74<BR>> To: sap-wug@mit.edu<BR>> Date: Thu, 18 May 2006 10:01:10 -0400<BR>> <BR>> Send SAP-WUG mailing list submissions to<BR>> sap-wug@mit.edu<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> or, via email, send a message with subject or body 'help' to<BR>> sap-wug-request@mit.edu<BR>> <BR>> You can reach the person managing the list at<BR>> sap-wug-owner@mit.edu<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of SAP-WUG digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. RE: Multiple agents per one work item in workflow<BR>> (Gardiner, Keith (CIS))<BR>> 2. RE: Multiple agents per one work item in workflow (May, Kevin)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Thu, 18 May 2006 14:51:37 +0100<BR>> From: "Gardiner, Keith \(CIS\)" <Keith.Gardiner@capita.co.uk><BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <B3064554D1913D46B23FF838ECEAD2370416549F@CISCHEEV01.central.ad.capita.co.uk><BR>> <BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> HI Kevin,<BR>> <BR>> Forgive my ignorance of your particular application, but why do you need<BR>> a terminating event on the task? If your workflow has n parallel paths<BR>> and each has to be completed before the workflow is complete I don't see<BR>> the need for a terminating event but that be due to my ignorance.<BR>> <BR>> <BR>> Regards<BR>> <BR>> Keith Gardiner<BR>> <BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of May, Kevin<BR>> Sent: 18 May 2006 14:43<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> <BR>> Hi Dave, I'm not exactly sure what you mean. The BSP raises an event<BR>> which is used as a terminating event for the task. If I raise this<BR>> event independently of the BSP I get the same result. I have a feeling<BR>> that because the object key does not include the work item id when the<BR>> event is raised it ignores the work item id and terminates the work item<BR>> regardless of the various ids. I've tried incorporating the work item<BR>> id into the object key which prevents them from all being terminated but<BR>> then the item hangs with the status 'STARTED'.<BR>> <BR>> Kevin<BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Dave Weston<BR>> Sent: Wednesday, May 17, 2006 4:55 PM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> <BR>> <BR>> Was just wondering, for the BSP are you using the dialog based service<BR>> with callback or w/o callback in trans wf_extsrv. If its with callback<BR>> is the bsp referencing work item id in the method call ?<BR>> <BR>> Dave <BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Gavin Mooney<BR>> Sent: Wednesday, May 17, 2006 4:21 PM<BR>> To: SAP Workflow Users' Group<BR>> Subject: Re: Multiple agents per one work item in workflow<BR>> <BR>> I wonder if the terminating event could be it. When you look in the log<BR>> (the tecnical one) it should show that the 'n' work items have all been<BR>> completed and if you expand the little tree it should show you who<BR>> completed them....So maybe in your case it shows that person 'x'<BR>> completed all the work items, or that the terminating event was raised<BR>> for all of the work items.<BR>> <BR>> Just a shot in the dark - how about turning on the "Confirm end of<BR>> processing" option on the task? Then it shouldn't disappear from the<BR>> inboxes automatically....<BR>> <BR>> - Gavin<BR>> <BR>> 2006/5/17, May, Kevin <KMay@petro-canada.ca>:<BR>> > Hi Gavin, OK here's the situation. I've got a step in a workflow <BR>> > which is has a multiline element called 'REVIEWERS'. 'REVIEWERS'<BR>> > contains a list of 'n' amount of R/3 user ids, lets say for example 3.<BR>> <BR>> > In the agent assignemnent of the step I have <BR>> > '&REVIEWERS[&_WF_PARFOREACH_INDEX&]&', in the 'Other' tab of the step <BR>> > I have 'REVIEWERS' in place. When the step executes it sends off the <BR>> > same work item to each of the 3 agents. Each instance of the work <BR>> > item has its own work item id, as expeected. The task assigned to the<BR>> <BR>> > step contains a call to a custom method of a custom object. This <BR>> > method calls a BSP. From the BSP the user is able to complete their <BR>> > task which is done by raising a custom event 'REVIEWED' from the same <BR>> > object. This event is a terminating event of the task. I think this <BR>> > is where the problem lies because the element is '_WI_OBJECT_ID'<BR>> instead of the work<BR>> > item id. What I need is for the work item to be completed by all<BR>> > designated agents before continuing to the next step. What do you <BR>> > think?<BR>> ><BR>> > Thanks much,<BR>> ><BR>> > Kevin<BR>> ><BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > Behalf Of Gavin Mooney<BR>> > Sent: Wednesday, May 17, 2006 3:19 PM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: Re: Multiple agents per one work item in workflow<BR>> ><BR>> ><BR>> > Kevin,<BR>> ><BR>> > This definitely IS possible without using a sub-workflow, I have a <BR>> > workflow in front of me that does it. What you described sounds <BR>> > exactly right.<BR>> ><BR>> > When you look in the workflow log, is a separate work item (i.e. a <BR>> > separate line in the log) being generated for each of the entries in <BR>> > the table of user IDs? The common problem is that several work items <BR>> > are generated, all of which go to several users. In your case I'm not <BR>> > clear on what is happening - it sounds like only one work item is <BR>> > being created and it being sent to multiple users. You could always <BR>> > try the old trick of removing the step and then putting it in<BR>> again.....<BR>> ><BR>> > Regards,<BR>> > Gavin<BR>> ><BR>> > 2006/5/17, May, Kevin <KMay@petro-canada.ca>:<BR>> > ><BR>> > ><BR>> > > Thanks, to you both. It's unfortunate because it looked like I had <BR>> > > multiple agents for the same work item but each had their own work <BR>> > > item id. It was so close and it seems like such a simple thing.<BR>> > > What's worse is that the 'Practical Workflow for SAP' book simply <BR>> > > says<BR>> ><BR>> > > in order to achieve this put the multiline element in the 'Other'<BR>> > > tab and then place the mulitiline element index in the agent <BR>> > > assignment of<BR>> ><BR>> > > the step and off you go.<BR>> > ><BR>> > > Thanks again,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > > Behalf Of Dave Weston<BR>> > > Sent: Wednesday, May 17, 2006 1:31 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > > Yes there has to be a sub workflow, with the task/step in the <BR>> > > subworkflow. I did this last year and it must be in a subworkflow, <BR>> > > especially if you want to return any check/approval results back to <BR>> > > the main flow.<BR>> > ><BR>> > > Dave<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > > Behalf Of Adao-Cruz, Miguel<BR>> > > Sent: Wednesday, May 17, 2006 12:00 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi,<BR>> > ><BR>> > > I went through the same problem some projects ago but I don't <BR>> > > remember<BR>> ><BR>> > > how I solved it. If your step where you put the mutiline element is <BR>> > > a task, try to put this task in a sub-workflow and do the same <BR>> > > settings at the sub-workflow level. It might solve the problem.<BR>> > ><BR>> > > Cheers<BR>> > ><BR>> > ><BR>> > ><BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > > Miguel Adao-Cruz | Capgemini | London Technology Services SAP <BR>> > > Application Architect<BR>> > ><BR>> > > T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com<BR>> > ><BR>> > > Join the Collaborative Business Experience <BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu on behalf of May, Kevin<BR>> > > Sent: Wed 17/05/2006 16:41<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi Miguel, the step is creating one workitem with multiple workitem <BR>> > > ids being sent uniquely to each agent identified in the multiline <BR>> > > element. This is working as I would expect dynamic parallel <BR>> > > processing to work. However when the first agent reserves the <BR>> > > workitem it is then removed from all other agents. I thought that <BR>> > > using the 'Other' tab would prevent this from happening.<BR>> > ><BR>> > > Thanks,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > > Behalf Of Adao-Cruz, Miguel<BR>> > > Sent: Wednesday, May 17, 2006 11:34 AM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi,<BR>> > ><BR>> > > You say "the workitem"! Is your workflow creating multiple workitems<BR>> <BR>> > > with one reviewer each time or ONE workitem with all the reviewers?<BR>> > ><BR>> > > Cheers<BR>> > ><BR>> > ><BR>> > ><BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > > Miguel Adao-Cruz | Capgemini | London Technology Services SAP <BR>> > > Application Architect<BR>> > ><BR>> > > T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com<BR>> > ><BR>> > > Join the Collaborative Business Experience <BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu on behalf of May, Kevin<BR>> > > Sent: Wed 17/05/2006 16:12<BR>> > > To: sap-wug@mit.edu<BR>> > > Subject: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi, I've got a workflow multiline element which contains user id's. <BR>> > > Currently all the agents in the multiline element are being sent the<BR>> <BR>> > > workitem, however the first agent to execute the workitem removes it<BR>> <BR>> > > from the other agent's inboxes. I've got the multiline element in <BR>> > > the 'Other' tab of the step and I've tried using the multiline <BR>> > > element index in the agent assignment of the step, i.e.<BR>> > > '&REVIEWERS[&_WF_PARFOREACH_INDEX&]&'. What am I forgetting?<BR>> > ><BR>> > > Thanks in advance,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > > ________________________________<BR>> > ><BR>> > ><BR>> > > This email communication is intended as a private communication for <BR>> > > the sole use of the primary addressee and those individuals listed <BR>> > > for<BR>> ><BR>> > > copies in the original message. The information contained in this <BR>> > > email is private and confidential and If you are not an intended <BR>> > > recipient you are hereby notified that copying, forwarding or other <BR>> > > dissemination or distribution of this communication by any means is <BR>> > > prohibited. If you are not specifically authorized to receive this <BR>> > > email and if you believe that you received it in error please notify<BR>> <BR>> > > the original sender immediately. We honour similar requests <BR>> > > relating to the privacy of email communications.<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Cette communication par courrier lectronique est une communication <BR>> > > priv e l'usage exclusif du destinataire principal ainsi que des <BR>> > > personnes<BR>> > dont les<BR>> > > noms figurent en copie. Les renseignements contenus dans ce <BR>> > > courriel<BR>> > sont<BR>> > > confidentiels et si vous n' tes pas le destinataire pr vu, vous tes<BR>> > avis ,<BR>> > > par les pr sentes que toute reproduction, transfert ou autre forme <BR>> > > de diffusion de cette communication par quelque moyen que ce soit<BR>> est<BR>> > > interdite. Si vous n' tes pas sp cifiquement autoris recevoir ce<BR>> > > courriel ou si vous croyez l'avoir re u par erreur, veuillez en <BR>> > > aviser l'exp diteur original imm diatement. Nous respectons les <BR>> > > demandes similaires qui touchent la confidentialit des <BR>> > > communications par<BR>> > courrier<BR>> > > lectronique. _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu<BR>> > > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > ><BR>> > ><BR>> ><BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> > --------------------------------------------------------<BR>> ><BR>> ><BR>> > This email communication is intended as a private communication for<BR>> the sole use of the primary addressee and those individuals listed for<BR>> copies in the original message. The information contained in this email<BR>> is private and confidential and If you are not an intended recipient you<BR>> are hereby notified that copying, forwarding or other dissemination or<BR>> distribution of this communication by any means is prohibited. If you<BR>> are not specifically authorized to receive this email and if you believe<BR>> that you received it in error please notify the original sender<BR>> immediately. We honour similar requests relating to the privacy of<BR>> email communications.<BR>> ><BR>> > Cette communication par courrier electronique est une communication<BR>> privee a l'usage exclusif du destinataire principal ainsi que des<BR>> personnes dont les noms figurent en copie. Les renseignements contenus<BR>> dans ce courriel sont confidentiels et si vous n'etes pas le<BR>> destinataire prevu, vous etes avise, par les presentes que toute<BR>> reproduction, transfert ou autre forme de diffusion de cette<BR>> communication par quelque moyen que ce soit est interdite. Si vous<BR>> n'etes pas specifiquement autorise a recevoir ce courriel ou si vous<BR>> croyez l'avoir recu par erreur, veuillez en aviser l'expediteur original<BR>> immediatement. Nous respectons les demandes similaires qui touchent la<BR>> confidentialite des communications par courrier electronique.<BR>> ><BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> --------------------------------------------------------<BR>> <BR>> <BR>> This email communication is intended as a private communication for the<BR>> sole use of the primary addressee and those individuals listed for<BR>> copies in the original message. The information contained in this email<BR>> is private and confidential and If you are not an intended recipient you<BR>> are hereby notified that copying, forwarding or other dissemination or<BR>> distribution of this communication by any means is prohibited. If you<BR>> are not specifically authorized to receive this email and if you believe<BR>> that you received it in error please notify the original sender<BR>> immediately. We honour similar requests relating to the privacy of<BR>> email communications.<BR>> <BR>> Cette communication par courrier electronique est une communication<BR>> privee a l'usage exclusif du destinataire principal ainsi que des<BR>> personnes dont les noms figurent en copie. Les renseignements contenus<BR>> dans ce courriel sont confidentiels et si vous n'etes pas le<BR>> destinataire prevu, vous etes avise, par les presentes que toute<BR>> reproduction, transfert ou autre forme de diffusion de cette<BR>> communication par quelque moyen que ce soit est interdite. Si vous<BR>> n'etes pas specifiquement autorise a recevoir ce courriel ou si vous<BR>> croyez l'avoir recu par erreur, veuillez en aviser l'expediteur original<BR>> immediatement. Nous respectons les demandes similaires qui touchent la<BR>> confidentialite des communications par courrier electronique.<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> This email has been scanned for all viruses by the MessageLabs SkyScan<BR>> service.<BR>> <BR>> **********************************************************************************<BR>> This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed. <BR>> If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system.<BR>> <BR>> Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.<BR>> ***********************************************************************************<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Thu, 18 May 2006 10:01:07 -0400<BR>> From: "May, Kevin" <KMay@petro-canada.ca><BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <2449B63CB6C05F419A8F871799E556AE0C312DB0@PCAM2.pcacorp.net><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Hi Keith, no it's a good question. Here's my reasoning. I believe a<BR>> terminating event for the particular task is necessary because I want to<BR>> ensure that the task is complete before continuing to the next step.<BR>> Basically what I need is the same work item to be reviewed by 'n' amount<BR>> of agents. Until either all agents have reviewed it or the deadline<BR>> monitoring is activated I don't want the workflow to continue to the<BR>> next step. I figured that using the 'REVIEWED' method as a terminating<BR>> event would afford the opportunity to expedite things should all 'n'<BR>> reviewers complete their task before the deadline monitoring takes<BR>> effect. I'm new to workflow so perhaps my understanding is thin.<BR>> <BR>> Kevin<BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Gardiner, Keith (CIS)<BR>> Sent: Thursday, May 18, 2006 9:52 AM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> <BR>> <BR>> HI Kevin,<BR>> <BR>> Forgive my ignorance of your particular application, but why do you need<BR>> a terminating event on the task? If your workflow has n parallel paths<BR>> and each has to be completed before the workflow is complete I don't see<BR>> the need for a terminating event but that be due to my ignorance.<BR>> <BR>> <BR>> Regards<BR>> <BR>> Keith Gardiner<BR>> <BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of May, Kevin<BR>> Sent: 18 May 2006 14:43<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> <BR>> Hi Dave, I'm not exactly sure what you mean. The BSP raises an event<BR>> which is used as a terminating event for the task. If I raise this<BR>> event independently of the BSP I get the same result. I have a feeling<BR>> that because the object key does not include the work item id when the<BR>> event is raised it ignores the work item id and terminates the work item<BR>> regardless of the various ids. I've tried incorporating the work item<BR>> id into the object key which prevents them from all being terminated but<BR>> then the item hangs with the status 'STARTED'.<BR>> <BR>> Kevin<BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Dave Weston<BR>> Sent: Wednesday, May 17, 2006 4:55 PM<BR>> To: SAP Workflow Users' Group<BR>> Subject: RE: Multiple agents per one work item in workflow<BR>> <BR>> <BR>> Was just wondering, for the BSP are you using the dialog based service<BR>> with callback or w/o callback in trans wf_extsrv. If its with callback<BR>> is the bsp referencing work item id in the method call ?<BR>> <BR>> Dave <BR>> <BR>> -----Original Message-----<BR>> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> Of Gavin Mooney<BR>> Sent: Wednesday, May 17, 2006 4:21 PM<BR>> To: SAP Workflow Users' Group<BR>> Subject: Re: Multiple agents per one work item in workflow<BR>> <BR>> I wonder if the terminating event could be it. When you look in the log<BR>> (the tecnical one) it should show that the 'n' work items have all been<BR>> completed and if you expand the little tree it should show you who<BR>> completed them....So maybe in your case it shows that person 'x'<BR>> completed all the work items, or that the terminating event was raised<BR>> for all of the work items.<BR>> <BR>> Just a shot in the dark - how about turning on the "Confirm end of<BR>> processing" option on the task? Then it shouldn't disappear from the<BR>> inboxes automatically....<BR>> <BR>> - Gavin<BR>> <BR>> 2006/5/17, May, Kevin <KMay@petro-canada.ca>:<BR>> > Hi Gavin, OK here's the situation. I've got a step in a workflow<BR>> > which is has a multiline element called 'REVIEWERS'. 'REVIEWERS'<BR>> > contains a list of 'n' amount of R/3 user ids, lets say for example 3.<BR>> <BR>> > In the agent assignemnent of the step I have<BR>> > '&REVIEWERS[&_WF_PARFOREACH_INDEX&]&', in the 'Other' tab of the step <BR>> > I have 'REVIEWERS' in place. When the step executes it sends off the <BR>> > same work item to each of the 3 agents. Each instance of the work <BR>> > item has its own work item id, as expeected. The task assigned to the<BR>> <BR>> > step contains a call to a custom method of a custom object. This<BR>> > method calls a BSP. From the BSP the user is able to complete their <BR>> > task which is done by raising a custom event 'REVIEWED' from the same <BR>> > object. This event is a terminating event of the task. I think this <BR>> > is where the problem lies because the element is '_WI_OBJECT_ID'<BR>> instead of the work<BR>> > item id. What I need is for the work item to be completed by all<BR>> > designated agents before continuing to the next step. What do you<BR>> > think?<BR>> ><BR>> > Thanks much,<BR>> ><BR>> > Kevin<BR>> ><BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > Behalf Of Gavin Mooney<BR>> > Sent: Wednesday, May 17, 2006 3:19 PM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: Re: Multiple agents per one work item in workflow<BR>> ><BR>> ><BR>> > Kevin,<BR>> ><BR>> > This definitely IS possible without using a sub-workflow, I have a<BR>> > workflow in front of me that does it. What you described sounds <BR>> > exactly right.<BR>> ><BR>> > When you look in the workflow log, is a separate work item (i.e. a<BR>> > separate line in the log) being generated for each of the entries in <BR>> > the table of user IDs? The common problem is that several work items <BR>> > are generated, all of which go to several users. In your case I'm not <BR>> > clear on what is happening - it sounds like only one work item is <BR>> > being created and it being sent to multiple users. You could always <BR>> > try the old trick of removing the step and then putting it in<BR>> again.....<BR>> ><BR>> > Regards,<BR>> > Gavin<BR>> ><BR>> > 2006/5/17, May, Kevin <KMay@petro-canada.ca>:<BR>> > ><BR>> > ><BR>> > > Thanks, to you both. It's unfortunate because it looked like I had<BR>> > > multiple agents for the same work item but each had their own work <BR>> > > item id. It was so close and it seems like such a simple thing.<BR>> > > What's worse is that the 'Practical Workflow for SAP' book simply <BR>> > > says<BR>> ><BR>> > > in order to achieve this put the multiline element in the 'Other' <BR>> > > tab and then place the mulitiline element index in the agent <BR>> > > assignment of<BR>> ><BR>> > > the step and off you go.<BR>> > ><BR>> > > Thanks again,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf Of Dave Weston<BR>> > > Sent: Wednesday, May 17, 2006 1:31 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > > Yes there has to be a sub workflow, with the task/step in the<BR>> > > subworkflow. I did this last year and it must be in a subworkflow, <BR>> > > especially if you want to return any check/approval results back to <BR>> > > the main flow.<BR>> > ><BR>> > > Dave<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf Of Adao-Cruz, Miguel<BR>> > > Sent: Wednesday, May 17, 2006 12:00 PM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi,<BR>> > ><BR>> > > I went through the same problem some projects ago but I don't<BR>> > > remember<BR>> ><BR>> > > how I solved it. If your step where you put the mutiline element is<BR>> > > a task, try to put this task in a sub-workflow and do the same <BR>> > > settings at the sub-workflow level. It might solve the problem.<BR>> > ><BR>> > > Cheers<BR>> > ><BR>> > ><BR>> > ><BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > > Miguel Adao-Cruz | Capgemini | London Technology Services SAP<BR>> > > Application Architect<BR>> > ><BR>> > > T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com<BR>> > ><BR>> > > Join the Collaborative Business Experience<BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu on behalf of May, Kevin<BR>> > > Sent: Wed 17/05/2006 16:41<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi Miguel, the step is creating one workitem with multiple workitem<BR>> > > ids being sent uniquely to each agent identified in the multiline <BR>> > > element. This is working as I would expect dynamic parallel <BR>> > > processing to work. However when the first agent reserves the <BR>> > > workitem it is then removed from all other agents. I thought that <BR>> > > using the 'Other' tab would prevent this from happening.<BR>> > ><BR>> > > Thanks,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > ><BR>> > > -----Original Message-----<BR>> > > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>> > > Behalf Of Adao-Cruz, Miguel<BR>> > > Sent: Wednesday, May 17, 2006 11:34 AM<BR>> > > To: SAP Workflow Users' Group<BR>> > > Subject: RE: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi,<BR>> > ><BR>> > > You say "the workitem"! Is your workflow creating multiple workitems<BR>> <BR>> > > with one reviewer each time or ONE workitem with all the reviewers?<BR>> > ><BR>> > > Cheers<BR>> > ><BR>> > ><BR>> > ><BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > > Miguel Adao-Cruz | Capgemini | London Technology Services SAP<BR>> > > Application Architect<BR>> > ><BR>> > > T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com<BR>> > ><BR>> > > Join the Collaborative Business Experience<BR>> > > ____________________________________________________________________<BR>> > > __<BR>> > > _____<BR>> > ><BR>> > > ________________________________<BR>> > > From: sap-wug-bounces@mit.edu on behalf of May, Kevin<BR>> > > Sent: Wed 17/05/2006 16:12<BR>> > > To: sap-wug@mit.edu<BR>> > > Subject: Multiple agents per one work item in workflow<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Hi, I've got a workflow multiline element which contains user id's.<BR>> > > Currently all the agents in the multiline element are being sent the<BR>> <BR>> > > workitem, however the first agent to execute the workitem removes it<BR>> <BR>> > > from the other agent's inboxes. I've got the multiline element in<BR>> > > the 'Other' tab of the step and I've tried using the multiline <BR>> > > element index in the agent assignment of the step, i.e.<BR>> > > '&REVIEWERS[&_WF_PARFOREACH_INDEX&]&'. What am I forgetting?<BR>> > ><BR>> > > Thanks in advance,<BR>> > ><BR>> > > Kevin<BR>> > ><BR>> > ><BR>> > > ________________________________<BR>> > ><BR>> > ><BR>> > > This email communication is intended as a private communication for<BR>> > > the sole use of the primary addressee and those individuals listed <BR>> > > for<BR>> ><BR>> > > copies in the original message. The information contained in this<BR>> > > email is private and confidential and If you are not an intended <BR>> > > recipient you are hereby notified that copying, forwarding or other <BR>> > > dissemination or distribution of this communication by any means is <BR>> > > prohibited. If you are not specifically authorized to receive this <BR>> > > email and if you believe that you received it in error please notify<BR>> <BR>> > > the original sender immediately. We honour similar requests<BR>> > > relating to the privacy of email communications.<BR>> > ><BR>> > ><BR>> > ><BR>> > ><BR>> > > Cette communication par courrier lectronique est une communication<BR>> > > priv e l'usage exclusif du destinataire principal ainsi que des <BR>> > > personnes<BR>> > dont les<BR>> > > noms figurent en copie. Les renseignements contenus dans ce<BR>> > > courriel<BR>> > sont<BR>> > > confidentiels et si vous n' tes pas le destinataire pr vu, vous tes<BR>> > avis ,<BR>> > > par les pr sentes que toute reproduction, transfert ou autre forme<BR>> > > de diffusion de cette communication par quelque moyen que ce soit<BR>> est<BR>> > > interdite. Si vous n' tes pas sp cifiquement autoris recevoir ce<BR>> > > courriel ou si vous croyez l'avoir re u par erreur, veuillez en<BR>> > > aviser l'exp diteur original imm diatement. Nous respectons les <BR>> > > demandes similaires qui touchent la confidentialit des <BR>> > > communications par<BR>> > courrier<BR>> > > lectronique. _______________________________________________<BR>> > > SAP-WUG mailing list<BR>> > > SAP-WUG@mit.edu http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > ><BR>> > ><BR>> > ><BR>> ><BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> > --------------------------------------------------------<BR>> ><BR>> ><BR>> > This email communication is intended as a private communication for<BR>> the sole use of the primary addressee and those individuals listed for<BR>> copies in the original message. The information contained in this email<BR>> is private and confidential and If you are not an intended recipient you<BR>> are hereby notified that copying, forwarding or other dissemination or<BR>> distribution of this communication by any means is prohibited. If you<BR>> are not specifically authorized to receive this email and if you believe<BR>> that you received it in error please notify the original sender<BR>> immediately. We honour similar requests relating to the privacy of<BR>> email communications.<BR>> ><BR>> > Cette communication par courrier electronique est une communication<BR>> privee a l'usage exclusif du destinataire principal ainsi que des<BR>> personnes dont les noms figurent en copie. Les renseignements contenus<BR>> dans ce courriel sont confidentiels et si vous n'etes pas le<BR>> destinataire prevu, vous etes avise, par les presentes que toute<BR>> reproduction, transfert ou autre forme de diffusion de cette<BR>> communication par quelque moyen que ce soit est interdite. Si vous<BR>> n'etes pas specifiquement autorise a recevoir ce courriel ou si vous<BR>> croyez l'avoir recu par erreur, veuillez en aviser l'expediteur original<BR>> immediatement. Nous respectons les demandes similaires qui touchent la<BR>> confidentialite des communications par courrier electronique.<BR>> ><BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> --------------------------------------------------------<BR>> <BR>> <BR>> This email communication is intended as a private communication for the<BR>> sole use of the primary addressee and those individuals listed for<BR>> copies in the original message. The information contained in this email<BR>> is private and confidential and If you are not an intended recipient you<BR>> are hereby notified that copying, forwarding or other dissemination or<BR>> distribution of this communication by any means is prohibited. If you<BR>> are not specifically authorized to receive this email and if you believe<BR>> that you received it in error please notify the original sender<BR>> immediately. We honour similar requests relating to the privacy of<BR>> email communications.<BR>> <BR>> Cette communication par courrier electronique est une communication<BR>> privee a l'usage exclusif du destinataire principal ainsi que des<BR>> personnes dont les noms figurent en copie. Les renseignements contenus<BR>> dans ce courriel sont confidentiels et si vous n'etes pas le<BR>> destinataire prevu, vous etes avise, par les presentes que toute<BR>> reproduction, transfert ou autre forme de diffusion de cette<BR>> communication par quelque moyen que ce soit est interdite. Si vous<BR>> n'etes pas specifiquement autorise a recevoir ce courriel ou si vous<BR>> croyez l'avoir recu par erreur, veuillez en aviser l'expediteur original<BR>> immediatement. Nous respectons les demandes similaires qui touchent la<BR>> confidentialite des communications par courrier electronique.<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> This email has been scanned for all viruses by the MessageLabs SkyScan<BR>> service.<BR>> <BR>> ************************************************************************<BR>> **********<BR>> This email and any files transmitted with it are confidential, and may<BR>> be subject to legal privilege, and are intended solely for the use of<BR>> the individual or entity to whom they are addressed. <BR>> If you have received this email in error or think you may have done so,<BR>> you may not peruse, use, disseminate, distribute or copy this message.<BR>> Please notify the sender immediately and delete the original e-mail from<BR>> your system.<BR>> <BR>> Computer viruses can be transmitted by e-mail. Recipients should check<BR>> this e-mail for the presence of viruses. The Capita Group and its<BR>> subsidiaries accept no liability for any damage caused by any virus<BR>> transmitted by this e-mail.<BR>> ************************************************************************<BR>> ***********<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>> End of SAP-WUG Digest, Vol 18, Issue 74<BR>> ***************************************<BR><BR><br /><hr />La future messagerie instantanée : <a href='http://ideas.live.com/programpage.aspx?versionId=0eccd94b-eb48-497c-8e60-c6313f7ebb73' target='_new'>Essayez gratuitement Windows Live Messenger Beta</a></body>
</html>