Supplying Data to 0INFOPROV

Every InfoProvider in a union is linked with the characteristic 0INFOPROV. This makes it possible to identify the involved provider, from which the data originates (like with a MultiProvider).

With a join, only one of the two sides of the join can be linked with the characteristic 0INFOPROV. With a CompositeProvider, only the left part is linked with 0INFOPROV.

Read requests for a CompositeProvider can only be split for providers that are linked with 0INFOPROV. Requests cannot be split for joins. This is important for functions that require a provider to explicitly specified. For InfoCubes with non-cumulative key figures, the InfoCube must be explicitly requested and must be linked with 0INFOPROV.

The 0INFOPROV link affects delta caching. Delta caching is only possible for providers that are linked with 0INFOPROV. For all other providers: when new data has been loaded, then all the data is read and not just the new data.

The 0INFOPROV link also influences whether the data integrity can be specified in the query definition. Setting data integrity is only possible for providers that are linked with 0INFOPROV. For all other providers: only data with the status All InfoProviders up to released status (0) is read.