ABAP Runtime Errors

ITAB_ILLEGAL_SCND_HASH_KEY SAP ABAP Runtime Error itab illegal scnd hash key







ITAB_ILLEGAL_SCND_HASH_KEY 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.


ITAB_ILLEGAL_SCND_HASH_KEY ABAP Runtime Error

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.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Invalid key entered for a secondary key of type HASHED Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to access table <runtime parameter> using secondary key <runtime parameter> of type Typ HASHED KEY with one of the following statements:

(a) READ/DELETE ... WITH KEY ... COMPONENTS k1 = v1 ... kn = vn.

(b) LOOP ... USING KEY ... WHERE (cond).

Table key <runtime parameter> was not completely provided with values by the key specified, meaning the specification of the secondary key would not have any effect, and the statement would have linear runtime behaviour.

A HASHED secondary key can only be entered if completely provided with values.

If a dynamic WHERE condition is entered (case (b)) , the "cond" condition must comply with the following rules:

(1) All subconditions must be linked with "AND".

(2) All components of the table key must be covered using subconditions as "comp = val" or "comp EQ val".

(3) To optimize the loop, the component and value should be categorized identically at "comp = val". See also SAP Note 1495892.

It is also possible to specify subconditions linked with "AND" containing relational operators other than "=" and "EQ". Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.