What setup must you ensure in your Fusion Application for FDI to move Descriptive Flexfields (DFFs) to the data warehouse?

What setup must you ensure in your Fusion Application for FDI to move Descriptive Flexfields (DFFs) to the data warehouse?

• A. Ensure that the DFFs and their attributes are BI-enabled in the Fusion Application.
• B. Ensure DFFs are disabled in Fusion.
• C. Rename DFF attributes for BI compatibility.
• D. Move DFFs to a separate BI domain.

Answer: (A)

In Fusion, Descriptive Flexfields (DFFs) will be moved to the data warehouse by Fusion Data Integrator only if they are marked for BI (Business Intelligence) use. This means both the DFF definitions and their individual attributes must be BI-enabled in the Fusion Application. When BI-enabled, FDI recognizes these fields as part of the BI metadata and includes their values in the data warehouse loads, ensuring the descriptive data is available for reporting and analytics. If DFFs are not BI-enabled, there’s nothing in the BI metadata for FDI to extract, so they won’t be moved. Renaming DFF attributes isn’t required and can complicate BI mappings, and placing DFFs in a separate BI domain isn’t a prerequisite for loading them via FDI.

In Fusion, Descriptive Flexfields (DFFs) will be moved to the data warehouse by Fusion Data Integrator only if they are marked for BI (Business Intelligence) use. This means both the DFF definitions and their individual attributes must be BI-enabled in the Fusion Application. When BI-enabled, FDI recognizes these fields as part of the BI metadata and includes their values in the data warehouse loads, ensuring the descriptive data is available for reporting and analytics.

If DFFs are not BI-enabled, there’s nothing in the BI metadata for FDI to extract, so they won’t be moved. Renaming DFF attributes isn’t required and can complicate BI mappings, and placing DFFs in a separate BI domain isn’t a prerequisite for loading them via FDI.