I am going to go through a few important SR’s I have raised in the past few months and majority will have enhancements made by Oracle.
The reason why I’m writing this is because I’m hoping other could avoid these bugs if they come across it.
UNABLE TO SHOW TEXT MEASURES IN OBIEE FROM ESSBASE DATASOURCE
I would like to first give an update from my previous blog on Creating Text Entry in Essbase when I said there’s a bug when trying to read text entries from OBIEE. Recently, Dev team replied to have this fixed in 18.104.22.168 which is coming soon. However, there will be a three restrictions as follows (notice it says 22.214.171.124, this should be 126.96.36.199) (Bug 17515163):
RELEASE NOTES: This trans contains essbase text measure support feature. There are following three restrictions. 1)Essbase text measure member can only be defined on Measure dimension. 2)User need to manually mark the varchar data type in rpd physical layer for text measure. 3)The text measure can be supported only for flat cube model.
I would understand that the text member will need to be defined on a Measure dimension but point 2 and 3 doesn’t really make sense. This means a manual edit will be needed to mark as varchar data type. Moreover, flattening a cube isn’t a best practice. I guess we’ll have to make another suggestion to Oracle.