ODTUG Configuring Workforce: Employee? Job? or Both?

Editor's Notes

• #8: Before we get into enabling Workforce, want to explain the 3 Workforce Plan Types, as they will be referred to throughout the enablement\configuration process. This is Unique from other modules, like Capital and Project, that have only 1 BSO cube. Workforce has 2 BSO cubes and 1 ASO cube out of the box. You can create your own ASO cube to include custom dimensions and smart list to dimensions, as needed. Or choose not to use it and aggregate the BSO planning cube or enable hybrid but there is a lot to consider in doing that.
• #10: Now we have 4 features to enable, with options. Granularity, Expense Planning, Headcount Planning and Workforce management. Granularity is required, but some of the others are optional. We will look at these in more detail on the next few slides Note that Once you enable, cannot undo, however, you can wait and enable one of the features at a later time
• #11: First item you have to decide is granularity Big decision as this drives dimensions, forms, reporting We’ll discuss more of the implications for each of these throughout the rest of the slides but wanted to mention a few key points up front
• #13: Expense Planning should always be checked to plan for Workforce expenses Non Comp is strictly input, by employee or job, no calculations ootb – company may want to keep at high level in Finance cube and not by employee Merit is global rate by entity, pick month to start
• #14: Optional
• #15: New hires for Employee or Emp/Job only granularity Something to think about for granularity – do you want new hire to be able to be assigned to job dimension If user has access to target entity/dept then one step, otherwise two step – goes to unspecified entity In last month’s update transfer rules now include custom dimensions
• #16: C is Answer
• #18: -Not all dimensions will be showing, but only 3 Custom dims and the ones allowed to rename, next slide has some examples -Ok to use “No Project” for everything until ready to integrate with Projects -Hopefully in the future, Oracle will make this enhancement
• #19: -Examples for each type of granularity -Not all dimensions will be showing, but only 3 Custom dims and the ones allowed to rename -These dims are in the different cubes -After choosing, click on Enable and cubes are created, along with forms, rules, etc.
• #20: Now that enablement is done, time to Configure Note that the Type is labeled as Optional or Mandatory Will look at the Mandatory configuration processes in next slides
• #22: Need to set up all dimensions – entity, employee, job Based on granularity – pay type, employee type, skill set, union code
• #23: -Prior to setting up the benefit/earning/tax wizard, have to set up the members in component dimension
• #25: Select Actual period and year, How many years Monthly, Quarterly, Yearly Drives the variables used in forms and rules Use Forecast then copy to Plan, Final
• #26: If don’t set this up, will get error trying to open forms to let you know to set up user variables
• #27: D is Answer
• #29: Filter for Scenario, Version, Benefit, Taxes, Earnings Will see list of benefits previously added to Component dimension All in OEP_WFSC cube
• #30: Rates, Simple, Custom If other than months, then payment frequency – first period, last period, one time One time asks which month
• #31: Uses User variables on form, no custom dimensions Can have different rates by entity Amount per month
• #32: Review
• #33: Rates, Simple, Custom Threshold – YTD Calendar year for US tax, if fiscal year is not Jan-Dec
• #35: Custom Component type Fill in the details, but it does not matter since it will be calculated based on custom formula Use custom if is not any of the value types or want to load rates by employee or a custom dimension
• #36: Member formula in OEP_WFP cube for OWP_Custom Expense property The OWP_Expense Amount property also has a member formula that looks to Custom first, if not, then use data from Wizard
• #37: OEP_WFSC – no custom dims, no employee detail, no job detail if job only Important to know up front how the earnings\benefits\taxes will be assigned to employee\job to be able to repurpose and set up the dimensions needed for Defaults By Entity and Currency
• #38: This client had multiple employees in different states, countries, in same entity. Needed to decipher which tax the employee needed, job didn’t matter Employee was loaded from HR system with the Union Code of “XX_XX” For taxes, just pick one of the tiers, doesn’t matter
• #39: First 4 were custom types – loaded rates and inputs Overtime was by Specific Job
• #41: Sync rules Member formulas on compensation accounts
• #43: Doesn’t have to be by individual entity
• #44: Form sits outside of modules
• #45: If you had selected Merit in enablement
• #46: B is Answer
• #47: After enablement and configuration done
• #48: At a minimum Compensation Planning and Analysis(Rptg)
• #51: Forms used in Benefit and Tax wizard and defaults
• #53: Uses forms in the Dashboard – Compensation folder
• #55: Uses forms in the Dashboard – Compensation folder Another dashboard has by Expenses