Do you have any question about this error?
Message type: E = Error
Message class: SEEF_BADI - Messages on BAdIs
Message number: 118
Message text: Enclosing literal characters '...' or `...` are superfluous
You want to define a comparison value for a character-type or
string-type filter, whose first and last character is a literal delimi
ter.
At runtime, the comparison value is automatically enclosed by suitable
literal delimiters.
Check whether you need delimiters in addition to the automatically
generated literal delimiters.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
SEEF_BADI118
- Enclosing literal characters '...' or `...` are superfluous ?The SAP error message SEEF_BADI118, which states "Enclosing literal characters '...' or
...
are superfluous," typically occurs in ABAP code when there are unnecessary quotation marks or backticks around a string literal. This can happen in various contexts, such as when defining strings or using them in method calls.Cause:
The error is caused by the presence of superfluous enclosing characters around a string literal. For example, if you have a string defined like this:
DATA(lv_string) = 'Hello World'.
And you mistakenly write it as:
DATA(lv_string) = ''Hello World''.
or
DATA(lv_string) = ``Hello World``.
In these cases, the additional quotes or backticks are unnecessary and lead to the error.
Solution:
To resolve this error, you need to remove the extra enclosing characters. Ensure that string literals are defined correctly. For example, change:
DATA(lv_string) = ''Hello World''.
to:
DATA(lv_string) = 'Hello World'.
or if you are using backticks, ensure they are used correctly in the context of the code.
Related Information:
ABAP Syntax: Familiarize yourself with the correct syntax for defining string literals in ABAP. Single quotes (
'
) are typically used for string literals, while backticks (`
) are used in specific contexts, such as for identifiers in certain SQL statements.Code Review: Regularly review your code for syntax errors, especially when dealing with string literals. Using an IDE like ABAP Development Tools (ADT) can help catch these errors early.
Debugging: If you encounter this error during runtime, use the debugger to trace back to the line of code causing the issue. This will help you identify the exact location of the superfluous characters.
Documentation: Refer to the official SAP documentation for ABAP programming to understand the correct usage of string literals and other syntax rules.
By following these guidelines, you should be able to resolve the SEEF_BADI118 error effectively.
Get instant SAP help. Start your 7-day free trial now.
SEEF_BADI117
Not possible in the case of BAdIs with filters
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEEF_BADI116
Single character "&1" is not permitted in "&2"; use duplicate: "&3"
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEEF_BADI119
Filter &1: Dictionary element &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEEF_BADI120
Filter &1: Class &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.