Should I delete the Job Dimension in Workforce Planning?
Hyperion Workforce Planning comes with pre-defined forms to enter data, pre-defined menus to add more flexibility to the forms, tasks lists to manage the process, and pre-defined calculations to make the implementation of a workforce application faster. But Workforce Planning also comes with pre-defined dimensions: the “classic” Planning dimensions (Entity, Accounts, Period, Scenario, Version) and two additional dimensions: Employee and Job. Employee makes a total sense but some clients don’t need the Job dimension. What should you do with it?
The Job dimensions is a new feature with Workforce Planning starting with 188.8.131.52 so I guess many clients were asking for this additional dimension and it is nice to have it out of the box for them. But what about clients who don’t need it?
Let’s have a look at the impact of removing the Job Dimension from a Workforce Planning database:
- Webforms: no big impact: you remove the job dimension and you will need to re-edit each form to re-generate the form. No big deal, you’ll have to do it for any dimension you add or any other significant structure change.
- Menus: same as Webforms, not the end of the world.
- Task Lists: no impact
- Business Rules: Removing it has a big impact and will require a complete re-validation of the rules. In the out of the box Calc Manager rules, there is a Design Time Prompt (DTP) testing the existence of a Project Dimension but the Job dimension is “hard coded” in every Business Rule.
- Member Formulas: one beautiful thing about Workforce Planning is how it leverages a mix of Business Rules and Member Formulas: if you remove the Job Dimension you will need to modify most of the Member Formulas and go through many validations of the outline.
So it is a lot of work to remove the Job dimension, I’ve not tried it but I estimate it to take a few days to comb through all of the rules and Member Formulas and remove that dimension.
So it is a lot easier to keep to Job dimension with only one Base Member (“No Job”) and make the parent Label Only. You might also want to explore making the Job dimension Dense as it won’t change the block size and depending on your configuration it might improve your performance.
I also noticed that most of HR systems have a Job dimension and even if at first, your client won’t ask for a Job dimension, you might be surprised to see that ultimately, they end up leveraging Jobs a lot more than what they anticipated during the Requirements and Design phase.