Skip to Content
author's profile photo Former Member
0
Former Member

Release Strategy redetermine for the lower vaule

Posted on Nov 30, 2014 at 03:50 PM 519 Views

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Arnold Canaria
    Arnold Canaria
    Posted on Dec 01, 2014 at 12:14 AM
    2

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2014 at 04:46 PM
    0

    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


    Capture.PNG (12.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2014 at 09:31 PM
    0

    This message was moderated.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.