Skip to main content

Module 5: InfoProviders & Modeling Objects (BW/4HANA 2.0)

In BW/4HANA, InfoProviders are no longer just physical objects.
Modern BW modeling is built on a mix of persistent and virtual providers, optimized for HANA pushdown and reuse.

This module explains:

  • CompositeProviders
  • Open ODS Views
  • aDSO vs CompositeProvider
  • Virtual Providers (intro)
  • When to use what (very important)

1. What is an InfoProvider in BW/4HANA?​

An InfoProvider is any object that can:

  • Provide data for reporting
  • Be consumed by BW Queries
  • Serve as a semantic layer for analytics
Key Shift

In BW/4HANA, InfoProviders are often virtual, not persisted.

2. CompositeProviders (Core Reporting Object)​

2.1 What is a CompositeProvider?​

A CompositeProvider is a virtual InfoProvider that:

  • Combines data from multiple sources
  • Performs joins and unions at runtime
  • Pushes logic to SAP HANA

It replaces:

  • MultiProviders
  • Many reporting DSOs
  • Aggregates

2.2 Key Characteristics​

  • No data persistence
  • HANA SQL pushdown
  • Join / Union support
  • Reusable modeling
  • Reporting-enabled
aDSO / Open ODS / CDS
        ↓
  CompositeProvider
        ↓
     BW Query

2.3 Typical Use Cases​

  • Reporting layer in LSA++
  • Virtual harmonization
  • Combining multiple aDSOs
  • Semantic modeling for reuse
Best Practice

CompositeProvider is the default reporting layer in BW/4HANA.

3. Open ODS Views (External & Virtual Data)​

3.1 What is an Open ODS View?​

An Open ODS View is a virtual BW object that exposes:

  • External tables
  • HANA views
  • Files
  • Non-SAP sources

…directly to BW without loading data.

3.2 Key Characteristics​

  • No data persistence
  • Source-system aligned
  • SQL-based access
  • BW Query–enabled

3.3 Typical Use Cases​

  • Data federation
  • Rapid prototyping
  • External data integration
  • Side-by-side analytics
warning

Open ODS Views are not meant for heavy transformations.

4. Advanced DSOs (aDSOs) vs CompositeProviders​

This is a very common interview and design question.

Comparison Table​

AspectaDSOCompositeProvider
PersistenceYesNo
Data StoragePhysicalVirtual
TransformationsYesLimited
ReportingOptionalPrimary
PerformanceLoad-timeQuery-time
ReusabilityMediumHigh

Architectural Rule​

Golden Rule

Persist facts in aDSO
Report via CompositeProvider

5. Virtual Providers (Intro)​

5.1 What is a Virtual Provider?​

A Virtual Provider provides data to BW Queries:

  • Without persistent storage
  • Using ABAP, HANA, or external logic

5.2 Types of Virtual Providers (High Level)​

  • HANA-based
  • ABAP-based
  • Open ODS–based

5.3 Typical Use Cases​

  • Real-time data access
  • Prototype scenarios
  • External calculation engines
warning

Virtual Providers can impact performance if misused.

6. Modeling Object Comparison (Big Picture)​

ObjectPersistedPushdownTypical Layer
Staging aDSOYesPartialAcquisition
Standard aDSOYesYesHarmonization
Data Mart aDSOYesLimitedFinal persistence
CompositeProviderNoYesReporting
Open ODS ViewNoYesFederation
Virtual ProviderNoDependsReal-time

7. When to Use What (VERY IMPORTANT)​

Use aDSO When:​

  • Data must be stored
  • History is required
  • Delta propagation is needed
  • Data quality must be enforced

Use CompositeProvider When:​

  • Combining multiple datasets
  • Creating reusable reporting models
  • Avoiding data duplication
  • Optimizing performance

Use Open ODS View When:​

  • Accessing external data
  • Avoiding data loads
  • Prototyping quickly

Use Virtual Provider When:​

  • Real-time access is mandatory
  • Persistence is not allowed
  • Volumes are controlled

8. BW/4HANA vs Classic BW (Modeling Shift)​

AreaClassic BWBW/4HANA
ReportingInfoCubeCompositeProvider
AggregatesMandatoryNot required
FederationLimitedOpen ODS Views
PushdownMinimalCore principle
Key Shift

BW/4HANA emphasizes virtualization over persistence.

9. Common Modeling Mistakes​

Avoid These

Reporting directly on Staging aDSOs
Creating one CompositeProvider per report
Persisting data just for joins
Mixing harmonization & reporting logic

10. Interview-Grade Explanation​

Q: What is the role of CompositeProviders in BW/4HANA?

Answer: CompositeProviders are virtual InfoProviders that combine data from multiple sources using HANA pushdown, replacing MultiProviders and reducing the need for persisted reporting layers.

11. Summary​

  • CompositeProvider is the primary reporting object
  • aDSOs persist data; CompositeProviders virtualize
  • Open ODS Views enable data federation
  • Virtual Providers support real-time access
  • Correct object choice is critical for performance

12. What's Next?​

➡️ Module 6: Data Flow & BW Objects
(DataSources, Transformations, DTPs)

Learning Tip

In BW/4HANA, what you do NOT persist matters as much as what you do.