Show TOC

Supported ProvidersLocate this document in the navigation structure

The CompositeProvider offers a range of providers for modeling.

Providers Supported for Union Operations
For CompositeProviders that only contain union assignments, the following providers are supported:
  • SAP HANA views (authorization views and analysis views)
  • The following BW InfoProviders: InfoCube, semantically partitioned object, analytic index, VirtualProvider, InfoSet
  • The following BW InfoProviders: DataStore object (with creation of SID values during reporting or activation), Open ODS view, InfoObject, aggregation level

SAP HANA views generated from BW InfoProviders are not supported.

MultiProviders are not supported.

Open ODS Views that you want to use in CompositeProviders can only contain fields with InfoObject-compatible data types. These are the following data types: CHAR, CUKY, CURR, DEC, DATS, FLTP, INT4, NUMC, TIMS, QUAN, UNIT. Data type STRG is also supported for particularly long characteristic-type field values.

Providers Supported for Join Operations
For CompositeProviders that only contain join assignments, the following providers are supported:
  • SAP HANA views (authorization views and analysis views)
  • The following BW InfoProviders: InfoCube, analytic index, semantically partitioned object
  • The following BW InfoProviders: DataStore object (with creation of SID values during activation), InfoObject

If the semantically partitioned object is based on DataStore objects, the option for creating SIDs when activating must be switched on. Only one semantically partitioned object can be used as a left join partner.

Providers Supported for Join and Union Operations
For CompositeProviders that contain both join and union assignments, the following providers are supported:
  • SAP HANA views (authorization views and analysis views)
  • The following BW InfoProviders: InfoCube, analytic index, semantically partitioned objects
  • The following BW InfoProviders: DataStore object (with creation of SID values), InfoObject

Semantically partitioned objects can only be used for the union. They cannot be used in the join, as all semantically partitioned objects contains unions. If the semantically partitioned object is based on DataStore objects, the option for creating SIDs when activating must be switched on.

Data can only be read from near-line storage of InfoCubes and DataStore objects (classic) if the relevant InfoProvider is assigned using a union in the CompositeProvider and there is no join in the CompositeProvider. If a join node exists above the union, no more data can be read from near-line storage.

With DataStore objects (advanced), data can be read from the near-line storage for unions and joins.

In the following example, Open ODS views, VirtualProviders, InfoSets and aggregation levels are not allowed in the join.

Inner Join with Union