hcm cloud service definition fusion hcm taleo integration connectivity

8/18/2019 HCM Cloud Service Definition Fusion HCM Taleo Integration Connectivity

1/8

Oracle Applications Cloud ServiceFusion HCM to Taleo Recruiting IntegrationConnectivity

O R A C L E W H I T E PA P E R | J A N U A R Y 2 0 1 6


2/8

ORACLE FUSION HCM CLOUD SERVICE – FUSION HCM T ALEO RECRUITING INTEGRATION CONNECTIVITY

Disclaimer

The following is intended to outline our general product direction. It is intended for information

purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any

material, code, or functionality, and should not be relied upon in making purchasing decisions. The

development, release, and timing of any features or functionality described for Oracle’s products

remains at the sole discretion of Oracle.


3/8


Fusion HCM-Taleo Recruiting Integration Connectivity

This document provides information about how to complete a service request (SR) to connect the

Oracle HCM Cloud Service to Taleo Recruiting to leverage the delivered integration between these two

products.

Note: This document and set of instructions does not apply if you are using a custom approach to

integrate Fusion HCM and Taleo Recruiting Cloud Services.

CHARACTERISTIC DESCRIPTION

Compatible

Release(s):

Oracle supports this service with the following release pairings:

Fusion HCM Release 9 & Taleo 13c, 14a, 14b, 15a

Fusion HCM Release 10 & Taleo 14a, 14b, 15a

Fusion HCM Release 11 & Taleo 15a

Service Type: Integration

Definition: This service enables connectivity between Fusion HCM and Taleo Recruiting

environments for the purpose of using Oracle’s out-of-the-box integration between the

two systems. Doing so allows customers with both products to migrate:

Foundation data from Fusion HCM to Taleo Recruiting

New hire candidate and requisition data from Taleo Recruiting to Fusion HCM

Employee and user data from Fusion HCM to Taleo Recruiting

Note that the use of this delivered integration requires that you implement Fusion

HCM before Taleo Recruiting. Customers who have implemented and are using

Taleo Recruiting and wish to integrate it with Fusion HCM must implement a custom

solution, using the integration tools provided by the two products.

To fully integrate Fusion HCM and Taleo Recruiting, you must file this connectivity SR

as well as a separate SR to establish single sign-on between the two systems. For

more information, see the section below entitled Related Services.

Business Need

Met:This service request establishes the connectivity required to integrate the recruiting

functions of Taleo Recruiting with the Fusion HCM Cloud Service.

Typical

Frequency: Once per implementation.

Fulfillment

Method: You file the SR and Cloud Central Support works with you to ensure the request is

fulfilled.

Formatted: Space After: 0.6 line


4/8



Fulfillment

Considerations:Plan ahead.

A 2-week minimum advance notice is required. File your request at least two

weeks prior to the date you need service fulfilled, to avoid any delay or disruption

to your implementation schedule.

No downtime is required.

SR Filing

Guidelines:Your SR may request integration between:

A Fusion HCM non-production environment to a Taleo non-production

environment

Your Fusion production environment to your Taleo production environment

Both options 1 and 2.

You can submit a Service Request (SR) to enable Fusion HCM and Taleo Recruiting

Integration Connectivity by completing the following steps.

1. Log on to My Oracle Support (MOS).

2. Select Create SR from the Services Requests section or tab.

3. Under the What is the Problem? section, enter Taleo Recruiting Integration as

the Problem Summary.

4. Under the Where is the Problem? section, select the Cloud tab and enter the

following:

Service Type: Oracle Fusion Global Human Resources Cloud Service

Problem Type: Taleo Integration -> Taleo Recruiting Connectivity

Support Identifier: Defaults to your CSI number.

5. Click Next and provide the requested information, which will be similar to the list

below.

The Fusion and Taleo non-production URL’s and the target date by

which you wish the in tegration completed and/or:

The Fusion and Taleo production URL’s and the date on which you are

targeting going into production.

Select the version of Taleo Recruiting with which you are integrating.

Provide contact information for the person at your organization who is

managing this integration.

How to Validate

ServiceYou should validate that the integration works as expected by first using it between



https://support.oracle.com/https://support.oracle.com/https://support.oracle.com/https://support.oracle.com/


5/8



Fulfillment: Fusion and Taleo non-production environments with a small set of data. Review the

Integration Guide for information about setting up Taleo Recruiting and performing the

first data transfer.

RelatedService(s):

Fusion HCM and Taleo Recruiting Integration – Single Sign-On (SSO):

You must open a separate SR for single sign-on (SSO) to fully implement the

integration between Fusion HCM and Taleo Recruiting. You may file the SSO SR at

the same time as the connectivity SR but note that SSO will not work until you have:

Established connectivity via the Fusion HCM and Taleo Recruiting Integration – Connectivity SR; and

Completed an initial Fusion HCM data load and data migration, using either a test load

of users/employees (to verify SSO) or a full load of all data from Fusion to Taleo (to fully

implement SSO).

Until you have completed these tasks and are using single sign-on, you may access

Taleo Recruiting using the default (i.e., non-SSO) URL. Once you are ready for SSO,

your users should access Taleo Recruiting using the SSO URL.

For more information, see the white paper attachment, “Fusion HCM Taleo Recruiting

Integration Single Sign On,” in My Oracle Support document, Doc ID 1534683.1

Fusion Environment Refresh and Taleo Zone Refresh:

After connectivity has been created between Fusion HCM and Taleo Recruiting,

pairings are established between your Fusion and Taleo production environment as

well as your non-production environments. When you need to migrate data from either

system’s production environment to its non-production environment (for example,

Fusion HCM), you must synchronize that request with a corresponding data migration

in the other system (for example, Taleo Recruiting). If you do not do so, you will very

likely introduce data integrity problems between the non-production environments

because the data will no longer be synched between them. Plan ahead to have your

Fusion Environment Refresh and Taleo Refresh services completed as closely to each

other as possible because integration processes can NOT be run until both refreshes

are complete.

Oracle recommends the following guidance to avoid data integrity problems between

your Fusion and Taleo non-production environments and to minimize the amount oftime during which you cannot run in tegration processes:

Schedule your Fusion Refresh and Taleo Refresh to occur as closely to each other as

possible. Note that there is no dependency on which runs first and there is no reason

that they cannot run concurrently.

https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1534683.1&_adf.ctrl-state=11va0h6810_9&_afrLoop=467426963454057https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1534683.1&_adf.ctrl-state=11va0h6810_9&_afrLoop=467426963454057https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1534683.1&_adf.ctrl-state=11va0h6810_9&_afrLoop=467426963454057https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1534683.1&_adf.ctrl-state=11va0h6810_9&_afrLoop=467426963454057


6/8



Do NOT run any Enterprise Scheduling Service (ESS) integration processes after either

the Fusion Refresh or Taleo Refresh has started and before both have completed. If

you have scheduled these processes to occur on a prescheduled basis, remove that

scheduling.

After both refreshes have completed, you may resume running integration processes

between all environments.

For more information, see the white paper attachments in, “Oracle Applications Cloud

Service Definition – Environment Refresh” in My Oracle Support document, Doc ID

2015788.1

Related

Information on

MOS:

N/A

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=2015788.1


7/8


Oracle Corporation, World H eadquarters

500 Oracle Parkway

Redwood Shores, CA 94065, USA

Worldwide Inquiries

Phone: +1 .650.506.7000

Fax: +1.650.506.7200

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and thecontents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability orfitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations areformed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and

are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo aretrademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 1115

Oracle Applications Cloud Service

Fusion HCM Taleo Recruiting Integration ConnectivityJanuary 2016

C O N N E C T W I T H U S

blogs.oracle.com/oracle

facebook.com/oracle

twitter.com/oracle

oracle.com


8/8

hcm cloud service definition fusion hcm taleo integration connectivity

Documents