Backdated assignment corrections can become complicated when an employee already has future-dated changes.

Updating the historical record does not always keep the future record aligned. This can leave old values in future promotions, transfers, or other assignment changes.

Oracle Fusion HCM 26D addresses this challenge by allowing eligible historical assignment changes to be automatically propagated to future-dated assignment records.

What Is Changing in 26D?

When an eligible assignment change is entered with an earlier effective date, Oracle can now:

• Identify existing future-dated assignment records.
• Determine which changed attributes are eligible.
• Show the user which future records will be affected.
• Carry the changed values forward after submission.
• Display the propagation results through a new dashboard.

This reduces the need to open and correct every future assignment record manually.

Let’s Understand This With a Simple Example

An employee currently has the Business Title HR Analyst with an FTE of 1.0.

A future-dated record already exists to reduce the employee’s FTE to 0.8 from 01 December 2026.

Effective Date	Business Title	FTE
Current record	HR Analyst	1.0
01 December 2026	HR Analyst	0.8

HR later identifies that the employee’s Business Title should have been changed to Senior HR Analyst from 01 October 2026.

After entering the backdated correction, the assignment history should appear as follows:

Effective Date	Business Title	FTE
01 October 2026	Senior HR Analyst	1.0
01 December 2026	Senior HR Analyst	0.8

With the 26D feature enabled, Oracle can propagate the eligible Business Title change to the December record while retaining the future FTE change.

Without this feature, HR would need to manually review and correct the future record.

Supported and Unsupported Redwood Flows

The feature applies only to specific date-effective Redwood Employment flows.

Supported Flows	Unsupported Flows
Change Assignment	Correct Employment Details
Change Location	Request My Assignment Change
Change Working Hours	Promote and Change Position
Promote	Change Manager
Transfer

Oracle also confirms that future date-effective assignment records created through Redwood Employment flows, HDL, HSDL, and REST can be considered during propagation.

However, the feature supports only standard assignment product attributes. Assignment flexfields are not supported.

How Does the Propagation Work?

1. Enter a Historical Assignment Change

Start one of the supported Redwood Employment flows and enter an effective date earlier than an existing future assignment record.

Update an eligible standard assignment attribute such as Business Title, Department, Location, Job, Position, Working Hours, or FTE.

2. Review the Future Records

When Oracle detects an eligible future record, an alert is displayed.

The user can open the Future Records drawer and review:

• The attribute being changed
• The existing value
• The value entered in the current transaction
• The value currently stored in the future record

Only the applicable fields are displayed.

3. Submit the Transaction

After reviewing the future records, submit the transaction through the normal process.

The Change Assignment notification identifies the future records affected by the change.

The Future Assignment Propagation section is not displayed in the post-approval notification.

Monitor the Results From the New Dashboard

Oracle has introduced a new quick action called Future Assignment Propagation Dashboard under My Client Groups.

HR users can use this dashboard to review the propagation results.

The dashboard helps administrators verify whether eligible changes were successfully applied to future assignment records.

How to Enable the Feature

This feature is not enabled automatically.

Profile Option	Default Value	Required Value
ORA_PER_EMPL_COPY_ASG_CHG_TO_FUT_REC	N	Y

Follow these steps:

1. Navigate to Setup and Maintenance.
2. Search for Manage Administrator Profile Values.
3. Search for ORA_PER_EMPL_COPY_ASG_CHG_TO_FUT_REC.
4. Select Site as the profile level.
5. Enter Y in the Profile Value field.
6. Click Save and Close.

Exclude Attributes From Future Propagation

Organisations may not want every eligible assignment attribute to be carried forward.

Oracle has introduced the following lookup to control attribute exclusions:

ORA_PER_EMPL_EXCL_FUT_PROP

Add the required leading attribute name as a lookup code. Once enabled, that attribute and any related attributes in the same group are excluded from future propagation.

Some commonly used lookup codes include:

Lookup Code	Attribute Excluded
ASSIGNMENT_NAME	Business Title
ORGANIZATION_ID	Department
JOB_ID	Job
LOCATION_ID	Location
POSITION_ID	Position
BUSINESS_UNIT_ID	Business Unit
NORMAL_HOURS	Working Hours and Frequency
STANDARD_HOURS	Assignment Standard Working Hours and Frequency
FTE	FTE and automatic FTE and headcount calculation
HEAD_COUNT	Headcount

The lookup code must be entered exactly as delivered by Oracle.

Refer to the Oracle readiness documentation for the complete list of supported exclusion codes and their related attribute groups.

Important Note for Position Synchronisation

When a changed assignment attribute is propagated, Oracle does not validate it against the position value effective on each future date.

Therefore, the propagated assignment value may temporarily differ from the corresponding position value.

The assignment is corrected during the next scheduled run of:

Synchronize Person Assignments from Position

Organisations using position synchronisation should include this scenario in their testing.

Key Limitations to Remember

• Assignment flexfields are not supported.
• Changes are not propagated to future inactive assignment records.
• Termination records are not updated.
• The assignment being changed must be active or suspended.
• Changes made to an inactive assignment are not propagated.
• If the transaction changes the Primary flag, none of the changes in that transaction are propagated.
• Action Occurrence ID, Action Code, Reason Code and termination attributes are not displayed for propagation.
• A maximum of 10 future records with Effective Latest Change = Y can be updated.
• A maximum of 25 future records can be considered in total.
• The 25-record limit includes multiple assignment changes created on the same effective date.
• The feature is not supported in every employment flow.

Recommended Testing

Before enabling the feature in production, test the following:

1. A worker with one future-dated assignment record.
2. Multiple future-dated records for the same worker.
3. A standard attribute included in future propagation.
4. An attribute added to the exclusion lookup.
5. A transaction that changes the Primary flag.
6. An inactive future assignment record.
7. A future termination record.
8. Position-synchronised assignment attributes.
9. Transactions with and without approvals.
10. Propagation results in the new dashboard.

Conclusion

This 26D enhancement solves an important date-effective data maintenance challenge in Oracle Fusion HCM.

HR users can enter an eligible historical assignment correction, review its impact on future records, and allow Oracle to carry the change forward automatically.

The feature will help reduce manual corrections and improve assignment data consistency. However, organisations must carefully review the supported flows, excluded attributes, record limits, flexfield restriction, and position synchronisation behaviour before enabling it in production.