Manage Workforce Lifecycle in Oracle Fusion HCM – Part 1
Managing the Workforce Lifecycle in Oracle Fusion HCM process encompasses every phase of an employee’s relationship with the organisation, from creating a personal record to ending work relationships. Human Resource (HR) Specialists and Line Managers perform the following activities:
- Add Person
- Manage Employment Information
- Change Employment
- Promote Worker
- Transfer Worker
- Terminate Worker
- Manage Personal Information
HR specialists access the Add Person task in the New Person work area, while all other tasks related to managing the Workforce Lifecycle in Oracle Fusion HCM are accessible through the Person Management work area. Line managers can access tasks via gallery search results, worker portraits, and the Manager Resources Dashboard.
Master Oracle Workforce Compensation – Salary Update Integration with our Mini Mastery course, perfect for rapid skill-building.
Add Person: Creating Person Records
A person’s record is created in situations such as:
- Hiring a new employee
- Adding a contingent worker
- Adding a non-worker
- Adding a pending worker
- Adding a contact to another person’s record
In Oracle Fusion, a person’s record is global, independent of any legal employer, and created only once per individual. If someone leaves the organisation, their work relationships are ended, but the person’s record remains. Should they return to the organisation, a new work relationship is established while the original person’s record continues to exist, even if they have no active work or contact relationships.
The following examples clarify when to create a person’s record versus a work relationship. In every case, if an existing person record is found, you proceed by setting up a work relationship for that person.
Adding a Person
Consider a scenario where Jayashree Prakash is beginning a position as a ‘Contingent Worker’ with a legal employer in the organisation. Jayashree has no prior history as an employee, contingent worker, or non-worker within the organisation’s legal entities. Additionally, she has never served as an emergency contact, dependent, or beneficiary for any other employee, contingent worker, or non-worker in the organisation. Since Jayashree has no existing person record, adding her as a contingent worker will establish both her person’s record and her initial work relationship.
Rehiring an Employee
John is set to begin employment with the organisation in France next month. He previously worked with the organisation in the United States but resigned three years ago. Since John was previously employed, he already has an existing person’s record. When you initiate the rehire, the system locates his person’s record. After confirming it is indeed John’s, you proceed with the rehire by establishing an employee work relationship with his new legal employer in France.
Hiring a Nonworker
Smruti currently holds a nonworker relationship with a legal employer, having served as a volunteer mentor for young workers for several months. Recently, Smruti successfully applied for employment with the same employer and plans to continue in the volunteer role even after being hired. When you initiate the hiring process, the system identifies Smruti’s existing person record. After verifying it, you proceed by establishing an employee work relationship with the legal employer. This results in Smruti holding both nonworker and employee relationships with the same employer.
Hiring a Contact
Mary Wood is set to begin working with the organisation tomorrow. She has no prior experience as an employee, contingent worker, or nonworker with any legal employer in the enterprise. However, she is married to Joe Wood, a contingent worker within the organisation, who has listed Mary as an emergency contact. As a result, Mary already has a person’s record. When initiating the hiring process, if Mary’s contact record has sufficient information for identification, the application locates her existing person’s record. In this scenario, you proceed by establishing an employee work relationship with her new legal employer. If not, the hiring process will create both her person’s record and work relationship.
Work Relationships for Workforce Lifecycle in Oracle Fusion HCM
A work relationship defines the connection between an individual and a legal employer. It establishes the context for a person’s assignments and is used to calculate service with both the enterprise and the legal employer. Each work relationship must include at least one assignment.
Types of Work Relationships
Work relationships are categorised into three types: Employee, Contingent Worker, and Nonworker. The type of worker selected when establishing a work relationship determines its classification.
Nonworker Work Relationships
A person is classified as a nonworker by holding a nonworker work relationship with a legal employer. This relationship does not imply active employment with the legal employer; rather, it signifies an established association between the individual and the legal employer through the work relationship and assignment.
Primary and Secondary Work Relationships
Each worker or nonworker is required to have one primary work relationship; all other relationships are secondary. By default, a person’s initial work relationship is considered primary. The primary work relationship includes the person’s main assignment, which may be referenced when only one assignment is needed, such as for certain government reports. Typically, a primary work relationship and assignment hold the greatest importance for the person, impacting factors like status, pay, benefits, and working hours.
Ending the Primary Work Relationship
Work relationships are what you terminate, not the workers or nonworkers themselves. If a person has multiple active work relationships, the primary one cannot be terminated until another primary relationship is designated. This rule is in place to ensure that a current worker or nonworker always has a primary work relationship without any gaps.
Identifying Matching Records for Workforce Lifecycle in Oracle Fusion HCM
As an HR specialist, the application identifies a match for a new person record if at least one national ID value matches an existing person record. Records with non-matching national IDs may still be considered matches if they meet at least one of the following criteria:
The first name, the initial of the last name, and the date of birth are identical.
The last name, the initial of the first name, and the date of birth are identical.
Even if one of these criteria is absent, the application will still recognise the record as a match if the other two criteria align.
Conclusion
Managing the Workforce Lifecycle in Oracle Fusion HCM effectively handles all aspects of an employee’s relationship with the organisation, from record creation to termination. HR specialists and line managers ensure the accurate establishment and maintenance of person records and work relationships, facilitating seamless transitions in hiring, rehiring, and management.
