CALL_FUNCTION_DEEP_MISMATCH 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.
Please see funcparm error for more details about the possible cause of this runtime error and how it could be avoided.
Type conflict while passing parameters in CALL FUNCTION
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
In function <runtime parameter>, parameter <runtime parameter> is typed in such a way that only actual
parameters that can be interpreted according to the type of the formal
parameter are permitted.
This means that the positions and types, the reference, string and
table components in the first part of the actual parameter, described
by the formal parameter, must agree with the formal parameter.
Actual parameter <runtime parameter> had a different type though.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_FUNCTION_DEEP_MISMATCH - call function deep mismatch CALL_FUNCTION_CREATE_TABLE - call function create table CALL_FUNCTION_CPICTERMIO_ERROR - call function cpictermio error CALL_FUNCTION_CONNECT_ERROR - call function connect error CALL_FUNCTION_CONFLICT_TYPE - call function conflict type CALL_FUNCTION_CONFLICT_TAB_TYP - call function conflict tab typ