How To Fix BRAIN_DEV655 - FIRST/LAST avec filtre temp. non convexe peut retourner des résul. inatt.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 655

• Message text: FIRST/LAST avec filtre temp. non convexe peut retourner des résul. inatt.

Quelle est la cause de ce problème?

The query contains a potentially non-convex time filter on a
non-cumulative key figure that is aggregated with exception aggregation
FIRST or LAST, and parts of this time filter might be outside the time
interval where values exist for all validity characteristic value
combinations (also called 'homogeneous area' ).
A non-convex time filter is a time filter with gaps, for example
<EX>CALMONTH = 01.2014 OR CALMONTH = 03.2014</>.
The effects that this kind of filter can have are shown in the following
example. We show the values of key figure "quantity" for the time period
01.2014 - 03.2014 for plants A and B. Plant is a validity
characteristic:
Plant/Calendar Month,,01.2014,,02.2014,,03.2014
<ZH>A</>,,20,,50
<ZH>B</>,,10,,30,,40
For the above mentioned non-convex time filter <EX>CALMONTH = 01.2014 OR
CALMONTH = 03.2014</>, a query with <EX>LAST</> exception aggregation
over time on key figure "quantity" would return:
Plant/Calendar Month,,01.2014,,03.2014,,Total
<ZH>A</>,,20,,[50],,50
<ZH>B</>,,10,,40,,40
<ZH>Total</>,,30,,90,,90
The problem here is that the total 50 for A is different to the last
valid value 20. The last stock change of A happened at a time that was
excluded by the time filter. According to the rules of virtual
indicators, the total 50 must not have a virtual indicator, as it is an
aggregate that includes valid (non-virtual) values.
This can produce a number of strange effects:
The total number for A (50) can change by navigation to 20, for example
if a filter on <EX>PLANT = 'A'</> is added.
The "strange" total number for A can be cached in the OLAP cache and
used in situations without non-convex time filters. As the total is not
a virtual value, this cannot be detected.
Unfortunately, it would be extremely costly for the analytic engine in
terms of query performance and memory consumption to detect and flag the
total on A as a virtual value here, and the performance of all
non-cumulative queries would be impaired.

Réponse du système

The query is executed as defined.

Comment corriger cette erreur?

Consider changing the query definition or switching off the cache for
this query in order to avoid unexpected numbers in other navigation
steps.

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.