cancel
Showing results for 
Search instead for 
Did you mean: 

How to apply SAP Note 2465072 ?

Former Member
0 Kudos

Dear Experts,

I am new in SAP HANA. Kindly request you to give me step by step process to apply SAP Note 2465072 - AMDP query Fails with message "AttributeEngine: this operation is not implemented for this attribute type"

caroleighdeneen
Community Administrator
Community Administrator
0 Kudos

Hi Shachi, Did you try the workaround described in the note you linked in your question? If so, please include details about the results you got and screenshots to help experts further consider and guide.

Former Member
0 Kudos

Dear Caroleigh Deneen,

I am not sure how to implement the workaround described in the Note. I need the guide line on how to use the workaround described in SAP note.

Thanks in advance..

Thank you,

Maruti Magadum

+919834170701

pfefferf
Active Contributor
0 Kudos

The guideline provides already all steps you need to adjust your specific AMDP coding. If you are not able to interpret the code snippets described in the note, please check the SQL Script reference which can be found in the official documentation.

Best Regards,
Florian

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear Frank,

We have not written any code directly. We have created analytical view. While checking the data into analytical view we are getting below error.

Error: SAP DBTech JDBC: [2948]: column store error: search table error: [6941] Attribute engine: this operation is not implemented for this attribute type;index=SLTECC:BKPFen,attribute='BUDAT' (207),Bwpopjoin2Inwards pop 12(SLTECC:BKPFen.BUKRS, .BUKRS, .BUDAT TO BELNR)

For this error SAP is suggesting to workaround and as i am working on it first time and not so familiar with SQL. I am not able to use this workaround.

It will be great if you can help me to use this workaround.

Thanks in advance

Thank you,

Maruti Magadum

+919834170701

architectSAP
Active Contributor
0 Kudos

Hello Shachi,

When you read the SAP Note carefully, you will realise, that SAP are working on a permanent fix for the issue, but there isn't one yet. Therefore they provide workaround information, i.e. you have to change your code to avoid the issue.

Best regards

Frank