Do you have any question about this error?
Message type: E = Error
Message class: BRAIN_DEV - BRAIN messages (for use by development)
Message number: 152
Message text: El caché se utiliza a pesar de la característica / ratio virtual
The query uses virtual characteristics or virtual key figures filled in
a BADI implementation. The result of this BADI implementation is stored
in the analytic engine query cache and might be reused in navigation
contexts with less characteristics in drill. This only leads to reliable
and reproducible query results if the operations performed in the BADI
implementation are interchangeable with aggregation. SAP Note 1717880
describes the problem and the possible solutions.
A simple example for a problematical BADI implementation
The BADI changes the value of a key figure with standard aggregation SUM
to 0 if it is negative. Assume the following data inside the
infoprovider:
Country,,Quantity
Germany,,-50 PC
France,,+20 PC
Netherlands,,+60 PC
If the data is read with the Country, all rows are processed by the
BADI, the quantity for Germany is changed to 0 PC, and the total
quantity is +80 PC. If the data is read pre-aggregated, only one row is
processed by the BADI, and the total quantity is +30 PC. Depending on
the granularity the result is different. Depending on the current
content of the query cache the result for the total can be different.
This is unexpected of course.
El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.
The following solutions are possible, depending on the type of
operations performed in the BADI implementation:
You can specify a level of detail in the user exit that is the minimum
level for the reading of the data.
You can use formulas with exception aggregation instead of virtual key
figures.
You can switch off the usage of the OLAP cache.
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
BRAIN_DEV152
- El caché se utiliza a pesar de la característica / ratio virtual ?Get instant SAP help. Start your 7-day free trial now.
BRAIN_DEV151
La parametrización &1 no se puede modificar para esta consulta.
¿Qué causa este problema? This field can't be changed for this query. In mass maintenance for query properties, fields show up if the InfoProv...
BRAIN_DEV150
Variable "&1": &2 no es un número válido con &3 cifras y &4 decimales
Mensaje autoexplicativo Dado que SAP cree que este mensaje de error específico 'se explica por sí mismo', no se ha proporcionado más información. ...
BRAIN_DEV153
El elemento &1 no debería utilizar la parametrización "Ampliación datos"
¿Qué causa este problema? Element &V1& uses another structure element in the 'Data Extension' disaggregation setting. In disaggre...
BRAIN_DEV154
Escenario integridad datos "G Datos estables garantizados" reducido a "S"
¿Qué causa este problema? The query is based on a MultiProvider or CompositeProvider that contains non-cumulative key figures. In addition<(>...
Haga clic en este enlace para buscar todos los mensajes de SAP.