Experts, We are facing an issue with respect to security for Release strategy. Our PR release strategy has about 26 Release codes. The requirement is that 1. PR release be restricted by plant 2. PR create / change required for multiple plants Example : A user may have Release code ZA (for $5000 limit) assigned for Plant XYZ0 in security profile. So he can approve upto $5000 for XYZ0 in Tcode: ME54N. However he also has PR create and change security access for multiple plants (ABC0, XYZ0) under Tcode: ME51N/ME52N. However ME54N restriction by plant (XYZ0) is being overridden by ME52N Plant setting of * or (ABC0, XYZ0) Result is that Tcode ME55 or ME54N gives him access to approve Release code ZA not only for XYZ0 but also for other plants(ABC0). PS: Our release strategy configuration does not have plant as characteristic. Otherwise Release codes would multiply by26. That will be in excess of 300 Release codes. We do not want this as data maintenance becomes too much. Not feasible option Any thoughts from experts what may be wrong from Security standpoint or otherwise would be appreciated. Regards,
↧