Business Units And Set IDs in Oracle Fusion HCM – Part 1
Business Units and Set IDs, originally introduced in PeopleSoft, have been incorporated into Fusion Applications. In a Global Human Resources implementation, you’ll encounter various enterprise structures and work structure tables that require your attention. These include enterprises, legal entities or employers, divisions, business units, departments, locations, jobs, etc. Business units and set IDs interact with several of these work structure tables, making it essential to make informed decisions during implementation.
If you’re unfamiliar with Business Units and Set IDs, this blog aims to provide you with a foundational understanding to help you configure business units and reference sets within Fusion applications.
In the diagram above, there’s a fictional enterprise called Jay Corp. In a Fusion HCM setup, there is a single enterprise, which acts as a firm boundary between one client and another. Beyond this, there are various layers such as Legal Entities and Divisions. However, the focus here is on Business Units. These are mandatory, and at least one must be created. Business Units serve as a way to organise your company, either by line of business or geographic region. In this example, Sales, Marketing, and Manufacturing represent the Business Units within Jay Garments.
Dive deeper into mastering Business Units and Set IDs with our
Oracle Core HCM Training: Applications and Best Practices
The key decision here is determining which options should be available when hiring someone into the Sales business unit. For example, what jobs, locations, or departments should be selectable? The goal is to ensure the Sales BU has roles specific to its operations, such as Sales Rep, Sales Manager, and Sales Executive. These roles should only be accessible within the Sales BU and not shared with other units like Marketing or Manufacturing. To achieve this, a unique Set ID is assigned. In this case, the Set ID is named ‘JGSALES’.
Next, it’s important to focus on the Marketing and Manufacturing business units. When hiring for these BUs, which jobs should be available to choose from? Specific Set IDs are used to categorise these jobs, such as ‘JGMRKT’ for Marketing and ‘JGMFG’ for Manufacturing.
For jobs that are shared across Sales, Marketing, and Manufacturing, a COMMON reference data set is utilised. This default set allows multiple business units to access shared reference data seamlessly.
After creating the Set IDs, the next step is to establish the business units: Sales, Marketing, and Manufacturing. Following this, the mapping process begins, where each business unit is linked to its respective Set ID. For example, Sales is associated with ‘JGSALES’ for its jobs, Marketing is linked to ‘JGMRKT,’ and Manufacturing uses ‘JGMFG.’
Conclusion
Understanding and effectively implementing Business Units and Set IDs is crucial for configuring Fusion Applications in a way that aligns with your organisation’s unique structure. By creating and mapping specific Set IDs to business units like Sales, Marketing, and Manufacturing, you ensure that each unit operates independently while sharing common data where necessary. This strategic setup streamlines operations enhances data organisation, and supports seamless decision-making in Global Human Resources implementation.
