1. Propagate Historical Assignment Changes to Future Records

Feature Overview

Oracle Fusion 26D introduces the ability to propagate eligible changes made to a date-effective assignment to future-dated assignment records.

Previously, when a historical assignment was corrected, administrators might need to manually update the corresponding future-dated assignment records. With this enhancement, when an eligible change is made, the application identifies the later assignment records and automatically applies the changed product attributes to those future records.

This feature is available in supported Redwood flows such as Change Assignment, Change Location, Change Working Hours, Promote, and Transfer.

How It Works

When an eligible change is made to a date-effective assignment, Oracle Fusion automatically identifies the applicable future-dated assignment records.

The changed assignment attributes are then propagated to those future records without requiring manual updates.

Users can review the affected records through the Future Records drawer and track the results through the Future Assignment Propagation Dashboard.

Benefits

• • Reduces manual effort by eliminating the need to update each future assignment record separately.
  • Improves data consistency by keeping future-dated assignment records aligned with historical changes.
  • Minimizes errors and provides better visibility into future record updates.

2. Retain Transaction Changes On Changing the Effective Date in Redwood Employment Processes

Feature Overview

Oracle Fusion 26D allows users to retain changes made to an in-progress transaction when they change its effective date in supported Redwood Employment flows.
The application rebuilds the transaction for the new date, reapplies the user’s changes, and validates them against the new date-effective context.
This prevents users from having to manually re-enter their changes after changing the effective date.

How It Works

When the effective date is changed, Fusion captures the existing changes, rebuilds the transaction for the new date, and reapplies the values.
It then re-evaluates dependent, defaulted, and derived values and validates all retained changes.
If a value is no longer valid for the new date, Fusion can warn, revert, or display an error depending on the applicable validation rule.

Benefits

• • Prevents data loss by retaining users’ in-progress transaction changes when the effective date is changed.
  • Reduces manual effort by eliminating the need to re-enter previously entered information.
  • Improves data accuracy by validating retained values against the correct date-effective context.

3. Improved Approval Routing for Document Records Based on Assignment Context

Feature Overview

Oracle Fusion 26D improves Document Records approval routing by considering the worker’s selected assignment when determining approvers.

For workers with multiple assignments, approvals are now routed to the appropriate approvers associated with the selected assignment instead of relying on the primary assignment.

The approval notification also displays the selected assignment details, helping approvers verify the correct employment context.

How It Works

When creating a person-level Document Record, the user selects the relevant assignment for the worker.

Fusion uses that selected assignment’s context to determine the appropriate approvers based on the configured approval rules.

The approval notification displays the assignment details, allowing the approver to confirm that the request relates to the correct assignment.

Benefits

• • Improves approval accuracy by routing requests to approvers associated with the selected assignment.
  • Supports multiple assignments by ensuring each assignment can follow its appropriate approval path.
  • Provides better visibility by displaying assignment details in the approval notification.

Oracle Fusion 26D delivers three Core HR updates that remove specific manual steps from the administrator’s day. Assignment corrections now propagate to future-dated records on their own, tracked through the Future Assignment Propagation Dashboard. In-progress transactions keep their entered values when the effective date changes, so administrators do not enter the same data twice. Document Records approvals route to the approver tied to the assignment a worker actually selected, not their primary assignment by default, and the notification shows that assignment so the approver can confirm it.

Teams running Oracle Fusion Cloud HCM should test these three features in a sandbox environment before the update reaches production, particularly if they use custom approval rules for Document Records or rely heavily on Redwood Employment transfer and promotion transactions.

Author: Harsha KubenderSingh