Purchase Requistions and PO's release

Griffiths, Mark mark.griffiths at sap.com
Fri Jan 28 09:41:25 EST 2005


You could build the logic you describe into your workflow and use one of
the release methods to release in the background if the initiator has
access to that release code (you could even read this from
authorisations with a BAPI call).

Alternatively you can just give your users access to the standard manual
release transactions - if your workflow is designed well any open
approvals will then be completed automatically.

Regards,

Mark

SAP UK

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Claude Bourque
Sent: 28 January 2005 14:01
To: sap-wug at mit.edu
Subject: Purchase Requistions and PO's release


Greetings,

Health Canada is using the PR and PO overall release WF's (WS20000077
and
WS20000075) and all works fine except that a manager that creates
his/her
own PR cannot "approve" it on ME51N. Instead, the manager gets a work
item
like everyone else. We would like to know if it's possible for the inbox
step to be skipped if a manager creates his/her own PR.

Is it something in the release strategy that has to be changed?

Thanks.

Claude Bourque
HR Consultant - Salary Management Team, FIRMS
Financial Information and Accounting Services Division
Departmental Planning and Financial Administration Directorate
Corporate Services Branch,  HEALTH CANADA
Qualicum Tower C,  C274 - 2932 Baseline Road,
Ottawa, ON, K1A 0K9

E-mail: claude_bourque at hc-sc.gc.ca



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



More information about the SAP-WUG mailing list