Many of the standard Oracle HRMS windows are multipurpose. For example, in the People window, you can enter or view details of employees, applicants, contingent workers, contacts, or other person types that you have defined. In the Element Entries window, you can make entries for all the elements you have defined.
You might prefer to have multiple versions of these windows, each version being used for just one purpose. This approach restricts the list of values on certain fields and therefore provides for faster data entry. It also enables you to limit access to certain types of information.
For example, you might create a version of the View Element Entry History for Employee window that does not display the earnings elements representing salary, bonus, and commission. Most users' menus would only give them access to this version of the window. For the small group of people authorized to view salary, bonus, and commission figures, your system administrator can define a menu function to allow access to the standard window.
You can do this using CustomForm.
When you create a people management template using the People Management Configurator (see People Management Configurator), you can specify whether the template handles employees, applicants, contingent workers or a combination of all three. This is a quick way to restrict your template windows by system person type. If you need to restrict the template windows by user person type, you can use CustomForm to create a restricted version of your template.
Attention: Make sure that the criteria you enter in the Form Customization window do not conflict with any restrictions you put on the template using the People Management Configurator. For example, if you restrict the template to Applicants Only in the People Management Configurator then create a version that only handles the user person type Graduate Intake (a type of employee), users will not be able to find any people using the template.
You can also use CustomForm to restrict People Management templates in other ways. You can restrict the special information types, extra information types, actions, and notifications that are available from your templates. You can also control the fields available for searching and the new records (applicant, employee, contingent worker, assignment or application) that users can create using the templates.
You can use CustomForm to restrict the information available in the windows listed in the table below. We also identify the criteria you can use to restrict access to information.
| Window | Restrict By | Values |
|---|---|---|
| Adjust Balance: (Oracle Payroll form) | Element Set | User defined |
| Adjust Balance: (Oracle Payroll form) | Element Processing Type | Recurring, Nonrecurring |
| Assignment Folder | Person Type | User defined |
| Element Entries | Element Set | User defined |
| Element Entries | Element Processing Type | Recurring, Nonrecurring |
| Element Entries | Entry Type | Override |
| Event Bookings | Employee or Applicant | Employee, Applicant |
| Extra Assignment Information | Extra Information Type | User defined |
| Extra Element Information | Extra Information Type | User defined |
| Extra Job Information | Extra Information Type | User defined |
| Extra Location Information | Extra Information Type | User defined |
| Extra People Information | Extra Information Type | User defined |
| Extra Position Information | Extra Information Type | User defined |
| List Employees by Element | Element Set | User defined |
| List Employees by Element | Element Processing Type | Recurring, Nonrecurring |
| List People by Special Information | Employee or Applicant | Employee, Applicant |
| List People by Special Information | Special Information Type | User defined |
| List People by Special Information | Person Type | User defined |
| Organization | Organization Classification | List of Organization Classifications |
| Payroll and Assignment Processes: (Oracle Payroll form) | Action Type | List of Action Types (e.g. Run, Pre-payments, Reversal) |
| People Folder | Person Type | User defined |
| People (PERWSEPI), People and Assignment (PERWSHRG): (Enter Personal Information) | Person Action | User defined |
| People (PERWSEPI), People and Assignment (PERWSHRG): (Enter Personal Information) | Person Function | User defined |
| People (PERWSEPI), People and Assignment (PERWSHRG): (Enter Personal Information) | Person Type | User defined |
| People Management | Person Type | User defined |
| People Management | Special Information Type | User defined, and some may be predefined |
| People Management | People Extra Information Type | User defined, and some may be predefined |
| People Management | Assignment Extra Information Type | User defined, and some may be predefined |
| People Management | Actions | List of available actions such as Hire Applicant |
| People Management | Workflow Notifications | Notifications defined in workflow; some predefined, you can add others |
| People Management | New Objects | New Applicant, New Employee, New Application, New Assignment |
| Position Occupancy Folder | Employee or Applicant | Employee, Applicant |
| Run QuickPaint Report | QuickPaint Inquiry | User defined |
| Run QuickPaint Report | Person Type | User defined |
| Run QuickPaint Report | Assignments | Assignment Sets, Assignments |
| Special Information | Special Information Type | User defined |
| Table Values: (Define User Values) | Table Name | User defined |
| View Element Entry History for Employee | Element Set | User defined |
| View Element Entry History for Employee | Element Processing Type | Recurring, Nonrecurring |
You can restrict the information that appears in a window by the following sorts of criteria:
Element processing type (recurring or nonrecurring)
Element set (user defined)
Person type (user defined)
Special information type (user defined)
Organization classification
Employee, applicant, or contingent worker
Note: If you choose to restrict access to your form by person type, you select the person type and then choose whether to include or exclude this person type.
QuickPaint report (user defined)
Extra Information Type (user defined)
Action for People Management
Workflow notification (user defined)
New objects that you can create using the People Management window
Fields you can search on using Advanced Find in the People Management window. The fields you select are excluded from the Advanced Find.
Attention: When you use a standard window, all types of information are available. When you use a configured version, you can only see the types of information that were selected on the Form Customization window. However, there is one exception. When you restrict the People Management window by Advanced Find Item, you can search in the configured version of the window on all Find items except the ones you selected on the Form Customization window.
If you want to restrict the data by a user defined information type, you must create it first:
To restrict by element set, create the set in the Element and Distribution Set window.
To restrict by QuickPaint Report, create the report in the Define QuickPaint Report window.
To restrict by Special Information Type, define your information type as an instance of the Personal Analysis key flexfield.
To restrict by person types, define your user person types in the Person Types window.
To restrict by Extra Information Type, define your information type as an instance of the appropriate extra information flexfield.
See: Setting Up Extra Information Types (Excluding Organization EITs)
To restrict by workflow notification, create your notifications using Oracle Workflow.
With selected restriction types, you can choose to include or exclude specific types. This is currently only possible with the Person Type restriction. In this case, the system checks whether any of the person types assigned to a person match any of the person types included or excluded using the Person Type restriction.
The different scenarios are best illustrated using examples. In each case, the employee has the person types of Employee and Applicant.
Scenario 1
| Included Person Type | Excluded Person Type |
|---|---|
| Employee |
Result: The employee is visible in the form. In this case, all persons with the person type of Employee are visible.
Scenario 2
| Included Person Type | Excluded Person Type |
|---|---|
| Employee |
Result: The employee is not visible in the form. In this case, all persons with the person type of Employee are excluded and all other persons are visible.
Scenario 3
| Included Person Type | Excluded Person Type |
|---|---|
| Employee | Applicant |
Result: The employee is not visible in the form. Even though the employee has the Person Type of Employee, which is included according to the restriction, the Excluded Person Type of Applicant takes priority over the Included Person Type and the employee is not visible in the form.
Note: It is not possible to include and exclude the same person type.