Business Units and SetIDs were concepts that were brought over into Fusion Applications from PeopleSoft. When you are working on Global Human Resources implementation, you have a series of enterprise structures and work structure tables that you need to address. Things like enterprise, legal entities or legal employers, divisions, business units, departments, locations, jobs and so on. Business units and sets work with several of those work structure tables, and you have some decisions to make when you are doing your implementation.

If you have no understanding of Business Units and SetIDs prior to this session, I'm hoping that you will gain a base understanding that will assist you in setting up business units and what we call reference sets within Fusion applications.

In the above diagram, I have a fictitious enterprise named Jay Corp. Within a Fusion HCM installation, you have one enterprise. Enterprise is really the hard partition between one client and another. And then you have many other layers like Legal Entities and Divisions that you can use. But the layer that I am going to talk about here is Business Units. Business Units are required and you have to have at least one. Business Units are a way to group your organization together. It can be by line of business or by geographic area. So in my example, Sales, Marketing and Manufacturing are the business units. These are Business Units within Jay Garments. 

Now what we have to decide here is, when I hire somebody into the Sales business unit, what jobs should I be able to select from? What location should I be able to select? When I hire somebody into the Sales business unit, what departments should I be able to select? The idea is that the Sales BU has jobs that are only used in Sales like Sales Rep, Sales Manager, Sales Executive. So I want to set up those jobs and make those as jobs that are only used by the Sales BU and they're not used by Marketing or Manufacturing BUs. The way I do that is by utilizing a different SetID. I am going to just use the SetID and I am going to call this one as 'JGSALES'.

Now it's time for me to consider the Marketing BU and Manufacturing BU. When I hire somebody in Marketing or Manufacturing what job should I be able to select? I have some jobs up here and I am going to just use the SetID and call them 'JGMRKT' and 'JGMFG'.

If I have a subset of jobs that are common to Sales, Marketing and Manufacturing, a COMMON reference data set is available as the default set. These can be assigned to several business units sharing the same reference data.

Once the above SetIDs are created I would go and create business units namely Sales, Marketing and Manufacturing. Then I would do the mapping. And this is where I would say, Sales uses JGSALES' for their jobs, Marketing uses 'JGMRKT' for its jobs and Manufacturing uses 'JGMFG' for its jobs.

In the next article, I will explain how to create SETIDs for Locations and Departments Work Structures.

Jayashree Prakash

Add comment