IMPORT_ALIGNMENT_MISMATCH SAP ABAP Runtime Error import alignment mismatch

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

IMPORT_ALIGNMENT_MISMATCH ABAP Runtime Error

There is a probably a new version of the program that does not match the dataset. The data may not have been converted. It is also possible that the field type of the imported field has been changed in the ABAP Dictionary. Please see generate program 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.

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.

Error when importing object <runtime parameter>. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

When importing object <runtime parameter>, the structure did not match the structure of the target object. The error occurred in component number <runtime parameter>.
The error is probably due to one of the following:
- The object does actually have a different structure (for example, the next field has a different data type)
- The same sequence of components were exported and imported. However, the fields were combined into different include units. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.