Importing Strategic Workforce Planning Data
You can download Strategic Workforce Planning 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.
Video
| Your Goal | Watch This Video |
|---|---|
|
Learn about importing Strategic Workforce Planning metadata and data from Oracle Fusion Human Capital Management using Data Management. |
|
|
Learn about integrating Human Capital Management with Strategic Workforce Planning using Data Management. |
|
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 Strategic Workforce 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_SWPDemandDataLoad_Plan.csv.JO_precedes template names for Job-only applications. For example:JO_JobPropertiesDataLoad_Plan.csv.
Note:
If your application is multicurrency, import data into the No Currency member. (The import templates are formatted to include the No Currency member for multicurrency applications.) If you've enabled Average Compensation, also import average compensation rates at No Currency in the entity. Also, Oracle assumes that you load Actuals historical data instead of entering or calculating it.
You can import properties and OWP_FTE to any month and year because the Process Loaded Strategic Workforce Data rule prompts for the starting point. However, skills assessment data, demand, and supply data are all loaded to BegBalance.
After importing data, run the Process Loaded Strategic Workforce Data rule.
Importing Demand Units for Demand Drivers
Use EJ_SWPDemandDataLoad_Plan.csv to import demand units for demand drivers.
Importing Rates for Demand Drivers and Demand FTE
Use EJ_SWPDemandDatabyJob_Plan.csv to import demand rates for demand drivers and demand FTE. To consider the Previous Year Ratio demand calculation, import this data for the year prior to the Plan Start Year.
If you are performing skill set planning, beginning with Release 21.08, you can load data only once to the Workforce cube (OEP_WFP), and then use a data map (Headcount and FTE Data for Reporting) to push the data to the Reporting cube (OEP_REP).
Previously, you were required to load FTE for Supply Planning, Demand Planning, and Workforce Planning to the Workforce cube (OEP_WFP), and for skill set planning you were required to load to the Reporting cube (OEP_REP). This required you to load the same value in two different places.
Importing Employee Information, FTE Per job, Entity, and Year to the Reporting Cube
Use EJ_EmployeeFTEDataLoad_REP.csv to import employee information, FTE per job, entity, year to the OEP_REP reporting cube. This information is the basis for deriving the average skill rating across different skill categories.
Importing Employee Skills Assessment Data
Use EJ_EmployeeSkillAssessmentDataLoad_Plan.csv to import skill assessment ratings for employees across different skills in the reporting cube. This information is the basis for deriving the average skill rating across different skill categories.
Importing Attrition Data by Job
Use EJ_SWPAttritionDatabyJob_Plan.csv to import values for attrition by job.
Importing Demand Data by Job
Use EJ_SWPDemandDatabyJob_Plan.csv to import values for demand data by job.
Importing New Hires
Importing Properties for New Hires
Use EJ_NewHiresPropertiesDataLoad_Plan.csv to import properties for new hires.
Importing Job Properties
Use JO_JobPropertiesDataLoad_Plan.csv to import job properties.
Importing Attrition Data by Job
Use JO_SWPAttritionDatabyJob_Plan.csv to import attrition data by job.
Importing Demand Data by Job
Use JO_SWPDemandDatabyJob_Plan.csv to import demand data by job.
If you are performing skill set planning, beginning with Release 21.08, you can load data only once to the Workforce cube (OEP_WFP), and then use a data map (Headcount and FTE Data for Reporting) to push the data to the Reporting cube (OEP_REP).
Previously, you were required to load FTE for Supply Planning, Demand Planning, and Workforce Planning to the Workforce cube (OEP_WFP), and for skill set planning you were required to load to the Reporting cube (OEP_REP). This required you to load the same value in two different places.
Importing Demand Units for Demand Drivers
Use JO_SWPDemandDataLoad_Plan.csv to import demand units for demand drivers.
About Importing Employee and Job Properties
Employee and Job properties provide the basis for Supply FTE data, before attrition. Whether you've enabled only Strategic Workforce Planning, only Workforce, or both, the application relies on the properties data in the import templates JO_JobPropertiesDataLoad_plan.csv or EJ_EmployeePropertiesDataLoad_Plan.csv. After importing with the appropriate properties file and running the rule Process Loaded Strategic Workforce Data, the information is available in Strategic Workforce Planning. To see the data, click Overview, and then Review Employee Information or Review Job Information.
If your application is single currency and both Strategic Workforce Planning and Workforce are enabled, you only need to import the properties file once. When you run the rule Process Loaded Strategic Workforce Data, the data is copied from the Year and Month in the file to years in yearRange. (Strategic Workforce Planning has a substitution variable, OWP_SWPYearRange.)
If your application is multicurrency and both Strategic Workforce Planning and Workforce are enabled, you must import the properties files twice, once to include the currency member for Workforce and again at the No Currency member for Strategic Workforce Planning. Run the Process Loaded Strategic Workforce Data rule and Process Loaded Data after each import.
If you've also enabled Workforce, see Importing Workforce Data.