In this four-part series, we would be covering different aspects of Oracle HCM Cloud Rel 11 to TEE 14A and above.
The first part of this series covers the overview of OOTB integration between Taleo and Oracle HCM Cloud.
The OOTB integration has been developed for new Fusion & Taleo implementations with Fusion to be setup first and Taleo implemented subsequently. The OOTB solution requires a specific Taleo configuration. This is specific in terms of Organization hierarchy, location hierarchy etc. This is one of the key reasons why this solution is targeted for Fusion first customers. Taleo first customers are not likely to have such a configuration. Customers with Taleo setup first are advised to integrate with Fusion using TCC, HDL and HCM Extract until the integration is further modified to be more flexible to customer needs.
SR needs to be created with Oracle first for Oracle Cloud HCM to point to Taleo instance.
The following diagram illustrates the various stages of integration.
In the first stage of integration, OLF (Organization, Location and Function) data is loaded from Oracle HCM Cloud to Taleo. The second stage of integration pushes the selected candidate’s information to Oracle HCM Cloud from Taleo. The final stage consists of transferring Employee information (User, Employment etc.) to Taleo to update the ‘selected candidate’ as Internal Employee.
Following table provides the details of ESS process, the data that is exchanged by the process and the recommended schedule.
In the next part of the series, we will talk in detail about the OLF data integration with Taleo and the key talking points.