What are the reasons for implementing CompositeProviders? (2)

Question

Options

• ATo load data into the Composite provider for report
• BTo use the Rank functionality
• CTo provide a virtual datamart layer
• DTo provide an interface for the queries

• A
  4% (1)
• B
  4% (1)
• C
  93% (26)

Explanation

CompositeProviders serve two architectural purposes in SAP BW: C - they create a virtual datamart layer by combining multiple InfoProviders (InfoCubes, DSOs, etc.) without physically storing data, and D - they expose a unified query interface so reporting tools like BEx or Analysis for Office can query across joined or unioned providers as if they were one source.

Why A is wrong: CompositeProviders do not load data - they are read-only, virtual structures. Data loading is the job of transformation/DTP processes into base providers.

Why B is wrong: Rank functionality is a feature available within queries (via calculated key figures or ABAP CDS), not a motivation for CompositeProviders themselves.

Memory tip: Think of a CompositeProvider as a "transparent glass layer" - it shows you data from multiple sources in one view (virtual datamart = C) and gives queries a single door to knock on (interface = D), but nothing is stored behind the glass and it doesn't rank anything.

No community discussion yet for this question.