EXTRACT_FCLOSE_FAILED 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: I - Internal Kernel 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.
If the cause of the error indicates that there is not sufficient disk
space for the extract, you need to make sure that the file system
containing directory <runtime parameter> (the extract uses this to create its help
files) has enough space, or choose a different directory using profile
parameter DIR_EXTRACT.
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 while closing the temporary extract file.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Temporary help file <runtime parameter>, which contains the extract dataset, could not
be closed (file size: <runtime parameter> bytes).
Error number: <runtime parameter>
Error text: <runtime parameter>
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
EXTRACT_FCLOSE_FAILED - extract fclose failed EXTRACT_BUFFER_NO_ROLL - extract buffer no roll EXTRACT_AFTER_SORT/LOOP - extract after sort-fs-loop EXSQL_WRONG_TYPE_FOR_LOCATOR - exsql wrong type for locator EXSQL_WRONG_TYPE_FOR_LOB - exsql wrong type for lob EXSQL_VARIABLE_TOO_BIG - exsql variable too big