So a little extra task for you: close the thread ... For now it's still This question is Not Answered.

Well ... as Informatica isn't an Oracle product you maybe can get more chances asking on an Informatica forum ... Assuming your question is about Informatica installed as part of OBIA for future needs you have the forum.

If you go in the Administration page of OBIEE and Manage Sessions from there you see the logs. In case you see only the logical SQL you must increase a bit the log level to see the physical query as well, in your case MDX. And also in the nqquery.log file.

Of course would be good if you can give some details (all what @rmoff mention and everything else you can). What I guess is that your source is Essbase, so it's a MDX query, without filter it works fine and with the filter it doesn't ... Can you compare the MDX with and without filter? Does it makes sense? Did you consider…

Hi, You get a message because if you select 31 and all the months there are many months where the 31 doesn't exist (if you select 28 you don't get the warning anymore as all the months have the 28). So there isn't a "checkbox" way to set an agent to run at the end of every month ... Do you really want to run it the last…

As said on the other one you are posting in the OBIEE forum, I guess you have more chances in the Data Quality forum ...

Hi, You are posting in the OBIEE forum, wouldn't it be better to ask in the Data Quality forum?

As Ebin posted your IF in SQL is a CASE WHEN (think at how would you make a SQL query managing that condition). If you want to exclude current day values (in case they exists) adapt what Ebin gave you and change into a BETWEEN <the given formula> AND <your timestamp -1> and you get the same result. I would just say to…

Just in case for the future ... For database questions will be better to ask on one of the Database forums instead of the OBIEE one (it gives you more chances to get the answer and also help others looking for the same thing but looking in the right place for it ...)

Of course +1 what you (Christian) wrote above But I'm also translating what you said in a different language so everybody understand (it's Friday)

To make it short: Yes you have an attribute meaning the data version in your database on the same row as your measures, but in OBIEE you must model it for what it is: an attribute and not a measure. According to Ralph Kimball, [1] in a data warehouse, a degenerate dimension is a dimension key in the fact table that does…

As mine is before yours .... it's you copying me... But I don't mind, not your fault if a bit slow

Hi Dilek, An attribute in a Fact table? It's not supposed to be there, if it's an attribute (not aggregate mesure) it's supposed to be in a dimension. So model your fact as a degenerate dimension, set the content levels etc. as your did for your other dims and things are supposed to work fine.

Hi, In the admin page where you see the sessions in the logs you are supposed to see the LSQL and then the physical SQL (as long as your query doesn't hit the cache). If you don't see it (and it's not the cache) then just increase your log level a bit. It's all about the log level if you don't see the physical query ...

Hi, In the bottom-left part of the "Results" tab you can select your view and click on the duplicate icon. All your settings and formatting on the pivot view will be there in the new duplicated view as well. Not sure what you call "report view" ...

Except if the OP is on 12c as GUID doesn't exist anymore ...

Take it more like a mid-long term advice ... A bit along the lines of : give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime.

You can also simple add a filter to your analysis with your "year" column between YEAR(CURRENT_DATE)-1 AND YEAR(CURRENT_DATE) and use a pivot view .... Actually there are many ways as that's the way OBIEE works: if you have a correct model with a proper time dimension by default your figures are aggregated at the year…

On OBIEE privileges Deny is stronger than Allow, so if Admin is allow and BI Consumer is deny and you are both you have a deny as a result. If you remove BI Consumer (so no deny or allow) then by default they have a deny. If doing that and allowing only Admin and Author your BI Consumer still see it then you have…

Hi, Have a look at time series functions, TODATE and AGO. Actually TODATE isn't needed as you can take the revenu directly at the year level and on 2016 you have the current year revenue and the same using AGO will give you 2015.