Are you just validating a an existing indicator? or trying to build a new one?

ok ... so you don't want an INTERNS table (strictly speaking) ... you could find out who was hired as an intern first and put their ID in a table ... then skip the fact modeling and put a lookup in the employee dimension (in RPD) to set a flag indicating it ... then at least it's reusable. With the Cloud offering I'm not…

It's not a script ... it's a technique to capture data changes and report facts at the historical view of the dimensional components. CREATE AS SELECT <- how are you going to refresh it regularly? Your issue is solved with more than just a simple DDL statement. Again, I come back to use of information drives data design.

I've counseled you on a type-2 SCD ... what you've got there is nowhere near that. Where are you executing that SQL? DB? RPD (o-view)? The 'ask' is: Which employees were initially hired as interns? The SQL you've got doesn't do that - which OBIA are you running? the _F and _WID naming is giving it away ... if so, and you…

in the type-2 slowly changing dimension ... do it at ETL time ... then you have it set once (even if the current record is now 10-yrs old)

Does the alias have a trailing space? Just looking at obvious points where the lookup will fail ...

Owen - are you running the OBIA Procure and Spend Analytics App? Sourced from EBS, PSoft, etc?

with SCD-2 you can have 'views' of the historical data ... DW_EMPLOYEE physical table can be represented with DW_EMPLOYEE_LST (where current_flg = 'Y') <-- current representation DW_EMPLOYEE_FST (where rank() on eff_dt = 1) <-- how the employee looked on day 1 You'll need a surrogate SCD id (this then is the ID that is…

Use of information drives data design ... if the employee currently is NOT an intern, then you should have a slowly changing dimension that has the history of when they were. This means you need a history of the employee ID, type/status, and effective date. Furthermore the status/type of an employee is not the same data as…

Sounds like he might be asking for support of a pre-built cloud offering ...

Apparently the analysis changes with every year ... which I seriously question that approach - if the business is always in a state of flux, howdo they know they are progressing. BI should be directly tied to corporate strategy -- operationally, tactically, and strategically. Much of what I get asked for falls into the…

Sounds like a defect in your presentation design ... as I see it, you need a distinct catalog location for each year AND a common catalog location. Then you need two distinct dashboards each pulling the parts from their own folders and parts from the common folder. Also sounds like you are missing the ability for each part…

You can't disable them as you describe ... you can however in your query choose to ignore the dates if a user picks some based on the Open/Closed

why did you replace your original question with this new one? now people don't have a correct answer tied to the original question. This is a forum - searchable for help. You need to make a new post for a new question.

Consult the documentation: https://docs.oracle.com/middleware/1221/biee/BIESG/answersconfigset.htm#BIESG3734 section 17.4

There is an option in the parameters to refresh others based on the parameter ... have you tried that?

A few of us speak french here ... we can translate your explanation back to English for the greater community's benefit ...

You aren't using Oracle SQL Syntax ... || (dbl pipe) for concat: select * from MYTABLE WHERE FIELD1 LIKE ('%' || :P_FIELD1 || '%') select * from MYTABLE WHERE TO_CHAR(FIELD1) LIKE ('%' || :P_FIELD1 || '%')

does UPPER(TABLENAME.Subject) LIKE (:Subject) work when you do it in SQL dev (nope it doesn't ...) you are missing basic SQL syntax try UPPER(TABLENAME.Subject) LIKE UPPER('%' || :Subject || '%') <- contains search try UPPER(trim(TABLENAME.Subject)) LIKE UPPER(:Subject || '%') <- begins-with search try…

Short answer is that OSSM doesn't store data, but rather leverages the BI Foundation's Semantic layer ... but with more clarity from you we might be able to give you a better answer - or guide you to a solution that meets the need. If you are asking about a Scorecard Object ... that is a collection of files in the catalog…