Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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.

TCC OLF Net-change

edited Mar 26, 2018 4:12PM in Taleo Enterprise 1 comment

Summary

OLF net-change ongoing interface scenario

Content

Hello,

We have the PeopleSoft department tree file inbound to Taleo for the Organization ongoing netchange import. Whenever there is a reorganization, for example  DIV A is renamed to DIV B and all departments under DIV A move to DIV B, then the ongoing netchange fails because the input file does not have the old parent row, i.e., row for DIV A. We have made a temporary fix by adding the missing rows for old parent nodes and rerunning the Setup & ongoing imports.

Now we are looking for a permanent solution to this. Since the PeopleSoft file will not have the rows for old parents in any case, the solution needs to be applied at TCC end only. Kindly advise if anyone has faced this issue earlier and managed to provide a permanent and automatic way to address this issue.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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