The Standard Profiles Infotype (1016)

Definition

The Standard Profiles infotype allows you to link system-defined authority profiles to organizational units, jobs, positions, or tasks (or standard tasks if your company uses Workflow).

Use

Authority profiles control the types of activities users can perform.A profile contains a list of authorizations that control, for example, access to accounting or personnel records. Authorities can also dictate the types of infotypes that users work with in the system. The authorities are valid across all system products. (Authority profiles are user-defined, at installation.)

For more information on authorization profiles, see BC Users, Authorizations and System Security

Authority profiles are applied to R/3 users on an individual basis, one at a time. However, the Standard Profiles infotype offers you a time-saving alternative since you do not have to enter an authority profile for each employee. The profiles related to organizational units, jobs, positions, or tasks are applied to all employees linked with these objects, after you run the report RHPROFL0 (Generate Authorization Profiles). (The connection between objects and employees, and authority profiles is made by running this report.)

The Standard Profiles infotype also allows you to include more than one authority profile in a single infotype record. This feature can be helpful since users sometimes need more than one profile to perform their duties. System administrators, for example, typically require several different authority profiles. Here again, this infotype offers a time-saving benefit.

To restrict the amount of information users can see while working with organizational plans in Personnel Planningt, you must either maintain the PD Profiles infotype, or table T77UA.

You can append Standard Profiles to organizational units, jobs, positions, or tasks (or standard tasks if your company uses Workflow). Before doing so, you should consider the type of object that is best suited for applying authority profiles.

For example, if authority profiles tend to be fairly standard for all workers in an organizational unit, then it may be most effective to apply profiles to organizational units. (Where exceptions occur for jobs or tasks, you can create additional profiles for them.) If, however, authorities vary by job or task, it may be best to apply profile to the jobs or tasks concerned.

It is important to note that the profile linked to a task does not cancel out the profile linked to a position, or job, or organizational unit. One infotype record does not override another. Rather, all profiles that are applied to an object directly or indirectly are considered valid.

Assigning Profiles to Different Organizational Objects

If you assign profiles to

Then

Individual tasks

The assignment is automatically passed on to the related positions and jobs. You can add supplementary authorizations to the jobs and positions, if required.

Jobs and positions

You can identify any special (specific) authorities to tasks, if required.

Organizational units

All jobs and positions assigned to the organizational units receive the same authorizations (and employees, if integration with PA master data is active).