Recruitment to HR
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
With an integration between Bullhorn and Oracle HCM Cloud, the first approved placement of a candidate who joins your payroll becomes a pending worker in Oracle, with legal employer, location code, projected start date and FTE. Freelancers from Bullhorn stay out of Oracle, and a next placement of the same person becomes an alert for HR.
What the integration does
Organisations that place consultants or seconded staff through Bullhorn and manage their staff in Oracle HCM Cloud create a pending worker by hand after a placement. HR converts hours per day to FTE and has to check with every next assignment whether the person is already in Oracle.
- The recruiter approves the Placement in Bullhorn.
- KoppelHet reads the placement from the event queue and keeps contractors out of Oracle.
- If the candidate is not in Oracle yet, KoppelHet creates a pending worker.
- If the candidate is already there, an alert goes to HR.
- HR completes the onboarding and converts the pending worker to an employee.
What to watch for with Bullhorn and Oracle HCM Cloud
- We did not find an Oracle HCM integration of Bullhorn's own; Oracle only appears with Bullhorn partners as Taleo, Oracle's recruiting system. KoppelHet reads the placements from Bullhorn's event queue and writes with Oracle's REST API.
- Oracle first takes in a new colleague as a pending worker, with a projected start date. For that date KoppelHet takes the day on which paid employment starts according to the Bullhorn placement, and that day is also the effective date of the call.
- Bullhorn records hours per day per placement, Oracle the size as FTE and headcount. KoppelHet multiplies by the working days per week from the table and divides by the employer's full week in Oracle; if the hours are missing, the hire stops with an alert.
- A candidate can get many placements in a row in Bullhorn. Only for the first does KoppelHet create a pending worker; after that KoppelHet recognises the person by the Bullhorn candidate number in its own link table and a new assignment goes to HR as an alert.
- In Bullhorn a candidate's country is stored as a number, with labels through the meta call. Oracle wants a legislation code such as NL or US with name and phone. KoppelHet translates the number with a table; an unknown country holds the hire back.
- The cost centre field on a placement is the client's cost centre and drives invoices. It says nothing about the own organisation, so KoppelHet does not put it in Oracle; employer and business unit follow from the assignment's location.
- On a placement, candidate and job order cannot be changed afterwards. If a placement is under the wrong name, the recruiter creates a new one; KoppelHet tells HR that the earlier pending worker in Oracle must be dealt with.
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
Do freelancers go to Oracle too?
Not in the first version. Contractors as contingent workers in Oracle can be added later as an extension.
Who converts the pending worker to an employee?
HR, in Oracle. Oracle then completes the conversion with a scheduled process.
Does the salary of the placement come along?
Not in the first version. HR records pay during onboarding in Oracle.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Bullhorn through the REST API after OAuth 2.0 and a REST login with BhRestToken. Event subscription on Placement (INSERTED and UPDATED) with GET event/subscription. Placement employeeType, employmentStartDate, hoursPerDay, jobLocation, positionCode and costCenter (Client Cost Center); Candidate firstName, lastName, email and address.countryID.
- Oracle HCM Cloud through POST /hcmRestApi/resources/11.13.18.05/workers with header effective-Of RangeStartDate; workRelationships with LegalEmployerName and WorkerType P; assignments with ActionCode ADD_PEN_WKR, ProjectedStartDate, BusinessUnitName, LocationCode and workMeasures (FTE and HEAD). Conversion through ReadyToConvertFlag by HR.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Bullhorn | Field in Oracle HCM Cloud | Notes |
|---|---|---|
Candidate firstName en lastName | names FirstName en LastName | |
Candidate email | emails (EmailType H1) | |
Candidate address.countryID | LegislationCode | Bullhorn number translated to country code |
Placement employmentStartDate | ProjectedStartDate en effective-Of RangeStartDate | |
Placement hoursPerDay | workMeasures FTE | Times working days, divided by the employer's full week |
Placement jobLocation of positionCode | LegalEmployerName, BusinessUnitName en LocationCode | Lookup table |
Placement employeeType | Filter: alleen Employee of W2 |
Related
Bullhorn → AFAS Profit
Bullhorn to AFAS integration: a consultant's first placement starts onboarding
Bullhorn → BambooHR
Bullhorn to BambooHR integration: first placement as an employee with a status row in BambooHR
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel