Best practices for implementing the secondment process and using the Global Temporary Assignment

We are seeking guidance on Oracle’s recommended best practices for using the out-of-the-box Global Temporary Assignment functionality for secondments.

Key Concerns:

• When an employee is seconded, a new assignment record is created while the original assignment remains in a suspended status.
• For longer secondments (typically one year or more), employees often experience multiple assignment and salary changes on the temporary assignment.
• The original assignment record remains unchanged during the secondment; therefore, when the employee returns, none of the updates or history from the temporary assignment are reflected on the source assignment.
• For example, for our first returned employee (Employee123), the source assignment salary was two levels below what the employee was earning abroad, further compounded by year-end salary increases. This outcome raised concerns about whether this behavior aligns with our original expectations.