How To Fix SADL_ENTITY_MD_INCON000 - Metadata inconsistent ('&1', '&2'): ACL IDs have to start with $au

SAP Error Message - Details

• Message type: E = Error

• Message class: SADL_ENTITY_MD_INCON -

• Message number: 000

• Message text: Metadata inconsistent ('&1', '&2'): ACL IDs have to start with $au

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 SADL_ENTITY_MD_INCON000 - Metadata inconsistent ('&1', '&2'): ACL IDs have to start with $au ?

  The SAP error message SADL_ENTITY_MD_INCON000 indicates that there is a metadata inconsistency related to Access Control List (ACL) IDs in the context of the SAP ABAP programming model for SAP Fiori applications. The specific message states that the ACL IDs must start with $au, which is a requirement for the system to recognize and process the ACLs correctly.
  Cause:
  The error typically arises due to one of the following reasons:
  
  Incorrect ACL ID Format: The ACL IDs defined in the metadata do not conform to the expected format, which requires them to start with $au.
  Metadata Configuration Issues: There may be inconsistencies or misconfigurations in the metadata definitions for the entity in question.
  Custom Implementations: If there are custom implementations or extensions, they may not adhere to the required standards for ACL IDs.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check ACL IDs: Review the metadata definitions for the entity that is causing the error. Ensure that all ACL IDs start with $au. If any ACL IDs do not conform to this format, update them accordingly.
  
  
  Review Metadata Configuration: Ensure that the metadata configuration for the entity is correct and complete. This includes checking for any missing or incorrectly defined properties.
  
  
  Regenerate Metadata: If you have made changes to the metadata or if you suspect that the metadata is out of sync, consider regenerating the metadata for the affected entity. This can often resolve inconsistencies.
  
  
  Check Custom Code: If you have custom code or extensions, review them to ensure they are not introducing any inconsistencies in the metadata definitions.
  
  
  Consult Documentation: Refer to the official SAP documentation for guidelines on defining ACLs and metadata for your specific version of SAP. This can provide insights into best practices and requirements.
  
  
  Testing: After making the necessary changes, test the application to ensure that the error is resolved and that the functionality works as expected.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on ACL configurations.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Help Portal: Utilize the SAP Help Portal for detailed documentation on metadata management and ACL configurations in SAP systems.
  
  By following these steps, you should be able to identify and resolve the issue related to the SADL_ENTITY_MD_INCON000 error message.