Do you have any question about this error?
Unlock AI-Powered SAP Support – Free for 7 Days! Try It Now
Message type: E = Error
Message class: BRAIN_DEV - BRAIN messages (for use by development)
Message number: 136
Message text: The formula "&1"(&2) contains different exception aggregations: &3, &4
The formula or calculated key figure "&V1&" (&V2&) contains different
exception aggregations. The result of multiple exception aggregations
depends on the order in which the aggregations are executed, if the
exception aggregations are not the same. An execution order of
exceptions aggregations defined as a single formula or calculated key
figure cannot be guaranteed.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Contact SAP support.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message BRAIN_DEV136 indicates that there is an issue with a formula in a query or report that involves different exception aggregations. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when you are trying to create or modify a query that uses multiple exception aggregations that are not compatible with each other.
Cause:
The error arises when the formula you are trying to use contains different exception aggregations that cannot be combined. Exception aggregations are special calculations that allow you to define how certain values should be aggregated differently from the standard aggregation methods. For example, you might have a formula that tries to aggregate sales data using both "SUM" and "AVERAGE" for different components, which is not allowed.
Solution:
To resolve this error, you can take the following steps:
Review the Formula: Check the formula mentioned in the error message. Look for any exception aggregations that are being used. Ensure that all parts of the formula use the same type of aggregation.
Standardize Aggregations: If you find that different exception aggregations are being used, modify the formula to use a single type of aggregation. For example, if you are using "SUM" for one part, ensure that all other parts also use "SUM".
Check Query Design: If the formula is part of a query, review the query design to ensure that the key figures and characteristics used in the formula are compatible with each other.
Test the Formula: After making changes, test the formula again to see if the error persists.
Consult Documentation: If you are unsure about the exception aggregations or how to modify the formula, refer to SAP documentation or help resources for guidance on exception aggregations and formula creation.
Seek Help from SAP Support: If the issue continues and you cannot resolve it, consider reaching out to SAP support or consulting with a colleague who has experience with SAP BW/BI.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the BRAIN_DEV136 error message in your SAP environment.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
BRAIN_DEV135 Too much data requested; Add filter or remove drilldown characteristic.
What causes this issue? The predefined maximum effort (see <DS:DE.RSR_OLAPEF...
BRAIN_DEV134 Intersection of dyn time filter with fixed filter/val is empty. CSID &1.
What causes this issue? No non-cumulative data will be read for the specified c...
BRAIN_DEV137 &1: exception aggregation ref. characteristic is compounded
What causes this issue? Calculated key figure "&V1&" with exc...
BRAIN_DEV138 &1: exception aggregation ref. characteristic is compounded
What causes this issue? Formula "&V1&" with exception aggrega...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.