All Release codes not resetting when PR Rejected

[Former Member]

We are changing our release strategy from 1 release code using work flow to 5 release codes with mult release strategies using work flow with classifications at the header level. If a later release is rejected, the earlier releases are not being reset.  Example:  Release codes  01, 02, 03, 04 and 05. 01, 02, 03 and 04 are released. release code 05 is rejected, code 01, 02, 03 and 04 do not get reset (I want them al to reset). My question is: is there a way to set this up in config, or is it done via a Bapi through ABAP or work flow?  I can not find anything in config to do the reset.

[Prasoon]

Hi,

    Release strategy will reset only if there is a change in value. Reject release doesnt lead to any value change and hence it wont trigger new release / it wont reset the other releases in standard. The rejection is applicable only at one level and it wont affect already released release codes. In addition, refer the note: 662993 - Resetting a release that already took place

    If you want a different behavior, you may check the feasibility of development with the FM: BAPI_REQUISITION_RESET_REL_GEN and the BAdI: ME_PROCESS_PR_CUST

Regards,

AKPT

[Former Member]

Thanks for the help,  I will stop looking in config and get with the programmer

thanks

[jagdeepsingh83]

Hi Alan

I do not think that standard settings that all level will be rejected if you reject at one level. I think you use BADI-ME_PROCESS_REQ_CUST, Interface face name-PROCESS_HEADER

Method-IF_RELEASABLE_MM~INITIATE_RELEASE to control Trigger Release/Reset Release

You have to explore this option with your abaper. Also I think You will not able use BAPI to reset release in the same transaction until as PR as object will be locked. You may create separate program that can run in background at certain frequency to reset the release.

[patrick_g1]

Hi,

  this is not possible in SAP standard.

If you have released a code this remains released also for documentation purpose.

Maybe you can work with this BAPI:

BAPI_REQUISITION_RESET_RELEASE

Sorry for this.

Best regards

Patrick