Any suggestion to solve the problem as below, thanks.
CMP problem occurred in characteristic [0STKEYFIG]Stat. key figure for InfoProvider u201CAAAAu201D
Message no. BRAIN313
Diagnosis
Characteristic [0STKEYFIG]Stat. key figure of the MultiProvider is not provided by the PartProvider u201CAAAAu201D; this means it is not identified. However, [0STKEYFIG]Stat. key figure is compounded to 0CO_AREA and 0CO_AREA is identified with characteristic 0CO_AREA for InfoProvider u201CAAAAu201D.
In this case, there is a compounding or CMP problem with [0STKEYFIG]Stat. key figure in the MultiProvider for PartProvider u201CAAAAu201D.
Processing characteristics with CMP problems in the data manager is very complicated and can have a negative impact on performance. The data manager cannot use SIDs for these characteristics (at least not in the corresponding InfoProvider) because the initial SID = 0 for [0STKEYFIG]Stat. key figure is not the same as the initial compound key for 0CO_AREA [0STKEYFIG]Stat. key figure (that is, when real values are posted in u201CAAAAu201D for 0CO_AREA).
For this reason, hierarchies for [0STKEYFIG]Stat. key figure must often be read at leaf level. Furthermore, it is not possible to use hierarchy aggregates for [0STKEYFIG]Stat. key figure or for the remaining InfoProviders.
System Response
Where possible, the system tries to avoid negative impacts on performance. Unfortunately, such performance issues cannot be avoided if the correct results are to be displayed.
Procedure
When working with important MultiProviders, you should always avoid characteristics with CMP problems.
Add characteristic [0STKEYFIG]Stat. key figure or a characteristic compounded to 0CO_AREA that can be identified using [0STKEYFIG]Stat. key figure to InfoProvider u201CAAAAu201D. The value for [0STKEYFIG]Stat. key figure can always be initial in u201CAAAAu201D.
If it is not convenient to have characteristic [0STKEYFIG]Stat. key figure in InfoProvider u201CAAAAu201D, you can set InfoProvider-specific properties, selection = '4' and CHANAV = '2', for [0STKEYFIG]Stat. key figure in InfoProvider u201CAAAAu201D.
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 the following fields in transaction SE16:
INFOCUBE: u201CAAAAu201D
OBJVERS: M
CHANM: [0STKEYFIG]Stat. key figure (only enter the technical name)
Set CHANAV = '2' for the selected record. If the InfoProvider is changed and reactivated in InfoProvider maintenance after this change is performed, then the CHANAV change also becomes effective.
[0STKEYFIG]Stat. key figure in InfoProvider u201CAAAAu201D is then hidden, that is, [0STKEYFIG]Stat. key figure is not displayed as an option in the Query Designer. InfoProvider u201CAAAAu201D is not actually changed, but the CMP problem for [0STKEYFIG]Stat. key figure in the MultiProvider is resolved. Note that in this case, the warning Brain 263 is displayed when the MultiProvider is checked; you can ignore this warning.
If all data records from u201CAAAAu201D for 0CO_AREA have the same value, you can set 0CO_AREA for InfoProvider u201CAAAAu201D as a constant value (see SAP Note 1038604). The system can then use an SID again for [0STKEYFIG]Stat. key figure and the CMP problem is no longer an issue.