How To Fix BRAINOLAPAPI111 - Disallowed MDX statement. Axes are discontinuous!

SAP Error Message - Details

• Message type: E = Error

• Message class: BRAINOLAPAPI - Message class for OLAP API

• Message number: 111

• Message text: Disallowed MDX statement. Axes are discontinuous!

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message BRAINOLAPAPI111 - Disallowed MDX statement. Axes are discontinuous! ?

  The SAP error message BRAINOLAPAPI111: Disallowed MDX statement. Axes are discontinuous! typically occurs in the context of SAP BW (Business Warehouse) when working with MDX (Multidimensional Expressions) queries. This error indicates that there is an issue with the structure of the MDX query, specifically that the axes of the query are not aligned or are discontinuous.
  Cause:
  
  Discontinuous Axes: The error suggests that the dimensions or hierarchies being referenced in the MDX query are not properly aligned. For example, if you are trying to retrieve data from multiple dimensions that do not share a common hierarchy or level, this can lead to discontinuity.
  Incorrect Query Structure: The MDX query may be incorrectly structured, leading to a situation where the axes do not match in terms of the data being queried.
  Incompatible Dimensions: The dimensions used in the query may not be compatible with each other, leading to a situation where the query cannot be executed properly.
  
  Solution:
  
  Review the MDX Query: Check the MDX query for any structural issues. Ensure that the dimensions and hierarchies being referenced are compatible and properly aligned.
  Align Dimensions: Make sure that the dimensions used in the query are related and can be combined. If necessary, adjust the query to ensure that the axes are continuous.
  Use Valid Hierarchies: Ensure that you are using valid hierarchies for the dimensions in your query. If you are using multiple hierarchies, ensure they are compatible.
  Test with Simplified Queries: If the query is complex, try breaking it down into simpler parts to identify where the discontinuity occurs. This can help isolate the problematic part of the query.
  Consult Documentation: Refer to SAP BW documentation or MDX query documentation for guidelines on constructing valid MDX queries.
  
  Related Information:
  
  MDX Basics: Understanding the basics of MDX and how it interacts with OLAP (Online Analytical Processing) can help in constructing valid queries.
  SAP BW Query Designer: Using the SAP BW Query Designer can help in visually constructing queries and ensuring that dimensions and measures are properly aligned.
  SAP Community and Forums: Engaging with the SAP community or forums can provide insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance, as they may provide more specific guidance based on your system configuration and the details of your query.