<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<BR>Hi Jake,<BR>
It is a really difficult to decide whether to settle for nesting. But you do not have to really have template in a template. Just consider this proposal.<BR>
When the part is released with 'Buy' and buyer receives the work item. Buyer thinks it is manufactured.<BR>
-> Buyer will reject.<BR>
-> then execute a background step and set the status of the material as in-process.<BR>
-> send an e-mail to the agent(s) who is responsible for release.<BR>
-> End the workflow.<BR>
<BR>
Then The agent will again correct the MRP view and set the part as released.<BR>
-> same template will trigger and you are all set.<BR>
<BR>
Cheers<BR>
SRamanan<BR><BR>
<BLOCKQUOTE>
<HR>
Subject: RE: 2-Way Workflow?<BR>Date: Wed, 6 Feb 2008 09:58:58 +0800<BR>From: jocelyn.dart@sap.com<BR>To: sap-wug@mit.edu<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<DIV id=EC_idOWAReplyText76315 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Jake, </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Surely a simple LOOP UNTIL (second user has approved) step would cover it for a scenario that simple? </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Or if it's really more complex, you might want to create your own events to trigger the different templates rather than nest things. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Jocelyn</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu on behalf of Schmidt, Jake (SN)<BR><B>Sent:</B> Wed 6/02/2008 3:33 AM<BR><B>To:</B> sap-wug@mit.edu<BR><B>Subject:</B> 2-Way Workflow?<BR></FONT><BR></DIV>
<DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2>Greetings WUG,</FONT></SPAN></DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2>Currently I have a material workflow that is "1-Way". If the first user classifies the material incorrectly then the next user has no way to send it back to the first user. </FONT></SPAN></DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2>The scenario I'd like to accomplish is this. <EM>User A releases a material. Workflow evaluates if material is Fabbed or Purchased. Workflow sends a work item accordingly. If the buyer receives the work item and finds that the part should actually be fabbed, he should reject the work item.</EM> At this point can I make the workflow restart at step 000224 (User A releasing material) in my workflow? Currently I don't think thats possible. From what I understand I need to break my existing workflow up into peices and then I can have each peice recalled when necessary. My thinking is I'll have templates inside of templates inside of templates. I know this would work but I don't think it's very elegant. Please advise if there is a better way to accomplish my goal!</FONT></SPAN></DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2>Jake Schmidt</FONT></SPAN></DIV>
<DIV><SPAN class=EC_147342516-05022008><FONT face=Arial size=2>Spirit Aerosystems</FONT></SPAN></DIV></DIV></BLOCKQUOTE><br /><hr />Shed those extra pounds with MSN and The Biggest Loser! <a href='http://biggestloser.msn.com/' target='_new'>Learn more.</a></body>
</html>