Release Strategy - Purchase requistion go back to unreleased

Question

Hi Friends,
I am facing  two  problem in release strategy in our client system.
Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
Current System Settings;-
Release Procedure:- Procedure with classification ( Also setting available for  setup procedure without classification maintained )
Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
Value maintained in CL24N for plant , Creation indicator.
Release Indicator:- 1 Stage:- X. Blocked
                                2 Nd Stage:- 4.RFQ/PO no changes
Scenario :- When  PR is created and released , If any one changes the Purchase Group in any line item  which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
I checked all the system setting and it seems to be correct except when i  use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
Checks re requisns. with item-wise release 3
-> Checks re release group and release class 2
-> No release group exists 1
Problem. 2:- Purchase Requisition not triggering when  PR is created from other source linked to SAP.
Please suggest the solution for the above problem.

Answer 1

Hello Kunal,
A few thoughts and questions on your problem:
You generally can't have both release procedure without classification and release procedure with classification working at the same time.
To get the system with classification working, you have to have several things in place and consistent: You need a release group.  It should have a class.  That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release).  You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
You have to choose item-based or overall release for each requisition document type.  You mark this on the document type.  You must also choose the same option for the release groups that the document type will be assigned to.  Example: document type NB is item-based.  Document type ZB is overall.  Document type will be a characteristic.  CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ.  Release group NN will be marked as item-based.  Release group ZB will be marked as overall-based.  Usually, I think, you will  just use one or the other, and it will be less complicated, but the release group must match the document type.
The indicators themselves have some configuration, including a field for changeability.  Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
If you are using workflow, there might be custom events related to the business objects involved that  can change things, as well.
Are you using workflow?
Are you using overall or item-based release?
Good luck,
- Jeff