DBTAB_UC_KEY_ERROR 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 program correction for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Illegal access to a database table in Unicode context
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
In a Unicode program, one of the following database statements was used
with generic key access:
- READ TABLE dbtab ... SEARCH GKEQ|GKGE ... VERSION vers
- READ TABLE dbtab ... SEARCH GKEQ|GKGE ... WITH KEY key
- LOOP AT dbtab ... VERSION vers
In Unicode, the key being used can only contain character-type
components (types C, N, D, T). In the present case however, the search
key for table <runtime parameter> contained non character-type components.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
DBTAB_UC_KEY_ERROR - dbtab uc key error DBTAB_UC_CONVERT_ERROR - dbtab uc convert error DBSQL_UNSUPPORTED_CONNECTION - dbsql unsupported connection DBSQL_UNKNOWN_CONNECTION - dbsql unknown connection DBSQL_TOO_MANY_OPEN_CURSOR - dbsql too many open cursor DBSQL_TOO_MANY_LOB_HANDLES - dbsql too many lob handles