Integrating Oracle Taleo and Fusion HCM Cloud Services: Part 1
Many Oracle customers are implementing some combination of Taleo and Fusion HCM Cloud offerings, taking advantage of the most current SaaS features and functionality. One of the big questions this approach immediately begs is that of how to integrate the two systems in the most efficient way possible, as they are intended to work together to reduce the level of manual effort your organization spends keying and maintaining data.
The approach an organization adopts will vary, depending on its needs and its current deployment. Out-of-the-box integrations between Fusion and Taleo exist that can be leveraged, but doing so requires (a) Taleo configuration to fall within specifically defined parameters (which you can read more about here), and
(b) that Taleo is not implemented before Fusion.
It’s critical to understand that if your organization has already implemented any Taleo offering, you will not be able to leverage Oracle’s delivered Fusion/Taleo integrations (unless you implement Fusion and then re-implement Taleo; but that, of course, requires an enormous effort).
Oracle is working on building these integrations for customers in your situation, but there’s no estimated release date yet. So for now, custom integrations must be built to fill the gap.
Building these integrations from scratch requires time and technical knowledge of both Fusion and Taleo. Recently, Velocity worked with an existing Taleo customer to successfully implement Fusion, including integrations between the two systems that automatically administer two types of data flow:
Transmitting organizational and user data from Fusion to Taleo
Transmitting new hires and rehires from Taleo to Fusion
In this post, I deal with #1. I will return to #2 in a subsequent post.
Extracting Data from Oracle Fusion HCM
After implementing Fusion HCM and it becomes your system of record for organizational and user data, that data can be extracted in a series of files and then uploaded into Taleo through Taleo Connect Client (TCC) to sync the Smart Org configuration. Custom extracts out of Fusion can be built using either HCM Extract or BI.
At our client, Velocity used BI to build six different extracts (with SQL data models and rtf template reports) that generated six respective data files containing the latest location, department, organization, job, user and candidate information. Because Fusion was replacing their PeopleSoft system, which was already integrated with Taleo, the files we generated simply had to match the format of the existing files generated from PeopleSoft, with the exception of several tweaks. Note that if you are not an existing Taleo customer and you find that the Taleo configuration you ultimately build isn’t compatible with Oracle’s out-of-the-box integrations with Fusion, you will need to define on your own the structure and format of the files to be loaded to Taleo through TCC.
To automate the data flow from Fusion to Taleo, each extract can be scheduled to run recurrently at any time and frequency you desire (our client chose once/day). BI extracts can be set up to create the data files on either Fusion’s designated SFTP server or some other server your organization specifies. Our client chose to create the files on Fusion’s SFTP server and then use a third-party software to automatically log on, retrieve the files, and load them to the Taleo server. At that point, their TCC programs were scheduled to automatically read the files and upload the updated data to the Smart Org, syncing Taleo with Fusion on a daily basis.
This completes a basic overview of the process flow from Fusion to Taleo. Again, building these integrations requires significant time and technical knowledge of both systems, so you will need to plan your resources accordingly if you embark down this path. But knowing what it entails will help you better manage a critical component of your implementation and increase your overall odds for success.