SAPSQL_LIKE_PATTERN_TOO_LONG is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Open SQL statement with WHERE ... LIKE and pattern that is too large.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The current ABAP program wanted to execute an open SQL statement whose
WHERE condition uses a LIKE operator.
The pattern for a LIKE operator can contain no more than <runtime parameter> characters
(excluding closing blanks). This is the minimum of <runtime parameter> and twice as
long as the database field (<runtime parameter>) that the condition is supposed to
apply for.
In the present case, pattern <runtime parameter> contains more than the permitted
maximum of <runtime parameter> characters.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_LIKE_PATTERN_TOO_LONG - sapsql like pattern too long SAPSQL_LIKE_ILLEGAL_FLDTYPE - sapsql like illegal fldtype SAPSQL_KEYS_NOT_CONVERTIBLE - sapsql keys not convertible SAPSQL_JOIN_ON_OJ_CMP - sapsql join on oj cmp SAPSQL_JOIN_ON_ILLEGAL_OR - sapsql join on illegal or SAPSQL_JOIN_ON_ILLEGAL_NOT - sapsql join on illegal not