LOAD_TYPE_VERSION_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: R - Error at ABAP Runtime
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 try again for more details about the possible cause of this runtime error and how it could be avoided.
Name of the changed type........: <runtime parameter>
New version of the type.........: <runtime parameter>
Old version of the type.........: <runtime parameter>
New user........................: <runtime parameter> <runtime parameter>
Version of the new user.........: <runtime parameter>
Old user........................: <runtime parameter> <runtime parameter>
Version of the old user.........: <runtime parameter>
Change made to a Dictionary structure while a program was running.
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
The ABAP runtime system has discovered that Dictionary type <runtime parameter> changed
while the transaction was running. Since the old version of the type is
already in use and in the same transaction the new version should be
used, the transaction was interrupted to avoid inconsistencies.
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
LOAD_TYPE_VERSION_MISMATCH - load type version mismatch LOAD_TYPEPOOL_VERSION_MISMATCH - load typepool version mismatch LOAD_TYPEPOOL_NOT_FOUND - load typepool not found LOAD_TRFO_PROGRAM_MISMATCH - load trfo program mismatch LOAD_TEXTPOOL_NO_PXA_MEMORY - load textpool no pxa memory LOAD_TEXTPOOL_NO_MEMORY - load textpool no memory