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
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

LUDS between Taleo and Oracle Fusion HCM

edited Apr 17, 2018 6:46PM in Taleo Enterprise 1 comment

Summary

LUDS have a different configuration between the two systems

Content

LUDS between Taleo and Fusion HCM are configured differently.  This impacts quite a few of our fields and the integrations between the two systems.  Our National Identifier field is the most impacted.  

We would like to know how other companies are configuring the LUD in Taleo so that the majority of records going into Fusion HCM don't fail.  

Here is an example of one of the values that we are looking at

The value New Identification Number is used by Malaysia only.  Then we have the value National Identifier which is available for use in multiple countries but excludes Malaysia.  We have looked at a few different options internally but we haven't been able to identify one that will resolve the issue for the majority of our errors without potentially causing additional confusion for our candidates.  We are currently collecting National Identifier in Onboarding from the majority of our countries.  

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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