The previous blog on Business Units and Set IDs in Oracle Fusion HCM covered the configuration of SetIDs for Jobs. This article focuses on setting up SetIDs for Locations and Departments within Work Structures.

Moving on to Locations, the Sales and Marketing business units are based in Toronto, while the Manufacturing business unit operates out of Montreal. To reflect this, a SetID named ‘JGTORONTO’ will be assigned to the Sales and Marketing BUs, and another SetID, ‘JGMONTREAL,’ will be designated for the Manufacturing BU.

In this case, each business unit is not being partitioned individually. Instead, location values are differentiated between the Manufacturing BU and the Sales and Marketing BUs, with the latter two sharing the same SetID. Moving forward with the setup, ‘JGTORONTO’ will be created for the Sales and Marketing BUs, while ‘JGMONTREAL’ will be designated for the Manufacturing BU. As mentioned in the previous article, the business units have already been set up. Now, the next step is mapping the locations: the Manufacturing BU will use ‘JGMONTREAL’ for its locations, while both the Sales and Marketing BUs will use ‘JGTORONTO’ for theirs.

Dive deeper into mastering Business Units and Set IDs with our
Oracle Core HCM Training: Applications and Best Practices

The final example focuses on Departments, taking a slightly different approach. Instead of creating a new SetID, the COMMON SetID provided by Oracle will be used for managing reference SetIDs for Departments. This approach is chosen because the Sales, Manufacturing, and Marketing BUs will all share the same department data.

After setting up the following: 

1. SETIDs -> JGSALES, JGMRKT, JGMFG, JGMONTREAL & JGTORONTO 
2. Business Units -> Sales, Marketing, and Manufacturing, along with their mappings 

The subsequent configurations will be implemented:

• The Sales BU will use JGSALES for jobs, JGTORONTO for locations, and the COMMON set for departments. 
• The Marketing BU will use JGMRKT for jobs, JGTORONTO for locations, and the COMMON set for departments. 
• The Manufacturing BU will use JGMFG for jobs, JGMONTREAL for locations, and the COMMON set for departments. 

With the SETIDs and business units mapped, the next step is to create the corresponding work structures.

Jobs

• Sales Representative, Sales Manager, and Sales Executive assigned to the reference SETID ‘JGSALES’. 
• Marketing Manager, Marketing Coordinator, Marketing Specialist, assigned to the reference SETID ‘JGMRKT’. 
• Sales Plant Operator, Production Manager, Parts Assembler, assigned to the reference SETID ‘JGMFG’. 

Locations

• Toronto, assigned to the reference SETID ‘JGTORONTO’. 
• Montreal, assigned to the reference SETID ‘JGMONTREAL’. 

Departments

• HR, Sales, and Manufacturing are all linked to the COMMON SETID. 
• Grades can either be shared or restricted across business units. 

By now, a clearer understanding of Business Units, SETIDs, and the mapping process should be established. The next article will demonstrate the creation of SETIDs, Business Units, Jobs, Locations, and Departments.

Conclusion  

The process of configuring SetIDs for Locations and Departments in Oracle Fusion HCM has been explored, building on the concepts covered in the previous discussion on SetIDs for Jobs. Establishing the appropriate SetIDs for different business units, mapping locations, and determining how departments will be shared across units has laid the groundwork for a well-structured system.

Stay tuned for the Final Part of our
Business Units and Set IDs in Oracle Fusion HCM 
blog series, where we’ll take these concepts further by demonstrating how to practically create & configure SETIDs, Business Units, Jobs, Locations, & Departments.