IMPORT_OBJECT_DESTROYED 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 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.
The IMPORT dataset has been destroyed.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Unable to import the dataset because it has an unexpected
format. It was
destroyed as a result of direct manipulation of the
IMPORT/EXPORT data by other means (for instance, explicit deletion
of parts of the dataset using SQL instead of DELETE FROM DATABASE).
In this case, the records in the dataset do not appear in the expected order, which is 0,1,2,3... (sequence counter in field SRTF2).
The next record expected here is number <runtime parameter>,
but number <runtime parameter> appears.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
IMPORT_OBJECT_DESTROYED - import object destroyed IMPORT_NAMETAB_WRONG_ID - import nametab wrong id IMPORT_LOGFILE_KEY_TOO_SHORT - import logfile key too short IMPORT_INIT_DECOMPRESS_FAILED - import init decompress failed IMPORT_ILLEGAL_MODULE_COMP - import illegal module comp IMPORT_ILLEGAL_MODE - import illegal mode