How To Fix /EACA/PMRT154 - Exception aggregation characteristic &1 is not requested

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACA/PMRT -

• Message number: 154

• Message text: Exception aggregation characteristic &1 is not requested

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 /EACA/PMRT154 - Exception aggregation characteristic &1 is not requested ?

  The SAP error message /EACA/PMRT154 Exception aggregation characteristic &1 is not requested typically occurs in the context of SAP's Business Warehouse (BW) or SAP Analytics Cloud (SAC) when dealing with exception aggregation in reporting or data modeling. This error indicates that a specific characteristic (denoted by &1) that is expected for exception aggregation is not included in the request or query.
  Cause:
  
  
  Missing Characteristic in Query: The characteristic that is mentioned in the error message is not included in the query definition or the data model. This can happen if the characteristic is not selected in the query designer or if it is not part of the data source.
  
  
  Incorrect Configuration: The configuration for exception aggregation may not be set up correctly, leading to the system not recognizing the characteristic as part of the aggregation process.
  
  
  Data Source Issues: The data source may not be properly configured to include the necessary characteristics for the exception aggregation.
  
  
  Solution:
  
  
  Check Query Definition: Go to the query designer and ensure that the characteristic mentioned in the error message is included in the query. If it is not, add it to the query.
  
  
  Review Exception Aggregation Settings: Check the settings for exception aggregation in the InfoObject or the data model. Ensure that the characteristic is marked for exception aggregation if it is supposed to be.
  
  
  Validate Data Source: Ensure that the data source (e.g., InfoProvider, DSO, etc.) includes the characteristic. If it is missing, you may need to adjust the data source or the underlying data model.
  
  
  Rebuild the Query: If the issue persists, consider rebuilding the query or the data model to ensure that all necessary characteristics are included and properly configured.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on exception aggregation and characteristics to ensure compliance with best practices.
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  
  
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues. You can find discussions, solutions, and best practices shared by other SAP professionals.
  
  
  Training and Documentation: If you are new to SAP BW or SAC, consider reviewing training materials or documentation that cover exception aggregation and query design to better understand how to configure these elements correctly.
  
  
  By following these steps, you should be able to resolve the error message and ensure that your queries and reports function as intended.