---
格式版本: 2
标题: "Oracle Fusion Data Intelligence: Frequent Data Refresh (FDR V2) – Semantic Model Extensions (SME) Use Cases | analytics"
原文链接: "https://blogs.oracle.com/analytics/oracle-fusion-data-intelligence-frequent-data-refresh-fdr-v2-semantic-model-extensions-sme-use-cases"
发布日期: "2026-08-20"
发布时间校准状态: "found"
发布时间需复核: "否"
发布时间来源: "rule:local:strict_original_body"
发布时间证据: "August 20, 2026 13 minute read"
发布时间校准原因: "规则确认唯一严格发布时间，来源 local:strict_original_body"
发布时间校准置信度: "high"
发布时间候选数量: 5
发布时间严格候选数量: 1
发布时间原页读取状态: "source template page reused from URL open"
发布时间未找到原因: ""
发布时间校准时间: "2026-08-21T10:06:05+08:00"
发布时间仲裁状态: "skipped"
发布时间仲裁尝试次数: 0
发布时间仲裁耗时毫秒: 0
发现时间: "2026-08-21T09:56:58+08:00"
入库时间: "2026-08-21T02:06:05.882Z"
来源平台: "固定入口"
搜索渠道: "fixed_url"
搜索词: "https://blogs.oracle.com/?page=news"
匹配关键词:
  - "performance"
  - "OAC"
  - "AI"
相关厂家:
  - "Oracle"
相关专家:
  []
内容类型: "网页"
抓取工具: "CDP Render"
清洗工具: "CDP Text + Defuddle/Readability 正文提取"
原始附件:
  []
AI优质: "否"
AI打分: 0
AI分档: "非优质"
AI质检状态: "不通过"
AI打分理由: "内容为Oracle Fusion Data Intelligence的FDR V2语义模型扩展指南，涉及企业数据分析/BI，与超节点/AI Rack等AI基础设施完全无关，也未提供任何相关技术或商业信号。"
AI质检模型: "ali-deepseek-v4-flash"
AI质检时间: "2026-08-21T10:06:23+08:00"
AI主题相关性: 0
AI来源权威性: 0
AI新颖性: 0
AI技术细节: 0
AI商业部署信号: 0
AI完整性: 0
AI摘要: "Oracle Fusion Data Intelligence 的 FDR V2 支持每小时刷新，实现近实时报表；"
AI摘要模型: "ali-deepseek-v4-flash"
AI摘要时间: "2026-09-07T02:13:04.741Z"
采集批次: "2026年8月21日9点50分40秒"
采集批次ID: "20260821-095040-035"
去重键: "https://blogs.oracle.com/analytics/oracle-fusion-data-intelligence-frequent-data-refresh-fdr-v2-semantic-model-extensions-sme-use-cases"
---

With inputs from Jay Pearson, Product Management Fusion Data Intelligence

Oracle Fusion Data Intelligence is a family of prebuilt, cloud-native analytics applications for Oracle Fusion Cloud Applications that provide ready-to-use insights to help improve decision-making. It’s extensible and customizable, allowing you to ingest data and expand the base semantic model with additional content.

## Introduction

The Frequent Data Refresh (FDR V2) process in Oracle Fusion Data Intelligence enables near real-time reporting with refresh intervals as frequently as once per hour. For more information on scheduling FDR V2, see [Schedule Frequent Data Refreshes.](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/schedule-frequent-refreshes-data.html#GUID-7DAB082F-FBDC-4B17-BB86-77C8D8DD21FA)

After FDR V2 completes, the system automatically exposes certain scenarios in the semantic model, making them immediately available for reporting. For more information, see [Automatic Availability of Frequently Refreshed Data in the Semantic Model.](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/automatic-availability-frequently-refreshed-data-semantic-model.html#GUID-A14C1096-070F-4098-8BBB-7AA7BA44AD5D)

The system doesn’t automatically expose all scenarios. In such cases, you can manually add the objects to the semantic model to make it available for reporting. For more information, see [Manual Addition of Frequently Refreshed Data in the Semantic Model.](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/manual-addition-frequently-refreshed-data-semantic-model.html)

This article examines three common dimension use cases that demonstrate what FDR V2 automatically supports, what you must manually configure in the semantic model, and what FDR V2 doesn’t support, along with the implementation approach for each scenario.

## Benefits

FDR V2 provides several benefits, including:

1. Improved performance while maintaining data consistency across refreshes.
2. Faster intra-day reporting through separate “Silver” tables, while “Gold” tables support daily analytics.
3. Flexible reporting, allowing you to seamlessly switch between daily and intra-day data using the FDR Flag.
4. Simplified report authoring, when the system automatically adds an FDR folder to the subject area. Even if the subject area contains multiple fact tables, the system displays only a single FDR folder and FDR flag.

## Use Case 1: Manual Scenario of FDR V2 in SME

In this example, you’ll learn how to add the **DW\_BUSINESS\_UNIT\_D\_FDI\_LAMBDA** view to the semantic model as a new dimension to expose the frequently refreshed Business Unit data in the **Financials – AP Invoices** subject area.

Enable FDR V2 for the **AP Payables** module and the prebuilt Business Unit conformed dimension **DW\_BUSINESS\_UNIT\_D** in the semantic model.

After the initial frequent refresh completes, the system automatically generates the **DW\_BUSINESS\_UNIT\_D\_FDI\_LAMBDA** view to combine the base data with the incremental data for **DW\_BUSINESS\_UNIT\_D**. However, because **DW\_BUSINESS\_UNIT\_D** is a prebuilt conformed dimension; the system doesn’t automatically expose it in the semantic model.

## Steps

**Add the Business Unit Lambda View as a custom dimension to the logical star**

1. Create or edit an existing sandbox on the Semantic Model Extensions page.
2. In **Perform Action**, click **Manage Logical Star**, then **Edit Logical Star**, then **Out of the box**, then select **Financials – AP Invoices** as the subject area, select **Fact – Fins AP Invoice Schedules** as the corresponding fact, and then click **Next**.
3. In step 1 of the Add a Dimension wizard, select **OAX$OAC** in **Schema**, select **DW\_BUSINESS\_UNIT\_D\_FDI\_LAMBDA** in **Object**, and enter a name in **Dimension Name**. Select the **Add Attributes** check box to add desired attributes. Select the **Use for Key** check box for **BUSINESS\_UNIT\_ID**. Click **Next**.
![Lambda View](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/3.png)

Lambda View

![Attributes](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/3.2.png)

Attributes

4. In step 2 of the wizard, select **Add hierarchy to Subject Area** check box to add a hierarchy. Set **Business Unit Id** as the primary key and display attribute in the logical star. Click **Done**. Click **Next** and **Finish.**
![Hierarchy](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/4.png)

Add Hierarchy

![Display Attribute](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/4.2.png)

Display Attribute

**Add the BUID physical column to the Fact – Fins AP Invoice Schedules prebuilt fact**

1. On the Logical Star: Fact page, right-click **Fact – Fins AP Invoice Schedules**, click **Manage Extension,** and then click **Add Columns.** On the Add Columns page, click **Add Physical Column**. In Select Physical Columns, select the check box for **BUID**, and then click **OK**.
![BU ID](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/Add-BU-ID-1.png)

Add BU ID

**Join the Business Unit Lambda View custom dimension to the Fins AP Invoice Schedules prebuilt fact**

1. On the Logical Star: Fact page, click and drag the custom dimension **Dim – DW Business Unit D Fdi Lambda** circle to the prebuilt fact **Fact – Fins AP Invoice Scedules** circle in the graphical format to open the Join dialog.
2. In the Join dialog, set **Join Type** as **Inner**, set **Content level** to **Detail**, set **Join Condition** as follows and then click **Done**:
	- For **Fact – Fins – AP Invoice Schedules**, select **BU ID (DOUBLE).**
		- For **Dim – Dw Business Unit D Fdi Lambda**, select **Business Unit Id (DOUBLE)**.
![BU](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/JoinBU.2.png)

Join Business Unit

3. Review the custom joins in the graphical format.
![Joins](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/join-bu.3.png)

Custom Joins

**Present the Business Unit Lambda View custom dimension in the semantic model**

1. Navigate back to your sandbox, click **Perform Action**, then **Manage Subject Areas**, and then click **Modify a Subject Area**. Select **Financials – AP Invoices** and click **Next**.
2. On the Modify a Subject Area – **Financials – AP Invoices** page, review the subject area details in step 1 of the wizard and click **Next**.
3. In step 2 of the wizard, click **Manage Elements,** and then click **Manage New Customizations**.
![SA](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/bu-lambda-3.png)

Modify Subject Area

4. In Add Subject Area, under **Custom**, select the desired attribute columns, and then click **Add**. This adds the **Dim – Dw Business Unit D Fdi Lamda** folder to the semantic model and places the columns within the folder. Click **Apply**.
![Add Elements](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/bu-lambda-4.png)

Add New Elements

![Review](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/bu-lambda4.2.png)

Review Columns

5. Rename the **Dim – Dw Business Unit D Fdi Lamda** folder to **Business Unit FDR.** Click N **ext** and **Finish**.
![Rename](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/bulambda-5.png)

Rename Presentation Folder

**Apply and publish the customizations**

1. Apply the changes to compile the sandbox and ensure that the sandbox is error free.
2. Use the Activity tab to debug, resolve errors, and confirm that the **Apply Changes** action completes and is successful.
3. Merge the changes to the main sandbox and publish the main user extensions to share the new extensions with consumers.

**Validate the results**

1. On the Fusion Data Intelligence Console, click **Go to Home Page**.
2. On the Oracle Analytics Home page, click **Create**, click **Workbook**, in Add Data, select the **Financials – AP Invoices** subject area, and then click **Add to Workbook**.
3. Expand the **Business Unit FDR** folder and add the **Business Unit** column onto the workbook.
4. Expand the **Fact** folder and add the **Invoices Amount** measure onto the workbook.
5. Expand the **FDR Flag Folder** and add the **FDR flag** as a filter and set it to **Y**.
6. Review the execution log to validate that the query uses the lambda views to retrieve the data.
![Review](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/validate6.png)

Review the log

## Use Case 2: Automated Scenario of FDR V2 in SME

In this example, you’ll learn how to extend the **Dim – AP Invoice Details** degenerate dimension with columns from the **DW\_FA\_X\_INV\_EXTN** data augmentation dataset table to expose frequently refreshed extended data in the **Financials – AP Invoices** subject area.

Enable FDR V2 for both the **AP Payables** functional area and the **DW\_FA\_X\_INV\_EXTN** data augmentation dataset table. After the initial frequent refresh completes, the system automatically updates the semantic model to expose the frequently refreshed data from the extended degenerate dimension, making the data immediately available for reporting in the **Financials – AP Invoices** subject area.

**Steps**

**Create a Dataset type of data augmentation**

1. Create a dataset type data augmentation to use the target table columns to extend **Dim – AP Invoices Details** prebuilt degenerate dimension table.
![DA](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2-1.png)

Data Augmentation

2. Select a **primary key** and **incremental key**, click **Next,** and click **Finish.**
![Keys](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2-2.png)

Define Keys

![DA](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2-2-2.png)

Data Augmentation

**Extend the Dim – AP Invoice Details degenerate dimension**

1. Navigate to **Semantic Model Extensions.**
2. Edit the logical Star fact: **Fact – Fins AP Invoice Schedules.**
![Extend Dim](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2extend2.png)

Extend Dimension

3. Right click **Dim – AP Invoice Details,** then select **Manage Extensions**.
![Manage Extension](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2extend3.png)

Manage Extension

4. Select the columns to extend, then click **Next.**
![Columns](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2extend4.png)

Select Columns

5. Define the join and click **Finish.**
![](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2extend5.png)

Define Join

**Present the extended degenerate dimension columns in the semantic model**

1. Navigate back to your sandbox, click **Perform Action**, then **Manage Subject Areas**, and then click **Modify a Subject Area**. Select **Financials – AP Invoices** and click **Next**.
2. On the Modify a Subject Area – **Financials – AP Invoices** page, review the subject area details in step 1 of the wizard and click **Next**.
3. In step 2 of the wizard, click **Manage Elements,** and then click **Extend Pre-Build Extensions**.
4. Select the desired attribute columns, and then click **OK**.
![](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2present4.png)

Extend Columns

5. Select the **Document Details** folder to add the extended columns. Click **Next**.
![select the folder](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2present6.png)

Select the folder

![](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2present6-2.png)

Review Columns

6. Review and confirm the added columns, click **Next**, then click **Finish**.
![Review](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2present7.png)

Review

**Apply and publish the customizations**

1. Apply the changes to compile the sandbox and ensure that the sandbox is error free.
2. Use the Activity tab to debug, resolve errors, and confirm that the **Apply Changes** action completes and is successful.
3. Merge the changes to the main sandbox and publish the main user extensions to share the new extensions with consumers.

**Validate the results**

1. On the Fusion Data Intelligence Console, click **Go to Home Page**.
2. On the Oracle Analytics Home page, click **Create**, click **Workbook**, in Add Data, select the **Financials – AP Invoices** subject area, and then click **Add to Workbook**.
3. Expand the **Invoice Details** folder and add the extended columns to the workbook.
4. Expand the **Fact** folder and add the **Invoices Amount** measure onto the workbook.
5. Expand the **FDR Flag Folder** and add the **FDR flag** as a filter and set it to **Y**.
6. Review the execution log to validate that the query uses the Lambda views to retrieve the data.
![Log Usecase2](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase2validate.png)

Review the log

## Use Case 3: Unsupported Scenario of FDR V2 in SME

In this example, you’ll learn the expected behavior when a custom dimension, **Dim ZX Registrations**, is created in **Autonomous Data Warehouse (ADW)** using a custom ETL process and joined to the **AP Invoice Schedule** prebuilt fact table.

You enable FDR V2 for the **AP Payables** functional area. After the initial refresh completes, the system automatically updates the semantic model to expose the frequently refreshed data from the **AP Invoice Schedule** fact table. However, because **Dim ZX Registrations** isn’t FDR V2-enabled, a custom ETL process populates it and its data isn’t refreshed. As a result, the custom dimension continues to display the data from its last ETL run.

**Steps**

**Add Dim ZX Registrations as a custom dimension to the logical star**

1. Use Semantic Model Extensions to add **Dim ZX Registrations** to logical Star fact: **Fact – Fins AP Invoice Schedules** and join it to **AP Invoice Schedule prebuilt fact table.**
![Custom Join](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase3-1.png)

Custom Join

![Add Elements](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase31-2.png)

Add Elements

**Validate the results**

1. On the Fusion Data Intelligence Console, click **Go to Home Page**.
2. On the Oracle Analytics Home page, click **Create**, click **Workbook**, in Add Data, select the **Financials – AP Invoices** subject area, and then click **Add to Workbook**.
3. Expand the **Dim ZX Registrations** folder and add desired columns to the workbook.
4. Expand the **Fact** folder and add the **Invoices Amount** measure onto the workbook.
5. Expand the **FDR Flag Folder** and add the **FDR flag** as a filter and set it to Y.
6. Review the execution log to confirm that the query uses the Lambda views to retrieve the frequently refreshed data for the **AP Invoice Schedule** prebuilt fact table. In contrast, the data from **Dim ZX Registrations** remains unchanged when you enable the **FDR Flag**, as FDR V2 doesn’t refresh the custom dimension. If your custom table must contain the latest data, schedule your custom ETL process to run after FDR V2 so it can incorporate the most recent changes.
![Review the log](https://blogs.oracle.com/analytics/wp-content/uploads/sites/86/2026/08/usecase3validate.png)

Review the log

## References

[Upgrade to Frequent Data Refresh V2](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/upgrade-frequent-data-refresh-v2-preview.html)

[Schedule Frequent Data Refreshes](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/schedule-frequent-refreshes-data.html)

[Manage Frequently Refreshed Data in the Workbooks](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/manage-frequently-refreshed-data-workbooks.html)

[Top FAQs for Frequent Data Refresh](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawag/top-faqs-frequent-data-refresh.html)

## FDR V2 Data Lineage

[CX – FDR V2 Data Lineage](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fawcx/appendix-frequent-data-refresh-v2-data-lineage.html)

[ERP – FDR V2 Data Lineage](https://docs.oracle.com/en/cloud/saas/analytics/26r2/faiae/frequent-data-refresh-v2-data-lineage.html)

[SCM – FDR V2 Data Lineage](https://docs.oracle.com/en/cloud/saas/analytics/26r2/fascm/appendix-frequent-data-refresh-v2-data-lineage.html)

## Conclusion

Frequent Data Refresh provides a powerful mechanism for delivering near real-time reporting in Oracle Fusion Data Intelligence. As demonstrated in this blog, the behavior of frequently refreshed data in the semantic model depends on the type of object that you use. You learned that the system automatically configures **prebuilt degenerate dimensions** for FDR V2, while **prebuilt conformed dimensions** require manual semantic model configuration to expose their frequently refreshed data. In contrast, FDR V2 doesn’t refresh **custom objects** that the external ETL process populate and you must update independently.

By understanding these behaviors and choosing the appropriate implementation approach for each scenario, you can extend the semantic model with confidence while ensuring that reports deliver the latest available data, maintain optimal performance, and preserve data consistency.

## Call to Action

For more information, see the [**About Semantic Model Customization**](http://docs.oracle.com/pls/topic/lookup?ctx=faw-latest&id=FAWAG-GUID-584A64B8-F4B9-4398-86CF-8E43F1260336) documentation to learn how to extend the semantic model using **Semantic Model Extensions**.

Now that you’ve read this article, try these techniques in your own environment. Share your experience in the [**Oracle Analytics Community**](https://community.oracle.com/products/oracleanalytics/discussion/23766/blogs-to-getting-started-with-oracle-analytics-ai), where you can ask questions, exchange best practices, and submit ideas for future enhancements.