Christina Yue, Customer Learning Manager |

It is critical that system administrators are aware of the integrations possible between Taleo and other systems to determine if a Taleo integration makes sense for their organization.  Nikki Bruner, Solutions Architect with Metaformers Inc. and the functional implementation lead for Erlanger Health System’s (EHS) successful integration of Taleo Recruiting and Onboarding with their PeopleSoft Core HR System, shares highly detailed and technical information about their integration experience.  EHS is the seventh largest public hospital in the United States.  Prior to their Taleo implementation, they ran PeopleSoft HCM and Financials, as well as PeopleSoft’s Talent Acquisition Management Version 9.2 for their recruiting system.

Taleo Integration Methods

Two Taleo integration methods exist – Web Services Application Program Interface (API) and Taleo Connect Client (TCC).  Several key factors impacted EHS’s decision to use TCC as their integration method.  Many clients such as EHS lack their own development platform; and rather than procuring one, TCC can be used as such.  Additionally, Bruner highlights the robustness of TCC, the increased control provided through features such as its scheduling feature, and its “functional friendly” and intuitive appeal, particularly for system administrators lacking developer backgrounds.  All integrations allowed for EHS’s data to be maintained in PeopleSoft while being available for use in Taleo.

Client Integration Examples

EHS chose to have four types of integrations:

1. Job Template:  For EHS, job requisition templates were created from what was already stored within PeopleSoft.  Not only did EHS have templates and position information that differed by job code but also templates that differed by a combination of job code and department.  With Taleo, there is also the ability to create user-defined fields (UDFs) to include any information wanted on a requisition with customizations such as internal and external description options to differentiate what an applicant may view on the job portal compared to what a recruiter may view about a position.
2. Department:  Using large-user defined selections (LUDS) and the creation of custom fields, EHS made the accommodations necessary to fit their own departments’ reporting needs.  Through SmartOrg and Organization-Location-Job Fields (OLF), unique customizations are possible to match how users do business.  Take note:  when taking actions to modify OLF in SmartOrg, the system must be in maintenance mode.  EHS resolved this by scheduling a nightly maintenance mode using TCC.
3. Employees:  Among its customizations, EHS chose to give all active employees in PeopleSoft user accounts and applicant profiles in Taleo, not because day-to-day business required it, but as a change management initiative.  The outcome was improved user adoption.  An ongoing hourly integration marked employees as active, terminated, or resigned to support different business processes, recruiting streams, and workflows within the organization.
4. New Hires:  Bruner refers to EHS’s final integration as the most popular across her clients:  new hire integration.  This integration allows an organization to specify what and when information is collected into Taleo and brought into its base system.  Among other essential new hires personal information, the maintenance of employee certification and licensure information was of top priority to EHS and is on their radar for a future integration with a license certification validation vendor.

Watch the full video here. 

Access more content through Quest Oracle Community.  For more stories from our customers about their Taleo Integration with Oracle Cloud HCM subscribe for FREE to the Quest cloud e-newsletter. Get weekly updates on the many educational and networking resources Quest delivers to its user community.