cancel
Showing results for 
Search instead for 
Did you mean: 

Excel function value() not working for attribute value

Former Member
0 Kudos
151

Hi,

I'm trying to create a local formula in an added query column. It's supposed to multiply columns E and H.

Column E is a custom attribute of 0Material storing the price per litre.

The idea was to have a function like this:   =value(E2) * H2

Unfortunately Analysis doesn't like that and always returns 'NA'. Same result for just a simple 'value(E2)'.

Is it in general possible what I'd like to achieve or am I simply doing something wrong?

Thanks

Stephan

Accepted Solutions (0)

Answers (2)

Answers (2)

reyemsaibot
Active Participant
0 Kudos

Hi,

I just tested it on AO 2.3 and it works fine. I only use =VALUE and had no problems.

BR

Tobias

Former Member
0 Kudos

Hi Tobias,

yes, it definitely works for key figure values. But my reference is a custom attribute of 0Material storing the prices per litre. Even after an update to 2.3 Analysis apparently can't handle this and still returns 'NA'.

Regards

Stephan

reyemsaibot
Active Participant
0 Kudos

Hi,

the difference is I created a column besides the AO Table and you created a AO Column for your formula. I had the same issue here http://scn.sap.com/thread/3918565. I think AO can't work with "real" excel formulas besides * + - /

So you can "fix" it by put your formula next to the AO Table.

BR

Tobias

TammyPowlas
Active Contributor
0 Kudos

Stephan: I'm guess it is because Analysis customers it to be a characteristic and not a measure.  Is the price stored any where else as a numeric key figure?  Then it should work.

Former Member
0 Kudos

Tammy: no, the price is not yet available as a key figure. To have that I would need to enhance the data model&flow and the report.

I'd hoped to make use of the new Analysis excel function features.

Uli_Stoeckl
Participant
0 Kudos

Hi Stephan,

supposed you are using a BEx Query as a data source maybe this will help:

Bye

Uli

Former Member
0 Kudos

Hi Uli,

yes, that would work, of course. But it's again a change I would need to address to our global support team. I'd still like to know if this can be solved locally in the Analysis workbook.

Thanks

Stephan