Message type: E = Error
Message class: BRAIN_DEV - BRAIN messages (for use by development)
Message number: 188
Message text: Inconsistent hierarchy settings for &1: filter changed
For characteristic &V1&, the presentation hierarchy and the hierarchy
used in the filter (default values) that define the initial dynamic
filter are not consistent.
The following consistency requirements are checked for a characteristic
based on the status of the presentation hierarchy:
Active presentation hierarchy: All filters (default values) have to be
defined on nodes of the presentation hierarchy. For non-compounded
characteristics, filters (default values) can be defined on single flat
values.
Inactive presentation hierarchy:
No Filters (default values) are defined on hierarchy nodes: The
hierarchy settings are considered as consistent.
At least one Filter (default values) is defined on a hierarchy node: The
same consistency requirements are checked as in the case of an active
presentation hierarchy.
No presentation hierarchy: Filter (default values) must not be defined
on hierarchy nodes.
The inconsistent filter (default values) is not evaluated for the
characteristic and is removed.
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.
The SAP error message BRAIN_DEV188, which states "Inconsistent hierarchy settings for &1: filter changed," typically occurs in the context of SAP BW (Business Warehouse) or SAP Analytics when there are inconsistencies in the hierarchy settings of a characteristic or when a filter applied to a query or report has been modified in a way that conflicts with the existing hierarchy settings.
Cause:
- Hierarchy Changes: The hierarchy for a characteristic has been modified (e.g., nodes added, removed, or changed) after a query or report was created, leading to inconsistencies.
- Filter Modifications: A filter applied to a query or report has been changed, which may not align with the current hierarchy settings.
- Data Model Changes: Changes in the underlying data model, such as updates to InfoObjects or InfoProviders, can lead to this error.
- Transport Issues: If the hierarchy settings were transported from one system to another (e.g., from development to production), inconsistencies may arise if the target system does not have the same settings.
Solution:
- Check Hierarchy Settings: Review the hierarchy settings for the characteristic in question. Ensure that the hierarchy is correctly defined and that any changes made are consistent with the queries or reports using it.
- Update Filters: If filters have been changed, ensure that they are compatible with the current hierarchy. You may need to adjust or remove filters that are causing the inconsistency.
- Rebuild Queries: If the issue persists, consider rebuilding the affected queries or reports to ensure they align with the current hierarchy settings.
- Transport Consistency: If the issue is related to transport, verify that all necessary objects and settings have been transported correctly and that the target system is in sync with the source system.
- Check for Notes: Look for SAP Notes related to this error message. SAP may have provided specific guidance or patches to address known issues.
Related Information:
By following these steps, you should be able to resolve the BRAIN_DEV188 error and ensure that your hierarchy settings are consistent with your queries and reports.
Sign up takes 1 minute. 7-day free trial.
BRAIN_DEV178 A hierarchy is set in the tuple filter for characteristic &1
What causes this issue? Hierarchies are not supported in the tuple filter.Syste...
BRAIN_DEV177 Tuple filter is not supported because query contains planning
Self-Explanatory Message Since SAP believes that this specific error message is ...
BRAIN_DEV189
Self-Explanatory Message Since SAP believes that this specific error message is ...
BRAIN_DEV190 For characteristic &1 only one hierarchy with key date derivation allowed
What causes this issue? The Analytic Engine only supports one hierarchy with ke...
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.