How To Fix ACMDT_OBJSTATUS235 - CDS entity is flagged as "Has DCLs" but has no related metadata entries

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 235

• Message text: CDS entity is flagged as "Has DCLs" but has no related metadata entries

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_OBJSTATUS235 - CDS entity is flagged as "Has DCLs" but has no related metadata entries ?

  The SAP error message "ACMDT_OBJSTATUS235: CDS entity is flagged as 'Has DCLs' but has no related metadata entries" typically indicates an issue with the Core Data Services (CDS) entity in your SAP system. This error arises when a CDS view is marked as having Data Control Language (DCL) annotations, but there are no corresponding DCL metadata entries defined for it.
  Cause:
  
  Missing DCL Annotations: The CDS entity is expected to have associated DCL annotations that define access control rules, but these annotations are either missing or not properly defined.
  Inconsistent Metadata: There may be inconsistencies in the metadata definitions, leading the system to believe that DCLs are present when they are not.
  Transport Issues: If the CDS view and its DCLs were transported from one system to another, there might have been an issue during the transport process that caused the DCL metadata to be lost or not included.
  
  Solution:
  
  
  Check DCL Annotations: Review the CDS view definition to ensure that the DCL annotations are correctly defined. If they are missing, you will need to create the appropriate DCLs for the CDS entity.
  Example of a DCL definition:
  define role <RoleName>
  {
      use create;
      use update;
      use delete;
      use read;
  }
  
  
  Create Missing DCLs: If the DCLs do not exist, create them in the appropriate package and ensure they are activated. Make sure that the DCLs are correctly linked to the CDS view.
  
  
  Check Transport Requests: If the issue arose after a transport, check the transport request to ensure that all necessary objects (both the CDS view and its DCLs) were included and successfully imported into the target system.
  
  
  Activate the CDS View: After making changes, ensure that you activate both the CDS view and the DCLs. Sometimes, reactivating the CDS view can resolve metadata inconsistencies.
  
  
  Check for System Notes: Look for any SAP Notes or updates related to this error message. SAP frequently releases notes that address specific issues or provide guidance on best practices.
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation on CDS views and DCLs for detailed information on how to define and manage them.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Debugging Tools: Use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to inspect the definitions of your CDS views and DCLs.
  
  By following these steps, you should be able to resolve the error and ensure that your CDS entity is properly configured with the necessary DCLs.