¶ Building MultiProvider and CompositeProvider Models in SAP BW/4HANA
In SAP BW/4HANA, combining data from multiple sources or InfoProviders for unified reporting is a common requirement. Two important objects that enable this are MultiProviders and CompositeProviders. While MultiProviders have been a staple in classic SAP BW, CompositeProviders represent the next-generation, HANA-optimized modeling approach.
This article explores the concepts, differences, and best practices for building MultiProvider and CompositeProvider models in the context of SAP BW/4HANA.
¶ Understanding MultiProviders and CompositeProviders
- A MultiProvider is a virtual InfoProvider that combines multiple InfoProviders (e.g., InfoCubes, DSOs) via union or concatenation.
- It does not physically store data but enables users to query multiple datasets as one.
- MultiProviders support union-based data combination, meaning data from underlying InfoProviders is stacked.
- MultiProviders were widely used in traditional BW but have limitations in flexibility and performance in a HANA environment.
- CompositeProviders are the recommended successor of MultiProviders in SAP BW/4HANA.
- They combine multiple InfoProviders using union and join operations, offering greater modeling flexibility.
- CompositeProviders support complex data layering, allowing data blending from different sources without replication.
- They are HANA-optimized and leverage the power of the in-memory database to execute queries efficiently.
- CompositeProviders also allow for filtering, calculated fields, and key figure calculations within the provider itself.
¶ Key Differences Between MultiProviders and CompositeProviders
| Feature |
MultiProvider |
CompositeProvider |
| Data Combination |
Union only |
Union and Join |
| Physical Storage |
No |
No (Virtual Provider) |
| Performance |
Less optimized for HANA |
Highly optimized for HANA |
| Calculation Support |
Limited |
Supports calculated fields and filters |
| Modeling Environment |
SAP GUI (classic BW) |
Eclipse-based BW Modeling Tools |
| Future-Proofing |
Legacy object |
Recommended for new developments |
While SAP BW/4HANA supports MultiProviders for compatibility, it is advisable to use them mainly for legacy scenarios.
Steps to create a MultiProvider:
- Access SAP GUI BW Modeling Workbench.
- Navigate to the MultiProvider creation transaction (
RSA1).
- Define a new MultiProvider and add required InfoProviders.
- Choose the union method (usually union all).
- Activate the MultiProvider and create queries on top.
CompositeProviders are created using the Eclipse-based BW Modeling Tools.
Steps to build a CompositeProvider:
- Open Eclipse and connect to your BW/4HANA system.
- Create a new CompositeProvider object.
- Add InfoProviders as data sources (e.g., ADSOs, Open ODS Views).
- Define the join or union relationships between the data sources.
- Configure any necessary filters, calculated fields, or restricted key figures.
- Validate and activate the CompositeProvider.
- Create BW queries on top for reporting or analytics consumption.
- Prefer CompositeProviders over MultiProviders for new developments.
- Use joins when you need to combine related datasets based on keys.
- Use unions to combine datasets with the same structure, e.g., regional sales data.
- Leverage calculated columns and filters inside CompositeProviders to reduce complexity in BW queries.
- Keep CompositeProviders modular for easier maintenance and scalability.
- Test performance and optimize join cardinality and filter pushdowns.
¶ Use Cases for MultiProviders and CompositeProviders
| Use Case |
Recommended Provider |
| Combining multiple datasets via union only |
MultiProvider (legacy) |
| Combining datasets with join conditions |
CompositeProvider |
| Adding calculations and filters at provider |
CompositeProvider |
| Integrating external data via Open ODS Views |
CompositeProvider |
| New BW/4HANA projects |
CompositeProvider |
In SAP BW/4HANA, CompositeProviders offer a modern, powerful, and flexible way to combine multiple data sources virtually, making them the preferred choice for most scenarios. MultiProviders remain supported mainly for backward compatibility.
Adopting CompositeProviders enables better performance, richer modeling capabilities, and easier maintenance, ultimately driving more efficient data warehousing and analytics solutions.