Purchase Requisition

Mon Nov 6 11:19:45 EST 2006

Nat,

   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.

   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.  

   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.

Thanks,
 John
Workflow Administrator
Brigg & Stratton
(414) 256 - 5136

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Nat 4 Govender
Sent: Sunday, November 05, 2006 10:59 PM
To: SAP Workflow Users' Group
Cc: SAP Workflow Users' Group; sap-wug-bounces at mit.edu
Subject: Re: Purchase Requisition

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.

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.

Regards

Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext. : 32645
Direct Line : +27 031 910 2645
Fax : +27 031 902 9633
E-mail : ngovender4 at toyota.co.za

=============================================
Never test the depth of the water with both feet. 
=============================================
 "Maorriyan Santoso" <maorriyan.santoso at gmail.com>

				"Maorriyan Santoso"
<maorriyan.santoso at gmail.com> 
				Sent by: sap-wug-bounces at mit.edu 

				2006/11/06 01:34 AM 

	Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To

"SAP Workflow Users' Group" <sap-wug at mit.edu>	

cc

Subject

Re:	

Hi Nat.
Just questioning from the MM business process point of view. Why you're
not using Workflow for Overall Release (header level) for this ?

On 11/3/06, Nat 4 Govender <ngovender4 at toyota.co.za
<mailto:ngovender4 at toyota.co.za> > wrote: 

	Hi All,

	We currently have a release strategy of purchase requisition
based on item level.

	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. 
	I remember something about grouping tasks would did help?

	Please advise

	Thanking you in advance

	Regards

	Nat Govender
	Toyota South Africa
	IT - SAP Workflow Specialist
	Internal Ext. : 32645 
	Direct Line : +27 031 910 2645
	Fax : +27 031 902 9633
	E-mail : ngovender4 at toyota.co.za
<mailto:ngovender4 at toyota.co.za> 

	============================================= 
	Never test the depth of the water with both feet. 
	============================================= 

________________________________

	This message is a privileged and private communication
	and may be read,copied and used only by the intended
recipient(s).
	If you are not an intended recipient, please let us know by
return
	email. Please then delete the message and do not disclose its 
	contents to any person. Neither the sender nor Toyota South
Africa
	Motors accepts any liability whatsoever as a result of the
further
	dissemination of this message. Whilst all reasonable steps are
	taken to avoid corruption of data or information, we do not
accept 
	any liability should such corruption occur. 

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

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/3a727764/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 105 bytes
Desc: graycol.gif
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/3a727764/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 45 bytes
Desc: ecblank.gif
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/3a727764/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2005_01_24 PR Overall Approval Determination Business	Rules.doc
Type: application/msword
Size: 506880 bytes
Desc: 2005_01_24 PR Overall Approval Determination Business
	Rules.doc
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061106/3a727764/attachment.doc