How To Fix DDLS105 - In the On condition, only the operator Equals is supported

DDLS105 - Overview

• Message type: E = Error

• Message class: DDLS - For DDL source handling

• Message number: 105

• Message text: In the On condition, only the operator Equals is supported

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.

DDLS105 - Details

• The SAP error message DDLS105 indicates that there is an issue with the use of the "ON" condition in a SQL statement, specifically in the context of a join operation. The error message states: "In the ON condition, only the operator Equals is supported." This means that when defining the join condition between two tables, you can only use the equality operator (=) to specify how the records from the two tables relate to each other.
  
  Cause:
  The error occurs when you attempt to use a non-equality operator (such as <, >, <=, >=, <>, etc.) in the ON clause of a join statement. In SAP HANA and certain other database systems, the join conditions must be based on equality to ensure that the join operation is well-defined and efficient.
  
  Solution:
  To resolve this error, you need to modify your SQL statement to ensure that all conditions in the ON clause of your join