Leila Fielding
Why I picked it
It ends one of the most frustrating jobs in Core HR: correcting a past change, then correcting it again on every future-dated record.
Where it helps
HR backdates a grade correction for someone with a promotion already scheduled next month, and the correction flows into the future record, shown for review before you submit.
Watch out: It covers eligible product fields only, not flexfields, and skips some transaction types.
From Oracle's note
Oracle can now carry eligible product-attribute changes made to an earlier effective date into matching future-dated assignment records, reducing duplicate corrections when a transfer, promotion or job change is already scheduled. In supported Redwood flows, a Future Records drawer shows affected values before submission; after processing, a notification and dashboard help HR review the outcome. The feature is opt-in through a site-level profile option, and it excludes flexfields and several transaction types.
- Review changed attributes and future values before submitting the transaction.
- Monitor propagation results in the Future Assignment Propagation Dashboard.
- Exclude selected attributes with the ORA_PER_EMPL_EXCL_FUT_PROP lookup.
Set ORA_PER_EMPL_COPY_ASG_CHG_TO_FUT_REC to Y at site level; its default is N. Propagation covers eligible product attributes, not flexfields, and excludes inactive or termination records and several flows. Oracle limits propagation to 10 latest-change records and 25 future records overall.
Last reviewed November 2026