How To Fix BRAIN016 - Lecture ciblée pour requête & lors navigation et expansion hiérarchie

BRAIN016 - Overview

• Message type: E = Error

• Message class: BRAIN -

• Message number: 016

• Message text: Lecture ciblée pour requête & lors navigation et expansion hiérarchie

Query & now reads data on demand when navigating and expanding the
hierarchy.
For a query, the OLAP processor can read the data in the fact table in
one of three ways:
Reading all of the data
When executing the query in the Business Explorer all of the fact table
data, that is needed for all possible navigational steps in the query,
is read in the main memory area of the OLAP processor. Therefore, all
new navigational states are aggregated and calculated from the data of
the main memory.
Reading the data on demand:
The OLAP processor only requests the corresponding fact table data that
is needed for each navigational state of the query in the Business
Explorer. Therefore, new data is read for each navigational step. The
most suitable aggregate table is used and, if possible, already
aggregated on the database. The data for identical navigational states
states is buffered in the OLAP processor.
Reading on demand when expanding the hierarchy:
When reading data on demand (2), the data for the entire - meaning
completely expanded - hierarchy is requested for a hierarchy drilldown.
For the read on demand when expanding the hierarchy (3), the data is
aggregated by the database along the hierarchy and is sent to the start
level of the hierarchy (highest node) in the OLAP processor. When
expanding a hierarchy node, the children of the node are then
respectively read on demand.

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.

In general, the reading of data on demand (2) provides much better
performance than reading all the data (1). This read mode should
especially be considered for queries with many, free characteristics. A
query that contains two or more free characteristics from different
dimensions (e.g. 'Customer' and 'Product'), will probably only be
efficiently executable in this mode, as the aggregates can only be
optimally used when reading the data on demand.
For large hierarchies, aggregates should be created a middle level of
the hierarchy and the start level of the query should be smaller or the
same as this aggregate level. For queries about such large hierarchies,
the read on demand when expanding the hierarchy method (3) should be
set.

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