PO Release Strategy

[Dave Weston]

Claude, if the changes you refer don't change the release strategy then
the existing PR/PO workflow is not affected and the release status is
not changed. Maybe check the release strategies and the classification
piece to see if you can do this there. I don't think you will be able to
do that though and may have to go with what I suggested. There is some
info on this in the SAP help for the workflow scenario.

Cheers
Dave

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Claude Bourque
Sent: Friday, December 09, 2005 2:24 PM
To: SAP Workflow Users' Group
Subject: RE: PO Release Strategy


Dave,

I was thinking of that but I find it strange that the MM config doesn't
seem to have a non-Workflow option.

Thanks.

Claude


 

                      "Dave Weston"

                      <Dave.Weston at cloc        To:       "SAP Workflow
Users' Group" <sap-wug at mit.edu>                                 
                      kwork.ca>                cc:

                      Sent by:                 Subject:  RE: PO Release
Strategy                                                       
                      sap-wug-bounces at m

                      it.edu

 

 

                      2005-12-09 02:21

                      PM

                      Please respond to

                      "SAP Workflow

                      Users' Group"

 

 





Hi Claude,

How about raise an event when the PO or PR is changed, via change docs I
hope, and then cancel any running workflow plus also in the workflow
process execute the BAPI or method in the business object to reset the
release.

Just an idea.

Dave

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Claude Bourque
Sent: Friday, December 09, 2005 1:25 PM
To: sap-wug at mit.edu
Subject: PO Release Strategy

We have a PO (and PR) workflow working fine since April 1 but the
customer has the following to add: when a PO's Cost Centre is changed it
should revert back to NOT released ready for approval again. The MM
config team is stumped and since I'm looking at it from a workflow point
of view only, I'm finding it odd that the config for the Release
Strategy does not allow this.

One option available is to select no changes allowed after release and
force them to create a new PO but I'm told that it's normal business
practice here to change a cost centre after releasing it.

What are we missing?

Thanks.

Claude Bourque
HR/Workflow Consultant
Health Canada
Version 4.7 (WAS 6.20)

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
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



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