It is a bad business process too. I have implemented BI in places where managers still had the old school mentality, I need all my data or I don't have my finger on the pulse. Here is the bottom line, only so many hours in the day, better then to have exception reporting so the managers can focus on what actually warrants…

Sorry, meant to add, and caught the post button prematurely; - Hi, this is your give away; - W_USERS_D T8402 /* Data Filter */ where ( T152.DATE_KEY = T6929.TIME_ID and T6929.M_ID = '17D06OB02K01' and T6929.OBJ_ID = T8402.OBJ_ID and T6929.FLAG = 'Y' and T8402.USER_ID = upper('cobeng') ) This definitely means that you have…

I think it is your display name you need to alter...

Hi, this is your give away; - W_USERS_D T8402 /* Data Filter */ where ( T152.DATE_KEY = T6929.TIME_ID and T6929.M_ID = '17D06OB02K01' and T6929.OBJ_ID = T8402.OBJ_ID and T6929.FLAG = 'Y' and T8402.USER_ID = upper('cobeng') )

As Michael says, examine the physical sql generated in the two cases, it will give you the best starter to resolve this.

Sounds like row level security - have you checked your rpd to see if any filters are being applied to data for the subject area by groups / users?

Final suggestion would be give yourself a user friendly name, a lot of people ignore people on the forum who are newbies who have machine generated names, as they tend to take and not mark / close questions.

Do you have any prompt levels or master / detail in your page, I have also seen it where one analysis catches those types of filters as a side effect My other suggestion would be (in a development environment) delete the analysis one at a time and repeat the test until you find the one that is driving the behaviour.

Have you tried using presentation variables in conjunction with protect filter to achieve the same ends, then you can explicitly ensure that each report only responds to the prompts that you want it to.

Maybe the pseudonym is appropriate, he briefly haunts a forum and then vanishes leaving only the impression that something un-natural was here... I for one find 100 column reports used as data dumps scary!

Hi, did we answer your question or do you need further explanation on my explanation?

You might want to have a look at this; - https://www.peakindicators.com/blog/testing-the-new-r-functions-on-the-obiee-12c-sampleapp

Can you kindly post the full error and the full current syntax of the filter.

HI, say you have 'YY MMM' as your value, what I am suggesting is that you concatenate the other elements that make up a valid date time format '01' (for DD') and 00:00:00 (for time) and then use explicit conversion to make it a wholly valid datetime. The problem usually comes where midway through the code there are two…

Hi, the most performant way to use OBIEE is to solve the snowflake issue by not building a snowflake with the ETLs that populate the data warehouse. Star is best 10 times out of 10. In a less performant environment, which can be as a consequence of real time requirements requiring 3NF modelling, or can be as a consequence…

You could use some javascript via a text area to achieve though?

Hi, I have experienced this kind of pain with datetime before. My advice will sound ridiculous, but it cured my issue so bare with me. You need to explicitly convert the result to a datetime, ensuring that you concatenate hard coded elements for all of the datetime that are not present in the original. If this is further…

And your YYYY / MM is treat entirely as text, it is not explicitly or implicitly converted to a date to filter a date / datetime column? The fact that you have no error when you remove it ties the error down to this one factor, so that is progress of a kind... Can you add a filter section to your presentation so you can…

What format is your month in, is it just a text field with no date conversion logic imposed on it? Also, if you examine the physical sql that generates the error what do you see? Finally, are you certain that there are no clashes with your prompt name, I once spent ages on a similar error to find out that there was…

This sounds like one to clear your log files, ramp your diagnostics to max, run your analysis with no other users on the system, get your log files, log an SR with My Oracle Support, though review your logs first it may give you a clue. Also look at the physical sql that is invoked for the drill action. I would also check…