DBPROC_OUTPUT_PARAMETER_MTDA 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.
Correct the settings for the SAP HANA database or install a new version
of the SAP HANA database.
See SAP Note 1811988.
Incompatible SAP HANA profile parameter
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
A database procedure was executed with version validation. The required
SAP HANA profile settings had not been made however.
A database procedure was executed on the SAP HANA database using
database connection <runtime parameter>. When calling the database procedure, the
database returned an SQL error (sql code = 339).
When the database procedure is excecuted, a version validation is
performed. Version validation must be activated explicitly in the SAP
HANA database. To do this, make the following profile setting in the
database:
indexserver.ini sqlscript/Omit_Table_Output_Parameter_Metadata = false
If necessary, version validation can also be deactivated in the SAP
system (though this is not recommended). To do this, set the SAP
profile parameter:
abap/sqlscript_version_validation = off
DBPROC_OUTPUT_PARAMETER_MTDA - dbproc output parameter mtda DBPROC_ILLEGAL_TYPE - dbproc illegal type DBPROC_DYNAMIC_UNKNOWN_KIND - dbproc dynamic unknown kind DBPROC_DYNAMIC_REF_INITIAL - dbproc dynamic ref initial DBPROC_DYNAMIC_NO_TABLE - dbproc dynamic no table DBPROC_DYNAMIC_NO_SCALAR - dbproc dynamic no scalar