<html><body>
<p>Hi All,<br>
<br>
Let me explain myself more clearly.<br>
We currently are working with a release strategy based on item level.<br>
The business wants the option to release a PR at both Item level or all the items for a particular PR that is in a user in-box at once.<br>
If user has 5 items in their in-box for a particular they wants to release all five at once or release each item on its own.<br>
<br>
<br>
Jocelyn can you please provide me with more information on your suggestion as I think that is what we are looking for here.<br>
<br>
<br>
<br>
Regards<br>
<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<br>
Fax : +27 031 902 9633<br>
E-mail : ngovender4@toyota.co.za<br>
<br>
=============================================<br>
Never test the depth of the water with both feet. <br>
=============================================<br>
<img src="cid:10__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="16" height="16" alt="Inactive hide details for "Dart, Jocelyn" <jocelyn.dart@sap.com>">"Dart, Jocelyn" <jocelyn.dart@sap.com><br>
<br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td style="background-image:url(cid:20__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za); background-repeat: no-repeat; " width="40%">
<ul>
<ul>
<ul>
<ul><b><font size="2">"Dart, Jocelyn" <jocelyn.dart@sap.com></font></b><font size="2"> </font><br>
<font size="2">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size="2">2006/11/07 02:31 AM</font>
<table border="1">
<tr valign="top"><td width="168" bgcolor="#FFFFFF"><div align="center"><font size="2">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></td></tr>
</table>
</ul>
</ul>
</ul>
</ul>
</td><td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">To</font></div></td><td width="100%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">"SAP Workflow Users' Group" <sap-wug@mit.edu></font></td></tr>
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">cc</font></div></td><td width="100%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
</td></tr>
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">Subject</font></div></td><td width="100%"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">RE: Purchase Requisition</font></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="58"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td><td width="336"><img src="cid:30__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td></tr>
</table>
</td></tr>
</table>
<br>
<font color="#0000FF" face="Arial">Just a thought - why don't you look at using a multi-approval option from the inbox? </font><br>
<font color="#0000FF" face="Arial">I.e. so they get the approve/reject buttons in their inbox list. </font><br>
<font color="#0000FF" face="Arial">And set up an inbox filter that groups the requisition items by requisition number. </font><br>
<font size="4"> </font>
<p><font size="2" face="Arial">Regards,</font><font size="4"> </font><b><font size="2" color="#000080" face="Arial"><br>
Jocelyn Dart</font></b><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
Senior Consultant</font><font size="4"> </font><b><font size="2" color="#808080" face="Arial"><br>
SAP Australia Pty Ltd.</font></b><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
Level 1/168 Walker St.</font><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
North Sydney <br>
NSW, 2060</font><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
Australia</font><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
T +61 412 390 267</font><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
M + 61 412 390 267</font><font size="4"> </font><font size="2" color="#808080" face="Arial"><br>
E jocelyn.dart@sap.com</font><font size="4"> </font><u><font size="2" color="#0000FF" face="Arial"><br>
</font></u><a href="http://www.sap.com/"><u><font size="2" color="#0000FF" face="Arial">http://www.sap.com</font></u></a><font size="4"> </font>
<p><font size="2" color="#FF0000" face="Times New Roman">The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. </font>
<p><font size="2" color="#FF0000" face="Times New Roman">Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.</font>
<p><font size="2" color="#FF0000" face="Times New Roman">Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. </font>
<p><font size="4"> </font><br>
<br>
<hr width="100%" size="2" align="left"><b><font face="Tahoma">From:</font></b><font face="Tahoma"> sap-wug-bounces@mit.edu [<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>] </font><b><font face="Tahoma">On Behalf Of </font></b><font face="Tahoma">Scheinoha, John</font><b><font face="Tahoma"><br>
Sent:</font></b><font face="Tahoma"> Tuesday, 07 November 2006 3:20 AM</font><b><font face="Tahoma"><br>
To:</font></b><font face="Tahoma"> SAP Workflow Users' Group</font><b><font face="Tahoma"><br>
Cc:</font></b><font face="Tahoma"> sap-wug-bounces@mit.edu</font><b><font face="Tahoma"><br>
Subject:</font></b><font face="Tahoma"> RE: Purchase Requisition</font><font size="4"><br>
</font><br>
<font color="#0000FF" face="Arial">Nat,</font><br>
<font size="4"> </font><br>
<font color="#0000FF" face="Arial"> Two years ago we worked with Thomas Kosog from SAP-America (Chicago) to develop a process where purchase requisitions could be approved at the line item level. If the overall requisition limit exceeded our company defined requisition limit, the requisition would also have to be approved from an overall approval standpoint. In the release strategy, we use "99" as the last approval for the line items. The "99" approval doe not become active until all of the other line item approvals have been complete.</font><br>
<font size="4"> </font><br>
<font color="#0000FF" face="Arial"> I have attached the business rules we used to define how Overall Approvers are determined at our company. We have a number of plants and it is possible for one purchase requisition to be created for more than one plant. </font><br>
<font size="4"> </font><br>
<font color="#0000FF" face="Arial"> This project is very do-able. It took use some some to discuss and determine how the overall approvers should be determined and how the process should work. I hope this helps. Please contact me and we can discuss more in detail.</font><br>
<font size="4"> </font><br>
<font color="#0000FF" face="Arial">Thanks,</font><br>
<font color="#0000FF" face="Arial"> John</font><br>
<font color="#0000FF" face="Arial">Workflow Administrator</font><br>
<font color="#0000FF" face="Arial">Brigg & Stratton</font><br>
<font color="#0000FF" face="Arial">(414) 256 - 5136</font><br>
<br>
<hr width="100%" size="2" align="left"><b><font face="Tahoma">From:</font></b><font face="Tahoma"> sap-wug-bounces@mit.edu [<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>] </font><b><font face="Tahoma">On Behalf Of </font></b><font face="Tahoma">Nat 4 Govender</font><b><font face="Tahoma"><br>
Sent:</font></b><font face="Tahoma"> Sunday, November 05, 2006 10:59 PM</font><b><font face="Tahoma"><br>
To:</font></b><font face="Tahoma"> SAP Workflow Users' Group</font><b><font face="Tahoma"><br>
Cc:</font></b><font face="Tahoma"> SAP Workflow Users' Group; sap-wug-bounces@mit.edu</font><b><font face="Tahoma"><br>
Subject:</font></b><font face="Tahoma"> Re: Purchase Requisition</font><font size="4"><br>
</font>
<p><font size="4">Because initially when we start the workflow the consultants told us that we could only use item level offcourse now we are a bit more wiser.<br>
<br>
The problem is that we have done so much now working on the item level. To implement the purchase requisition release at header level will be a project and I was looking as ways to temporary solve this until we can start with this process.<br>
<br>
Regards<br>
<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<br>
Fax : +27 031 902 9633<br>
E-mail : ngovender4@toyota.co.za<br>
<br>
=============================================<br>
Never test the depth of the water with both feet. <br>
=============================================<br>
</font><img src="cid:40__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="16" height="16" alt="Inactive hide details for "Maorriyan Santoso" <maorriyan.santoso@gmail.com>"><font size="4">"Maorriyan Santoso" <maorriyan.santoso@gmail.com><br>
<br>
</font>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="56%">
<ul>
<ul>
<ul>
<ul>
<ul>
<ul>
<ul>
<ul><b>"Maorriyan Santoso" <maorriyan.santoso@gmail.com></b> <br>
Sent by: sap-wug-bounces@mit.edu<font size="4"> </font>
<p>2006/11/06 01:34 AM<font size="4"> </font></ul>
</ul>
</ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<table width="100%" border="1">
<tr valign="top"><td width="100%" bgcolor="#FFFFFF"><div align="center">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></div></td></tr>
</table>
</td><td width="44%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="17%"><img src="cid:50__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="58" height="1" alt=""><div align="right">To</div></td><td width="83%"><img src="cid:60__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="1" height="1" alt=""><br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></td></tr>
<tr valign="top"><td width="17%"><img src="cid:70__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="58" height="1" alt=""><div align="right">cc</div></td><td width="83%"><img src="cid:80__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="1" height="1" alt=""></td></tr>
<tr valign="top"><td width="17%"><img src="cid:90__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="58" height="1" alt=""><div align="right">Subject</div></td><td width="83%"><img src="cid:100__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="1" height="1" alt=""><br>
Re:</td></tr>
</table>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="15%"><img src="cid:110__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="1" height="1" alt=""></td><td width="85%"><img src="cid:120__=CDBBF88CDF88FF0B8f9e8a93df9@toyota.co.za" width="1" height="1" alt=""></td></tr>
</table>
</td></tr>
</table>
<font size="5"><br>
Hi Nat.<br>
Just questioning from the MM business process point of view. Why you're not using Workflow for Overall Release (header level) for this ?<br>
</font><font size="4"><br>
</font><font size="5"><br>
On 11/3/06, </font><b><font size="5">Nat 4 Govender</font></b><font size="5"> <</font><a href="mailto:ngovender4@toyota.co.za"><u><font size="5" color="#0000FF">ngovender4@toyota.co.za</font></u></a><font size="5">> wrote: </font>
<ul>
<ul><font size="5">Hi All,<br>
<br>
We currently have a release strategy of purchase requisition based on item level.<br>
<br>
What the business now want is if a user get more than one purchase requisition item for the same purchase requisition they want to release them all at once. <br>
I remember something about grouping tasks would did help?<br>
<br>
Please advise<br>
<br>
Thanking you in advance<br>
<br>
<br>
Regards<br>
<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645 <br>
Direct Line : +27 031 910 2645<br>
Fax : +27 031 902 9633<br>
E-mail : </font><a href="mailto:ngovender4@toyota.co.za" target="_blank"><u><font size="5" color="#0000FF">ngovender4@toyota.co.za</font></u></a><font size="5"><br>
<br>
============================================= <br>
Never test the depth of the water with both feet. <br>
=============================================</font><font size="4"> </font>
<p><font size="5"><br>
</font><font size="4"><br>
</font><hr width="100%" size="2" align="left">
<p><font size="4">This message is a privileged and private communication<br>
and may be read,copied and used only by the intended recipient(s).<br>
If you are not an intended recipient, please let us know by return<br>
email. Please then delete the message and do not disclose its <br>
contents to any person. Neither the sender nor Toyota South Africa<br>
Motors accepts any liability whatsoever as a result of the further<br>
dissemination of this message. Whilst all reasonable steps are<br>
taken to avoid corruption of data or information, we do not accept <br>
any liability should such corruption occur. </font>
<p><font size="5"><br>
<br>
</font><font size="4"><br>
</font><font size="5"><br>
<br>
_______________________________________________<br>
SAP-WUG mailing list</font><u><font size="4" color="#0000FF"><br>
</font></u><a href="mailto:SAP-WUG@mit.edu"><u><font size="5" color="#0000FF">SAP-WUG@mit.edu</font></u></a><u><font size="4" color="#0000FF"><br>
</font></u><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><u><font size="5" color="#0000FF">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></u></a><font size="5"><br>
</font></ul>
</ul>
<tt><font size="4">_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu</font></tt><tt><u><font size="4" color="#0000FF"><br>
</font></u></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><u><font size="4" color="#0000FF">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></u></tt></a><font size="4"><br>
</font><tt>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</tt><tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></tt><tt><br>
</tt>
<p></body></html>