How To Fix ACMDT_OBJSTATUS090 - PFCG-Aspect has &1 detail entries, its related AC-Condition has &2

ACMDT_OBJSTATUS090 - Overview

• Message type: E = Error

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

• Message number: 090

• Message text: PFCG-Aspect has &1 detail entries, its related AC-Condition has &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_OBJSTATUS090 - Details

• The SAP error message ACMDT_OBJSTATUS090 typically relates to issues with authorization objects in the context of role maintenance using transaction PFCG (Profile Generator). This error indicates that there is a discrepancy between the number of detail entries in the PFCG aspect and the associated access condition.
  
  Cause:
  
  
  Mismatch in Entries: The error arises when the number of detail entries in the PFCG aspect does not match the expected number of entries defined in the access condition. This can happen due to:
  
  Manual changes made to the roles or authorization objects that are not properly synchronized.
  Deletion or modification of authorization objects or roles that lead to inconsistencies.
  Changes in the underlying data or configuration that affect the authorization checks.
  
  
  
  Transport Issues: If roles or authorizations were transported between systems (e.g., from development to production), inconsistencies may arise if the transport did not include all necessary objects or if there were changes made directly in the target