Hierarchy

⤷

⤷

IMG Activity
ID | CPRO_PRP_ROLE | Define Role Types |
Transaction Code | S_APL_52000028 | (empty) |
Created on | 20020703 | |
Customizing Attributes | CPRO_PRP_ROLE | Define Roles for Project Type |
Customizing Activity | CPRO_PRP_ROLE | Define Roles for Project Type |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CPRO_PRP_ROLE |
Use
Resource planning requires you to create roles for each project. In this Customizing activity, you define possible role types and assign them to the project types. These role types are then used as default values in the application when you create roles.
You can make the same assignments in the Customizing activity Define Project Types. We recommend that you use the Define Project Types activity if you want to assign multiple role types to a project type. Use the Define Role Types activity if you want to assign multiple project types to a role type.
The role describes the function exercised by a resource in a project. It contains information about the qualifications the resource must have and when and how long the resource will be available for.
A similar resource description can be found in organizational management where the required resources for the organizational plan are described by the positions.
You can assign authorizations as default values for each role type. If a user staffs a role via his or her business partner of the type 'employee', the authorizations of the assigned role type are set for the user in the project definition or project template.
Note:
- You can only extend existing authorizations.
Example: If 'write' authorization is active for a user in the project definition and the default authorization of the role type is 'read', the authorization is not changed. If, the other way round, 'read' authorization is active and the default authorization is 'write', the authorization for the user is changed to 'write'. - Changing a role type in a role can lead to the users from role staffing having their authorization extended in the project definition or project template.
- If you assign multiple authorizations to the role type within the main authorization chain ('admin', 'write', 'read', 'none'), the system always uses the highest assigned authorization. 'Admin' is the highest authorization, followed by 'write', 'read', and then 'none'.
In addition, you can assign other authorizations of your choice ('evaluate', 'accounting', 'resource management', 'staffing manager', or 'candidate manager') to the role type. - The default authorization does not influence the authorization that is set in a project element if a responsible or editing role or resource is assigned there. In this case, 'write' authorization is always assigned in the relevant project element for the users from role staffing provided that the authorizations 'write' or 'admin' are not already active there.
Requirements
Standard settings
The role types delivered with the standard system (and named accordingly) each have an authorization from the main authorization chain assigned to them.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | CPRO_PRP_ROLE | 0 | APL0000031 | Resources |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
DPR_VC_PART_ROLE | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20090127 |
SAP Release Created in | 200 |