ABAP Runtime Errors

SAPSQL_SELECT_ILLEGAL_ORDER SAP ABAP Runtime Error sapsql select illegal order







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


SAPSQL_SELECT_ILLEGAL_ORDER ABAP Runtime Error

When sorting pooled and cluster tables, you should only use ORDER BY PRIMARY KEY at present. 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.

Invalid ORDER-BY condition with SELECT on non-transparent table. table. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

The current ABAP/4 program contains an ABAP/4 Open SQL SELECT statement with an ORDER-BY condition used to read the non-transparent database (pooled or cluster) table <runtime parameter> in sorted order.

With pooled and cluster tables, you can only sort by primary key at present.

In this particular case, the sort sequence requested in the ABAP/4 program differs from the primary key. the ABAP/4 program differs from the primary key. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.