Message type: E = Error
Message class: BRAIN -
Message number: 120
Message text: Variable &2 is not allowed for the exchange rate type.
The query cannot be generated.
Check the query or translation type &V3&.
Error message extract from SAP system. Copyright SAP SE.
BRAIN120
- Variable &2 is not allowed for the exchange rate type. ?The SAP error message BRAIN120 indicates that a specific variable (denoted as &2) is not allowed for the exchange rate type in the context of a report or query. This error typically arises in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with queries that involve currency conversion or exchange rates.
Cause: Invalid Variable: The variable you are trying to use is not compatible with the selected exchange rate type. This could be due to the variable being defined incorrectly or not being allowed for the specific context of the query. Exchange Rate Type Configuration: The exchange rate type may not be configured to accept the variable you are trying to use. This can happen if the variable is not set up in the relevant InfoObject or if it is not linked correctly to the exchange rate type. Query Design Issues: The query might be designed in a
Get instant SAP help. Sign up for our Free Essentials Plan.
BRAIN119
Variable &2 is not allowed for the conversion key date
CAUSE& Only parameter variables for InfoObject date are permitted when determining the key date for a currency translation. However &V2& ...
BRAIN118
SQL error occurred while reading value set table &1
What causes this issue? The query uses a variable that represents a <ZK>precalculated value set </>. An SQL error occurred while reading ...
BRAIN121
&1 is not a valid key figures for InfoProvider &2
What causes this issue? Customer enhancement RSR00002 or the implementation of BAdI RSR_OLAB_BADI delivers &V1& as the key figure to be calcu...
BRAIN122
&1 is not a valid characteristic for InfoProvider &2
What causes this issue? InfoObject &V1& is not included in InfoProvider &V2&. There might be several reasons for this: InfoObject &a...
Click on this link to search all SAP messages.