PR Release workflow

[akshay.bhagwat@wipro.com]

Hi Yogesh,
 
Another point is no. of levels which can be allowed under release
strategy, I think it is up to 7 or 8 levels, verify it from your end.
 
  

Thanks and Regards, 

Akshay Bhagwat

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of yogesh patil
Sent: Thursday, June 19, 2008 6:44 AM
To: sap-wug at mit.edu
Subject: PR Release workflow


Hi Wugers,
 
I have a requirement for a PR (purchase Requsition ) approval
Workflow.following is the functionality desired :
 
1.when the requisitioner creates the Purchase requisition,it should go
for approval to the requisitioners manager and hence up the org
hierarchy(managers' manager and so on ) untill it gets approved by the
person who has the authority to approve that dollar limit.
 
my question is can we use the standard workflow delivered for Pr release
to achieve this hierarchial approval with the purchasing customization
in SPRO or we need to create a zworkflow which would fetch the approvers
from the org hierarchy depending on the dollar limit ?
 
in short i want to know can we use the standard workflow functional
delivered by SAP for Purchase release(WS0000038) to achieve this
hierarchial approval or do we need to go for a Z workflow?
 
 
Thanks,

YP


________________________________

Explore the seven wonders of the world Learn more!
<http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBR
E>  

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/20080619/d9b0b178/attachment.htm