ORACLE HUMAN RESOURCES

1. What are the seeded Person Types?
Person types are used to describe people entered into the Oracle Human Resources product. The person types names may be modified if needed, or new person types can be added. In 10.7 and 11.0.3 there are eight person types delivered by the system, and identified by a system name. For each, there is a predefined user name. You can change the predefined name and you can create unique user names.
The 10.7 and 11.0.3 delivered person types are:
Applicant
Applicant and Ex-Applicant
Employee
Employee and Applicant
Ex-applicant
Ex-employee
Ex-employee and Applicant
External
In 11i additional person types have been delivered to accommodate legislations
and customers using 11i benefits modules.
The information is stored in PER_PERSON_TYPES.
In 10.7 and 11.0.3 go to PER_ALL_PEOPLE_F to PER_PERSON_TYPES. In 11i go to PER_PERSON_TYPE_USAGES_F and then to PER_PERSON_TYPES.

2. Where do I add or change the person types? (10.7/11.0.3 & 11.5.x)
In application versions 10.7, 11.0.3 and 11.5.x follow this navigation:
Other Definitions > Person Types.
To change a user name for a Person Type:
Delete the contents of the User Name field and type in your preferred name. To map other User Names to a Person Type system name:
A. Select New Record from the Edit menu.
B. Enter a unique User Name and select the System Name to which you want to map.
Deactivating User Names
You cannot delete User Names in use in the system, but you can deactivate them by unchecking the Active check box. Notice that you cannot deactivate a default User Name. You must first select another User Name as the default.

3. Can external Person Types be contacts?
Yes, anything defined with a System Name of External is considered a contact and will appear in the Contact Type list of values. A contact is someone associated with an employee or an applicant. For example, people who are dependents of employees, people whom employees name as beneficiaries, and people whom employees list as their contacts in case of emergency are all entered as contacts.

4. There is a new form in application version 11.5.x called Person Type Usage. How
does this work in connection with the person types?
This new form in 11.5.x (Navigation: People> Enter & Maintain, Others) is called Person Type Usage. If you need to change the user value for any person type applied to a person, you do this in the Person Type Usages window, which is now datetracked for HR user person type changes. The information is stored in the table: PER_PERSON_TYPE_USAGES_F. The form is also used by 11i Benefits module customers for managing benefits.

5. What is the difference between the Contact Type and the Relationship Type on the Contact form (PERWSDPC)?
The Type field refers to the Person Type as defined in the Person Types form. The information is stored in the PER_PERSON_TYPES table. It is defined and maintained in the Person Types (PERWSDPT) form located under Other Definitions off the main navigation menu. Anything defined with a system name of external is considered a Contact and will show up in the Contact Type list of values.
The Relationship Type refers to the definition of the association that this contact has to the employee (i.e. spouse, emergency contact, friend, etc.). The information is stored in the PER_CONTACT_RELATIONSHIPS table. The list of values is created and maintained in the Other Definitions > QuickCode Values navigation on the main menu.

6. Why does the Person Type that I just created not show up on my list of values on the Enter and Maintain form?
If the Person Type has a system name of 'External' then that Person Type is not eligible for this list of values. 'External' system name values are Contacts.

7. How do I delete or end date a Person Type?
Person Type cannot be deleted or end dated. The Person Type may only be deactivated. Navigate to Other Definitions > Person Types. The user may either check or uncheck the Active column.

8. What has happened to the 11i person types since applying PER G (1988754)?
After applying PER G, the person type field is not available for direct updates on the Person form. (Navigation: People > Enter & Maintain) The functionality of this field has been changed. The Type field (person_type) now works in relation to the Action field that appears under the Type.
These changes were also explained in the PER G readme.
The manner in which person types are recorded against a person has been changed to enable you to record multiple person type records against a person. Now you can update a person's type using the new Actions field available on the People form. For example, when you create a new employee select the Create Employment action and a list of user person types for the system person type of Employee is displayed for your selection. If this person also becomes an applicant, you select the Create Applicant action and an applicant record is created for the person. The Type value now displayed will be Employee.Applicant.
Previously, using the example above, this person would have been given a single person type of 'Employee and Applicant'. With this new functionality this person will have two records, one Employee and one Applicant. This is displayed in the Type field as a concatenated version of the two types. If you are using the default user values for these types, the value displayed is Employee.Applicant.
If you need to change the user value for any person type applied to a person, you do this in the Person Type Usages window, which is now datetracked for HR user person type changes.
Navigation: People > Enter & Maintain, Others.
This means you can reduce the number of system person types that need to be maintained and offer greater flexibility in defining person type combinations. The eight system person types previously recognized by the application continue to be maintained for existing persons but can no longer be used for new records in 11i.
Because of this update you may need to make a few changes to your application in order for it to work with the latest data.
If you are using the USER_PERSON_TYPE column of the PER_PERSON_TYPES table
in your custom reports or forms you must redirect them. Instead of going from PER_ALL_PEOPLE_F to PER_PERSON_TYPES, you will need to initially join to PER_PERSON_TYPE_USAGES_F and then go to PER_PERSON_TYPES.
If you have any formulas that use the following database items, you should replace them with the new items as the current ones will be obsoleted in a future patch. See the following listed columns of Current DB Items and its corresponding New DB Items.
Current DB Item: New DB Item:
PER_PERSON_TYPE PTU_PER_PERSON_TYPE
CON_PERSON_TYPE PTU_CON_PERSON_TYPE
REC_PERSON_TYPE PTU_REC_PERSON_TYPE
SUP_PERSON_TYPE PTU_SUP_PERSON_TYPE
The new person type usages model enables you to have more flexibility when using person type as a parameter to create customized windows. You should no longer need be able to customize windows by Person Function and therefore this option will be removed.