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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Locations Child Data Group returning records at unexpected events
We've a changes only extract to retrieve person, assignment data.
In assignment DFF, we've utilized 1 for Site-location(Attribute1) which LOV is retrieved as internal_location_code from hr_all_locations.
Extract Name: Worker_INT_XX
1. Root Data Group - PER_EXT_SEC_PERSON_NOW_FUTURE_UE
2. Child of #1 - PER_EXT_SEC_ASSIGNMENT_RANGE_UE
3. Child of #2 - PER_EXT_SEC_LOCATION_UE - yields location address details
Connections between #2 and #3 is PER_EXT_SEC_ASSIGNMENT_RANGE_UE.attribute1 = PER_EXT_SEC_LOCATION_UE.internal_location_code
So, here, even when there is no change in assignment or person block - Location address details are populating unnecessarily on random days on the very 1st run of the day.
0