If you’ve used Oracle EBS’s $FLEX$ substitution to inject flexfield values into reports, you’ll find the same idea in Oracle Fusion: OTBI’s Dependent Parameters let one prompt drive another — cleaner, dynamic reports without manual value copying. Great for cascading filters (Country → State → City) and smarter dashboards.
Quick OTBI how-to (practical)
-
In OTBI Analysis, create a parameter (e.g., P_COUNTRY).
-
Create a second parameter (e.g., P_STATE) and set it to depend on P_COUNTRY (Configure the list of values or filter query so it uses the parent parameter).
-
Use parameters in your analysis filters or as presentation variables (
@{pv.P_COUNTRY}, depending on context) so the child parameter value is filtered automatically when parent changes. -
Test the cascade: selecting a country should limit the state list to that country.
Small example (cascading filters)
-
Parent param:
P_COUNTRY(values: India, USA, UK) -
Child param:
P_STATE(L.O.V. query usesWHERE country = @{pv.P_COUNTRY})
Result: selecting India shows only Indian states in P_STATE.
Notes on differences (short)
-
Conceptually same: both let one piece of context drive another.
-
Implementation differs: EBS
$FLEX$is a substitution/token approach in reports/concurrent programs; OTBI uses parameters/presentation variables & built-in dependent-parameter configuration in the analysis UI. -
Use cases overlap: cascading filters, injecting contextual values into queries, making reports dynamic.
