Diagnosis
Characteristic &V1& of the MultiProvider is not provided by thePartProvider &V2&; this means it is not identified. However, &V1& iscompounded to &V4& and &V4& is identified with characteristic &V3& forInfoProvider &V2&.
In this case, there is a compounding or CMP problem with &V1& in theMultiProvider for PartProvider &V2&.
Processing characteristics with CMP problems in the data manager is verycomplicated and can have a negative impact on performance. The datamanager cannot use SIDs for these characteristics (at least not in thecorresponding InfoProvider) because the initial SID = 0 for &V1& is notthe same as the initial compound key for &V4& &V1& (that is, when realvalues are posted in &V2& for &V4&).
For this reason, hierarchies for &V1& must often be read at leaf level.Furthermore, it is not possible to use hierarchy aggregates for &V1& orfor the remaining InfoProviders.

System Response
Where possible, the system tries to avoid negative impacts onperformance. Unfortunately, such performance issues cannot be avoided ifthe correct results are to be displayed.

Procedure
When working with important MultiProviders, you should always avoidcharacteristics with CMP problems.
Add characteristic &V1& or a characteristic compounded to &V4& that canbe identified using &V1& to InfoProvider &V2&. The value for &V1& canalways be initial in &V2&.
If it is not convenient to have characteristic &V1& in InfoProvider &V2&
, you can set InfoProvider-specific properties, selection = '4' andCHANAV = '2', for &V1& in InfoProvider &V2&.
CHANAV cannot be changed directly in the provider-specific properties.CHANAV must be changed using transaction SE16 in table RSDICHAPRO.
To change this property for the relevant characteristic, fill thefollowing fields in transaction SE16:

• INFOCUBE: &V2&


• OBJVERS: M


• CHANM: &V1& (only enter the technical name)

Set CHANAV = '2' for the selected record. If the InfoProvider is changedand reactivated in InfoProvider maintenance after this change isperformed, then the CHANAV change also becomes effective.
V1 in infoprovider v2 is then hidden, that is, v1 is not displayedas an option in the Query Designer. InfoProvider &V2& is not actuallychanged, but the CMP problem for &V1& in the MultiProvider is resolved.Note that in this case, the warning Brain 263 is displayed when theMultiProvider is checked; you can ignore this warning.
If all data records from &V2& for &V4& have the same value, you can setV4 for infoprovider v2 as a constant value (see sap note 1038604).The system can then use an SID again for &V1& and the CMP problem is nolonger an issue.