HR data to BI
Oracle HCM to Power BI integration: workers, assignments and history from Oracle Fusion in Power BI
With an integration between Oracle HCM Cloud and Power BI, workers, work relationships, assignments, departments and jobs from Oracle Fusion sit in a fixed Power BI model, with history per effective date. KoppelHet fetches the large volumes through HCM Extracts with changes only, so headcount and turnover per country and department keep up daily in Power BI.
What the integration does
Organisations that run Oracle Fusion Cloud HCM next to Oracle Fusion ERP and report locally in Power BI often pull lists from Oracle by hand. Those count employees with two assignments twice, and a retroactive correction makes last month's figures differ from what was already sent to management.
- Oracle administration sets up an HCM Extract with only the fields the report needs, in changes-only mode.
- KoppelHet collects the extract file after the scheduled run and processes the changes in the history.
- Departments, jobs and locations come along separately as dimensions.
- Months that change because of a correction are recalculated and flagged.
- KoppelHet refreshes the Power BI model; office managers see only their own departments.
What to watch for with Oracle HCM Cloud and Power BI
- In Oracle HCM a departure is the end of the work relationship, not the end of an assignment. Someone who changes assignment within the same employer has not left. KoppelHet therefore counts turnover on work relationships, so an internal move is not a departure in Power BI.
- A worker can have several assignments at the same time in Oracle. KoppelHet keeps worker and assignment separate in the model, so headcount in persons and in assignments are both right and nobody counts twice.
- For date-effective data Oracle has both an update, which creates a new time slice, and a correction, which overwrites an existing slice. A correction therefore changes the past without a new row. KoppelHet recalculates the months changed by a correction and flags them in Power BI, so it is clear why an earlier report differs.
- Oracle returns 25 records per page by default through the REST API. For reporting on thousands of workers that means many requests. KoppelHet therefore uses an HCM Extract in changes-only mode, and the REST API only for individual checks.
- According to Oracle a changes-only HCM Extract only works fully when the threading details in the extract definition are also set up. KoppelHet checks that during setup and compares with a full extract once per period, so no change is missing in Power BI.
- Without a date Oracle's REST API returns the current position, and with a date the position on that one day. A monthly history through the REST API would need a separate request per worker per month. KoppelHet therefore builds the history from the extract with effective dates and records a snapshot every month.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why not load OTBI or Oracle reports into Power BI?
That works for a single overview. History, corrections and turnover on work relationships need a model of their own that keeps up daily.
Can we put the data next to Oracle ERP figures?
Yes. Department and cost centre are dimensions in the model, so figures from Oracle ERP can sit alongside. That link can be added later as an extension.
What about the GDPR?
You are the controller and KoppelHet is the processor, under a data processing agreement. The extract contains only the fields the report needs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Extracts with the CHANGES_ONLY parameter and threading details in the extract definition; delivered as a file. Additionally the REST API for Oracle Fusion Cloud HCM (workers with child resources workRelationships and assignments, departments, jobs, locations), with effectiveDate for the position on a date and limit, offset and hasMore for pagination (25 per page by default).
- Authentication according to Oracle's OWSM policy (basic, SAML 2.0 bearer or JWT, always over SSL). Power BI semantic model in import mode, refreshed through the Power BI REST API, with row-level security on department.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Power BI | Notes |
|---|---|---|
PersonNumber | Persoonsleutel | |
Work relationship (start, einde, reden) | Tabel dienstverbanden en verloop | |
Assignment (afdeling, job, locatie, ingangsdatum) | Tabel assignmenthistorie | A worker can have several assignments |
Departments | Dimensie afdeling | |
Jobs | Dimensie functie | |
Locations | Dimensie locatie en land |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud