nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle AI and Analytics

venkata_k · 2026-05-06T20:50:23+00:00

* Add support for HCM subject areas to allow the feature to be used for HR, workforce, payroll, talent, absence, benefits, and other HCM reporting needs. * Increase the schedule limit from 3 to at least 5 or 6 schedules so reports can refresh approximately every 2 hours during the business day, supporting more timely…

Child Item

Frequent Data Refresh V2 preview enhancements

venkata_k

Add support for HCM subject areas to allow the feature to be used for HR, workforce, payroll, talent, absence, benefits, and other HCM reporting needs.
Increase the schedule limit from 3 to at least 5 or 6 schedules so reports can refresh approximately every 2 hours during the business day, supporting more timely financial reporting during month end close where journal entries update throughout the day & financial leadership needs the most up to date income statements.
The current setting of 13 month lookback period prevents a Current year vs Prior Year YTD with intraday updates which is a common form of financial analysis during month end activities. Please increase the oldest date to report setting to at least 24 months, preferably 36 months to support current year versus prior year comparisons, longer trend analysis, and subject specific reporting needs. We would have to create customizable views that would effectively recreate the lambda views to accomplish this.
Condense to one FDR Flag for Financials - Balance Sheet and Financials -Profitability subject areas. Scenario is a very common attribute in financial reporting, and this will create confusion with overstated numbers due to duplication.
https://docs.oracle.com/en/cloud/saas/analytics/26r1/faiae/frequent-data-refresh-v2--data-lineage.html?utm_source=chatgpt.com#GUID-18B7FAAB-A001-460C-AD82-4A76F7792D45

Find more posts tagged with

FDI

Needs Votes

Frequent Data Refresh (FDR)

Fusion ERP Analytics

Fusion Data Intelligence FDI

Financial

Status: Needs Votes

Comments

KrishnaSanga

Thank you for posting this Idea Venkat, This is the absolute non starter for us as typically Volume of HR data is less in comparatively with other Pillars and FDR v2 enablement for additional areas that have been announced yesterday as part of the 26 R2 will contain additional support.

Govardhana Gurumal

For effective performance analysis and optimization of the FDR process, it is crucial to monitor specific metrics.Specifically, we require access to the following information for each FDR execution:•Processing Duration: The total time taken for the refresh to complete.•Execution Status: Indication of success or rejection.•Timestamps: Start and end times of the refresh process.•Row-Level Metrics: Counts of rows inserted, updated, and deleted during the refresh.While we are aware of the Data Pipeline Status page and the Warehouse Refresh Statistics dashboard for rejected records , we are looking for a consolidated view that provides these detailed telemetry metrics. This information is vital for identifying bottlenecks, troubleshooting issues, and ensuring the efficient operation of the FDR feature.