TABLES_SCND_KEYS_NOT_IN_RFC 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 abap error for more details about the possible cause of this runtime error and how it could be avoided.
TABLES with secondary keys cannot be used in the RFC.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Tables with secondary keys cannot be used as TABLES parameters in RFC
calls. To submit tables with secondary keys, use the IMPORTING,
EXPORTING, or CHANGING parameters.
In the present case, the variable submitted, <runtime parameter>, has type <runtime parameter>, which
contains secondary keys.
Caution: The previously specified name of the variable need not
correspond with the variable name submitted. This is the case with
field symbols for example. The specified variable name always points to
the submitted table however.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
TABLES_SCND_KEYS_NOT_IN_RFC - tables scnd keys not in rfc SYSTEM_VIEW_INCONSISTENT - system view inconsistent SYSTEM_TYPE_NOT_ELEMENTARY - system type not elementary SYSTEM_TPOL_TYPE_MISSING - system tpol type missing SYSTEM_TOO_MANY_PCBS - system too many pcbs SYSTEM_TOO_MANY_INTERFACES - system too many interfaces