CALL_FUNCTION_CONFLICT_TAB_TYP 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.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Type conflict in a function module call.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
When calling function module <runtime parameter>, an attempt was made to pass internal
table <runtime parameter> to formal parameter <runtime parameter>. This resulted in a type conflict
between the formal and actual parameters.
Please see itab type conflict for more details about the possible cause of this runtime error and how it could be avoided.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_FUNCTION_CONFLICT_TAB_TYP - call function conflict tab typ CALL_FUNCTION_CONFLICT_LENG - call function conflict leng CALL_FUNCTION_CONFLICT_GEN_TYP - call function conflict gen typ CALL_FUNCTION_CANT_SET_USERKEY - call function cant set userkey CALL_FUNCTION_CANNOT_REGISTER - call function cannot register CALL_FUNCTION_BLOB_TYPE - call function blob type