Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

enforce modify access restrictions for abap repository objects at package level

former_member188019
Active Participant

‎08-12-2013 12:40 PM

0 Kudos

Hi All,
there are two different teams working on different projects (project ABC, and project XYZ).


all the repository objects ( like, abap reports, classes, tables, webdynpros etc) for first project have to be created in package Z_ABC only. and similary for the second project in a package Z_XYZ.


the developer userid of first project team is user_abc, and of second project team is user_xyz.

both the user ids have developer access, se80, and they can create and change repository objects.

how can we restrict such that the user_abc can create/change objects only in package Z_ABC and not in other pacakge like Z_XYZ.

similarly, the user_xyz should be able to modify only the objects in package Z_XYZ.

we dont mind with view access. but we want to restrict only the change/create/delete access in other packages.

How can we enforce this modify authorization/access restriction.

Thanks,

Madhu.

1 REPLY 1

ThomasZloch
Active Contributor

‎08-12-2013 1:06 PM

0 Kudos

Sounds like standard functionality, please search for information on how to properly use authorisation object S_DEVELOP.

How many actual developers are sharing one ID (if I understand correctly...)? Can't there be locking problems? Is this covered by SAP's licensing model?

Thomas