Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from archanavithlani on Jul 13 at 9:42 AM Hi Steve,
There was an alternate solution that was proposed in the thread
https://scn.sap.com/thread/3420578
the user created a custom release strategy and named it ZZ, to allow the
system to check for all the Release Strategies to be checked before it
lands on ZZ.
the user created a dummy code ZZ and assigned it to a user, who in
emergency would be able to release PR
in CL24N the characteristic value * was maintained in order to cater for
scenarios where if a new value gets created and with no corresponding RS
value, then by defualt RS 'ZZ' will be used.
Hope this helps.
Regards,
Archana
| | | ---------------Original Message---------------
From: sapsec34
Sent: Wednesday, July 01, 2015 9:21 AM
Subject: Cross-Approval of PRs
Create a custom table to maintain PR approvers based on release code and plant/cost center. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
