Connect Oracle Fusion Cloud HCM with Oracle Workforce Planning
This tutorial demonstrates the seeded Oracle Data Integration approach for bringing employee, organization, job, assignment, salary and compensation information into the Workforce module of Oracle EPM Planning.
Oracle Fusion Cloud HCMHCM ExtractsEPM Data IntegrationPlanning Modules – WorkforceMetadata + Data
BISP Trainings Learning Edition: This tutorial combines functional Workforce Planning concepts, Oracle HCM integration design, Data Integration mappings, BI Publisher/HCM Extract concepts, testing and troubleshooting so learners understand the complete implementation lifecycle—not only individual screens.
Target Architecture
Oracle HCM
Worker, assignment, salary, elements
Worker, assignment, salary, elements
→
HCM Extracts
Seeded extract definitions
Seeded extract definitions
→
EPM Data Integration
Import, map, validate, export
Import, map, validate, export
→
Workforce Planning
Employee master + compensation
Employee master + compensation
Recommended pattern: first load metadata such as Entity, Employee, Job and Salary Component members; then load employee properties and compensation data; finally run Workforce synchronization and compensation calculations.
Example Business Scenario
Vision India Pvt Ltd wants to import 2,500 active employees from Oracle HCM into the FY27 Working forecast. The load includes employee number, name, hire date, department, legal employer, job, grade, location, FTE, status, annual salary, salary basis, bonus, benefits and employer taxes.
2,500Employees
12Entities
85Jobs
FY27Planning year
Roles and Access
| System | Typical responsibility | Purpose |
|---|---|---|
| Oracle HCM | Application Implementation Consultant / HCM Integration Specialist | Import and configure extracts, submit extract flows, access output. |
| Oracle EPM | Service Administrator | Configure Workforce, register HCM source, create integrations and mappings. |
| Security | Identity administrator | Create integration account, assign least-privilege roles, manage password rotation. |
Technical Readiness
Privacy: Load only attributes needed for planning. Avoid sensitive personal data such as government IDs, bank details, medical data or personal contact data unless there is a documented business and compliance requirement.
Step 1 — Enable and Configure Workforce
1
Open configuration.
Home → Application → Configure → Workforce
Home → Application → Configure → Workforce
2
Select planning granularity.
Choose Employee, Job, or Employee and Job based on the approved design. For person-level compensation planning, Employee or Employee and Job is normally required.
Choose Employee, Job, or Employee and Job based on the approved design. For person-level compensation planning, Employee or Employee and Job is normally required.
3
Enable Expense Planning.
Enable Compensation Expenses. Add Additional Earnings, Benefits, Taxes and Non-Compensation Expenses as required.
Enable Compensation Expenses. Add Additional Earnings, Benefits, Taxes and Non-Compensation Expenses as required.
4
Configure planning frequency and range.
Set monthly planning, starting year, number of years, and workforce assumptions.
Set monthly planning, starting year, number of years, and workforce assumptions.
5
Complete mandatory configuration tasks.
Review entities, accounts, employee properties, salary grades, benefits, taxes and assumptions.
Review entities, accounts, employee properties, salary grades, benefits, taxes and assumptions.
PlanningApplication ▾
Configure: Workforce
✓ Expense Planning ✓ Compensation Expenses ✓ Benefits ✓ Taxes
Employee and Job
Monthly
Step 2 — Register Oracle HCM Cloud as a Source Application
- Open Home → Data Exchange → Data Integration.
- From Actions, select Applications.
- Click Add or Register Application.
- Select the application type for Oracle HCM Cloud extracts.
- Enter the HCM service URL, integration username and password.
- Test the connection and save the application.
- Register the Workforce Planning target application if it is not already available.
Credential practice: Use a dedicated integration account. Do not use a personal administrator account, and never place credentials in scripts, screenshots or training files.
Data IntegrationApplications
Register Application
Oracle HCM Cloud
HCM_PROD
https://<your-hcm-host>
Step 3 — Download and Deploy Seeded HCM Extracts
1
In Data Integration, open the Workforce target application and review its dimension details.
2
Classify seeded dimensions correctly, especially Employee, Job, Property and Union, when applicable.
3
From the application Actions menu, select Download HCM Extract.
4
Import the downloaded extract templates into Oracle HCM using the HCM Extracts administration pages.
5
Validate the extract definitions, delivery options, parameters, security and output format.
6
Submit a small test run for one legal employer or department and verify that output is generated.
Common Seeded Extract Domains
| Extract domain | Examples | Target use |
|---|---|---|
| Employee | Person number, display name, hire date, termination date, status | Employee metadata and employee properties |
| Assignment | Department, legal employer, business unit, job, grade, location, FTE | Entity and job assignment |
| Salary | Salary amount, basis, frequency, annualized salary | Base salary planning |
| Compensation components | Bonus, allowance, benefit, tax or payroll element information | Additional earnings, benefits and taxes |
Step 4 — Load Metadata Before Data
Metadata loads create valid Planning members before employee data references them.
| Sequence | Metadata | Example source | Example target |
|---|---|---|---|
| 1 | Entity | Department / legal employer | ENT_1100_Sales |
| 2 | Job | Job code | JOB_FIN_ANALYST |
| 3 | Employee | Person number | EMP_100245 |
| 4 | Salary component | Element or component code | Annual_Bonus |
| 5 | Merit / grade / union | Grade, merit band or union code | GRADE_G7 |
Design recommendation: use stable codes as member names and business descriptions as aliases. Do not use employee names as unique member names because names can change or duplicate.
Step 5 — Define Employee Personal and Assignment Detail Load
| HCM field | Workforce target | Transformation example |
|---|---|---|
| Person Number | Employee member | EMP_ + Person Number |
| Display Name | Employee alias | Trim and standardize spaces |
| Hire Date | Start Date property/account | Convert YYYY-MM-DD to target date format |
| Termination Date | End Date property/account | Blank for active employees |
| Assignment Status | Employee Status | ACTIVE → Active; SUSPENDED → Inactive |
| Department Code | Entity | Map HCM department to Planning entity |
| Job Code | Job | Prefix with JOB_ |
| Grade Code | Grade property | Direct or mapped |
| Location Code | Location property | Map to approved location members |
| FTE | FTE | Validate range 0–1 or approved convention |
Example result: Person 100245 becomes employee member EMP_100245, alias “Anita Rao,” assigned to ENT_1100_Sales and JOB_FIN_ANALYST with FTE 1.0.
Step 6 — Define Compensation Load
| HCM compensation field | Example value | Workforce target |
|---|---|---|
| Annualized Salary | 1,200,000 INR | Salary Rate / Base Salary |
| Salary Basis | Annual | Salary Basis |
| Salary Frequency | 12 | Payment frequency or annualization driver |
| Bonus Target | 10% | Additional Earnings – Annual Bonus |
| Transport Allowance | 60,000 INR | Additional Earnings – Transport |
| Medical Benefit | 36,000 INR | Benefits – Medical |
| Employer Tax | 12% | Taxes – Employer Contribution |
| Effective Start Date | 2026-04-01 | Period from which amount applies |
Example annual salary calculation
Monthly Salary = 100,000 INR
Annualized Salary = Monthly Salary × 12
= 1,200,000 INR
Monthly Bonus Accrual = Annualized Salary × 10% ÷ 12
= 10,000 INRAvoid double counting: decide whether HCM sends annualized salary, periodic salary, or payroll element amounts. Map one authoritative amount and make the annualization rule explicit.
Step 7 — Create Import Format, Location and Mappings
- Create an integration between the registered HCM extract source and the Workforce target.
- Review the generated import format and source columns.
- Map source dimensions to target dimensions.
- Create explicit mappings for department, entity, job, grade, component and currency codes.
- Use “Like” or multi-dimension mappings only when governed and tested.
- Create unmapped-member controls; do not silently map unknown values to a generic member in production.
| Source | Mapping type | Target |
|---|---|---|
| DEPT_SALES_IN | Explicit | ENT_1100_Sales |
| FIN_ANALYST_2 | Explicit | JOB_FIN_ANALYST |
| BASE_SALARY | Explicit | OWP_Salary |
| ANNUAL_BONUS | Explicit | OWP_Annual Bonus |
| INR | Explicit | INR |
Step 8 — Run the Integration
1
Open the HCM-to-Workforce integration in Data Integration.
2
Select POV values: Scenario = Forecast, Version = Working, Year = FY27, and the required period.
3
Set import mode and export mode according to the design. Begin with a safe test scope.
4
Run Import, inspect staging, then run Validate.
5
Correct rejected or unmapped records before export.
6
Run Export to Workforce Planning.
7
Run the appropriate Workforce synchronization and compensation calculation rules.
Data IntegrationHCM_EMPLOYEE_COMP_LOAD
Forecast
Working
Apr-27
Step 9 — Validate and Reconcile
| Control | HCM | Workforce | Expected result |
|---|---|---|---|
| Active employee count | 2,500 | 2,500 | Match |
| Annual base salary | ₹2,184,000,000 | ₹2,184,000,000 | Match after currency/unit check |
| FTE | 2,420.5 | 2,420.5 | Match |
| Unmapped departments | 0 | 0 | No rejected records |
| Duplicate employee IDs | 0 | 0 | Unique keys |
Recommended unit tests
- Active full-time employee with annual salary.
- Part-time employee with FTE 0.5.
- New hire effective mid-month.
- Terminated employee.
- Employee transferred between departments.
- Employee promoted to a new job and grade.
- Employee with bonus, allowance, benefit and employer tax.
- Employee paid in a non-base currency.
Step 10 — Design Incremental Loads
After the initial full load, process only new and changed employees whenever possible.
- Run a baseline full load at the start of the planning cycle.
- Store the successful extract timestamp or effective date.
- Extract hires, terminations, transfers, salary changes and assignment changes since the last run.
- Load only affected employees and periods.
- Run employee-specific synchronization or calculation rules where supported.
- Schedule daily or weekly based on planning needs and HCM change volume.
Performance benefit: incremental processing reduces staging volume and calculation scope compared with repeatedly loading the entire workforce.
BI Publisher Details Used During HCM Integration
Oracle HCM Extracts use the built-in BI Publisher integration to format and deliver extract output. In a Workforce Planning integration, BI Publisher can be used as the formatting and delivery layer for employee, assignment, salary and compensation extracts.
Where BI Publisher Fits
1. HCM Data
Person, assignment, salary and element records
Person, assignment, salary and element records
→
2. HCM Extract Definition
Defines records, attributes, criteria and parameters
Defines records, attributes, criteria and parameters
→
3. BI Publisher Template
Transforms XML output into CSV or another required format
Transforms XML output into CSV or another required format
→
4. Delivery Option
Defines file name, output format and delivery method
Defines file name, output format and delivery method
→
5. EPM Data Integration
Imports, maps, validates and exports to Workforce
Imports, maps, validates and exports to Workforce
Step-by-Step BI Publisher Configuration
1
Confirm the extract data model.
Define the employee, assignment, salary and compensation attributes in the HCM Extract definition. Include stable keys such as Person Number, Assignment Number, Department Code and Job Code.
Define the employee, assignment, salary and compensation attributes in the HCM Extract definition. Include stable keys such as Person Number, Assignment Number, Department Code and Job Code.
2
Generate sample XML.
Run the extract for a limited population and download sample XML. The sample is used to design and test the BI Publisher template.
Run the extract for a limited population and download sample XML. The sample is used to design and test the BI Publisher template.
3
Create or update the BI Publisher layout.
Use an eText, RTF or other supported template according to the required output. For Data Integration, a structured CSV output is usually easiest to map and validate.
Use an eText, RTF or other supported template according to the required output. For Data Integration, a structured CSV output is usually easiest to map and validate.
4
Define the output columns.
Keep a consistent column order and header names. Do not use commas or line breaks inside unescaped values.
Keep a consistent column order and header names. Do not use commas or line breaks inside unescaped values.
5
Attach the template to the HCM Extract delivery option.
Select the template, output type, file name and delivery method. Secure the output so only authorized integration users can retrieve it.
Select the template, output type, file name and delivery method. Secure the output so only authorized integration users can retrieve it.
6
Parameterize the extract.
Common parameters include effective date, legal employer, business unit, payroll, department, employee range and last successful run date.
Common parameters include effective date, legal employer, business unit, payroll, department, employee range and last successful run date.
7
Test output quality.
Verify delimiters, encoding, date formats, decimal separators, null handling, duplicate records and record counts before connecting the output to EPM.
Verify delimiters, encoding, date formats, decimal separators, null handling, duplicate records and record counts before connecting the output to EPM.
Recommended BI Publisher Output Design
| Column | Example | Reason |
|---|---|---|
| PERSON_NUMBER | 100245 | Stable employee key for the Employee dimension. |
| DISPLAY_NAME | Anita Rao | Employee alias; not the unique member key. |
| ASSIGNMENT_NUMBER | E100245-1 | Supports employees with more than one assignment. |
| DEPARTMENT_CODE | DEPT_SALES_IN | Maps to the Workforce Entity dimension. |
| JOB_CODE | FIN_ANALYST_2 | Maps to the Workforce Job dimension. |
| EFFECTIVE_START_DATE | 2026-04-01 | Determines the first planning period. |
| ANNUALIZED_SALARY | 1200000 | Avoids ambiguity between monthly and annual salary. |
| CURRENCY_CODE | INR | Supports local and reporting currency design. |
| LAST_UPDATE_DATE | 2026-07-20T14:35:00 | Supports incremental extraction and reconciliation. |
Important distinction: The standard Workforce integration is commonly based on HCM Extracts. BI Publisher formats and delivers the HCM Extract output. A separate custom BI Publisher report-based integration is another possible pattern, but it should not be confused with the seeded HCM Extract process.
Sample CSV Output
PERSON_NUMBER,DISPLAY_NAME,ASSIGNMENT_NUMBER,DEPARTMENT_CODE,JOB_CODE,FTE,ANNUALIZED_SALARY,CURRENCY_CODE,EFFECTIVE_START_DATE 100245,Anita Rao,E100245-1,DEPT_SALES_IN,FIN_ANALYST_2,1.00,1200000,INR,2026-04-01 100317,Rahul Mehta,E100317-1,DEPT_FIN_IN,FIN_MANAGER,1.00,1800000,INR,2026-04-01
Frequently Asked Questions — Oracle HCM Integration
Use the search box to filter common implementation questions.
What employee data can be loaded from Oracle HCM?
Typical data includes employee number, name or alias, hire and termination dates, assignment status, department, legal employer, business unit, job, grade, location, FTE, salary basis, salary amount, additional earnings, benefits and employer taxes. Load only information required for planning and approved by your privacy policy.
What is the difference between HCM Extracts and BI Publisher?
HCM Extracts define which HCM records and attributes are selected. BI Publisher is integrated with HCM Extracts to format the generated XML into CSV, Excel, PDF or other supported outputs and to support delivery options.
Can the integration load only changed employees?
Yes. Design an incremental process using effective dates, last update timestamps or extract parameters. Always maintain a full-load option for baseline initialization and recovery.
How are new hires handled?
Load the new employee metadata and assignment first, then load salary and compensation data with the correct effective start date. Run Workforce synchronization and compensation calculations for the affected employee and periods.
How are terminated employees handled?
Load the termination or assignment end date and status. Workforce calculations should stop compensation according to the configured termination and partial-period rules.
How should an employee transfer be loaded?
Use the primary effective-dated assignment. Map the new department to the target Entity and load the transfer effective date. Test whether the design moves the employee or creates a new employee-job combination.
How are multiple assignments handled?
Use Assignment Number as an additional key when the Workforce design supports Employee and Job or multiple assignments. Do not collapse multiple assignments without a documented business rule.
Why is salary sometimes 12 times too high or too low?
The usual cause is a mismatch between monthly salary and annualized salary. Confirm salary basis, frequency, annualization factor, currency and the target Workforce calculation logic.
Why must metadata be loaded before compensation data?
Employee data references Entity, Employee, Job, Grade and component members. If these members do not exist, the records may be rejected or mapped incorrectly.
How should personal data be secured?
Use a dedicated integration account, least-privilege roles, secure delivery locations, restricted Data Integration access and retention controls. Avoid loading sensitive personal attributes that are not required for workforce planning.
What should be reconciled after every load?
Reconcile employee count, active and inactive counts, total FTE, annual base salary, component totals, entity totals, rejected records, duplicates and unmapped source values.
How often should HCM data be loaded?
The frequency depends on the planning process. Monthly can be sufficient for annual budgeting, while weekly or daily incremental loads may be appropriate during active forecast cycles or high-volume hiring periods.
How BISP Trainings Helps You Learn Oracle EPM at Expert Level
BISP’s learning approach connects functional planning knowledge with application configuration, integration, calculation, testing and production support scenarios.
Functional Workforce Planning
Learn headcount planning, FTE, salary basis, merit, bonus, benefits, taxes, transfers, promotions, new hires, terminations and vacancy planning.
End-to-End Implementation
Practice application design, dimensions, metadata, forms, assumptions, business rules, security, integration, reporting and deployment.
HCM Integration Workshops
Build employee and compensation integrations using HCM Extract concepts, BI Publisher output design, Data Integration mappings and reconciliation controls.
Case Study–Based Learning
Work through realistic implementation scenarios rather than only learning menus and software navigation.
Calculation & Performance Skills
Understand Essbase calculations, Workforce rules, data volumes, incremental processing, debugging and performance optimization.
Testing & Support Readiness
Create unit tests, system integration tests, user acceptance scenarios, reconciliation reports and production support playbooks.
Interview Preparation
Prepare for implementation, integration, troubleshooting and design questions commonly asked for Oracle EPM consulting roles.
Cross-EPM Expertise
Develop connected knowledge across Planning, FCCS, PCMCS/EPCM, EDMCS, Essbase, Smart View and Oracle Cloud integration.
Connect with BISP Trainings
Website: www.bisptrainings.com
Mohit: 7694095404
Use this tutorial as a starting point for a complete Workforce Planning integration lab covering HCM extract design, BI Publisher output, EPM mappings, calculation, reconciliation and troubleshooting.
Troubleshooting Guide
Connection test fails
Confirm the HCM URL, account status, roles, password expiry, network access and HTTPS certificate chain. Test with the dedicated integration user.
Extract completes but no file is returned
Review extract delivery options, payroll flow security, output path, parameter values, effective date and whether the user can access extract results.
Employee record is rejected
Check that Entity, Job, Grade, Employee and component metadata exist before loading data. Review invalid dates, duplicates and blank required fields.
Salary is 12 times too high or too low
Check salary basis, periodicity, annualization factor, currency units and whether the source amount is monthly or annual.
Employee appears under the wrong department
Review effective-dated assignments, primary assignment flag, department-to-entity mappings and transfer effective date.
Loaded data is visible but compensation is not calculated
Run the required Workforce synchronization and existing employee compensation calculation rules for the relevant Scenario, Version, Entity, Employee and time range.
Go-Live Checklist
Oracle Documentation References
- Integrating with Oracle HCM Cloud — Oracle EPM Data Integration documentation.
- Process Description for Integrating Data from Oracle HCM Cloud.
- Registering an Oracle HCM Cloud Application.
- Loading Oracle HCM Cloud Metadata and downloading HCM extracts.
- Configuring Workforce and enabling expense planning.
- Loading and Calculating Incremental Workforce Data.
This training asset uses an Oracle-inspired visual style for educational purposes. It is not an Oracle product screen and is not affiliated with or endorsed by Oracle.