Мне нужно сделать так, чтобы пользователю был открыт доступ к настройкам (spro) только в режиме просмотра, т.е. разрешено всё кроме изменения настроек. Подскажите, плиз, как это сделать

SPRO: Authorization Check for IMG Activity
SAP Note Number: 1029225

Symptom

You would like to maintain authorization checks for IMG Activities, called via the Easy access menu, or in SPRO, Reference IMG. This note gives you information on how-to.


Other terms

SPRO, Reference IMG, Easy Access Menu, User Restriction, Authorization Check, Maintenance object, Customizing objects


Reason and Prerequisites

IMG Activities are used to maintain customizing in the system landscape. There are various types of objects which can be maintained using an IMG Activity - BAdIs, Enhancements, or any of the Customizing objects (Tables, Views, View Cluster, Logical Transport Objects, Individual Transaction Objects, and Dummy objects).

Whenever an IMG activity is defined, a transaction code is generated automatically, of the pattern S_XXX_ followed by random digits. The <XXX> usually is the name of a system. When IMG Activities are executed from easy access menu, these generated transactions are called directly, which in turn makes the object-specific calls.
When an activity is executed from an IMG, these generated transactions does not play any role.

Thus, it is not possible for the IMG to provide any generic functionality of authorizations for IMG activities. Instead, the authorizations must be maintained via transaction SU22 for the
generated transaction.

Solution

Authorizations for standard object types must be maintained at the individual object level for the calls from SPRO or IMG structures. These include objects like BAdIs, Views, View Clusters, and Tables. For Logical Transport objects (L), once again, the authorizations must be maintained for the standard objects comprising the piece-list.
Object level maintenance would take care of calling the necessary authorization checks whenever these objects are called, from IMG Activities, or elsewhere.
For all other objects like Individual Transaction objects (T), or Dummy objects which in turn call application transactions/reports, authorization have to be taken care of by these application areas in turn.

For authorizations from Area Menu, they must be maintained via transaction SU22 for the generated Transaction codes via IMG.

Hence, the IMG is not designed to carryout any authorization checks for the generated transactions automatically. Necessary transactions have to be maintained in SU22.


Header Data
Release Status Released for Customer
Released on 21.02.2007
Priority Recommendations/additional info
Category Consulting
Primary Component BC-CUS-TOL-IMG Implementation Guide
Secondary Components BC-CUS-TOL-PAD Project Administration (IMG)



Release
Release-Independent


Correction Instructions
No correction instruction available


Support Packages
No Support Packages available


Related notes
No related notes available


Attributes
No attributes available


Attachments
No attachments available