The Employment Model in Oracle Fusion HCM is designed to support diverse and evolving workforce structures across global organisations. Whether you’re managing straightforward employment scenarios or complex, multi-assignment setups, understanding how this model functions is essential for HR professionals. This blog explores the core components of the Employment Model in Oracle Fusion HCM, including work relationships, assignments, and employment terms, to help you configure your system efficiently and effectively.

Understanding Employment Terms in Oracle Fusion HCM 

The Employment Model in Oracle Fusion HCM is built to handle both straightforward and complex global workforce scenarios. Unlike Oracle EBS, where an employee with work relationships across two Legal Entities requires separate Assignment records in each, Fusion HCM allows this to be managed centrally. Since it operates on a global framework, a single record is sufficient even if the employee is linked to multiple Legal Entities. This global person concept significantly benefits multinational organisations by enabling accurate representation of employment relationships within the enterprise. 

Advantages of using Employment Term

Employment Terms offer flexibility and ease in managing a worker’s association with multiple legal employers, multiple assignments, or distinct contractual arrangements. When an individual is expected to hold several similar assignments within a work relationship, those assignments can automatically inherit details defined in the employment terms. This approach enhances efficiency by allowing information to be entered just once, ensuring consistency across related assignments. Additionally, it provides control by enabling restrictions or limitations on direct changes at the assignment level. 

When setting up the Employment Model, if your enterprise or legal employer has restricted overrides at the assignment level, any details inherited from Employment Terms cannot be modified directly in the assignment. Instead, changes must be made within the Employment Terms, and those updates will automatically apply to all linked assignments. This method is ideal when you want to enforce consistent values for specific assignment attributes. It’s important to note that this restriction only applies to fields inherited from the Employment Terms. For example, if working hours are not defined in the Employment Terms, you can assign different working hours to each associated assignment. 

Types of Employment Models 

Oracle Fusion HCM offers two distinct employment model options: the Two-Tier model and the Three-Tier model. 

These models can be set up at either the enterprise level or the legal employer level, with the legal employer configuration overriding the enterprise setting when both are defined. 
By default, Oracle Fusion HCM is configured to use the Two-Tier model, which operates with a single assignment structure. 

Take your expertise to the next level with our
Oracle Fusion HCM Core Implementation Training

If a Three-Tier model is selected, the HR specialist has the ability to specify whether information defined in the employment terms can be modified at the assignment level. 

Three-Tier Employment Model 

The Three-Tier Employment Model includes three components: Work Relationships, Employment Terms, and Assignments. It allows users to capture contract-related information within the employment terms. When setting up the employment model at either the enterprise or legal employer level, you have four configuration options to choose from within this model. 

Single Employment Terms with Single Assignment 

In this setup, every work relationship is associated with a single set of employment terms, which in turn connects to one assignment. The system automatically creates both the employment terms and the assignment during the creation process. 

Single Employment Terms with Multiple Assignments 

In this setup, a single work relationship includes one set of employment terms that may be linked to one or more assignments. As soon as the work relationship is created, the system automatically generates the employment terms along with the initial assignment. Any extra assignments must be added manually. These additional assignments can either be associated with the existing employment terms or maintained independently. 

Multiple Employment Terms with Single Assignment 

In this configuration, a work relationship may include multiple employment terms, where each term is linked to a single assignment. When a work relationship is initiated, one set of employment terms along with its corresponding assignment is created by default. Any additional sets of employment terms and their respective assignments need to be added manually. These added assignments can either be tied to specific employment terms or maintained independently of them. 

Multiple Employment Terms with Multiple Assignments 

In this configuration, one work relationship may consist of several employment term sets, and each set can be linked to one or multiple assignments. When the work relationship is initially created, one set of employment terms along with a related assignment is generated automatically. Additional employment terms and their corresponding assignments need to be entered manually. These additional assignments may either be linked to specific employment terms or managed independently. 

Two-Tier Employment Model 

The two-tier model consists of two primary components: work relationships and assignments. It differs from the three-tier model by not incorporating employment terms. When setting up the employment model at either the enterprise or legal employer level, you can choose from three available two-tier configurations. 

Single Assignment 

When the Single Assignment option is selected, every type of work relationship is limited to just one assignment. This assignment is automatically generated as soon as the work relationship is established. 

Single Assignment with Contract 

When the Single Assignment with Contract option is used, contract details can be added directly to the assignment. This setup is ideal for regions where employment regulations mandate the inclusion of contract data, allowing compliance without the need for a three-tier employment model. Once the work relationship is created, the system automatically generates the assignment, while adding contract information remains optional. 

Multiple Assignments 

When the Multiple Assignments option is selected, a single work relationship—regardless of its type—can have more than one assignment. The first assignment is automatically created during the setup of the work relationship, while any additional assignments can be added manually if needed. 

Changing the Employment Model 

The employment model for either the enterprise or a legal employer can be configured during the initial implementation or modified later. However, there are specific conditions that must be met when transitioning between certain employment models. You can make the following changes: 

• Move from a two-tier model to a three-tier model only if there are no existing work relationships within the enterprise or legal employer. 
• Shift from a three-tier model to a two-tier model only if no work relationships currently exist. 
• Switch between any of the available three-tier configurations at any time. 
• Change from Single Assignment to Multiple Assignments. 
• Change from Single Assignment to Single Assignment with Contract, and vice versa, provided there are no existing work relationships. 
• Transition from Multiple Assignments to Single Assignment. 
• Move from Multiple Assignments to Single Assignment with Contract. 

Conclusion 

A well-configured Employment Model in Oracle Fusion HCM is key to maintaining data consistency, ensuring compliance, and optimising HR processes. By selecting the model that best aligns with your organisation’s structure—whether two-tier or three-tier—you can streamline operations and improve workforce management. With a solid grasp of the Employment Model in Oracle Fusion HCM, HR teams can confidently adapt to business needs while maintaining control and flexibility in their HCM environment.