How To Fix BRAIN035 - Query &1/&2 contains non-cumulative values but no time restriction

BRAIN035 - Overview

• Message type: E = Error

• Message class: BRAIN -

• Message number: 035

• Message text: Query &1/&2 contains non-cumulative values but no time restriction

What causes this issue?

Query / uses non-cumulative key figures. It requires calculation for
non-cumulative values for more than 2000 periods in time. The most
common reason for this is that the non-cumulative InfoCube has a very
large validity interval and the query has no time restrictions. With
exception aggregation AVERAGE (AV1 or AV2) in particular, this lack of
time restriction would result in considerable memory and performance
problems.

System Response

Query / cannot be executed in this way.

How to fix this error?

Restrict the time interval for the query to a suitable interval.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BRAIN035 - Query &1/&2 contains non-cumulative values but no time restriction ?

  The SAP error message BRAIN035 indicates that a query in SAP BW (Business Warehouse) is attempting to use non-cumulative values without a time restriction. This typically occurs when you are trying to aggregate or analyze data that is not cumulative (like daily sales figures) without specifying a time dimension, which can lead to incorrect or ambiguous results.
  
  Cause:
  
  Non-Cumulative Values: The query is using key figures that are defined as non-cumulative (e.g., daily sales, monthly expenses) which cannot be aggregated over time without a specific time context.
  Missing Time Restriction: The query does not have a time filter or restriction applied, which is necessary to ensure that the non-cumulative values are aggregated correctly.
  
  
  Solution:
  To resolve the BRAIN035 error, you can take the following steps:
  
  
  Add a Time Restriction:
  
  Modify the query to include a time dimension (e.g., year, month, day) in the selection criteria. This will help the system understand how to aggregate the non-cumulative values