#UNAVAILABLE error in measures when using substr() in BO XI 3.1 SP3

[Former Member]

Hi All,

I'm using BO XI 3.1 SP3 with Essabse 11 for OLAP Connection.

I got #UNAVAILABLE value for database delegated measures when using substr() on the dimension.

The aggregation function have to be database delegated because the measure need to be calculated again in aggregation level, such as MOM (month on month) and YOY (year on year) etc.

Can someone help to solve this problem?

Regards

Sofian

[alfons_gonzalez]

Hello,

I am writting this post becauseI have seen that you have succesfullyretrieved data from Esbasse 11 using BO XI R3. Wehn creating the universe connection, Essbase 11 does not appears in my case (only Essbase 9). How have you created the connection?

Thanks

[Former Member]

Hi, Sofian!

We also are trying to work in XI 3.1 SP3 with Essbase as data source.

As I understand there is no support for any essbase mdx/xmla calculations or functions in universe.

In document called "OLAP universes - best practice" are given some examples for SAP BW and MSAS only.

With Essbase OLAP source I can't even make simple measure like Measure1+Measure2, @Select doesn't work too.

All I've reached in this field - creating filters, prompts and LOV-dimensions with restricted number of levels in hierarchy (by filter in Where part.

But the main problem for us is - YTD calculations.

In our Essbase it is dynamic calculated objects, so I need to use Y-T-D function to use it.

Also we want to use Level-based, not Gen-based, ordering dimensions, but I didn't find any information about it

Did you find some examples, documents or reviews in this area?

Now, it seems like there is no any big project BOE+Essbase in the world...

[Former Member]

Hi,

Thanks for the response. I'm using Essbase OLAP for webbi connection, I have tried to use substring in Universe, but i always got parsed failed or invalid expression. Do you know the right MDX syntax for substring in webbi with Essabse OLAP Connection?

Thanks & Regards

Sofian

[Former Member]

Hi Sofian,

Sorry, no I don't, but I can't imagine there is different syntax for this in Webi. I think the issue goes back to either the way the object is defined in the Universe, or before that. Webi syntax is the same Webi syntax for everything. If Webi is having a problem, it is related to the object definition coming into Webi.

Is the field coming into the Universe numeric/string/other?

How is the Universe and Webi showing the object?

You may be able to convert the object within Webi in a variable that you can then do with what you need.

Sorry I can't be of more help!

Thanks

[Former Member]

Hi Wavery,

Thanks for your reply and help, sorry i just back in.

We are using Oracle Hyperion Essbase (OLAP) as connection in the universe, the dimension is coming with string and the measurement is numeric. I have tried some MDX syntax to modify a measure or to create a new measure with a formula, but i always got invalid parsing. I'm still curious, how far hyperion essbase is supported in BO?

Do you have reference or experience between hyperion essbase and BO?

Thanks & Regards

Sofian

[Former Member]

Hi Sofian,

According to the Webi documentation this error is caused when you filter against a smart measure, meaning "database delegated" measure.

Take a look at this entry in Dave Rathbun's blog:

http://www.dagira.com/2008/11/10/designer-xi-3-new-feature-database-delegated-measures/

Can you create the substring object in the Universe instead?

Thanks