Skip to Content
avatar image
Former Member

System unreleasing old PRs after deploying a new Release Strategy

We are facing an issue after deploying a New Release Strategy specifically in Services PR created via PS module (CNMM).

All such PRs that were created by old release strategy are having their release revoked even after PO is created and in most of the cases SES is posted too. All material PRs created via PS module (CNMM) and MM module (ME51N) are behaving normally.

We have determined that with every change in Network Planning, system is showing this behavior.

please help

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Nov 06, 2017 at 10:09 AM

    did you only create a new strategy or did you change the existing strategy?

    Had you already checked your strategies for inconsistencies? is right in the same IMG path.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 06, 2017 at 10:47 AM

    SAP note 493900 (FAQ : Release strategy) explained, there are only three circumstance the release strategy will reset.

    1) If release id is set to 4 (RFQ/PO no changes)

    2) If the purchasing document is still subject to the previous release strategy - I am suggesting you to check all relevant tables T16FS, T16FG, T16FV and T16FK for any inconsistency.

    3) New net value is higher than the old net value

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 06, 2017 at 10:49 AM

    Thanks for your immediate response. We have created a new header level Release strategy and system is behaving as defined above . Please also elaborate what will be the impact if we have gone for modifications in existing Release strategy. Currently we have defined characteristics of Doc. Type,

    PR Value,

    Purchasing group,

    Plant and

    Desired Vendor.

    Add comment
    10|10000 characters needed characters exceeded

    • Please also elaborate what will be the impact if we have gone for modifications in existing Release strategy

      We have lot of discussions about this matter or even some OSS notes are there to explain this.

      You may need to read also about the criteria of resetting release strategy. You will get the answer for your initial question.

      You said "We have determined that with every change in Network Planning", have you checked the changes log of requisition ? Does it affect value in your requisition ?

      You said "We have created a new header level Release strategy", was it at item level previously ?