How To Fix SADL_GW_ATC_CONSMPTN811 - @Consumption.ranking irrelevant, since no @EnterpriseSearch-annotation

SAP Error Message - Details

• Message type: E = Error

• Message class: SADL_GW_ATC_CONSMPTN - SADL Gateway: ATC Messages for Consumtion Annotations

• Message number: 811

• Message text: @Consumption.ranking irrelevant, since no @EnterpriseSearch-annotation

What causes this issue?

The view carries @Consumption.ranking-annotations, but there is no
@EnterpriseSearch-annotation. As Enterprise Search is currently the only
instance to evaluate @Consumption.ranking, these annotations are void.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Either you remove the meaningless @Consumption.ranking-annotations, or -
if this is intended - you add the necessary
@EnterpriseSearch-annotations to make the view fit for Enterprise
Search.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SADL_GW_ATC_CONSMPTN811 - @Consumption.ranking irrelevant, since no @EnterpriseSearch-annotation ?

  The SAP error message SADL_GW_ATC_CONSMPTN811 @Consumption.ranking irrelevant, since no @EnterpriseSearch-annotation typically occurs in the context of SAP Gateway and the SAP ABAP programming environment when working with annotations related to OData services and consumption views.
  Cause:
  This error indicates that there is an issue with the use of the @Consumption.ranking annotation in your ABAP CDS (Core Data Services) view. The @Consumption.ranking annotation is used to define the ranking of the entity in the context of enterprise search. However, if the entity does not have an @EnterpriseSearch annotation, the ranking is considered irrelevant, leading to this error message.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Add the @EnterpriseSearch Annotation: If your CDS view is intended to be used with enterprise search, you should add the @EnterpriseSearch annotation to your CDS view. This will make the @Consumption.ranking annotation relevant.
  Example:
  @AbapCatalog.sqlViewName: 'Z_MY_CDS_VIEW'
  @AbapCatalog.compiler.compareFilter: true
  @AccessControl.authorizationCheck: #CHECK
  @EnterpriseSearch: true
  @Consumption.ranking: 10
  define view Z_MY_CDS_VIEW as select from my_table
  {
      key field1,
      field2,
      ...
  }
  
  
  Remove the @Consumption.ranking Annotation: If the CDS view is not intended for enterprise search, you can simply remove the @Consumption.ranking annotation from your CDS view.
  Example:
  @AbapCatalog.sqlViewName: 'Z_MY_CDS_VIEW'
  @AbapCatalog.compiler.compareFilter: true
  @AccessControl.authorizationCheck: #CHECK
  define view Z_MY_CDS_VIEW as select from my_table
  {
      key field1,
      field2,
      ...
  }
  
  
  Check for Other Annotations: Ensure that other relevant annotations are correctly defined in your CDS view, as they may also affect the behavior of the view.
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation on CDS views and annotations for more details on how to use @Consumption and @EnterpriseSearch annotations.
  SAP Community: Engage with the SAP Community forums for discussions and solutions related to similar issues.
  Debugging: If the issue persists, consider debugging the CDS view or checking the activation logs for more detailed error messages.
  
  By following these steps, you should be able to resolve the error and ensure that your CDS view is correctly configured for its intended use.