SAPSQL_JOIN_OJ_1SIDED 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.
A dynamically specified FROM clause has an unexpected format.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field <runtime parameter>. The
field <runtime parameter> contains a comparison of two different OUTER tables in an ON
condition. In Open SQL, such a comparison is illegal.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_JOIN_OJ_1SIDED - sapsql join oj 1sided SAPSQL_JOIN_NO_SELECT - sapsql join no select SAPSQL_JOIN_LEFT_DEEP - sapsql join left deep SAPSQL_JOIN_ILLEGAL_TABLE_TYPE - sapsql join illegal table type SAPSQL_ITAB_CANT_SCAN - sapsql itab cant scan SAPSQL_IN_ITAB_ILL_STRUCTURE - sapsql in itab ill structure