BUS2012 - ReleaseStepCreated

Thu Dec 18 07:56:59 EST 2003

Hello All,

I have a follow-up question.  Our company requires that all purchase =
order changes that affect price be approved even if the price is =
reduced.  I have the release strategies and workflow working for =
increases using change indicator '6' but need to trigger it when the =
price decrease.  Any ideas?

Thanks,

Paul

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Cristiana D'Agosto
Sent: Thursday, December 18, 2003 6:14 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: BUS2012 - ReleaseStepCreated

Thanks Stephen,

that sounds good! I can get to the system now and try it out (it is 10pm
in Australia but this problem has kept me awake - might be able to relax
now, some good options were give for me to try tomorrow!).

I will let you know how I did go!

Cheers

Cristiana

"Becker, Stephan" <stephan_becker.ext at siemens.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
18/12/2003 10:08 PM
Please respond to "SAP Workflow Users' Group"

        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: BUS2012 - ReleaseStepCreated

Have a look at the below. It answers your question. Your suspicion is
correct, the customizing is not complete.

HTH,
Stephan

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Hi Monique,
I recently investigated the configuration related to =
Release/Changeability
indicators (OMGQ/S).

Using a Changeability Indicator of 4 (Changeable, new release in case of
new
strat. or value change) with a tolerance of x% of the order's value =
means
that:

        Changes (within tolerance) made to an order after release are =
not
subjected to a release strategy.

        Changes (outside tolerance) made to an order after release and
prior
to output are subjected to a release strategy.

        Changes (outside tolerance) made to an order after release and
output are not subjected to a release strategy. Therefore, where orders
are
auto-outputted, changes are possible without being subjected to a =
release
strategy.

Reference to OSS note 47716 indicates that Changeability Indicator 6
(Changeable, new rel. if new strat. or value change/ouputted) can be =
used
to
prevent changes being made to an order that has been both released and
outputted. I tested this and it worked as expected. The release that was
previously effected was reset (even though the order had been ouputted).

I hope this helps....

Cheers,

Drosoula Kalavriotis
SAP Security Analyst
Change Management
Coles Myer Ltd
Tel:  03 9278 1427
Fax:  03 9278 1449
E-mail:  Drosoula.Kalavriotis at colesmyer.com.au

-----Original Message-----
From: Stephens, Monique S L [mailto:moniques at bcm.tmc.edu]
Sent: Tuesday, 8 January 2002 8:40
To: SAP-WUG at MITVMA.MIT.EDU
Subject: PO Workflow Release Indicators

We are currently on release 4.0B.  We are experiencing some problems =
with
workflow and I am not sure if I have it configured correctly.  When a PO
is
blocked in Purchasing or released by Purchasing, a 25% change in the =
total
dollar value of the PO resets workflow.  Some of our PO's that exceed =
the
25% are not resetting.  There is a changeability column in the IMG for
release indicators.  In that column, you can specify any of the =
following:

1 Cannot be changed

2 Changeable, no new determination of strategy

3 Changeable, new release in case of new strategy

4 Changeable, new release in case of new strategy or value change

5 Changeable, new release if new strategy/outputted

6 Changeable, new release if new strategy or value change/outputted

Blank Changeable, new release in case of new strategy

For PO's blocked in Purchasing, the changeability is set to "4"; for
released PO's, it is "6".  Can anyone explain to me what these actually
mean?  What we want to accomplish is to reset workflow if the PO total
value
changes more than 25%.

Monique Stephens
SAP Analyst
Baylor College of Medicine
713-798-1349
713-798-1326 (FAX)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-----Mensaje original-----
De: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
Enviado el: 18 December 2003 11:53
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: Re: BUS2012 - ReleaseStepCreated

Thanks Flavio,

I will try that. How is the weather in Brasil? I have a feeling you are
brazilian!

Cheers

Obrigada

Cristiana

Flavio Oliveira <oliveiraflavio at hotmail.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
18/12/2003 09:39 PM
Please respond to "SAP Workflow Users' Group"

        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: BUS2012 - ReleaseStepCreated

Cristiana:

When I was working with Purchase Requisition release I found a problem
that
is very similar of yours. On the requisition, when you change it but the
release strategy was not modified, no new event is raised. This causes =
the
problem you are mentioning.

On the requisition this was a bug and SAP did not solve it, so I did =
this:

- Save the release strategy before the PO change on a WF container
- After the PO change I compare the new release strategy with the old =
one
- If they are the same you can raise the event by yourself, so a new
workitem will be generated.

I am not sure if the problem with the PO is the same as I had with
requisition, but if it is this is a possible solution.

Flavio.

>From: Cristiana D'Agosto <cristiana.dagosto at au1.ibm.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: BUS2012 - ReleaseStepCreated
>Date: Thu, 18 Dec 2003 18:04:07 +1100
>
>G'day all!
>
>we are in version 4.6c
>
>We have a PO release strategy (02) with the following criteria
>(transaction code OMGS in config)
>- value >$100,000
>- purchasing group LAU Admin
>- order type : standard PO
>
>The release strategy required 2 approvers (release codes), AC and then
AK,
>both are set as workflow relevant.
>
>The scenario that is a problem has the following steps:
>- PO is raised for $110,000 (therefore require release by approvers AC
and
>then AK) -> BUS2012.ReleaseStepCreated is raised; workflow is triggered
>- AC receives workflow item and releases the PO -> an individual =
workflow
>is started for each wf-relevant release code
>- AK receives workflow item and REJECTS the PO -> another workflow is
>triggered, as an individual workflow is started for each wf-relevant
>release code
>- The PO Administrator receives the workflow item and he/she modifies =
the
>PO value to $210,000.  -> BUS2012.CHANGED is raised
>- A workflow should be triggered for AC to release (this is not
>happening).
>
>When the PO is changed, the currently running instance of the workflow =
is
>terminated because of a Wait step (PO Changed).
>
>I thought that if the PO is changed the system would automatically
>re-assess the PO to determine whether it should issue event
>'ReleaseStepCreated' to trigger the workflow again?
>
>I have a strong feeling that there is something missing in the MM =
config
>for workflow but I am not sure where. I thought the
>BUS2012.ReleaseStepCreated would be published once the system =
re-assessed
>the PO?
>
>Any ideas where I should look?
>
>Many thanks and regards
>
>Cristiana
>
>PS> Merry Xmas and have a fantastic 2004!

_________________________________________________________________
MSN Messenger: instale gratis e converse com seus amigos.
http://messenger.msn.com.br