How To Fix ACMDT_OBJSTATUS347 - Auth. object of PFCG aspect (&1) and of related PFCG mapping (&2) differ

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 347

• Message text: Auth. object of PFCG aspect (&1) and of related PFCG mapping (&2) differ

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 ACMDT_OBJSTATUS347 - Auth. object of PFCG aspect (&1) and of related PFCG mapping (&2) differ ?

  The SAP error message ACMDT_OBJSTATUS347 indicates a discrepancy between the authorization object defined in the PFCG role and the authorization object that is mapped to it. This typically occurs when there is a mismatch in the authorization settings or when changes have been made to the role or its associated authorization objects.
  
  Cause:
  
  Mismatch in Authorization Objects: The authorization object defined in the PFCG role does not match the one that is mapped to it. This can happen if the authorization object was changed or if the role was modified without updating the mapping.
  Transport Issues: If roles or authorization objects 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 in the target system.
  Manual Changes: Manual changes to the authorization objects or roles that were not properly synchronized can lead to this error.
  
  
  Solution:
  
  Check Authorization Object Definitions: