Do you have any question about this error?
Message type: E = Error
Message class: DDLS - For DDL source handling
Message number: 381
Message text: Escape characters in LIKE must only be literals
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.
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.
The SAP error message DDLS381 indicates that there is an issue with the use of escape characters in a SQL
LIKE
clause. Specifically, the error states that escape characters must only be literals, meaning that you cannot use variables or expressions as escape characters in your SQL statements.Cause:
The error typically occurs when you are trying to use a dynamic or non-literal value as an escape character in a
LIKE
condition. For example, if you have a SQL statement that looks like this:SELECT * FROM table_name WHERE column_name LIKE 'pattern' ESCAPE variable_name
In this case,
variable_name
is not a literal value, which leads to the error.Solution:
To resolve this error, you need to ensure that the escape character used in the
LIKE
clause is a literal value. Here’s how you can modify your SQL statement:
Use a Literal Escape Character: Replace the variable with a literal character. For example:
SELECT * FROM table_name WHERE column_name LIKE 'pattern' ESCAPE '\'
In this case, the backslash (
\
) is used as a literal escape character.Hardcode the Escape Character: If you need to use a specific escape character, hardcode it directly in your SQL statement instead of using a variable.
Check for Dynamic SQL: If you are constructing SQL dynamically, ensure that any escape characters are defined as literals before executing the SQL statement.
Related Information:
LIKE
operator is used in SQL to search for a specified pattern in a column. It can include wildcard characters such as %
(matches any sequence of characters) and _
(matches a single character).%
, you would use an escape character to indicate that the %
is not a wildcard.LIKE
operator and escape characters.By ensuring that your escape characters are literals, you should be able to avoid the DDLS381 error and successfully execute your SQL queries.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
DDLS380 The current expression is not supported in SEARCHED CASE after THEN
Self-Explanatory Message Since SAP believes that this specific error message is ...
DDLS379 SEARCHED CASE: Type information of default value is not correct
Self-Explanatory Message Since SAP believes that this specific error message is ...
DDLS382 Escape character after LIKE must only have length 1
Self-Explanatory Message Since SAP believes that this specific error message is ...
DDLS383 ASCII characters are allowed as escape characters (not SPACE, ', _, or %)
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.