TCC OLF Net-change
Summary
OLF net-change ongoing interface scenarioContent
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.