Message type: E = Error
Message class: BRAIN_DEV - BRAIN messages (for use by development)
Message number: 656
Message text: Virtual key figure &1 depends on non-matching key figure &2
The query contains a virtual key figure, which depends on another key
figure. One of the two key figures is non-cumulative, the other is a
normal cumulative key figure. This is not permitted. Cumulative and
non-cumulative key figures are read separately from each other.
Therefore a user exit cannot combine cumulative and non-cumulative key
figures.
Query generation is aborted.
Split the virtual key figure calculation into a cumulative part and a
non-cumulative part, and combine the two parts using a normal query
formula.
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.
BRAIN_DEV656
- Virtual key figure &1 depends on non-matching key figure &2 ?The SAP error message BRAIN_DEV656 indicates that there is a dependency issue between two key figures in a query or a data model. Specifically, it means that a virtual key figure (key figure &1) is dependent on another key figure (key figure &2) that does not match in terms of characteristics or data structure. This can occur in SAP BW (Business Warehouse) or SAP HANA environments when creating or modifying queries in BEx Query Designer or similar tools.
Cause: Incompatible Key Figures: The virtual key figure is trying to reference a key figure that has a different set of characteristics or aggregation levels. Data Model Issues: The underlying data model may have inconsistencies, such as missing or incorrectly defined characteristics. Query Design Errors: The query may have been designed incorrectly, leading to mismatched dependencies between key figures.
Solution: Check Key Figure Definitions: Review the definitions of both the virtual key figure and the non-matching key figure.
Get instant SAP help. Sign up for our Free Essentials Plan.
BRAIN_DEV655
FIRST/LAST with non-convex time filters can produce unexpected results
What causes this issue? The query contains a potentially non-convex time filter on a non-cumulative key figure that is aggregated with exception aggr...
BRAIN_DEV654
Total number of structure element combinations exceeds allowed limit
What causes this issue? The query is too complex to be processed. The allowed limits are: Each structure used should have less than &V1& elem...
BRAIN_DEV657
InfoProvider fill states have been auto-refreshed
What causes this issue? Data was deleted in an underlying provider of the query. Therefore the transaction data has been refreshed.System Response T...
BRAIN_DEV658
Ongoing data deletion in InfoProvider. Subsequent refreshes failed.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.