How To Fix BRAIN313 - Das Merkmal &1 hat für den Partprovider &2 ein CMP-Problem

SAP Error Message - Details

• Message type: E = Error

• Message class: BRAIN -

• Message number: 313

• Message text: Das Merkmal &1 hat für den Partprovider &2 ein CMP-Problem

Was verursacht dieses Problem?

Characteristic &V1& of CompositeProvider/MultiProvider is not provided
with data from the included InfoProvider &V2&. This means that it is not
identified. &V1& is compounded to &V4& however, and &V4& is identified
for InfoProvider &V2& with characteristic &V3&.
There is a compounding or CMP problem with &V1& in the
CompositeProvider/MultiProvider for InfoProvider &V2&.
During query execution, is very complicated to process characteristics
with CMP problems and can result in long runtimes:

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

BW in general uses artificial surrogate identifiers (SIDs) as keys to
link characteristic values to any kind of fact or master data at query
runtime. These SIDs are 4-byte integer values. They are also used as
keys for compounded characteristics. In the compounded case, a single
SID replaces a compounded key.
Example 1: simple characteristic country
<EX> Country SID</>
<EX> initial 0</>
<EX> DE 1</>
<EX> US 2</>
<EX>Example 2: compounded characteristic region</>
<EX> Country Region SID</>
<EX> initial initial 0</>
<EX> DE initial 1</>
<EX> DE BY,,,,2</>
<EX> DE BW,,,,3</>
With a CMP problem, the analytic engine cannot use SIDs for
characteristics of this kind - or at least not for the InfoProvider -
because the initial SID = 0 for &V1& is not the same as the initial
compound key for &V4& &V1& (if actual values are posted in &V2& for
&V4&).
Hierarchies for &V1& must therefore often be read at leaf level. Also,
it is not possible to use hierarchy aggregates for &V1& or for the
remaining InfoProviders.

Systemantwort

The system tries to avoid negative impacts on performance wherever
possible. Unfortunately, performance issues cannot be avoided in some
cases if you want to display the correct results.
Also pushdown of OLAP functionality into SAP HANA/BWA is limited or even
completely prevented if CMP problems occur.

Wie behebe ich diesen Fehler?

SAP strongly advises not to use CompositeProviders or MultiProviders
with CMP problems. There are 3 ways to overcome CMP problems:
Add the characteristic &V1& to all InfoProviders within the
CompositeProvider or MultiProvider
Add characteristic &V1& or a characteristic compounded to &V4& that can
be identified using &V1& to InfoProvider &V2&. The value for &V1& can
always be initial in &V2&.
Hide the affected characteristic &V1& in the CompositeProvider or
MultiProvider
If it is not convenient to have characteristic &V1& in InfoProvider &V2&
, you can hide it by setting the InfoProvider-specific properties,
selection = '4' and CHANAV = '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 the
following fields in transaction SE16:
INFOCUBE: &V2&
OBJVERS: M
CHANM: &V1& (enter the technical name only)
Set CHANAV = '2' for the selected record. If the InfoProvider is changed
and reactivated in InfoProvider maintenance after this change is
performed, the CHANAV change also becomes effective.
This means that &V1& remains hidden in InfoProvider &V2&, which means
that &V1& is not available in Query Designer. InfoProvider &V2& is not
actually changed, but the CMP problem for &V1& in the
CompositeProvider/MultiProvider is resolved. Note that warning message
Brain 263 will be displayed when the CompositeProvider/MultiProvider is
checked, but you can ignore this warning.
Set the compounding parent characteristic &V4& as a constant in the
affected InfoProvider &V2&
If all data records from &V2& for &V4& have the same value, you can set
&V4& 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 will
no longer be an issue.

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE