Person Types

You use person types to identify different groups of people in your enterprise.

For example, for purposes of reporting, you might want to identify the following:

• Contractual workers in your enterprise with the Contingent Worker person type.
• Regular employees with the Employee person type.

On the basis of the person type, you can:

• Maintain information for a group of people
• Secure access to information

System Person Types

These are predefined person types that the application uses to identify a group of people. You can't change, delete, or create additional system person types.

Not Managed by HR System Person Type

Not Managed by HR (NMBHR) is a system person type that’s used for nonworkers who are neither employees nor contingent workers, and they’re primarily managed in a system or process other than Oracle Fusion HCM. For more information about NMBHR, see What’s the Not Managed by HR system person type?

Person Security Profile

You need to review your person security profiles if you want to search and view people that are created with this system person type. You can choose any of these options.

• The person security profile might be defined without a reference to person types. In such case, you can review and test the profile to ensure that the criteria includes people with this system person type.
• You can create a new person security profile with Not Managed by HR system person type.
  • You must not use Employee, Contingent Worker, Nonworker, or Pending Worker person types in the same security profile. This is a known limitation of the person security profile.
  • You need to create a new role associated with this security profile and assign it to users who need access to people with this system person type.
• You can create a new person security profile and use custom SQL.
• You can use the Oracle-delivered 'View All People' person security profile.

User Person Types

Each system person type contains a user person type that you can configure to your requirements. You can change, remove, or create additional user person types to suit your enterprise requirements. For example:

• If your enterprise refers to its employees as associates instead of employees, you change the Employee user person type to Associate.

• You can also add user person types under the Employee system person type. For example, if you want to classify employees further as equity partners, nonequity partners, and associates,

  Note:

  When you create, delete, or cancel a person type work relationship record, then the person type usages record is deleted and recreated for that worker. As a result, a new person type usage ID is generated for the worker.