cancel
Showing results for 
Search instead for 
Did you mean: 

Block access for set of users

former_member184111
Active Contributor
0 Kudos

Hello,

Is it possible to block CREATE access for a set of users say all users under one Org node in SRM without doing it at user level and security related changes?

Users should not be able to create or change SC in Portal but should be able to view existing carts and do confirmation.

Thanks,

Anubhav

Accepted Solutions (0)

Answers (3)

Answers (3)

ivy_li
Active Contributor
0 Kudos

Hi,

You may control this by copying employee role /SAPSRM/EMPLOYEE via trx PFCG to generate a Z-role. Then edit authorization object BBP_PD_SC to control display or change activity.
By the way, you may also control this by assigning responsible organization.

At last, assign this Z-role to the expected users.

BR,
Ivy

laurent_burtaire
Active Contributor
0 Kudos

Hello Anubhav,

what about creating a specific single role with only display mode for SC (authorization object BBP_PD_SC, class BBP)?

Regards.

Laurent.

former_member184111
Active Contributor
0 Kudos

Thanks Laurent and Ivy,

Any ways to achieve this without changes at role and user level, as I mentioned in the first post in the thread?

The scenario is that some company codes and users under these companies(Org Units) in SRM will be removed from the current system and set up in a new system, during this transition there is a blackout period where the users should be able to view carts, process PO and confirmations but not change or create carts in existing system, after this black out period users will be using the new system. Hence we want to achieve blocking via changes in Org structure or attributes, if possible and avoid any changes it individual user or role level.

Regards,

Anubhav

ivy_li
Active Contributor
0 Kudos

Hi Anubhav,

This BADI should be of help for your requirement
Please also refer to this wiki page for its usage:

BADI BBP_AUTHORITY_CHECK in Document Control - Supplier Relationship Management - SCN Wiki

BR,
Ivy

former_member186144
Participant
0 Kudos

try modifying the attribute in the org node

Yosea

former_member184111
Active Contributor
0 Kudos

Which attribute?