What's new in Customer Journeys?

Connect and learn more! ×
OOTB integration for multiple entities in Taleo Recruit Vs Single Core HCM system — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

OOTB integration for multiple entities in Taleo Recruit Vs Single Core HCM system

Received Response
37
Views
3
Comments
edited May 2, 2017 11:41AM in HCM Integrations 3 comments

Content

Hello Friends,

Need your suggestions to handle the below scenario:
 

We have 5 entities for our customer, where we have Taleo Recruit and Core HCM system integrated through OOTB.

As far as OOTB is concerned, the standard data flows seamless as per the data provided in OOTB configuration guide.

How to handle the integration when it comes for multiple entities?

In Taleo Recruit, we have OLF structure being defined as per the OOTB format and we are retaining the same for all 5 entities.

Main challenge we face is the Requisition templates, which comes from Fusion as Jobs. We would like to restrict the Requisition templates from viewing in Taleo Recruit after it flows from Fusion HCM. Let us say each entity has 10 jobs, so 5*10 = 50 Jobs flows into Taleo as Requisition templates.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!