Developing customized integrations between Fusion HCM and Taleo

Introduction
This document describes how to develop customized integrations between Fusion HCM and Taleo
Recruiting using tools such as Taleo Connect Client, File Based Loader (FBL) and HCM Extract. These
integrations enable users to move data between the two systems. We consider a situation where Taleo
was implemented prior to Fusion HCM. Various techniques and recipes for data movement are
described. Readers of this document may choose to adopt and modify these recipes to meet their own
unique needs.
It is assumed that the reader is familiar with the use of the various tools (TCC, FBL, HCM Extract)
described in this document.
Purpose of custom integration
It is important to note that an Out-of-the-Box (OOTB) integration between Fusion HCM release 8 and
Taleo Recruiting 13B and 13C is available. The customized integration scenarios described here are
different from the Out-of-the-Box solution since they require the use of tools such as FBL, TCC and HCM
Extract. The OOTB integration is simpler and much quicker to deploy. Customized integration must be
considered only when OOTB integration is not an option.
Currently, the OOTB integration is available only for customers who implement Taleo along with (or
after) implementing Fusion. This is because a specific Taleo zone configuration is required for the
implementation of the OOTB integration. It is possible that the configuration of a Taleo zone that was
implemented before Fusion will match the requirements of the OOTB integration. In this case the
customized integration recipes described below may allow customers to preserve their existing Taleo
configuration and still move data between Taleo and Fusion HCM. These integrations can be carried out
between Fusion Release 7 & higher and Taleo version 13A & higher. The custom integration also
supports the exchange of user defined fields between the two systems, which is currently not supported
in the OOTB integration.
Typical integration process flow
The integration is designed to accomplish the following

Set up Fusion as the system of record. Fusion will be the source of foundational (work structure)
data and this data will be fed into Taleo. All Taleo processes (e.g. requisition creation) will use this
data

Export hired candidates from Taleo into Fusion. These candidates will be converted into workers in
Fusion.

The customized integration involves moving objects between Fusion and Taleo. These objects are
mapped as follows

Taleo

Fusion

Organization

Business Unit

Location

Location

Job Field

Job Family

Department

Department

Legal Employer (User Defined Field)

Legal Employer

Grade (User Defined Field)

Grade

Position (User Defined Field)

Position

Candidate, User

Worker

Talent

Talent Profile

Offer

Salary

As a prerequisite, the Enterprise level setup of the Fusion instance must be complete. This setup ensures
the mandatory Fusion data elements such as Enterprises, Reference Data Set, Legal Entity, Assignment
Status, etc. have been configured in Fusion HCM. The customized integration described in this document
consists of the following steps.
Step -1. Extracting key Fusion objects and configuring Taleo for the integration
When loading work structure or person data in Fusion using FBL, certain Fusion IDs must be present in
the FBL upload files for a successful load. The following objects must be extracted from Fusion:

Legal Employer

Assignment Status Type Id

SetId

Legal Employers and Assignment Status must be stored in Taleo as Large User Defined Selections and
initialized with the corresponding data from Fusion. The Fusion SetId is required for loading work
structure data into Fusion using FBL and must be included in the TCC scripts. Exportable status must
also be setup for each Candidate Selection Workflow in Taleo. The candidates will be ready for export
into Fusion when they reach this step/status.
Step -2. Setting up Fusion as the System of Record (Onetime Process)
Given that Taleo was implemented before Fusion, one may want to initialize Fusion work structures
Page 2

using data stored in Taleo. In this document, we assume that an initial (one time) synchronization
process is run to export Organizations, Locations, Job Fields and Departments from Taleo and then
imported into Fusion. Once this synchronization is completed, Fusion will be treated as the System of
Record. This means, any future changes to these entities are made in Fusion and then imported (synced)
into Taleo.
To keep Fusion and Taleo in sync, each object must share a unique, common identifier across the two
systems. For each object, the unique identifier is stored in the CustomerID field in Taleo and as a
GUID in Fusion. These unique identifiers are generated as part of the initial reverse sync process. For
each entity, the Taleo field Number, prefixed by a set of characters, is used as the GUID. This ensures
uniqueness of each object. For example the GUID created for Organization is BU_+ Number
(BU_987654321).
The foundation data is exported from Taleo to Fusion using TCC. The export files are output in a format
that is recognized by FBL.
Step -3. Incremental data sync between Fusion and Taleo
The two systems are in sync now and Fusion is the system of record. Incremental data changes in Fusion
are synchronized with Taleo by extracting the data from Fusion using HCM Extract and loading the
modified data in Taleo using TCC.
Step -4. Candidate selection & hiring
The systems are now ready for recruiting and hiring tasks.
Step -5. New hire export
Once the selected candidates are ready for export into Fusion, they can be extracted from Taleo using
TCC. These TCC scripts must be configured to run using a single Last Run Date and to generate the
output in the format required by FBL to load the worker data into Fusion.
Important note on Taleo zone configuration
The integration process described below assumes that the Taleo zone is configured with a single level
Organization hierarchy, a four level Location hierarchy and a single level department. The readers
should modify the TCC scripts provided with this sample (or create additional TCC Scripts) according to
their specific Taleo zone configuration requirements.
Instructions
Below we describe each step in the integration process and explain how to use the various artifacts
provided. It is assumed the Fusion HCM instance has been configured and setup with all the required
data. The prerequisites are:
TCC has been installed & Taleo zone & Fusion instance has been set-up

Page 3

 The archive containing the TCC scripts and the HCM Extract definitions has been downloaded
and saved on the C drive. The files have been extracted in the folder C:\TCCScript\. This is
important because the TCC scripts refer to the file/folder locations on the C drive.
1. Extracting key Fusion objects and configuring Taleo for the integration
Reading the Fusion Objects
Two of the key Fusion objects required for this integration are Legal Entity and Assignment
Status Type. This data is available in the XREF file. The Section -1 in the Appendix details on the
process for obtaining the XREF file. The XR_LEGAL_ENTITY.dat file contains the legal entity
information. The Assignment Status Type ID is contained in the file
XR_ASSIGNMENT_STATUS_TYPE.dat. This file contains all the assignment status types that are
defined in Fusion. The desired assignment status type ID can be selected from this file.
Generally, ACTIVE assignment, seeded in Fusion, can be used. The extraction and usage of SetID
is explained in section 2.3 below.
Creating user defined fields in Taleo to store the Fusion objects
Requisition field LUDS must be created in Taleo to store the Legal Entity and Assignment Status
Type. See appendix for the steps to create and assign the user defined field to Requisitions.
Entering the values in the user defined fields
The Legal Entity data extracted from XR_LEGAL_ENTITY.dat file must be entered in the Legal
Employer LUDS created to store this data. Navigate to the Legal Employer LUDS and create a
new record. Enter the value corresponding to FusionGUID from the file into the Taleo field
Code; enter the Description from the file into the Taleo field Description and select the radio
button Always active. Click the button Done.

Page 4

The Assignment Status Type ID must be entered in the LUDS created to store this data in Taleo.
Navigate to the Assignment Status Type ID LUDS and create a new record. Enter the
FusionGUID value corresponding to the description ACTIVE_PROCESS from the file
XR_ASSIGNMENT_STATUS_TYPE.dat into the Taleo field Code; enter a suitable Description in
the Taleo field Description and select the radio button Always active. Click the button Done.

Page 5

Setting up Fusion HCM as the System-of-Record

In this step, foundational data is exported from Taleo and loaded into Fusion.
2.1 Generating a unique identifier for each record that is exported from Taleo
The provided TCC scripts must be executed to generate these identifiers. There is one script for
each object (Organization, Location, and Job Field). Only TCC export files are provided. The TCC
configuration file required to run the export file must be manually created. See Appendix for
how a configuration file can be created.
The scripts are located in the folder - C:\TCCScript\import\GUIDGenerator\
Generate identifiers for Organizations (Business Units)
2.1.1

Create a TCC configuration file called BU_data_validator_cfg.xml. Use it to load and run
the provided export file BU_data_validator_sq.xml.

2.1.2

Upon successful execution, this script generates a file with two fields from the
Organization entity - Number and CustomerID. This script generates the CustomerID
field for those records where this field is empty.

2.1.3

The value of CustomerID generated is BU_+ Number.

2.1.4

Set the output file name to C:\TCCScript\DataFiles\Organizations.csv

Generate identifiers for Departments (Departments)

2.1.5

Create a TCC configuration file called DEPT_data_validator_cfg.xml. Use it to load and

run the provided export file BU_data_validator_sq.xml.

2.1.6

Upon successful execution, this script generates a file with two fields from the
Department entity - Number and CustomerID. This script generates the CustomerID field
for those records where this field is empty.

2.1.7

The value of CustomerID generated is DEPT+Number

2.1.8

Set the output file name to C:\TCCScript\DataFiles\Dept.csv

Generate identifiers for Locations (Work Locations)

2.1.9

Create a TCC configuration file called LOC_data_validator_cfg.xml. Use it to load and run
the provided export file LOC_data_validator_sq.xml

2.1.10 Upon successful execution, this script generates a file with two fields from the Location
entity - Number and CustomerID. Manually enter the CustomerID field for those records
where this field is empty.
2.1.11 The value of CustomerID must be LOC+Number
2.1.12 Set the output file name to C:\TCCScript\DataFiles\Loc.csv

2.2 Update records in Taleo with the generated unique identifier

Records in Taleo must be updated with the unique identifiers generated in the previous step.
Page 6

This is done by running a TCC import script for each entity.

Update Organizations with unique identifier
2.2.1

Create a TCC configuration file called BU_ID_BACKFILL_cfg.xml. Use it to load and run
the provided import file BU_BACK_FILL_ID_ld.xml.

2.2.2

This script uses the field Number to lookup the organization record and updates the
field CustomerID with the value generated in step 2.1.

2.2.3

Set the import file name to C:\TCCScript\DataFiles\Organizations.csv. Set the output

file name to C:\TCCScript\DataFiles\out.txt

Update Departments with unique identifier

2.2.4

Create a TCC configuration file called DEPT_BACK_FILL_cfg.xml. Use it to load and run
the provided import file DEPT_BACK_FILL_ld.xml.

2.2.5

This script uses the field Number to lookup the department record and updates the field
CustomerID with the value generated in the step 2.1.

2.2.6

Set the import file name to C:\TCCScript\DataFiles\Dept.csv. Set the output file name
to C:\TCCScript\DataFiles\out.txt

Update Locations with unique identifier

2.2.7

Create a TCC configuration file called LOC_BACKFILL_cfg.xml. Use it to load and run the
provided import LOC_BACKFILL_ld.xml.

2.2.8

This script uses the field Number to lookup the organization record and updates the
field CustomerID with the value generated in step 2.1.

2.2.9

Set the import file name to C:\TCCScript\DataFiles\Loc.csv. Set the output file name to
C:\TCCScript\DataFiles\out.txt

2.3 Export data from Taleo in FBL compatible format

TCC export scripts are available in the folder c:\TCCScript\export\work structure\.
Export Organizations
2.3.1

Create a TCC configuration file FT_BU_EXPORT_cfg.xml. Use it to load and run the
provided export file FT_BU_EXPORT_sq.xml.

2.3.2

The column ORGANIZATION_ID contains the unique identifier (GUID) generated in the
step 2.1. The column - ORG_INFORMATION4 contains a hardcoded value, which is the
GUID reference to the Set extracted from Fusion. This will be the Business Unit's default
set assignment. See Appendix section 1 for the process of extracting the set assignment
id from Fusion.

2.3.3

Set the output file name to

C:\TCCScript\output\BusinessUnit\F_BUSINESS_UNIT_VO.dat. This step will generate
the file that is an FBL-formatted Business Unit file.

Export Departments
This step involves the creation of FBL formatted Department and Department_detail files

Page 7

2.3.4

Create a TCC configuration file FT_DEPARTMENT_EXPORT_cfg.xml. Use it to load and

run the provided export file FT_DEPARTMENT_EXPORT_sq.xml.

2.3.5

This is the TCC extract definition to extract the Department data. The column SET_ID in
this script is hardcoded. This value must be replaced by the correct SET_ID from the
reference file as explained in the Section 1 in the Appendix.

2.3.6

Set the output file name to C:\TCCScript\output\

Department\F_DEPARTMENT_VO.dat. This step will generate an FBL-formatted
Department file.

2.3.7

Create a TCC configuration file FT_DEPARTMENT_DETAIL_EXPORT_cfg.xml. Use it to

load and run the provided export file FT_DEPARTMENT_DETAIL_EXPORT_sq.xml

2.3.8

Set the output file name to C:\TCCScript\output\

Department\F_DEPARTMENT_DETAIL_VO.dat This step will generate an FBL-formatted
Department Detail file.

Export Locations
This step involves the creation of FBL formatted Location files
2.3.9

Create a TCC configuration file FT_LOC_EXPORT_cfg.xml. Use it to load and run the
provided export file FT_LOC_EXPORT_sq.xml

2.3.10 This is the TCC extract definition to extract Location data. Complete work location
address is extracted for each location in FBL consumable format. The column SET_ID in
this script is hardcoded. This value must be replaced by the correct SET_ID from the
reference file as explained in the Section 1 in the Appendix
2.3.11 Set the output file name to C:\TCCScript\output\ Location\F_LOCATION_VO.dat. This
step will generate an FBL-formatted Location file.
2.4 Load work structures into Fusion using FBL
This step involves loading the work structure data in Fusion
2.4.1

The three folders generated in step 2.3 (BusinessUnit, Department, and Location) must
be zipped into a single archive file

2.4.2

Upload the file into UCM

2.4.3

Follow the usual process of loading content into fusion using FBL. See appendix section
2 for details

3. Synchronize work structure information from Fusion to Taleo

Once Fusion has been setup as the System-of-Records, the incremental updates (changes to the
Business Units, Departments and Locations) can be synchronized between Fusion and Taleo using
HCM Extract and TCC
3.1 Export work structures from Fusion using HCM Extract
The extraction definitions and the BI Publisher output templates are available in the folder
c:\TCCScript\HCMExtract.

Page 8

3.1.1 Upload Extract Definitions

The following extract definitions must be loaded into your Fusion instance.

BU.xsd - Extract changes to Business Units

Loc.xsd - Extract changes to Locations

Dept.xsd Extract changes to Departments

Extracts can be loaded as follows

From the Navigator click on Data Exchange

Page 9

Click on Manage Extract Definition

Click on the button Import Extract

Page
10

Import the extract definitions (.xsd files) Leave the Legislative Data Group blank

Compile the fast formulas

Page
11

3.1.2 Upload Output templates

The following output templates must be loaded into your Fusion instance

Business Unit.rtf Generate output file containing Business Units

Department.rtf Generate output file containing Departments

Location.rtf Generate output file containing Locations

Steps to upload these templates are as follows

Click on Reports and Analytics from the Navigator

Select Report

Page
12

Page
13

Click on New Report

Click on the find icon near Data Model

Page
14

Select Global Reports Data Model

Click on Use Report Editor and then click Finish

Page
15

Save the Report with Name Taleo under Shared Folders->Custom

Click on Upload

Page
16

Upload the three .rtf files.

Enter the Layout Name BU For Business Unit Extract, LOC for Locations and DEPT for
Departments extract layout

The three layouts will appear as in the screen below

Page
17

3.1.3 Periodically export work structures from Fusion

The loaded extracts can be executed using HCM Extract as follows

Click on Checklists under Payroll from the Navigator

Click on Submit a process or Report

Page
18

Select the extract created with its name and click on the button Next:

Enter a unique flow name; select the current date as the effective date. For the field
Business Object enter DEPARTMENT_VO for Department extract, BUSINESS_UNIT_VO
for Business unit extract and LOCATION_VO for Locations extract. For Extract type, enter
GUID. The click next

Page
19

Click to the next screen

Select As soon as possible and click next and in the following page click and click Submit

Page
20

Click on Ok and view checklist

Click on Go To Task icon

Page
21

Click on the icon to view the results

The extract can be viewed by clicking on the link

Page
22

Further details on using HCM Extract are available at:

http://docs.oracle.com/cloud/latest/globalcs_gs/OAPNT/F1006720AN111DC.htm
BI Publisher can be configured to schedule and deliver the extracts. For details see the link:
http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e26384/delivery_dests.htm#sa_delive
ry
3.3. Import work structures into Taleo using TCC
TCC import scripts are available in the folder C:\TCCScript\import\merge
Import Business Units (Organizations)
3.3.1

Create a TCC configuration file BU_MERGE_FROM_HCMEXTRACT_cfg.xml. Use it to load

and run the provided import file BU_MERGE_FROM_HCMEXTRACT_ld.xml

3.3.2

Set the import file name to C:\TCCScript\DataFiles\BU Taleo.txt. The file BU Taleo.txt
contains Business Units extracted from Fusion in step 3.2

3.3.3

Set the output file name to C:\TCCScript\DataFiles\out.txt

This script runs a merge operation. Any updates made to the Business Units in Fusion are
synchronized with the corresponding Taleo Organizations. Any new Business units created in
Fusion are also created in Taleo. For new Business Units, HCM Extract (step 3.2) generates the
corresponding unique identifiers (GUIDs). These GUIDs are also synchronized into Taleo.
Import Departments (Departments)
3.3.4

Create a TCC configuration file DEPT_MERGE_FROM_HCMEXTRACT_cfg.xml. Use it to

load and run the provided import file DEPT_MERGE_ld.xml.

3.3.5

Set the import file name to C:\TCCScript\DataFiles\Dept Taleo.txt. The file Dept
Taleo.txt contains Departments extracted from Fusion in step 3.2

3.3.6

Set the output file name to C:\TCCScript\DataFiles\out.txt

This script runs a merge operation. Any updates made to the Department data in Fusion is
updated in Taleo. Any new Departments created in Fusion are also created in Taleo. For new
Departments, HCM Extract generates the corresponding unique identifiers (GUIDs). As a part of
this merge operation, the GUID is also synchronized with Taleo
Import Locations (Work Locations)
3.3.7

Create a TCC configuration file LOC_ID_SYNC_cfg.xml. Use it to load and run the
provided import file LOC_ID_SYNC_ld.xml.

3.3.8

Set the import file name to C:\TCCScript\DataFiles\Loc Taleo.txt. The file Loc Taleo.txt
contains Locations extracted from Fusion in step 3.2

3.3.9

Set the output file name to C:\TCCScript\DataFiles\out.txt

The script runs an update. At this time, only updates to existing locations made in Fusion can be

Page
23

applied to the locations in Taleo. New locations created in Fusion cannot be brought back into
Fusion. The Location is set as a 4 level hierarchy in Taleo. The locations are flat in Fusion. Using TCC
the location hierarchy cannot be created and imported into Taleo.
4. New Hire export
Exporting new hire data (HIRES) using provided TCC Scripts
Once the two systems have been setup, new hires from Taleo can be exported into Fusion using
TCC and FBL. The folder FTExtract contains the TCC scripts and the batch files required to create
the new hire export in the format required for loading this data in Fusion using FBL. The new
hire export can be scheduled to run on a regular basis, generally daily. This folder contains
several TCC scripts for extracting the Person and Work Relationship data from Taleo. Below is
the list of the TCC scripts and the corresponding Fusion object generated from these scripts.

FT_NH_PERSON_sq.xml - This script generates the data corresponding to Fusion Person

object. The resulting output is the F_PERSON_VO.dat file.
FT_NH_PERSONNAME_sq.xml - This script generates the data corresponding to Person
Name. The resulting output is the F_PERSON_NAME_VO.dat file.
FT_NH_PERSON_ADDRESS_sq.xml - This script generates the data corresponding to
Person Address. The resulting output is the F_PERSON_ADDRESS_VO.dat file.
FBL_PERSON_PHONE_sq.xml - This script generates the data corresponding to Person
Phone number. The resulting output is the F_PERSON_PHONE_VO.dat file.
FBL_PERSON_EMAIL_sq.xml - This script generates the data corresponding to Person
Email. The resulting output is the F_PERSON_EMAIL_VO.dat file.
FT_NH_WORK_ASSIGNMENT_sq.xml - This script generates the data corresponding to
Fusion Assignment object. The resulting output is the F_ASSIGNMENT_VO.dat file
FT_NH_WORK_RELATIONSHIP_sq.xml - This script generates the data corresponding to
work relationship in Fusion. The resulting output is the F_WORK_RELATIONSHIP_VO.dat
file
FT_NH_WORK_TERM_sq.xml - This script generates the data corresponding to Work
term details. The resulting output is the F_WORK_TERMS_VO.dat file

These scripts can be modified as needed, that is, the Taleo data elements mapped with Fusion
fields in these TCC scripts can be changed as required, however, the format, name and path of
the output files must not be changed.
All the scripts in this folder use the same Last Run Date for extracting the new hire data. This
ensures the data extracted for each object is within the same time frame and thus there are no
phantom records in any of the extracts. If a script fails during execution, the last run date will
not be updated. Once the error has been corrected, the extract can be rerun individually or the
entire process can be rerun. When the entire process is rerun, any script that has already run

Page
24

successfully will not rerun but the remaining scripts will be executed.
Logging and alerting is also supported with the Apache log4j library. It can be configured in
\FTExtract\bin\Windows\core\bin\log4j.xml. This file can also be configured to email
notifications in case of errors. The log files are created during the execution of the scripts in the
folder FTExtract\log\. For detailed presentation of the log4j API, please refer to
http://logging.apache.org/log4j/1.2/
Additional details on the FTExtracts are included in the Appendix in section 4. To run the new
hire extract, you must first setup the environment as explained in the following steps:
4.1

Set up TCC
4.1.1

Set up a user with the user type System Integration (Administrator WebTop) in
your Taleo zone. To create a new user account, log into your Taleo environment
and navigate to Configuration > SmartOrg Administration > User Accounts.

4.1.2

Download and install TCC on your server.

4.1.3

Synchronize the UDFs. Log in to TCC using this user create above and
synchronize the UDFs by clicking to the icon as highlighted in the screenshot
below.

The tasks listed above are explained in detail under the section "Installation", in the Taleo
Connect User Guide.
4.2

Environment configuration
You must configure the environment to run TCC from the command line
4.2.1

Edit the environment.bat file and set the TCC_HOME environment variable to
the root of the TCC installation (e.g. C:\Program Files\Taleo Connect Client).

4.2.2

Edit the bin\TaleoConnectClient.bat file to put the correct proxy settings.

Page
25

4.2.3

Edit the configboard\default.configuration_brd.xml file inserting email settings

for error notification. This can be done directly into the file or by opening in
TCC.

4.2.4

Download FTExtract.zip and extract the files on your local drive. The new hire
export process can be configured for the client staging zone. It is recommended
to copy the whole project into a different folder for staging and production
environments.

The provided batch files are designed for the Windows environment. They can be used as
samples to build the corresponding UNIX scripts if required.
4.3

Initialize last run date variable

All the TCC scripts use the same last run date for extracting the new hire data. The batch
file \bin\Windows\RunDateManager.bat initializes the last run date. Run this batch file at
least once before running the FTExtracts. This batch file can also be used to reset the last
run date when needed. Last run date is stored in the files named same as the query file
but with an extension .lrd in the folder \lrd (e.g. FT_NH_PERSON_sq.xml has a
corresponding file named FT_NH_PERSON.lrd).

4.4

Run the new hire export

Run the new hire export by executing \bin\windows\Newhire_Extract.bat script. This script runs
all the TCC scripts in a sequence and puts the results in the \data\outbound\ folder. The output
of this process is a zip file containing directories named Person and WorkRelationship. The zip
file is named in a yyyy-mm-dd_newhire.zip format. Note that there is no dependency or
mandatory sequence between extracts.
Importing the new hire data (HIRES) in Fusion using FBL
You can now load the zip file containing the Person and Work relationship data created in the
previous step in the UCM and then invoke FBL to import the file in Fusion. The section -2 in the
Appendix details on loading data into Fusion using FBL.

Page
26

APPENDIX

Page
27

Section 1 Obtaining SET Assignment value from Fusion

Different organizations within a single company often need to use different sets of reference data to
serve the same purpose. SetIDs enable you to share a set of reference data across many organizations.
Before you can transfer seed data, the .zip file that contains the .dat files with this data must be
generated by the Fusion system. Contact your Fusion system administrator to verify that this file is
available before completing the steps in this section.
Additional details on SetId:
http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e15524/bs_setid.htm
The SetId is seeded data and is available in XREF file. Here are the steps to access it:
Generate XREF file
Step 1: Login to Fusion instance
Step 2: Under Navigator click Setup and Maintenance link

Step 3: Enter Manage HCM Configuration for Coexistence in Name field and click Search, Under
Search Results section Click Go to Task icon.

Page
28

Step 4: Under Generate Mapping File for HCM Business Objects section click Submit to Generate
Latest XREF files

Page
29

Download XREF files

Step 1: Login to Fusion instance
Step 2: Under Navigator click at File Import and Export link

Step 3: Select Account as hcm/dataloader/export

Page
30

Step 4: Click at Search, select and click file

Step 5: Click Ok to start downloading XREF file into your System.

Page
31

Step 6: Access the zip file, the files are as listed below. Select the file XR_SETID_SET.dat

Step 7: Open the file and search for the FusionGUID for required SET

Page
32

Step 8: Open the Organization export definition (FT_BU_EXPORT_sq.xml) in TCC and select the
projection named ORG_INFORMATION4 . Replace the FusionGUID with the value selected in the
previous step

Step 9: Open the Department export definition (FT_DEPARTMENT_EXPORT_sq.xml) in TCC and select
the projection SET_ID. Replace the FusionGUID with the value selected in the Step 7

Page
33

Section -2 Loading data in Fusion using FBL

Step 1. Uploading the file to the UCM
To import a file in Fusion using FBL, the file must be uploaded to the UCM.
Log into the UCM,

Click on the new check-in link

Enter the following information

Type : Document-Any Generic Document

Page
34

Title : Name of the document

Security Group : FAFusionImportExport
Account : hcm$/dataloader$/export$
Content ID : Enter the Content Id (unique name of the zip file will suffice). This
value as it is a parameter needed for loading the file

Submit/ check in the file

Step 2. Loading file into Fusion using FBL

Log into Fusion

Click on Navigator> Data Exchange

Page
35

Click the link Load Data For Coexistence

Click on the Import button

Page
36

 Enter content Id and other details

Select the correct set of Business Objects (in case of work structures Business unit,
Department, etc)

Click on refresh to see the uploaded file.

This step will initiate FBL file upload.

Page
37

Section -3 Creating configuration file in TCC

In a TCC based workflow, a configuration file contains the information required to communicate with
the Taleo zone along with the path of extract or import definition and the path of the output file.
Creating the configuration file from the extract definition (sq.xml file)
Setp 1. Log into TCC and click on File>New>New Configuration Wizard

Step 2. Select the first option Based on an export specification and select the sq.xml file and click Next

Page
38

Step 3. Select the desired Taleo zone as the Endpoint and click on Finish

Step 4. In the configuration file created for the data export, the complete path and name of the output
file must be specified. This name can be specified under the Response panel.

Page
39

Step 4. The new configuration is created. It must be saved before it can be used

Creating the configuration file from the import definition (ld.xml file)
Setp 1. Log into TCC and click on File>New>New Configuration Wizard

Page
40

Step 2. Select the second option Based on an import specification and select the ld.xml file and click
Next

Step 3. Select the desired Taleo zone as the Endpoint and click on Finish

Page
41

Step 4. In the configuration file created for the data import, the complete path and name of the data file
to be imported must be specified. In addition the name and the path of an output file must also be
specified. This file contains the result of execution of the import process. The name and path of the data
file to be imported can be specified under the Request panel.

The name and the path of the output file can be specified under the Response panel.

Step 5. The new configuration is created. It must be saved before it can be used

Page
42

Creating Large User Defined Selection fields in Taleo

Steps for creating the Legal Employer User-defined Selection
Step 1.Log into Taleo and navigate to Selection Lists
Configuration > [Recruiting] Administration > [Fields] Selection Lists
Step 2. Create the user defined field
Click the Large Selections tab, then the Custom tab.
Click New...
In the Code field, enter Fusion_LegalEmployers.
In the Name field, enter Fusion_LegalEmployers.
In the Language Requirements section, select the option Require descriptions in
WebTop languages.
The selection and its elements will be available in the Recruiting Center only.
Do not select the option Activate effective dating.
In the Associated Structure Type menu, select Organization.
Do not select the option Require mapping for every element.
Translate the selection into all available languages. Languages are available at the upper
right of the page.
Click Done.
Step 3. Associate the field to Requisitions
Go to the Fields configuration page
Configuration > [Recruiting] Administration > Fields
Click Requisition.
Click Create User-defined Field.
In the Type list, select Fusion_LegalEmployers.
Page
43

In the Name field, type Fusion_LegalEmployers_UDF.

In the Label field, type Fusion Legal Employer.
In the Attributes section, select the following:
Display code.
Display description.
Display the folder tree.
Click Save.
Back on the Requisition Fields list, click Show User-defined Fields.
Click Fusion_LegalEmployers_UDF.
Click the Edit Field Availability link.
Select the Taleo Recruiting option.
Click Save.
Steps for creating the Fusion_Status_Type User-defined Selection
Step 1.Log into Taleo and navigate to Selection Lists
Configuration > [Recruiting] Administration > [Fields] Selection Lists
Step 2. Create the user defined field
Click the Large Selections tab, then the Custom tab.
Click New...
In the Code field, enter Fusion_LegalEmployers.
In the Name field, enter Fusion_LegalEmployers.
In the Language Requirements section, select the option Require descriptions in
WebTop languages.
The selection and its elements will be available in the Recruiting Center only.
Do not select the option Activate effective dating.
In the Associated Structure Type menu, select Organization.
Do not select the option Require mapping for every element.
Translate the selection into all available languages. Languages are available at the upper
right of the page.
Click Done.
Step 3. Associate the field to Requisitions
Go to the Fields configuration page
Configuration > [Recruiting] Administration > Fields
Click Requisition.
Click Create User-defined Field.
In the Type list, select Fusion_LegalEmployers.
In the Name field, type Fusion_Status_Type.
In the Label field, type Fusion Assignment Status Type ID.
In the Attributes section, select the following:
Display code.
Display description.
Display the folder tree.
Click Save.
Back on the Requisition Fields list, click Show User-defined Fields.
Click Fusion Assignment Status Type ID.
Page
44

Click the Edit Field Availability link.

Select the Taleo Recruiting option.
Click Save.

Note: To make the user-defined field visible in the Taleo Recruiting Center, the customer needs to
determine if and where the user-defined field should be displayed (for example, requisition form or
requisition template). For details, refer to the Field Layout chapter in the Oracle Taleo Enterprise Recruiting Configuration Guide.

Page
45

Section -4 Process flow of new hire export

1.

Execution Flow

The extraction process used to retrieve new hires is described in the following diagram (The
figure is the representation of individual extract process).

The above diagram is shows one extract being executed. Due to the nature of these extracts for
new hire data from Taleo, it is necessary to extract multiple files. The Newhire_Extract.bat
contains the sequence of these extracts to be run.
2. Execution steps
There is one common cfg.xml file which is delivered for managing all the extracts in order to
ensure all extracts use the same LRD. The steps within this cfg.xml file are listed below:

The pre & processing steps in grey

are non standard TCC steps
included in the scripts.
The cfg.xml can be extended or
modified to meet the specific needs
of the environment within which it
is being used via TCC.

Recruiting_PRO_cfg.xml Steps

Page
46

Explanation of the steps

Step

Description

LRDPreStep

Reads the last run date (LRD) from the local .lrd file and get the current
run date (CRD) from the local machine. These date/stamp values are used
to substitute the LRD filter within the sq.xml extract specification with a
Between LRD And CRD filter.
As delivered the step is configured that the CRD and LRD are
synchronized on midnight, which means the extracts are filtered from
midnight on the last run date to midnight on the current date. This step
also prevents running twice the same extract on the same day, by
comparing the CRD and LRD. (Custom)

Prepare Export

Internal TCC step to prepare the export request. (Standard)

Wrap SOAP

Wraps the extract request into a SOAP envelope. (Standard)

Send

Send the extract request to the Oracle Taleo Integration Server hosted
within Oracle's data center. (Standard)

Poll

Polls the Oracle Taleo Integration Server at a given interval until the
extract request has been processed. (Standard)

Retrieve

Retrieve the result file for the extract request from the Oracle Taleo
Integration Server. (Standard)

RaiseExportErrorPostSte
p

This step forces an exception in some cases where TCC does not. E.g.
When the daily extract limit is reached, an error is signaled in the file
contents, but the process does not fail. This caused the LRD to be falsely
updated. This step is to prevent this. (Custom - optional - usefully if large
amounts of data are already been extract from the zone on a daily basis.)

Strip SOAP

Removes the SOAP envelope and renders the result in flat file format.
(Standard)

Transform with XSL

A custom XSL transformation to prepare the data for the next step.
(Custom - optional)

ReplaceAllPostStep

Replace a series of characters with their substitute within content of the

result file. (Custom - optional, but useful for scrubbing data)

RemoveEmptyLinesPostS
tep

TCC leaves an empty line at the end of the results file. This step removes
it before appending the header and footer.

ExportHeaderFooterPost
Step

Append a header and footer to the file contents, based on a template.

(Custom - optional)

LRDPostStep

Overwrites the previous LRD with the actual CRD only if the whole
process was successful.

Page
47

3. List of included files in FTExtract folder

Following folders and files are included:
/bin/Windows

Directory for executable scripts

Cleanup.bat

Delete files and subfolders that are older than a

given number of days.

Newhire_Extract.bat

Script for running all the new hire extracts from

Oracle Taleo Recruiting

RunDateManager.bat

Script for the run date manager

/bin/Windows/core Directory for TCC.bat executable script

TCC.bat

Main script used for running the local instance of

TCC.

/bin/xsl/ Directory for Host retrieval script

GetDefaultHost.xsl

XSL transformation to retrieve host information

/configboards
default.configuration_brd.xml

Configuration board containing the required

parameters for executing the TCC extract scripts

/doc
TCCCustomSteps_1.4.37-doc.zip

Java docs on the custom steps used within the

Extract process.

/data/outbound
zipcreater.bat

Creates a zip file containing the directories Person

and WorkRelationship and named as yyyy-mmdd_newhire.zip.

/featurepacks
Recruiting_Taleoxxx.x.x.pip

/lib

The integration PIP file for the product version that

is being used. This will need to be provided copied
from the Feature pack folder in the main
installation directory of TCC or the FP location
changed in the environrment.bat file to the main
installation directory.

Directory for Java libraries used for the custom steps

Page
48

TCCCustomSteps_7.5.5.jarLibrary of
TCC Custom Steps

Developed by Taleo Technical Services. Also

contains the source code

velocity-dep-1.5.jar

Apache Velocity templating

(http://velocity.apache.org/)

velocity-tools-generic-1.4.jar

Apache collection of utility classes for building

Velocity
templates
(http://velocity.apache.org/tools/releases/1.4/ge
neric/)

/scripts

library

Directory containing the for TCC scripts

Recruiting_PRO_cfg.xml
/scripts/xsl

engine

TCC configuration file for standard extracts

Directory XSL transformation files

CustomFieldsToCSV.xsl

Stylesheet to transform the result of a "All

Custom Fields" query in CSV format. (optional)

/scripts/Recruiting/FT_NHRXtracts Directory containg the extraction scripts

Sq.xml files

Contain the extract definitions.

Page
49