How To Fix SADL_ENTITY_RUNTIME035 - Function import '&1' is not unique for actions &2 and &3

SADL_ENTITY_RUNTIME035 - Overview

• Message type: E = Error

• Message class: SADL_ENTITY_RUNTIME - Messages of SADL runtime and DDIC SADL entity runtime

• Message number: 035

• Message text: Function import '&1' is not unique for actions &2 and &3

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_RUNTIME035 - Function import '&1' is not unique for actions &2 and &3 ?

  The SAP error message SADL_ENTITY_RUNTIME035 indicates that there is a conflict in the function imports defined in your SAP system. Specifically, it states that the function import you are trying to call is not unique for the specified actions. This typically occurs in the context of SAP Gateway or OData services when there are multiple actions or function imports that match the same name or signature.
  
  Cause:
  
  Duplicate Function Imports: There are multiple function imports defined in your OData service with the same name, which leads to ambiguity when the service is called.
  Conflicting Actions: The actions that are being referenced in the error message (&2 and &3) may have similar signatures or names, causing the system to be unable to determine which one to execute.
  Service Definition Issues: The service definition might not be properly configured, leading to conflicts in the function imports.
  
  
  Solution:
  
  
  Check Function Imports: Review the function imports defined in your OData