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.
Effective Data Parameter
Summary:
The seeded extract Ascender GPI HCM Extract is scheduled using Fast Formula to avoid schedules around pay finalize days, so does not run on all days.
The Extract's Effective Date and Start Date Parameters are setup with Post Bind Variables and the assumption was that the Post Bind Variable would set a value when the Extract Runs (ie the Effective Date is left blank and when it runs it sets the date to the Current Date + 4 days). What seems to be happening is that the Post Bind Variable is being set when the job is submitted. So when the Extract Runs on 2-May and then resubmits for the 3-May it sets the effective date as 6-May (ie 2-May + 4). When it runs on
0