SAP Basis

ADM100 Lesson: Authorization Concept
for the authorization. The above example deals with access to files. Role
maintenance cannot “guess” whether data access should only be read
access, or should be read and write access.
Some fields appear in many authorizations. A number of important fields
were therefore combined into organizational levels, such as the company
code. If you maintain the organizational level, you maintain all fields in
it. Therefore, a red traffic light indicates an unmaintained organizational
level.
Once all authorizations are maintained as required, the authorization
profilecanbegeneratedbychoosingGenerate. Important: The second
character of the profile name must not be an underscore (“_”) (see
SAP Note 16466). After creation, this name cannot be changed. The
authorizations are combined in profiles. The profiles must be entered in
the user master record (by the role maintenance) for the authorizations
to take effect for the user.
Users and Roles
Assign users, for example from the demo above: TestAdmin (alternatively,
you can use the user Admin, to which no roles are assigned), and save.
Display in transaction SU01 how a role (such as ZPFUD) is assigned here.
The assignment of users to roles is performed in the role maintenance
transaction (transaction PFCG) or in the user maintenance transaction
(transaction SU01). Select the tab page User and the user IDs to be
maintained there. When selecting user IDs, the system uses the current
date as the start of the validity period of the assignment; it sets 31.12.9999
as the end date. You can restrict both values.
2003/Q3 © 2003 SAP AG. All rights reserved. 421