KoppelHet
ContactNederlandsDiscuss your integration
Menu
SolutionsIntegrationsCustomersPricingKnowledgeAboutHow we workImplementation and architectureTrust centerContactNederlandsDiscuss your integration
SAP SuccessFactors logoOracle Fusion ERP logo

HR to ERP

SAP SuccessFactors to Oracle Fusion ERP integration: employees from Employee Central in Oracle, with expense account and manager

With an integration between SAP SuccessFactors and Oracle Fusion ERP, every employee from Employee Central appears in Oracle automatically, with business unit, manager and a default expense account derived from their legal entity and cost centre. A new employee can then submit expenses from day one, and approval follows their manager from SuccessFactors.

Discuss your integrationHow the integration works
Written by Marcel van Beek, founder and integration specialistLast updated:

What the integration does

Organisations with SuccessFactors as HR system and Oracle Fusion for finance and expenses load employees into Oracle with spreadsheets. A new colleague can only submit expenses once someone in finance has filled in their expense account, and a new manager in SuccessFactors approves nothing in Oracle yet.

  1. KoppelHet fetches the changed employees from Employee Central, including records with a future effective date.
  2. Per employee KoppelHet determines legal employer and business unit, and builds the expense account from legal entity and cost centre.
  3. KoppelHet creates a load file for HCM Data Loader and loads it into Oracle.
  4. KoppelHet reads the load status and reports rejected lines to HR or finance.
  5. A termination goes to Oracle with the end date from SuccessFactors.
SAP SuccessFactors → KoppelHet → Oracle Fusion ERPSOURCESAP SuccessFactorsTARGETOracle Fusion ERPKoppelHetmapping · logging · monitoringSAP SuccessFactors → KoppelHet → Oracle Fusion ERPSOURCESAP SuccessFactorsTARGETOracle Fusion ERPKoppelHetmapping · logging · monitoring
Out: Person with name and work email · Work relationship with a legal employer · Assignment with business unit and department · Manager · Default expense account

What to watch for with SAP SuccessFactors and Oracle Fusion ERP

  • Oracle does not let anyone without a default expense account submit an expense report. Employee Central has no ledger account; KoppelHet builds that account from the legal entity and cost centre on the job information, with a table finance maintains.
  • HCM Data Loader recognises a record by a source key, whose owner must first exist as a value in an Oracle lookup. Reading source keys back afterwards is not possible. KoppelHet therefore sets its own owner for SuccessFactors and the user ID as source ID in the first load, so every later run updates the same person.
  • Employee Central and Oracle both work with effective dates. The OData API returns only today's record by default; KoppelHet also requests future records and loads a transfer with its effective date, so the new manager in Oracle takes over approval on that day.
  • A legal entity in Employee Central must be a legal employer in Oracle with a business unit attached to the ledger. KoppelHet only loads employees of legal entities that exist like that in Oracle, and lists the rest.
  • Cost centres are often managed as a foundation object in SuccessFactors, while in Oracle they are a segment of the chart of accounts. A new cost centre in SuccessFactors without a segment value in Oracle gives an invalid account; KoppelHet checks the combination beforehand and reports it to finance.
  • SAP is retiring basic authentication for the SuccessFactors APIs. KoppelHet reads Employee Central with OAuth 2.0 and its own API user with read-only access to the fields Oracle needs.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Do we need Oracle HCM?

No. Oracle Fusion ERP keeps employees in its own workforce data; SuccessFactors stays the HR system.

Does pay data go to Oracle?

No. It is not needed for expenses and approvals. The payroll journal is a separate integration that can be added later as an extension.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Employee Central through the OData API (v2) with OAuth 2.0 (SAML bearer assertion): EmpJob (company, costCenter, department, managerId), EmpEmployment, PerPersonal and PerEmail, fetched with fromDate and toDate=9999-12-31 and filtered on lastModifiedDateTime.
  • To Oracle through HCM Data Loader (Worker.dat with Worker, PersonName, PersonEmail, WorkRelationship, WorkTerms, Assignment with BusinessUnitId, DepartmentName and DefaultExpenseAccount, and AssignmentSupervisor), with SourceSystemOwner from the HRC_SOURCE_SYSTEM_OWNER lookup and SourceSystemId. The expense account goes as a concatenated segment value.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in SAP SuccessFactorsField in Oracle Fusion ERPNotes
userIdSourceSystemIdWith its own SourceSystemOwner for SuccessFactors
PerPersonal en PerEmailPersonName en PersonEmail
EmpJob companyLegal employer en BusinessUnitIdThrough a table
EmpJob departmentDepartmentName
EmpJob managerIdAssignmentSupervisor
EmpJob company + costCenterDefaultExpenseAccountCombination of ledger segments
EmpEmployment startDate en endDateBegin- en einddatum werkrelatie
Sources

Related

Ashby logoSAP SuccessFactors logo

Ashby → SAP SuccessFactors

Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central

Bullhorn logoSAP SuccessFactors logo

Bullhorn → SAP SuccessFactors

Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central

Carerix logoSAP SuccessFactors logo

Carerix → SAP SuccessFactors

Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central

Greenhouse logoSAP SuccessFactors logo

Greenhouse → SAP SuccessFactors

Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.

Discuss your integrationSecurity documentation