Issue with retriggering Release Strategy

Question

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy  for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Answer 1

Hi Arnand,
After investigation by searching customer messages database ,I found              
other customer has  similar problem as the release strategy has changed           
after creation of the SES please review the  explanation from developer           
:(whose release code is 03 )                                                                               
When you try to revoke the acceptance of the service entry sheets                 
in ML81N or ML81, the 'Enter release code' pop  up window appears, but            
entering the code that is determined via the menu path Goto -> Entry              
Sheet -> Release Strategy (which is the 03), the SES remains the same.            
Nothing changes. The status does not vary and no error or warning                 
message is issued.                                                                               
Checking the customizing for the release strategy, the release code               
03 should have never been assigned to the SES 800024272 as the values             
for the relevant characteristics were not included under that code.               
I do not know how it was managed to accept the SES.                                                                               
Now, when you try to revoke it, it seems that no release                          
strategy can be determined, not even including the values RCARESANO               
and 012 between the valid values for the characteristics of the release           
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS                        
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).                                                                               
The only Possibility is to change now the SES so that the release                 
strategy can be re-determined by the system.This is the Only possible             
way that the system can  redetermine the Release Strategy , but it will           
not be possible to do so as the SES is already accepted with the Old              
strategy and it does not admit any further changes.                               
To be able to change it you would need to revoke the SES first,                   
but this Will also not be possible as the Release Strategy was changed            
and the system still applies the old rules for determining the Release.           
Solution to our Problem                                                                               
The Only way to revoke the SES is to Restore back the Old Strategy that           
was prior to 03 in the customizing.So now what will happen is that by             
applying the Old Rules the System will be able to revoke the SES that#s           
using the Old one. Once the necessary SES are revoked then go back to             
customizing and apply the new strategy as it was did now, and                     
Change the SES and save , the new value of the Release Strategy will get          
updated in the table ESSR and the field frgsx will now have 03.                                                                               
Problems associated if the Release strategy is changed                                                                               
Actually the release strategy is not supposed to be changed when there     
are some documents in the System that uses it and even if you change the   
Strategy the Old records will not get AUTOMATICALLY UPDATED by the        
system.The Release Strategy routine has to run again to update the         
values. This is Possible by changing the document SES ,                    
This change will happen only if the SES is not accepted and if its         
accepted then you need to revoke and to revoke you need to restore the     
old strategy , revoke and then change the SES , and have to go back to     
customizing and Start using the New strategy from now on by doing so the   
Routine will update the old record with the new strategy.                 
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy    
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew