Release Strategy redetermine for the lower vaule

[Former Member]

Hi Gurus

PO having value different value approval range

0-1000 USD  ( Release strategy S1)

> 1000 - 5000 USD ( Release strategy S2 )

> 5000- 10000 USD ( Release strategy S3 )

> 10000 USD  ( Release strategy S4 )

Suppose PO is created having value 5500USD so got selected Release strategy S3 . PO is released and PO price got reduced to 4500 USD , now release strategy got redetermined to S2 . As the PO is already approved for higher value , release strategy should not redetermined if the PO price change to lower than the released value .

Many Thanks .

Regards

SK

[Former Member]

This message was moderated.

[Former Member]

You or your developer will need to do some jumping around hoops in order to make this happen.

Off the top of my head. Alexandre suggestion is a good place to start: you'll need to work with structure CEKKO inside FM ME_REL_STRATEGIE_EKKO. There should be an point inside that FM where you can add an customer enhancement to modify the contents of CEKKO so that the flags that inform the rest of the program to redetermine the release strategy arent set.

[Former Member]

Hello SK,

It depends of the settings attached to the release code :

It is possible for instance to avoid resetting the release strategy if the value is changed within a predefined interval using the changeability key 4 and setting up a percentage.

Also, it is possible to use the key 2, in this case there will not be any new strategy for the change.

Otherwise, the standard behavior is to start a new strategy. There are several reasons for this, one aspect is that the release codes are assigned via authorization another aspect is the workflow integration...

Overall, to have complex rules like "do not reset the release strategy if the value is decreased", it requires some development. It is possible to link characteristics to function modules and so on .. and much more !

Have a look at 493900 - FAQ: Release Strategy

Regarding enhancements, there are resources on scn like Purchase Order Release using ABAP Classes - ABAP Development - SCN Wiki

Cheers,

Alexandre

[Former Member]

Hi Alexandre

Many Thanks fro your reply.

I am looking for a option " do not reset the release strategy if the value reduced to lower than released PO value, if the changed PO price is higher than the released value release strategy must be redetermined   " .

Regards

SK

[former_member183424]

I think you are using release indicator changeable as BLANK, 3, 4, 5 or 6 (in Alex's screen shot). You can use the release indicator changeable as 2 - Changeable, no new determination of strategy.

But then you wont be able to reset release strategy when value will increase or in any case.

[Former Member]

Hello SK,

Yes, your post is clear in this regard . It is just that you cannot achieve that with the standard configuration.

Alexandre

**edit**

In previous projects, similar rules were managed via a custom FM.

Message was edited by: Alexandre N.

[former_member183424]

It is not possible in standard, If you will go to the release indicator changeability options, then you will find these entries :

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 strat. or val. change

5 Changeable, new release if new strategy/outputted

6 Changeable, new rel. if new strat. or value change/outputted

   Changeable, new release in case of new strategy

Here, you can see instead of 1 and 2, all other options has the facility "New Strategy"

So if you will use any of other than 1 or 2, then system will always trigger the new release strategy.

So, either you need to check your flexible development or you need to use 1 or 2 .

[Former Member]

Thanks Dibyendu for confirming what I suggested.

Otherwise SK, check the method GetReleaseInfo for BUS2012, this is where you can define your own release rules.

[Former Member]

Actually, to be more precise, the rules are managed with a custom FM, then the values are passed to an extension of CEKKO and read with the GetReleaseInfo.