Hi, What about a customized skin/style ? A patch will not affect it (yes, your DBA is right on that point, don't touch default files).

Hi, would be better if you post in English ... As it's an international forum English is the official language to make sure we all understand each other (more or less )

Try to avoid double posting : java.exe hitting 70% CPU Usage after upgrading to OBIEE 9 It generally produces less answers ... The users reading Business Intelligence are the same reading Business Intelligence Suite Enterprise Edition .

Just don't confuse and mix the ODBC connection required to use the Admintool in "online" mode and the Admintool itself. You need to use the Admintool to add a source to your RPD, and you can do it offline (so creating a RPD locally and you will then upload it on the server) or connect online to the RPD deployed on the…

Hi, You probably need to have a look at a tutorial ... Creating a Repository Using the Oracle BI Administration Tool It's based on a older version of OBIEE but it works in the same way with 12c.

AjeetR wrote:... [nQSError: 14023] None of the fact sources for Activity Local Amount:[DAggr(Fact - Fins - GL Balance.Activity Local Amount by [ Dim - Date Fiscal Calendar.Fiscal Year Wid, Dim - Date Fiscal Calendar.Year] )] are compatible with the detail filter [Fact - Fins - GL Balance.Debit Credit Indicator = 'CREDIT'].…

Same variable for both prompts? Which version of OBIEE? There are ways to make it works, I just prefer to avoid suggesting the most random possible solutions

Hi, Can you be a bit more precise of what actually happen? (maybe with a screenshot)

Hi, Why isn't month part of you time dimension? If you want to do month-to-date analysis the simplest way is to just add the month to the time dimension have model it as an alternate hierarchy in OBIEE (because weeks and months don't have a direct parent-child relation, even if it looks your weeks are strange as a week can…

Good that you have you 2 variables and no error anymore So you can maybe close the thread? For now it's still This question is Not Answered.

From the OBIEE point of view if you have independent connection pool, even if they point to the same DB, it's like different things. So in your case it looks like Subject Area 1 has its own connection pool and so you are supposed to use 500 for your calculation. (I'm not saying the rule you found is right or not) Just also…

To make it short the usage tracking table is setup for insert and not for analysis, so nothing is done on the table to make it fast for analytical needs. So going back to what Christian posted you can move data out of it and create table (one or many) optimized for your analysis needs. It can be real tables or also…

You maybe still have the second init bloc defined? (you forgot to delete it...)

From cache it will load the values of the prompt (all the values) if something is in cache ... Do you maybe set a presentation variable or something?

Challenge the ETL process populating the data: who decided to apply that logic? Is it used somewhere? If the answer is "yes" you have another problem: in your organisation there are 2 different rules for "fiscal date", and this is an issue as the role of OBIEE is to provide a unified enterprise model, so with 2 rules ...…

Hi, Did you set the scope of your prompts? Because what you see is the default behaviour for a prompt with a scope wider than just the page.

So you are saying your time dimension is built in that way (a fiscal year return calendar dates of the previous year) and you want to change that? Well ... the answer you have it: change the time dimension. What is the point in having a fiscal year column if it's not the values you want? It's not OBIEE role to fix data…

Hi, 3174977 wrote:It should retreieve data for 2015 right ? Well, not right ... You must know how you built your time dimension, you must know how you modeled it. So is it right to get 2014 data when selecting a 2015 fiscal year? Yes, just because that's what you created as data and as model. OBIEE will never guess things,…

Hi, Why don't you just merge the 2 queries together and return both variables from a single init block? It's pure SQL, so you can perfectly do it ...

If you read the error OBIEE return you when using your formula you see that TIMESTAMPDIFF is used to get the difference (in your case in days) between 2 dates, so your "-7" isn't really a date ... Maybe you wanted to use TIMESTAMPADD ? With your current parameters it will work, so if you set a filter like "date" >=…