Which features Can be leveraged using a CompositeProvider in SAP BW/4HANA? (3)

Question

Options

• ACombine InfoProviders using Joins and Unions
• BIntegrate SAP HANA calculation views
• CDefine new restricted key figures
• DDefine new calculated fields
• EIntegrate a BW query as an InfoProvider.

• A
  70% (26)
• C
  19% (7)
• E
  11% (4)

Explanation

A CompositeProvider in SAP BW/4HANA is a virtual InfoProvider that acts as a flexible data integration layer - it can combine multiple InfoProviders via Joins and Unions (A), integrate SAP HANA Calculation Views (B) to leverage in-memory analytics, and define new calculated fields (D) derived from existing data within the provider definition.

Why the distractors are wrong:

• C (Restricted Key Figures): These are defined at the BW Query level (in BEx Query Designer or Query Modeler), not within the CompositeProvider itself.
• E (Integrate a BW Query as an InfoProvider): A BW Query can be exposed as a data source in certain contexts, but it is not a feature you integrate into a CompositeProvider - the CompositeProvider sits below the query layer.

Memory tip: Think of CompositeProvider as a data plumber - it connects pipes (Joins/Unions), taps into HANA natively (Calculation Views), and calculates on the fly (Calculated Fields). Anything that belongs to the reporting/query layer (like Restricted Key Figures or Queries themselves) is out of scope for the CompositeProvider.

No community discussion yet for this question.