How To Fix BRAIN_DEV300 - Impossible de supprimer ambiguïtés du ratio &1. Remodélisation requise.

SAP Error Message - Details

• Message type: E = Error

• Message class: BRAIN_DEV - BRAIN messages (for use by development)

• Message number: 300

• Message text: Impossible de supprimer ambiguïtés du ratio &1. Remodélisation requise.

Quelle est la cause de ce problème?

Key figure &V1& needs ambiguous join handling because there is a join
involved that causes ambiguities for this key figure. At the same time
<(>,<)> this key figure is mapped from several PartProviders or parts of
the union, and the ambiguities in these parts are different.
Example:
A CompositeProvider consists of 2 parts, and each of the parts consists
of a join:
( PP1 join B ) union ( PP2 join C )
A key figure amount is contained in PartProvider PP1 and PP2, and it is
contained in the CompositeProvider with a mapping from both PP1 and PP2.
PartProviders B and C have different characteristics. The
characteristics of B that are not join characteristics cause ambiguities
for amount from PP1, the characteristics of C that are not join
characteristics cause ambiguities for amount from PP2.
As the ambiguities are resolved in the analytic engine, the analytic
engine needs information about these ambiguities, and needs to treat
data from PP1 differently with respect to ambiguities than data from
PP2. This is currently not possible.

Réponse du système

The system raises this warning during activation of the
CompositeProvider or MultiProvider, and when using such key figures in a
query.

Comment corriger cette erreur?

The situation can be resolved with remodeling. Key figure &V1& in the
CompositeProvider has to be replaced: For each of the union parts or
PartProviders that have different ambiguities<(>,<)> a separate key
figure has to be exposed in the CompositeProvider or MultiProvider.
These key figures must not have exception aggregation.
A calculated key figure can then be defined that includes all these
separate key figures. If the original key figure has had exception
aggregation, the exception aggregation has to be defined with the
calculated key figure.
In the example above, replace the key figure amount in the
CompositeProvider with two different amount key figures:
amount_pp1 mapped from PP1
amount_pp2 from PP2
calculated key figure amount_ckf: amount_pp1 + amount_pp2.

Procédure pour les administrateurs système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Extrait du message d'erreur du système SAP. Copyright SAP SE.