How To Fix ACMDT_OBJSTATUS091 - PFCG-Aspect has auth.object &1, but its PFCG mapping has auth.object &2

ACMDT_OBJSTATUS091 - Overview

• Message type: E = Error

• Message class: ACMDT_OBJSTATUS - ACM: Messages for the Object-Status of Designtime-Objects

• Message number: 091

• Message text: PFCG-Aspect has auth.object &1, but its PFCG mapping has auth.object &2

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.

ACMDT_OBJSTATUS091 - Details

• The SAP error message ACMDT_OBJSTATUS091 indicates a mismatch between authorization objects in the PFCG role definition and the actual authorization objects assigned to the role. Specifically, it states that the PFCG aspect has one authorization object, but its mapping has a different authorization object.
  
  Cause:
  This error typically arises due to one of the following reasons:
  
  Inconsistent Role Definition: The role has been modified, and the authorization objects have not been updated consistently across all aspects of the role.
  Transport Issues: If roles are transported between systems (e.g., from development to production), inconsistencies can occur if the transport does not include all necessary changes.
  Manual Changes: Manual changes to authorization objects in the role or the underlying authorization profiles can lead to discrepancies.
  
  
  Solution:
  To resolve this error, follow these steps:
  
  
  Check Role Definition:
  
  Go to transaction PFCG and open the role that is causing the error.
  Review the authorization data and ensure that the authorization objects listed in the