Dump in Native SQL join statement

[Former Member]

Hello,

When the same is used in the ecc 5.0 it was working good but when this code is executed in ecc 6.0 then it is throwing dump.

This is the code :

EXEC SQL PERFORMING MAIN_ITAB_SUB5_APPEND.

SELECT A.WERKS, A.MATNR, B.MAKTX, SUM(A.LBLAB), C.MEINS

INTO :ZIT_WEBIF_SUB5

FROM MSLB A, MAKT B, MARA C

WHERE A.MANDT = :SY-MANDT

AND A.LIFNR = :P_I_LIFNR

AND A.MANDT = B.MANDT

AND A.MATNR = B.MATNR

AND B.SPRAS = sy-langu

AND A.MANDT = C.MANDT

AND A.MATNR = C.MATNR

GROUP BY A.WERKS, A.MATNR, B.MAKTX, C.MEINS

ENDEXEC.

The same native sql is converted into open SQL and it is working fine. Since there is no inconsistancy in the Database. Also when i remove the joins it is working fine.

Dump error :

One of the columns addressed in a table or view does not exist in the database.

table) exists in the ABAP/4 Dictionary, but not in the database.

The error 904 occurred in the current database connection "DEFAULT".

Any suggestions would be apprecaitaed.

Regards,

Kittu

[Former Member]

Hi

Dump error : 
One of the columns addressed in a table or view does not exist in the database.
table) exists in the ABAP/4 Dictionary, but not in the database.

I think it is itself saying the answer , u have given some field in native SQL SELECT where that field is not there check ur TABLES in Native SQL for fields details, which fields it contain.

Regards

Sachin

[Former Member]

Hello,

Thank you for your quick response!

I had checked it and in debuggiung the open SQL is working fine and there are no inconsistency.

It is working fine in ECC 5.0 and it is working fine with single table. It is throwing dump only when join is used.

If you have any example of native sql with join statement then please provide it.

It would be very helpful...

Thanks & Regards,

Kittu

[Former Member]

HI,

Thank you for your quick response and time.

I am closing this thread as there was no response available and

I think insted of Native SQL I need to use only SQL here so that issue will be fixed...

Regards,

Kittu

[Former Member]

Hi Kittu,

I think you have taken a right decision to use open sql as it is always better to use.

Thanks.