Importing Workforce Data

You can download Workforce data import templates from within the application. The templates are generated based on the features you’ve enabled and the custom dimensions that you added when you enabled features. See Importing Data.

Only load data to accounts that are part of the data load templates.

Note:

If you want to load only changed and new Workforce data since the last load, you can improve load performance using Data Integration. See Loading and Calculating Incremental Workforce Data.

Note:

You can bulk load new hire data using Data Integration. For more information, see Bulk Loading Workforce New Hire Data in Administering Data Integration for Oracle Enterprise Performance Management Cloud.

Note:

As of the February, 2020 Release, Workforce supports a new Start Date property. The data import templates include headers and examples for loading data such as Hire Date to OWP_Start Date rather than to OWP_Start Month. You can still load data to Start Month, and the Process Loaded Data rules convert the data to Start Date using the first of the month provided in the Start Month account. So, existing data integrations based on Start Month data continue to work. You'll get more accurate calculations, however, if you load data into Start Date.

The templates reflect the CurYr that you set in the Planning and Forecast Preparation configuration task. After importing your data and refreshing the cube, run the rule Process Loaded Data to copy the data to the necessary periods in the planning year range.

The prefix of each template name depends on the application's granularity:

  • EJ_ precedes template names for Employee and Job applications. For example: EJ_EmployeePropertiesDataLoad_Plan.csv.
  • EO_ precedes template names for Employee-only applications. For example: EO_EmployeePropertiesDataLoad_Plan.csv.
  • JO_ precedes template names for Job-only applications. For example: JO_JobOtherCompensationDataLoad_Plan.csv.

Importing Employee Properties

Use these templates to import properties for existing employees:

  • EmployeePropertiesDataLoad_Plan.csv—Import plan properties for employees. (You don't need to load Headcount and Partial Payment Factor unless you want to explicitly set these values. If you don't load Headcount and Partial Payment values, they're set to 1 and 100% respectively for every employee.)

    Note:

    For the EJ_EmployeePropertiesDataLoad_Plan.csv template, don't load to No Union Code or to OWP_All Union Code. Instead add and use new child metadata member of Total Union Code. Otherwise, the synchronize rules may not work properly.

  • EmployeePropertiesDataLoad_Actuals.csv—Import actual properties for employees.

Note:

You can use EJ_EmployeePropertiesDataLoad_Plan.csv and EO_EmployeePropertiesDataLoad_Plan.csv to load employee master FTE data to OEP_Home Entity. Data loaded at OEP_Home Entity is copied to future periods in the load year (starting from the data load month) and future years when you run Process Loaded Data.

You must enter or import the Master FTE value for each employee if you enable Split-Funded FTE.

Importing Employee Compensation

Use EmployeeSalaryDataLoad_Plan.csv to import data used to calculate salary.

Importing Actual Employee Compensation

Use EmployeeCompensationDataLoad_Actuals.csv to import actual compensation data for employees.

To use this template, set these Data Load Settings:

  1. From the Home page, click Navigator Navigator icon, and then under Integration, click Data Load Settings.

  2. Set these parameters for importing data:

    • Data Load Dimension: Account
    • Driver Dimension: Period. Member: BegBalance,ILvl0Descendants(YearTotal)
    • Data Load Dimension Parent:
      • OWP_Total Earnings. Driver Dimension Unique Identifier: BegBalance
      • OWP_Total Benefits. Driver Dimension Unique Identifier: BegBalance
      • OWP_Total Taxes. Driver Dimension Unique Identifier: BegBalance

Importing Employee Other Compensation Data

Use EmployeeOtherCompensationDataLoad_Plan.csv to import other compensation data—benefits, taxes, and additional earnings—for employees.

OWP_Value is an optional field. If you include the rate value in the template, that rate is copied to the planning year range for the specified employee.

Importing Salary Grades

Use Salary Grade-Basis.csv and Salary Grade-Value.csv to import salary grades into Assumptions.

Importing Properties and Rates for Additional Earnings, Benefits, and Taxes

Use these templates as examples when importing properties and rates for additional earnings, benefits, and taxes into the Benefits and Taxes Wizard.

  • Earnings,Benefits and Taxes-Properties.csv—Import properties for additional earnings, benefits, and taxes.
  • Earnings,Benefits and Taxes-Rates.csv—Import rates for additional earnings, benefits, and taxes.

Importing Job Properties

Use JobPropertiesDataLoad_Plan.csv to import job properties.

Importing Job Salaries

Use JobSalaryDataLoad_Plan.csv to import salaries for jobs.

Importing Job Other Compensation Data

Use JobOtherCompensationDataLoad_Plan.csv to import other compensation data for jobs: benefits, taxes, and additional earnings.