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
