What does Oracle recommend when using DFF Attribute Mapper to extend prebuilt subject areas with DFFs from the source Fusion Application?

What does Oracle recommend when using DFF Attribute Mapper to extend prebuilt subject areas with DFFs from the source Fusion Application?

• A. Enable all attributes.
• B. Only use BI-enabled attributes.
• C. Select the attributes required for your implementation.
• D. Disable DFF attributes.

Answer: (C)

When extending prebuilt subject areas with DFFs from the source Fusion Application using the DFF Attribute Mapper, the recommended approach is to select only the attributes you actually need for your implementation. This keeps the data model lean and focused, which improves query performance and makes maintenance easier. Pulling in every available attribute can dramatically increase data volume, complicate mappings, and slow down ETL and reporting. While it might seem tempting to restrict to BI-enabled attributes, the right practice is to map just the specific DFF fields that are required for your analytics needs—no more, no less. Disabling DFF attributes would prevent you from leveraging the DFF data altogether, which defeats the purpose of this mapping.

When extending prebuilt subject areas with DFFs from the source Fusion Application using the DFF Attribute Mapper, the recommended approach is to select only the attributes you actually need for your implementation. This keeps the data model lean and focused, which improves query performance and makes maintenance easier. Pulling in every available attribute can dramatically increase data volume, complicate mappings, and slow down ETL and reporting. While it might seem tempting to restrict to BI-enabled attributes, the right practice is to map just the specific DFF fields that are required for your analytics needs—no more, no less. Disabling DFF attributes would prevent you from leveraging the DFF data altogether, which defeats the purpose of this mapping.