Login
Register

Home

Trainings

Fusion Blog

EBS Blog

Authors

CONTACT US

Oracle Fusion HCM
  • Register

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

webinar new

Search Courses

The following video illustrates the topic of Creating Security Profiles in Oracle Fusion HCM Security

apps2fusion23 PLAY

HCM Secured Objects
The following HCM business objects are secured by default:
• Person
• Organization
• Position
• Legislative Data Group
• Country
• Document Type
• Payroll
• Payroll Flow
Unless you grant access to these objects, users cannot access them.
Granting Access to HCM Secured Objects
To grant access to HCM secured business objects, you Create Security Profile, Included the Security Profile to HCM Data Role and Provide the Date Role to the Users. 

HCM Security Profiles
An HCM security profile is a set of criteria that identifies one or more business objects of a single type, such as persons or positions. The business objects identified by the criteria in the security profile are known as a Data Instance Set. Security profiles identify instances of Human Capital Management (HCM) objects. For example, a person security profile identifies one or more person records, and a payroll security profile identifies one or more payrolls.
You include security profiles in HCM data roles to identify the data that users with those roles can access. You can also assign security profiles directly to abstract roles, such as employee. However, you're unlikely to assign them directly to job roles, because users with same job role usually access different sets of data. For example, you could create security profiles to identify the following data instance sets:
• All contingent workers in a legal employer whose last names are in the range A through H
• All legal employers in the enterprise
• Positions below Regional Sales Manager in the enterprise position hierarchy
• Worker medical records
You can create security profiles for the following HCM object types:
• Person 

       - Managed person - Identifies people you can perform actions against.

       - Public person - Identifies people you can search for in the worker directory

• Organization
• Position
• Legislative data group (LDG)
• Country
• Document type
• Payroll
• Payroll flow
Predefined HCM Security Profiles
The following HCM security profiles are predefined:

23 FHE
You can include the predefined security profiles in any HCM data role, but you can't edit them. The View all option is disabled in any security profile that you create. This restriction exists because predefined security profiles meet this requirement.
HCM Security Profiles Best Practices
Planning your use of HCM data roles and security profiles enables you to minimize maintenance and ease the introduction of HCM data roles and security profiles in your enterprise. 
Identifying Standard Requirements
Most enterprises are likely to have some standard requirements for data access. For example, multiple HCM data roles may need access to all person records in a specific legal employer. If you create a person security profile that includes all person records in that legal employer, then you can include it in multiple HCM data roles. This approach simplifies the management of HCM data roles and security profiles, and may also prevent the creation of duplicate security profiles.
Naming HCM Data Roles and Security Profiles
You're recommended to define and use a naming scheme for HCM data roles and security profiles.A security profile name can identify the scope of the resulting data instance set. For example, the person security profile name All Employees Sales Department conveys that the security profile identifies all employees in the Sales Department. An HCM data role name can include both the name of the inherited job role and the data scope. For example, the HCM data role Human Resource Analyst Finance Division identifies both the job role and the organization within which the role operates. HCM data role names must be less than 55 characters.
Planning Data Access for Each HCM Data Role
An HCM data role can include only one security profile of each type. For example, you can include one organization security profile, one managed person security profile, and one public person security profile. Therefore, you must plan the requirements of any HCM data role to ensure that each security profile identifies all required data instances. For example, if a user accesses legal employers and departments, then the organization security profile in the user's HCM data role must identify both types of organizations.
Providing Access to All Instances of an Object
To provide access to all instances of an HCM object, use the appropriate predefined security profile. For example, to provide access to all person records in the enterprise, use the predefined security profile View All People.


Jayashree Prakash

Add comment


Security code
Refresh

About the Author

Jayashree Prakash

Jayashree Prakash

Jayashree is a Oracle Fusion HCM certified consultant who has over fifteen years' experience with Oracle. She has worked as a consultant with several of Alberta's energy companies. She lives in Edmonton and her interests include staying active in the warmer months and vacationing in the Caribbean in the winter

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Mar 2024  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
      1  2  3
  4  5  6  7  8  910
11121314151617
18192021222324
25262728293031

Enquire For Training

Related Items

Fusion Training Packages

Get Email Updates


Powered by Google FeedBurner