PO Approval workflow without Release Strategy

[Florin Wach]

Yes Gerald,

you will need a release strategy in order to implement the approval process (in the way you're planning to do it).

The benefit of using the release indicators is, that you can suppress output printing and further processing of the purchase order, as long as it isn't approved.
However in your scenario the configuration of the release strategy is quite straight forward, so you could possibly use the "Release strategy without classification" (which is plant-based activated), which is really easy.

For further annotations on the PO release strategy I would also suggest to scan this  user group's threads and the SDN workflow forums.

Best wishes,
Florin


-------- Original-Nachricht --------
> Datum: Thu, 13 Dec 2007 12:40:18 +1300
> Von: "Gerald Pecover" <pecover at gmail.com>
> An: sap-wug at mit.edu
> Betreff: PO Approval workflow without Release Strategy

> Your help with this query is greatly appreciated.
> ---------------------------------------------------------------------
> I am developing a workflow for a very standard and simple Purchasing
> scenario.
> 1 Purch. Org, 1 Plant, a few SLOCs and every PO must be approved.
> In most cases, there is only 1 agent. All the criteria to determine who
> that
> agent is,
>  is contained in a custom table and is determined within the workflow.
> 
> I do not want to use a Release Strategy however...
> when testing, the agent cannot approve the PO and we see the message :
> 
> Message No: W5105
> 
> Diagnosis: You do not have to process this document with your release
> code.
> 
> Workflow error message: Release outside field of responsibility.
> 
> This seems to indicate we need a Rel.Strategy.
> 
> I have 2 questions :
> 
> 1. If you know what the message means, please let me know.
> Is it just some missing Authorisation object?
> 
> 2. Can you confirm that a Release Strategy is not mandatory
> when developing an approvals process?
> 
> -- 
> Regards
> 
> Gerald Pecover
> 
> pecover at gmail.com