Solution : https://service.sap.com/sap/support/notes/1045683 (SAP Service marketplace login required)
Summary :
When a MultiProvider is modeled such that the characteristic Cm, which is compounded with Fm, is not identified in PartProvider P, it results in CMP issues, especially when Cm relies on Fm's identification through PartProvider Fp. This leads to the necessity of reading hierarchies at leaf level because hierarchy aggregates for Cm cannot be utilized. To address this, either configure Fp as constant if all values are identical or add and map characteristic Cp in PartProvider P. Adjustments in provider-specific settings via transaction SE16 and table RSDICHAPRO may also be required to manage how these characteristics interact within the InfoProvider.
Key words :
provider-specific properties chasel = '4', provider-specific properties directly, system issues warning brain 263, prerequisites modelingif characteristic cm, poor system performance, displaying incorrect results, cp remains invisible, master data id, initial compounded key, partprovider characteristic fp
Related Notes :
| 1038604 | How to set characteristic constant CHACONST for InfoProvider |
| 1009987 | Compounding problem in MultiProviders |
| 1005764 | What effect has CHACONST in a MultiProvider? |
| 986892 | SAPBWNews BW Support Package 21 NW'04 Stack 21 RIN |
| 914305 | SAPBINews NetWeaver 7.0 BI Support Package 11 |
| 879290 | Problems with hierarchy selections in MultiProviders |
| 787479 | Problems with hierarchy selections in multiproviders |