How To Fix ACM370 - Ranktable field &1 nor part of PFCG mapping neither of the dimension key

ACM370 - Overview

• Message type: E = Error

• Message class: ACM - Message-Class for all ACM functions/exceptions

• Message number: 370

• Message text: Ranktable field &1 nor part of PFCG mapping neither of the dimension key

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 ACM370 - Ranktable field &1 nor part of PFCG mapping neither of the dimension key ?

  The SAP error message ACM370 indicates that a specific field (denoted as &1) in a rank table is not part of the PFCG (Profile Generator) mapping or the dimension key. This error typically arises in the context of SAP BW (Business Warehouse) or SAP Analytics, where rank tables are used for ranking data based on certain criteria.
  
  Cause:
  
  Field Not Mapped: The field specified in the error message is not included in the PFCG role mapping. This means that the user or role does not have the necessary authorizations to access this field.
  Dimension Key Issues: The field may not be part of the defined dimension keys in the data model, which can lead to inconsistencies when trying to access or rank data.
  Data Model Changes: If there have been recent changes to the data model, such as adding or removing fields, this can lead to discrepancies in the rank table configuration.
  
  
  Solution:
  
  
  Check PFCG Role