Defaults (and assumptions) drive the calculations for workforce-related expenses.
If you want a default for salary, additional earnings, benefits, or taxes to be used for all employees in a specific job, select that job when adding the default. For example, if you select Accountant when adding the default for Job, then all employees who are Accountants are assigned that default.
If Employee and Job granularity is enabled, you must set defaults based on Job and Union Code. This setting defaults compensation elements for new hires for a specific job. For example, you might set the default Salary Grade to Grade 3 for a Warehouse Worker with the Union Code of Teamster.
To apply a compensation element default to all employees in all jobs, such as when setting defaults for salary, additional earnings, benefits, and taxes, select the OWP_All <member>. For example, select the OWP_All Union Code member and the OWP_All Jobs member if you want the default compensation element to be used for all employees in any job and in any union. So for example, if you select the OWP_All Union Code member and the OWP_All Job member, then Sue Doe in Accounting (whose Union Code is Default No Union Code) would get the same compensation element default as Tom Blue in the Warehouse (whose Union Code is Teamsters).
Workforce seeds a level 0 member named No Union Code as a sibling to Total Union Code. However, when you add defaults for salary, additional earnings, benefits, and taxes, No Union Code isn't available for selecting in the runtime prompt. To meet this need, Workforce expects you to add at least one sibling null metadata member (such as OWP_Unspecified Union Code) to OWP_All Union Code.
If your company doesn't use Union Code, you can rename that dimension to something that’s meaningful to your business when you enable Workforce. If you didn’t rename Union Code when you enabled Workforce, you can create whatever members you want in the Union Code dimension and change the alias of the dimension to your preferred name.
Set Workforce defaults by clicking or tapping Compensation Planning, then the Defaults tab. Then:
To set Salary defaults, click Salary. These defaults are used for new hires or job salary defaults. Using Assumptions, and then Salary Grades , planners can then set the salary basis (for example, Annual or Hourly) and the salary rate for the Salary Grades that you imported.
If you import the salary basis and salary rates to the OEP_No Entity member, they are used across all entities. Alternately, select OEP_No Entity (in Compensation Planning, then Assumptions, and then Salary Grades).
- To set Additional Earnings defaults, click Additional Earnings.
- To set Benefits defaults, click Benefits.
- To set Taxes defaults, click Taxes.
When adding defaults, you can select parent driver dimension members or level zero members.
For information about Salary Mapping and Merit Mapping, see Customizing the Mapping for Integration between Workforce and Financials.
Tip:To copy defaults for Salary, Additional Earnings, Benefits, and Taxes; or the mappings for Basic Salary or Merit from one entity to other entitites, right-click a member and then select Copy Data Across Entities, and then click OK. Select From and To entities, and then click Launch. This action clears the target before copying the members.
Use Copy Data Across Entities for Grades to copy grades, rate information, and Financials mappings for grades.
Tutorials provide instructions with sequenced videos and documentation to help you learn a topic.
|Your Goal||Learn How|
|This 45-minute tutorial shows you how to modify out-of-the-box templates in order to disable Salary Defaults. You first create a new Salary Option Smart List, and then modify Groovy Templates used in Workforce--Add Requisition, Change Requisition, and Change Existing Details--to use the salary options specified in the smart list: Salary Grade, and Salary Basis & Rate.|