Model MultiProviders so that the characteristics you want to use in reporting and analysis are in all InfoProviders belonging to the MultiProvider.
Use MultiProviders to keep the InfoProviders small.
To make sure that the system only reads the relevant data when executing the query, you need to:
use constants when modeling the InfoProviders
model the InfoProviders with different key figures
include characteristic 0INFOPROV when designing the query for the MultiProvider, so that you can filter by InfoProvider.
Use MultiProviders to define a layer for the data analysis. This makes it easier to enhance data analysis scenarios. If you add an InfoProvider to a MultiProvider later, the technical name of the query you have defined remains the same.
Do not combine InfoProviders in a MultiProvider if their data models are very different. In cases like this, use the report-report interface between queries defined on the basis of different InfoProviders.
Do not use parts of compound characteristics in InfoProviders. See SAP Note 702542l for more details.
Performance of MultiProviders
Do not use a large number of InfoProviders when defining a MultiProvider. If several InfoProviders are read by a query simultaneously, it can take a long time for the system to calculate the results.
If your MultiProvider contains a large number of InfoProviders, you should use the function for pruning based on metadata.
If a MultiProvider contains an InfoCube with non-cumulative key figures, all subqueries are processed sequentially.
You can only use OLAP performance optimization tools (like caching and aggregation) for a MultiProvider if all the InfoProviders in the MultiProvider support this tool.