Manage People and Roles in Oracle ERP HRMS

HCM

1. Copyright © 2007, Oracle. All rights reserved.
Managing People and Roles

2. Copyright © 2007, Oracle. All rights reserved.
Objectives
After completing this module, you should be able to:
•Discuss roles and privileges
•Create and update roles

3. Copyright © 2007, Oracle. All rights reserved.
Agenda
•People and Roles Administration Overview
•Managing Roles
•Summary

4. Copyright © 2007, Oracle. All rights reserved.
Item Security Levels
In many Oracle applications, there is limited security for item
information. For example, you have access to the Item Master
or you do not. You might not have update access, but you
probably have view access.
•Forms Menu Exclusions
•Inventory Organization Access
•Forms Personalization

5. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario
Vision Operations
•Builds computers and PDAs
Industrial
•Supplies components for the computers
•Competes with Vision Operations in the PDA segment
•Requirement
–Industrial must have the ability to view Computer product
information, but should not have the ability to view PDA
product information.

6. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Item/Product Information
•Marketing
•Engineering
•Sales
•Pricing
•Cost
•Sourcing
•Strategy
•Distribution
•Manufacturing
•Planning
•Suppliers
•Customers
•Compliances groups
•Maintenance
•Service and after market
•Quality department
•Manufacturing reps
•C - Level

7. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Using Item Information
•Using data on a day-to-day basis:
–Planning
–Costing
–Order Management
–Purchasing
•Strategic needs - possible proprietary data:
–Design impacts
–Marketing and campaigns
–Sourcing
–Compliance groups
–Pricing guidelines

8. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Processing Attributes
Item Attributes
Order
Management
Item Attributes
Item Attributes
Item Attributes
Item Attributes
Item Attributes
Item Attributes
Inventory
Main
Bills
Cost
Purchasing
MPS/MRP
Planning

9. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Data Issues
•Data is required to operate the system, so data is made
available.
•Proprietary or confidential data is not required for system
operation.
•Data is kept in different areas and formats, creating
fragmented data. For example, data may be segmented as
follows:
–Design data
–Pricing data
–Marketing data
–Compliance data

10. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Bringing it Together with Security
Main
Purchasing
Order
Management
Item Attributes
Item Attributes
Item Attributes
Item Attributes
Design Data Pricing DataMarketing DataCompliance Data
MPS/MRP
Planning

11. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Solution Steps
1.Create user-defined attributes and associate them with
items.
2.Create attribute access security.

12. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Solution Thought Process
Item Attributes
Order
Management
Item Attributes
Item Attributes
Item Attributes
Purchasing
MPS/MRP
Planning
Main
Design Data
Pricing Data
Marketing
Data
Compliance
Data
User Defined
Attributes
User Defined
Attributes
User Defined
Attributes
User Defined
Attributes

13. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Step 2 - Create Security
•Ensure that those roles who need to maintain data can grant
permission to update data.
•Ensure that those roles who need to view the data can grant
permission to view data.
•Ensure that those roles who do not require access cannot
find data; therefore, deny permission to discover data.

14. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Create Privileges to Data
View Compliance Data Privilege
Update Compliance Data Privilege
Design Data
Pricing Data
Marketing
Data
Compliance
Data
User Defined
Attributes
User Defined
Attributes
User Defined
Attributes
User Defined
Attributes
View Design Data Privilege
Update Design Data Privilege
View Pricing Data Privilege
Update Pricing Data Privilege
View Marketing Data Privilege
Update Marketing Data Privilege

15. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Privileges Defined
Design Data Pricing Data Marketing DataCompliance Data
Roles UpdateView UpdateView UpdateView UpdateView

16. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Roles Needing Permission
To complete daily responsibilities or jobs:
•What roles require permission to view data?
•What roles require permission to update data?
•Define a role for that person.

17. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Privileges Granted to Jobs or Roles
Design Data Pricing Data Marketing DataCompliance Data
Role UpdateView UpdateView UpdateView

Update
View
Design
Engineer
X X
Marketing
Manager
X X
Compliance
Manager
X X
Pricing
Manager
X X

18. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Who has the Position in the Organization
•There are many users defined in the organization.
–Each user may have many jobs or positions within the
organization.
–Each user does not necessarily require access to product and
item information.
–Each user may have multiple roles.
–Each role has multiple privileges.

19. Copyright © 2007, Oracle. All rights reserved.
User and Role Scenario:
Users Assigned to Jobs or Roles
Design Data Pricing Data Marketing DataCompliance Data
Role UpdateView UpdateView UpdateView UpdateView
ABRISLEY
Design
Engineer
X X
Marketing
Manager
X X
JSMITH
Compliance
Manager
X X
Pricing
Manager
X X

20. Copyright © 2007, Oracle. All rights reserved.
Agenda
•People and Roles Administration Overview
•Managing Roles
•Summary

21. Copyright © 2007, Oracle. All rights reserved.
People and Roles - Concepts
•Privileges
•Roles
•Role Types
–Item Catalog Category Role
–Item Role
–Change Role
–Catalog Role
–Group Role
•Role Assignment

22. Copyright © 2007, Oracle. All rights reserved.
Business Requirement – Scenario
Scenario:
•Steve Williams and Mary Robinson are Product Managers
for Vision Engines.
–Steve Williams is responsible for the Diesel Engines product
–Mary Robinson is responsible for the Electric Motors product
•Steve Williams needs permission (or the privilege) to create
new items for diesel engines.
•Mary Robinson needs permission (or the privilege) to create
new items for electric motors.

23. Copyright © 2007, Oracle. All rights reserved.
Managing Roles
As the People and Roles Administrator, you are responsible for
creating and maintaining the roles required by your enterprise’s
Product Lifecycle Management implementation:
•Manage Roles: You can update roles
•Create Roles: You can create roles

24. Copyright © 2007, Oracle. All rights reserved.
Managing Roles
Managing roles includes the following tasks:
•Defining change roles (required)
•Defining item roles (required)
•Defining item catalog category roles
•Defining catalog roles

25. Copyright © 2007, Oracle. All rights reserved.
Change Roles
Change roles enable access to change data and objects, such
as ideas, files, issues, change requests, and change orders.
•Change Role Mapping is performed for change objects not
related to items, such as issues or ideas
•Some seeded change roles:
–Change Design Engineer
–Change Engineering Manager
•All change roles have the same privileges:
–View basic change information
–Edit and delete change role assignments

26. Copyright © 2007, Oracle. All rights reserved.
Item Roles
•Oracle system-defined item roles:
–Item Author
–Design Engineer
–Third Party Reviewer
–Design Reviewer
–Supplier Engineer
•User-defined item roles (define as many as you need)
•User-defined item privileges (define as many as you need)

27. Copyright © 2007, Oracle. All rights reserved.
Item Catalog Category Roles
Enables creation of new items within an Item Catalog Category.
•Oracle system-defined item catalog category roles
–Item Catalog Category User
•Oracle system-defined item catalog category privileges
–Create items within an item catalog category

28. Copyright © 2007, Oracle. All rights reserved.
Catalog Roles
Following are the seeded catalog roles in the Product Lifecycle
Management application:
•Catalog Manager
•Catalog Viewer

29. Copyright © 2007, Oracle. All rights reserved.
Defining Roles

30. Copyright © 2007, Oracle. All rights reserved.
Viewing Roles
You can view roles to examine the privileges that are
associated with them.
However, you must have the View Role function to access
roles.

31. Copyright © 2007, Oracle. All rights reserved.
Creating and Updating Roles
Administrators must have the Manage Role and Create Role
functions to create and update roles.
If you only have the Manage Role function, then you can only
update roles.
If you only have the Create Role function, you can only create
roles.
Both functions are required to manage roles.

32. Copyright © 2007, Oracle. All rights reserved.
Agenda
•People and Roles Administration Overview
•Managing Roles
•Summary

33. Copyright © 2007, Oracle. All rights reserved.
Summary
In this module, you should have learned how to:
•Discuss roles and privileges
•Create and update roles