PO Workflow

[Dart, Jocelyn]

Monique, 
Yes its possible but not standard.
 
I've done this before - 
1. All POs needed to be created with a release strategy - even if that
effectively states they are automatically approved on first creation
2. we used a workflow (I think started by the significantly changed
event) to explicitly reset the release code
3. Resetting the release code in turn started the standard workflow
 
It was a while ago but the process should still work.

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

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. 

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.

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. 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Stephens, Monique S L
Sent: Friday, 17 February 2006 6:54 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: PO Workflow


I need some assistance with PO workflow.  Prior to SRM, our users were
creating PO's that were then routed through the system for approvals.
We had particular release indicators set up.  Therefore, if a PO is
blocked at a particular release level, a pre-determined percentage
change would need to be made for the PO to go back through workflow.
The release indicators identify this percentage.
 
Now, with SRM, our users create shopping carts that route through
approvals.  But, when the cart transfers over to SAP and turns into a
PO, no workflow is initiated.  Our users are not allowed to change these
PO's.  We would like to look at our pre-SRM workflow, enhance it, and
use it for the newer PO's.  In order to do this, we need to tell the
system that either a percentage change (already identified in the
release indicators) or value change will reset the releases.  We only
want workflow to be initiated after a PO has already been generated and
changed after the fact.  Is there a way to set up workflow to look at
value and percentage like it can for invoice tolerances? 
 
 
Monique Stephens
SAP Analyst
Baylor College of Medicine
713-798-1349
713-798-1326 (FAX)
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060217/5c15d143/attachment.htm