Transferring Employees

Transferring an employee changes the department (or entity) against which their compensation expenses are calculated. Managers transfer employees using either of these processes:

One-step Transfer—Use the Transfer rule if you own both the source and target entities (that is, you have access permissions to the source and target entities).
In a Job only application, use the Transfer Headcount rule. When you run the Transfer Headcount rule, compensation data is automatically calculated.
Two-step Transfer—Use the Transfer Out and Transfer In rules if you don't have access permissions to both the source and target entities. The two-step transfer provides security. For example, it ensures that managers in Department A can't see member data for Department B if they don't have access permissions to the Department B entity. You should transfer out an employee during the same month in which the receiving department transfers in the employee.

After an employee is transferred out, most of their data is cleared in the source as of the transfer month. Applicable Union Code, Employee Type, Pay Type, and Status will remain but the Status will show as Transfer Out. When the employee is transferred to the target, the status is set to Active for the target, and the employee's salary is calculated in the target.
You can transfer an employee across custom dimensions, entities, and job in a one-step or two-step transfer. While transferring an employee from one source to another source, select the target dimension(s) and month for transfer. At least one target dimension must vary from the source or the transfer will fail. Use Basic Details to select core dimensions. Click Additional Details to select custom dimensions. The same applies to transferring headcounts in Job only models also.
When planning an employee’s transfer, make sure you enter a new month that is in accordance with your application’s fiscal calendar, rather than the dates entered for the new hire. Employee transfer is based on fiscal year and month rather than the dates entered for new hire.
In the source's transfer year, most of the employee properties, including FTE and Headcount, are cleared out starting in the transfer month. Applicable Union Code, Employee Type, Pay Type, and Status will remain but the Status will show as Transfer Out.
If the employee transfer month is after the merit month in the year of transfer, merit rates are copied from the source. For subsequent years in the target entity, merit rates are calculated based on the target rates. When the employee is not active, the recommended merit rate is not populated. If the employee transfer month is before the merit month, merit rates are copied from the target.
FTE Assumption and Headcount Assumption accounts are used to calculate values and should never be used for reporting purposes. Use the Total FTE and Total Headcount account hierarchies for all reporting needs, as these reflect the accurate values based on the assumptions, transfers, departures, and so on.

To use the two-step employee-transfer process:

Click Compensation Planning, then Manage Employees, and then Existing Employees.
Click the Actions gear, and then Transfer Out.

Transfer Out causes the employee's name to be displayed in the Review Pending Transfers form.
To transfer the employee into the target department, in Review Pending Transfers, select the employee, then Actions, and then Transfer In.

Tip:

Oracle recommends that you review pending transfers before approving a plan.