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.

How to identify the changed record when effective start date change?

edited Apr 19, 2024 6:39AM in Payroll and Global Payroll Interface (GPI) 2 comments

On changes only extracts in situations where the effective start date can change, do you have any suggestions on how to identify the changed record?

The use case is our element entry extract has key attributes of element entry id, effective start date, everything works fine on any updates UNLESS the start date moves. We don’t get the “old” values because it’s a new “primary key”.

The problem is that in our DB environment we don’t see the OLD and don’t have a record to tie back to so we end up creating a row that overlaps the existing value.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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