Reduce authorisation roles for PR release codes

[former_member595900]

Hi Experts,

We have multiple authorisation roles for PR release codes which we want to reduce.

Basically PR release strategy is based on the purchasing groups and each purchasing group has different approvers.

Lets take one purchasing group example:

Purchasing Group Georgia : Release group is G1

G1 has 7 release codes(L1 to L7) as Director, VP, Controller etc.

Here, we have created role for Director as "ZS_PR_REL_DIR_G1_L1" and assigned to User ID who is authorised to release PRs for purchasing group Georgia.

We did same activity for each role of director for each purchasing group. As we have total 15 purchasing groups I created 15 roles for Director and assigned them to different users.

In the same way we did for each release codes for each release groups.

So now my question: Is there any work around where functionality will remain the same but we can reduce the number of roles?

Thanks in advance,

Sandeep.

[BalaAP]

Hi,

Your role definition is right (rel.group/rel.code combination).

Roles can be reduced by combining these authorizations with any other existing role which are already assigned to such purchasing powers/users.

regards,

Bala

[former_member595900]

Hi Bala,

Thanks for your reply.

Other existing roles are common roles (Assigned to multiple users) where we can not add release roles.

Do you have any other option ?

Regards,

Sandeep.

[BalaAP]

Hi,

Other option could be to re-look at the number of release groups & codes. We generally don't straightaway assign purchasing groups to release groups. Purchasing groups will go inside the classification.

Release codes are also very large in number (7 levels). Should really a PR under-go 7 levels of approvals?

If your company is having many company codes (like MNC), then this could be justifiable.

(I am making comment without looking at your configuration and release strategies. My comment may not be relevant also). If your release strategies are in-line with your business processes, then your options are correct.

regards,

Bala

[former_member595900]

Hi,

Just a thought..If we create one common role for all directors where we will assign all release groups and L1 release code then by using user exit if we can restrict other unwanted release groups at ME54N.

I don't know whether any user exit is available for this or not.

Kindly suggest.

Thanks,

Sandeeep