1. To enter a new assignment:
1. Select the organization to which you want to assign the employee. The default
organization is the Business Group.
If a location is defined for this organization, it also appears as a default.
2. Select the job, position, and supervisor for the employee's assignment.
The employee's supervisor is the default next approver for all purchasing documents if
the Use Approval Hierarchies check box in the Financial Options window is checked.
3. The Set of Books field displays the set of books for your installation. The Default
Expense Account field displays the concatenated description of the Account.
In some applications, you can select another flexfield structure that the employee's
expenses should debit. Oracle Payables uses this information to generate expense reports
for your employees.
4. Select a location for the assignment. The address of this location is displayed.
Updating Employee Assignments Over Time
Project Accounting users can select the Assignment History region to view and update employee
assignments over time.
The date fields in this region display the start and end dates of the assignment.
In the New Assignment region, you can insert a change to the assignment, as from a particular
start date. The Assignment History region shows one row for every change to the organization,
job, location, manager, or billing title of the assignment. Each row is valid between the dates
shown at the bottom of the Assignment History region.
To insert a change to an assignment:
1. Query the assignment you want to change in the Assignment History alternative region
of the Person Information window.
2. In the New Assignment region, enter the start date of the change.
The other fields in this region display the values that are valid at this date.
3. Update any of the values in the New Assignment region, and save your changes.
Action Sequence: 10
Action Type: Property
Action Object Type: Item
Action Target Object: PERSON.D_TITLE

2. Action Property Name: REQUIRED
Action Value: TRUE
STEP 2
Create another Personalization as below ( to make Title field Optional)
Sequence: 51
Description: Make Person Title Mandatory when Person Type is Employee.
Trigger Event: WHEN-NEW-ITEM-INSTANCE
Trigger Object: PERSON.PTU_ACTION_TYPE
Condition: NVL(${item.person.d_ptu_user_person_type.value},'xxyyzz') != 'Employee'