SORT_EXTRACT_INDEX_NO_ROLL SAP ABAP Runtime Error sort extract index no roll

SORT_EXTRACT_INDEX_NO_ROLL 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: O - Resource Shortage

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.

SORT_EXTRACT_INDEX_NO_ROLL ABAP Runtime Error

Unless specified otherwise, the system will sort by all fields in field group HEADER.
By specifying other fields in the SORT statement, you can reduce the amount of memory required. Please see not enough roll 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.

The data created with EXTRACT is too large for sorting. Restrict the size of the dataset so that the sort volume is smaller.
Try calling this function with fewer other applications open - or in isolation if possible - so that a smaller amount of main memory is required by these other applications. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.

For sorting, one index entry is built per extract record, in order to make sorting as fast as possible.
The memory required for this is calculated as follows: Number of data records * (4 bytes) When trying to sort the (<runtime parameter>/4) extracted data records, the ABAP processor requested <runtime parameter> bytes of memory. This request could not be complied with. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.