You can enrich Workforce to reflect your organization's planning needs.
To help you decide the granularity you want:
Table 6-3 Overview of Granularity Level
|Employee||If you select Employee, the Employee dimension is added, which stores the organization's employees. Calculations for salary and related compensation can be performed for existing employees or in planning for new hires. Oracle anticipates that you import existing employees from a Human Resources system, such as PeopleSoft.
If you select this option, you must set defaults for Pay Type (for example, Exempt or Non-exempt) and Employee Type (Regular, Contractor, and Temporary). Or, if you don't use this information, set them to null (the No <member name>). See Setting Defaults.
|Job||If you select Job, the Job dimension is added, which stores the roles assigned to employees. Examples of jobs: Engineer, Software Developer, and Mechanic.
If you select this option, you must set defaults for Pay Type and Skill Set. Or, if you don't use this information, set them to null (the No <member name>). See Setting Defaults.
|Employee and Job||With this option, the Job dimension is used with the Employee dimension to facilitate analysis of roles across the organization, to track new hire requests, and to identify employees by role.
If you select this option, you must assign defaults for Job and Union Code. See Setting Defaults.
If you don't track Union Codes, when you enable Workforce, you can use Map/Rename Dimension to rename Union Code to something that's meaningful to your business. If you rename Union Code when enabling Workforce, you must still assign a default for the renamed dimension.
You can rename Employee, Job, or Employee and Job in Map/Rename Dimensions.