How To Fix /IWBEP/SBDSP_UI060 - Only attributes can be set as max hits

SAP Error Message - Details

• Message type: E = Error

• Message class: /IWBEP/SBDSP_UI -

• Message number: 060

• Message text: Only attributes can be set as max hits

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 /IWBEP/SBDSP_UI060 - Only attributes can be set as max hits ?

  The SAP error message /IWBEP/SBDSP_UI060 Only attributes can be set as max hits typically occurs in the context of SAP Gateway or OData services when there is an attempt to set a maximum hit limit on a non-attribute field in a service definition. This error indicates that the system expects only attributes (fields that are part of the entity) to be configured with a maximum hit limit, and other types of fields (like navigation properties or complex types) cannot be set in this way.
  Cause:
  
  Incorrect Configuration: The error is usually caused by trying to set a maximum hit limit on a field that is not an attribute. For example, if you are trying to set a limit on a navigation property or a complex type, the system will throw this error.
  Service Definition Issues: There may be issues in the service definition where the fields are not correctly categorized as attributes.
  
  Solution:
  
  Review the Service Definition: Go to the service definition in the SAP Gateway Service Builder (transaction code SEGW) and check the fields you have defined. Ensure that you are only setting the maximum hit limit on fields that are defined as attributes.
  Adjust the Configuration: If you find that you have mistakenly set a maximum hit limit on a non-attribute field, remove that configuration. Only attributes should have a maximum hit limit set.
  Regenerate the Service: After making the necessary changes, regenerate the service and test it again to see if the error persists.
  Check for Updates: Ensure that your SAP system is up to date with the latest support packages and notes, as there may be fixes or improvements related to this issue.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to OData services and the specific error message for any additional guidance or known issues.
  Documentation: Refer to the official SAP documentation on OData services and the Gateway framework for best practices on defining entities and attributes.
  Community Forums: Consider searching or posting on SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the error and ensure that your OData service is configured correctly.