When you use the Global Deployments function to transfer an employee temporarily to another business group, HRMS automatically:

• Creates or updates employee records in the destination business group

• Suspends the employee's current assignments in the source business group

During the secondment, the employee has records to maintain in both business groups.

Maintaining Employee Records in Multiple Business Groups

HRMS provides standard mechanisms for maintaining employee data in multiple business groups:

• Employees have both local records (at the business-group level) and a corporate record (which links records for the same employee in multiple business groups). Some employee data is held in the corporate record, and the application automatically applies changes made to that data in one local record to all local records for the employee.

  See: People in a Global Enterprise

• HRMS can automatically synchronize person data that is considered to be global and that is held in multiple business groups for the same employee, such as e-mail address and correspondence language.

  See: Person Record Synchronization

Creating and Maintaining Optional Records

When the HR Professional initiates a deployment, HRMS does not create most optional components of the employee record, such as the competency profile and the qualifications record. However, the following records are visible by default from other business groups:

• Qualifications

• Establishments Attended

• Competency Profile (global competencies only)

You may need to create and maintain such records manually in the destination business group if, for example, you want to perform an appraisal or record additional competencies achieved during a secondment.

Returning from Secondment

When a secondment ends, HRMS automatically:

• Terminates the employee record in the destination business group

• Reinstates suspended assignments in the source business group

During a secondment, HRMS can maintain most employee data automatically. However, you are recommended to review employee records in the source business group when a secondment ends and make any additions or corrections. For example, you may want to update the employee's competency profile or qualifications record.

If person record synchronization has not been enabled during the secondment, run the Person Synchronization report to identify differences and make any changes manually.

See: Person Record Synchronization

Data Items Transferred During the Predefined Global Deployment Process

Following is a list of data items transferred during a deployment in the predefined Global Deployment process:

• Person Type

• Department

• Position

• Job

• Grade

• Location

• New Manager (Name, Assignment Number and Department. Oracle HRMS retains direct reports in case of permanent deployment)

• Dependents (if any)

• Employee Number (will be transferred to the destination business group if there is no such employee number in the destination business group, otherwise the application prompts to enter the valid employee number for the destination business group)

• Segments mentioned in the Person developer descriptive flexfield

• Payroll Name

• People Group Name

• Assignment Status

• Assignment Status Change Reason

• Assignment Category

• Adjusted Service Date (if any)

• Work Schedule

• Person Extra Information Type (EIT) (Displays the list of EITs available while creating deployment proposal. User can select the ones that need to be transferred to the destination business group).