ABAP Runtime Errors

DYN_CALL_METH_PARAM_TAB_TYPE SAP ABAP Runtime Error dyn call meth param tab type







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


DYN_CALL_METH_PARAM_TAB_TYPE ABAP Runtime Error

Please see abap error 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.

Table type conflict in a dynamic method call 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 submit the internal table to formal parameter <runtime parameter> of method <runtime parameter> of class <runtime parameter>. This resulted in a type conflict between the formal and actual parameters.

In the present case, one of the following conditions was violated:

1. The access types defined for the tables are not compatible. The compatibility rules are set by the following hierarchy:

ANY_TABLE (INDEX_TABLE (STANDARD_TABLE, SORTED_TABLE), HASHED_TABLE)

A concrete access type is only compatible with its predecessors in the hierarchy (for example: STANDARD_TABLE is compatible with INDEX_TABLE and ANY_TABLE, but is not compatible with HASHED_TABLE).

2. The row types in the two tables are incompatible.

3. The table keys for the two tables do not match.

4. One of the tables was defined with a UNIQUE key, the other with a NON UNIQUE key. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.