X

The Oracle BI Application Blogs provides the latest and tips and tricks on Oracle BI Applications Product (OBIA)

Cross Referencing Taleo Recruiting Data With HCM

 

Applies to OTBI-Enterprise Version 2 PB 10

 

TABLE OF CONTENTS

Business Needs and Overview.. 3

Feature Overview.. 3

Supported Use Cases. 4

Oracle HCM Cloud and Oracle Talent Cloud (Taleo) Integration using the OOTB Integration Product. 5

How to set up?. 5

Configure the required parameters. 5

Custom Integration of Oracle Talent Cloud (Taleo) with Any HCM System.. 6

How to set up?. 6

Configure the required parameters. 6

Provide Cross Reference data to OTBI-E. 7

Download templates and prepare your Cross Reference Data Files. 7

Understand and Prepare your Cross Reference Data Files. 9

file_tlo_appl_empl_xref_ps.csv. 10

file_tlo_busn_location_xref_ps.csv. 11

file_tlo_dept_int_org_xref_ps.csv. 12

file_tlo_int_org_xref_ps.csv. 13

file_tlo_job_xref_ps.csv. 14

file_tlo_user_empl_xref_ps.csv. 15

Upload your Cross Reference Data Files. 16

Upload your Cross Reference Data Files using Automation. 17

Configuration and Implementation Tips. 18

Business Needs and Overview

Oracle Talent Cloud (Taleo) Recruiting module uses some basic OLF data (Organization, Location, Job) from the HCM system to get on with its business. More than often, the HCM system represents the master source of data for such items. You would pre-populate Taleo Recruiting with all potential Organizations/Departments, Locations and Job Codes from your HCM system. These are the items your Recruiters or Hiring Managers will “select” (and not “enter”) when they create a Job Requisition in Taleo. In terms of data, we essentially have the same data set in two different systems.

Candidates usually come straight into Taleo Recruiting through the portal. Some get dropped in the process of recruitment cycle, while some may be selected for on-boarding. For those selected for hire, Taleo sends the candidate’s information back to the HCM system, where the hire process kicks in. With this, we end up having the same person in two different systems, again.

These data can get changed in the individual systems and without a proper master data management mechanism, there is no way one can get a 360 degree view of the data in its “master” form. We need to be able to process the knowledge that the “Candidate X” who was interviewed in the Taleo system is essentially the “Employee Y” in our HCM system. Similarly, the Job “S/W Dev 1” in Taleo system is essentially the same as the Job “Software Developer IC1” in our HCM system. In the reporting layer, we should not need to worry about how to tie up these data that came from different sources. Our reporting should always automatically (unless chosen otherwise) show the master attributes of these entities, and the metrics should add up to these master data.

Feature Overview

OTBI-Enterprise offers a unique feature to cross reference your master data when working with a given source data. In short, the way it works is this:

a) OTBI-E stores the Master – to – Source relation in its most granular level. This is the biggest challenge and we will discuss this later in our use cases.

b) Load the data warehouse normally, as a multi-source ETL.

c) As post load steps, enrich the facts to refer to the master dimension data.

There is no difference in what you see in the final reporting layer (OBIEE Answers). You use OTBI-E, as usual, without paying any attention whatsoever about master data. You pull in your data elements to your report and rest assured that what is see is the synched-up data between your HCM system and Taleo Recruiting (well, obviously if Cross Reference feature was enabled to start with).

For the OTBI-E Recruiting subject area, the following are the dimensions that can potentially go through this Cross Referencing process:

· Employee/Candidate

· User

· Organization/Department

· Location

· Job

· Assignment

· HR Person/HR Person Legislation

You could use any of the above dimensions in your report and get advantage of the feature. On top of these, you can always use additional (and important) dimensions such as “Job Requisitions”, “Recruitment Events” and/or “Recruitment Source” seamlessly. However, since these dimensions are mastered only in your Taleo Recruiting source, they don’t have to go through the cross referencing process.

The success of the entire feature depends on the step (a) above, getting to store the Master – Source relation for each entity at a ground zero level. In the following sections on supported use cases, we will touch upon that topic and later, go to more details on what this really relates to.

Supported Use Cases

At a high level, there are two major supportable use cases. Oracle HCM Cloud (Fusion HCM) has an Out-Of-The-Box (OOTB) integration product at the application level that talks to the Oracle Talent Cloud (Taleo). This product allows those initial “pushes” of seed data (mostly OLF) from Fusion HCM into Taleo. Furthermore, the on-boarding process also allows the Taleo Candidate to be “hired” in Fusion HCM as a reverse push from Taleo into Fusion HCM. Finally, that candidate (now an employee in Fusion HCM) gets pushed again from Fusion HCM into Taleo to update its property as an “Internal Employee Candidate”.

So, the first use case is this.

1. Support those Fusion HCM and Taleo customers that use the OOTB integration product.

The flip side to this is for those cases where this OOTB product is not usable for a variety of reasons (like No-Fit, or Taleo-First-Fusion-Second kind of a situation). Or even the cases where Taleo is your recruiting cloud solution but your HCM source isn’t Fusion HCM – let’s say it is PeopleSoft or E-Business Suite or something else. Whatever be the case, in order to get going with Taleo, you must have propagated those OLF data from your HCM source into Taleo, and you must have adopted business processes that kicks in the “Hire” event in your HCM source once a candidate is selected for hire in Taleo. And so on. To do all these, you didn’t take advantage of an Oracle provided Integration Product (because there’s none) – you did it yourselves.

Therefore, the second use case is this.

2. Support all other customers who use a custom approach to HCM – Taleo integration. Note that this may also include you, a Fusion HCM customer, who didn’t employ the OOTB integration solution.

We will now go over these two use cases one at a time. The complexities differ, and so does the configuration that you carry out in OTBI-Enterprise.

Oracle HCM Cloud and Oracle Talent Cloud (Taleo) Integration using the OOTB Integration Product

So you are a Fusion HCM customer and was able to make use of the OOTB integration product to integrate your Fusion HCM with your Taleo Recruiting. Nice! More than half the work is already done. OTBI-E now already knows about the Master to Source relations and you don’t need to tell us anything about it. We will pull in things as necessary. What else do you need to configure? Just a few items as described below.

How to set up?

There are three parameters you would need to configure, and that is all. They are:

Configure the required parameters

CROSS_REFERENCE_ENABLED

This parameter is used to control the cross reference feature. For whatever reasons, if you do not wish to enable this entire feature, keep it as “N”. Else, switch it to a “Y”. This decision doesn’t have to be taken at the very first load. You can choose to turn it on at a later point as well. However, remember that once turned ON (meaning, with a value “Y”) there is no turning back. We mentioned that OTBI-Enterprise would have already enriched your fact tables referring to the master dimensions. This
cannot be undone. For whatever reasons if you choose to disable this feature, you need to carry out a “Reset Data warehouse”, or a “Full Load” in other
words.

TLO_INTEGRATED_HCM_DSN  (Taleo Integrated HCM Data Source Number)

When you registered your Fusion HCM source in BIACM, you would have picked a Data Source Number that represents this source. Put that same number here. This is how you indicate to OTBI-Enterprise to treat your Fusion HCM source as the “master” source. Obviously, the Taleo source becomes the subordinate one, but you don’t have to tell this. OTBI-Enterprise will assume that. If the CROSS_REFERENCE_ENABLED was set to “N” in the previous step, it doesn’t matter what you set for this current parameter. However, if CROSS_REFERENCE_ENABLED is a “Y”, OTBI-Enterprise needs a valid Data Source Number here.

TLO_CUSTOM_INTEGRATION (Taleo Custom Integration)

This parameter indicates that you do not use the OOTB Fusion-Taleo integration product and that you have done the application layer integration yourself. For the current use case we are dealing with, set this to “N”. The default is “N”, so just leave it like that.

Custom Integration of Oracle Talent Cloud (Taleo) with Any HCM System

So you don’t use the Fusion-Taleo integration product at the application layer. You could be a Fusion HCM customer but didn’t want to use that OOTB product, or you are a PeopleSoft HCM of E-Business Suites HRMS customer using Taleo for your Recruiting. Or your HCM source is something that is completely non-Oracle (like SAP, Workday, home-grown, whatever). But since you are running your business with Taleo Recruiting, you must have pushed those OLF data into Taleo and have a process developed as to how to turn the “on-boarding to hire” from Taleo to your HCM source. In other words, you know how to relate entities between your HCM source
and your Taleo source. Well, that’s what OTBI-Enterprise needs as data feeds from you. Plus, you set the same three parameters as before. We do in detail below.

How to set up?

Let’s get the easy part first – setting up the parameters.

Configure the required parameters

CROSS_REFERENCE_ENABLED

This parameter is used to control the cross reference feature. For whatever reasons, if you do not wish to enable this entire feature, keep it as “N”. Else, switch it to a “Y”. This decision doesn’t have to be taken at the very first load. You can choose to turn it on at a later point as well. However, remember that once turned ON (meaning, with a value “Y”) there is no turning back. We mentioned that OTBI-Enterprise would have already enriched your fact tables referring to the master dimensions. This
cannot be undone. For whatever reasons if you choose to disable this feature, you need to carry out a “Reset Data warehouse”, or a “Full Load” in other words.

TLO_INTEGRATED_HCM_DSN (Taleo Integrated HCM Datasource Number)

When you registered your HCM source (E-Business Suite or PeopleSoft or Universal) in BIACM, you would have picked a Data Source Number that represents this source. Put that same number here. This is how you indicate to OTBI-Enterprise to treat your HCM source as the “master” source. Obviously, the Taleo source becomes the subordinate one, but you don’t have to tell this. OTBI-Enterprise will assume that. If the CROSS_REFERENCE_ENABLED was set to “N” in the previous step, it doesn’t matter what you set for this current parameter. However, if CROSS_REFERENCE_ENABLED is a “Y”, OTBI-Enterprise needs a valid Data Source Number here.

TLO_CUSTOM_INTEGRATION (Taleo Custom Integration)

This parameter indicates that you do not use the OOTB Fusion-Taleo integration product and that you have done the application layer integration yourself. For the current use case we are dealing with, set this to “Y”. The default is “N”, so make sure you change it to a “Y”.

Provide Cross Reference data to OTBI-E

Providing the cross reference data (master – source relation) is the challenging work here. But there is no way out of it. OTBI-Enterprise needs to know the master entity ID for each of your source entity IDs. The steps looks not too difficult. There are currently six CSV files encompassing all the supported dimensions where OTBI-Enterprise supports cross referencing today. These are more of “configuration files” rather than “data files” – although technically you can argue the other way round. You download these configuration (template) files for your Taleo source from BIACM, add data to them, and upload them back.

As and when your cross reference data change, you re-download/edit/re-upload the files.

Note that it is not necessary for you to go overboard and provide cross reference data for all files in the first go itself. You can stagger the file delivery at times comfortable to you. Same stands for corrections to already-provided cross reference data. You can get them in as and when you find time. But until OTBI-Enterprise receives the correct cross reference data set, it cannot do proper enrichment of the facts. You might see two “same” entities as though “different” in OTBI-Enterprise. The moment OTBI-Enterprise knows they are same, they will be merged into one.

Detailed steps below.

Download templates and prepare your Cross Reference Data Files

Login to BIACM.

Go to System Setups -> Define Business Intelligence Applications Instance.

Select your Taleo source (say Taleo 14B, as in this case) and click on the Actions menu.

 

Click on Manage Source Configuration Data Files. You should see the “Manage Source Configuration Data Files” screen, as below:

Click on the “Export Source Configuration Data Files” button at the top.

It displays the six files on the left side. Move them to the right, and click on “Export”. This should export the six files as “zipped” in your local downloads folder.

Unzip the six files, as below:

1. file_tlo_appl_empl_xref_ps.csv

2. file_tlo_busn_location_xref_ps.csv

3. file_tlo_dept_int_org_xref_ps.csv

4. file_tlo_int_org_xref_ps.csv

5. file_tlo_job_xref_ps.csv

6. file_tlo_user_empl_xref_ps.csv

These are the six files where you need to provide the cross reference data to OTBI-Enterprise. To know more about the content of these files, you will need to go through the following section about the files.

Understand and Prepare your Cross Reference Data Files

Depending on your master source (E-Business Suites, or PeopleSoft, or Fusion) you should look carefully at the description of the “MSTR**” columns for that source. The “SRC**” columns are about Taleo, which are essentially your source entities. They follow Taleo terminology, such as Candidate Number, and so on.

Go through the file and column descriptions of these potential six cross reference CSV files. You need to be very clear in what you provide here, as your reporting experience is going to heavily depend upon that.

file_tlo_appl_empl_xref_ps.csv

Description: Stores the Taleo Candidate to Master Employee reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM source registration

2

SRC_CANDIDATE_NUMBER

Source Candidate Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
Candidate Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM
source (such as PSFT, EBS, or

Fusion, as configured
during BIACM source registration

4

MSTR_PERSON_OR_EMPL_ID

Master Person or Employee
ID

String

80

 Y

This column tracks the
master information, and means

differently for different sources,
as mentioned below:

Oracle PeopleSoft:

PS_PERSON.EMPLID

Oracle E-Business Suite:

PER_ALL_PEOPLE_F.PERSON_ID

Oracle Fusion:

FscmTopModelAM.PersonAM.

GlobalPersonForETLPVO.PersonId

5

MSTR_PRIMARY_ASSIGNMENT_ID

Master Primary Assignment
ID

String

80

 Y

This column tracks the
master information, and means

differently for different
sources, as mentioned below:

Oracle PeopleSoft:

PS_JOB.EMPLID||'~'||PS_JOB.EMPL_RCD

Also to be noted that the
EMPL_RCD should correspond to the Primary Assignment

(JOB_INDICATOR = ‘P’ from
the same table).


Oracle E-Business Suite:

PER_ALL_ASSIGNMENTS_F.ASSIGNMENT_ID


Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.

AssignmentAM.AssignmentTempPVO.AssignmentId

6

MSTR_PRIMARY_LEGISLATION_CODE

Master Primary Legislation
Code

String

80

 Y

This column tracks the
master information, and means

differently for different
sources, as mentioned below:

Oracle PeopleSoft:

PS_JOB.REG_REGION

Oracle E-Business Suite:

HR_ORGANIZATION_INFORMATION.

ORG_INFORMATION9

Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.

AnalyticsServiceAM.TerritoriesPVO.TerritoryCode

file_tlo_busn_location_xref_ps.csv

Description: Stores the Taleo Location to Master Location reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM source registration

2

SRC_LOCATION_NUMBER

Source Location Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
Location Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM
source (such as PSFT, EBS, or Fusion, as configured during BIACM source
registration

4

MSTR_LOCATION_ID

Master Location ID

String

80

 Y

This column tracks the master
information, and means differently for different

sources, as mentioned
below:

Oracle PeopleSoft:

PS_LOCATION_TBL.SETID || ‘~’ || PS_LOCATION_TBL.LOCATION


Oracle E-Business Suite:

HR_LOCATIONS_ALL.LOCATION_ID


Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.LocationAM.

HRLocationsPVO.LocationPEOLocationId

 

file_tlo_dept_int_org_xref_ps.csv

Description: Stores the Taleo Department to Master Department reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM source registration

2

SRC_DEPARTMENT_NUMBER

Source Department Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
Department Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM
source (such as PSFT, EBS, or Fusion, as configured during BIACM source
registration

4

MSTR_INT_ORG_ID

Master Internal
Organization ID

String

80

 Y

This column tracks the master
information, and means differently for different sources, as mentioned below:

Oracle PeopleSoft:

PS_DEPT_TBL.SETID||’~’|| PS_DEPT_TBL.DEPT_ID


Oracle E-Business Suite:

HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID


Oracle Fusion:
FscmTopModelAM.OrganizationAM.OrganizationUnitPVO.

OrganizationId

 

file_tlo_int_org_xref_ps.csv

Description: Stores the Taleo Organization to Master Organization reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM source registration

2

SRC_ORGANIZATION_NUMBER

Source Organization Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
Organization Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM
source (such as PSFT, EBS, or Fusion, as configured during BIACM source
registration

4

MSTR_INT_ORG_ID

Master Internal
Organization ID

String

80

 Y

This column tracks the
master information, and means differently for different sources, as mentioned
below:

Oracle PeopleSoft:

PS_BUS_UNIT_TBL_HR.BUSINESS_UNIT


Oracle E-Business Suite:

HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID


Oracle Fusion:
FscmTopModelAM.OrganizationAM.OrganizationUnitPVO.

OrganizationId

 

file_tlo_job_xref_ps.csv

Description: Stores the Taleo Job Information to Master Job reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM source registration

2

SRC_JOB_INFO_NUMBER

Source Job Information
Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
Job Information Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM
source (such as PSFT, EBS, or Fusion, as configured during BIACM source
registration

4

MSTR_JOB_ID

Master Job ID

String

80

 Y

This column tracks the master information,
and means differently for different sources, as mentioned below:

Oracle PeopleSoft:

PS_JOBCODE_TBL.SET_ID || '~' || PS_JOBCODE_TBL.JOB_CODE

Oracle E-Business Suite:

PER_JOBS.JOB_ID

Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.JobAM.JobPVO.

JobId

 

file_tlo_user_empl_xref_ps.csv

Description: Stores the Taleo User to Master Employee reference.

** DSN = Data Source Number

#

Col Name

Col Business Name

Data Type

Len

Reqd.

Col Description

1

SRC_DATASOURCE_NUM_ID

Source DSN

Numeric

10

 Y

Oracle Talent Cloud (Taleo)
DSN as configured during BIACM

source registration

2

SRC_USER_NUMBER

Source User Number

Numeric

20

 Y

Oracle Talent Cloud (Taleo)
User Number

3

MSTR_DATASOURCE_NUM_ID

Master DSN

Numeric

10

 Y

DSN of the Master HCM source
(such as PSFT, EBS, or Fusion, as

configured during BIACM
source registration

4

MSTR_PERSON_OR_EMPL_ID

Master Person or Employee
ID

String

80

 Y

This column tracks the master information,
and means differently for different sources, as mentioned below:

Oracle PeopleSoft:

PS_PERSON.EMPLID

Oracle E-Business Suite:

PER_ALL_PEOPLE_F.PERSON_ID

Oracle Fusion:

FscmTopModelAM.PersonAM.GlobalPersonForETLPVO.

PersonId

5

MSTR_PRIMARY_ASSIGNMENT_ID

Master Primary Assignment
ID

String

80

 Y

This column tracks the
master information, and means differently

for different sources, as
mentioned below:

Oracle PeopleSoft:

PS_JOB.EMPLID||'~'||PS_JOB.EMPL_RCD

Also to be noted that the EMPL_RCD
should correspond to the

Primary Assignment
(JOB_INDICATOR = ‘P’ from the same table).


Oracle E-Business Suite:

PER_ALL_ASSIGNMENTS_F.ASSIGNMENT_ID


Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.AssignmentAM.

AssignmentTempPVO.AssignmentId

6

MSTR_USER_ID

Master User ID

String

80

 Y

This column tracks the
master information, and means differently for different sources, as mentioned
below:

Oracle PeopleSoft:

PSOPRDEFN.OPRID

Oracle E-Business Suite:

FND_USER.USER_ID

Oracle Fusion:
HcmTopModelAnalyticsGlobalAM.UserAM.UserPVO.

UserHistoryPEOUsername

Once ready, fill out these six CSVs. The next step would be to upload them back to OTBI-Enterprise.

Upload your Cross Reference Data Files

Uploading navigation is same as downloading.

Log into BIACM.

Go to System Setups -> Define Business Intelligence Applications Instance.

Select your Taleo source (say Taleo 14B, as in this case) and click on the Actions menu.

Click on Manage Source Configuration Data Files, then click on the “Import Source Configuration Data Files” menu at the top.

The following dialog will allow you to import the files, one at a time. You could zip up all the files and upload one zip file, or update
individual files separately.

 

Upload/Import the six files.

Upload your Cross Reference Data Files using Automation

Speaking about change management in providing the cross reference data, information such as Job or Department or Organization wouldn’t probably change as much. However, Candidate to Employee Cross Reference, or User Cross Reference information are examples that can potentially be fast changing. Downloading or uploading the corresponding CSV files manually may not be optimum. OTBI-Enterprise BIACM offers some automations around that using Web Services. If you can program the preparation of the CSV files (managing the change captures etc.) at your end, you can use the BIACM Web Services in your program to upload them directly to where they are supposed to go.

ETL Source Configuration files can now be imported using REST style web services exposed from Configuration Manager Application. Once the files are ready, use the following REST API to import them programmatically:

REST API to import ETL Source Files

Method

http://<host:port>/biacm/rest/biacmservice/importETLSourceFiles

Request Type

POST

Parameters

PLV – Product Line Version of the source registered in CM [For Taleo 14B, the value would be
TALEO_14_B, for Taleo 15A it is TALEO_15_A etc.]

DSN – Data Source Number of the source registered in CM [in this case, Taleo DSN]

File – The full name and path of the file to be uploaded

Authentication

Provide the username/password used to login to CM

Note that multiple files can be imported as one single ZIP file. OTBI-Enterprise will UNZIP them while storing them in the necessary
folder.

An Example ….

Any REST client can be used to invoke the web services. Here is an example using curl:

curl -i
-F "file=@<file to be uploaded>" http://<host:port>/biacm/rest/biacmservice/importETLSourceFiles?plv=<plv>&dsn=<dsn>

-u username:password

Response Codes

HTTP Code

Description

200

Success

400

Validation Errors

401

Unauthorized

Configuration and Implementation Tips

Ø If you choose to make use of the feature, make sure you configure all three parameters correctly. If you choose to not use this, then  CROSS_REFERENCE_ENABLED parameter should be configured to ‘N’ and the remaining two isn’t necessary.

Ø If you enabled the Cross Reference feature and later wish to disable it, you will need a full load. So make your call thinking through very deeply.

Ø Out of all the CSV files, it is apparent that the file “file_tlo_appl_empl_xref_ps.csv” will potentially change very frequently. It is worth to develop an automation around creation of this file. The rest of the files wouldn’t change that frequently (hopefully).

Ø Provide the data only when there is a source to master mapping. Source entities that does not have a corresponding master doesn’t need to be added to the files. Except in one use case below, with asterisk (*).

Ø How to do source – master relation (cross reference dataset) corrections?

o You indicated a wrong master for a given source which you want to correct now.

Just provide the same source to master mapping the next day, this time providing the correct master. OTBI-Enterprise will honor this correction and make appropriate change.

o You want to undo a master source relation. Meaning, a source to master mapping isn’t valid. This source is the master to itself.

(*) Just removing the old source to master mapping in the following day’s load won’t help. You need to provide that source to master mapping again in the following day, except that this would be a source to source map. This will enable OTBI-Enterprise to understand that this source entity is the master of itself. In other words, this has no master mapping.

 

Join the discussion

Comments ( 2 )
  • Harrison Tuesday, September 20, 2016

    Wow, I had no idea this feature existed! We are trying to implement PSFT and Taleo at my client and I would like to give this a shot. We are using on-premise OBIA 11.1.1.10.1, PeopleSoft 9.2 and Taleo 15A.

    I have set CROSS_REFERENCE_ENABLED = "Y" and TLO_INTEGRATED_HCM_DSN = [PS DSN], however the parameter "TLO_CUSTOM_INTEGRATION" doesn't exist...

    Furthermore, when I go to export the configuration files there are none to export for Taleo!! Any ideas?


  • Harrison Tuesday, September 20, 2016

    Fascinating post, had no idea this was possible!

    We are trying to implement this using on-premise OBIA 11.1.1.10.1 and Taleo 15A / PeopleSoft 9.2 however we don't see the TLO_CUSTOM_INTEGRATION parameter in BIACM. Also, when attempting to export the configuration files for Taleo, nothing happens (no files are shown in the dialog). Any ideas???


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content