Create ability to filter aliases at the schema level

[IamtheLaw382]

I think there should be a way to filter the aliases themselves at the schema level (e.g. have FND_LOOKUP only where the Lookup type = WIP_STATUS_TYPE). 

Our company uses Oracle as our ERP.  As we transition more into using "blueprints" (in our cases having lots of straight pulls of Oracle tables instead of bespoke queries on those tables), we've run into an interesting problem.  Oracle leverages a lot of lookups that exist in a very tall table with different lookup types.  We've created a lot of aliases for the different types of looks up leverage join filters to ensure we're only grabbing the meanings from the correct lookup type.  Unfortunately, when one of these aliases is used as a dashboard filter, my end users are inundated with all of the meanings and not just the ones that are actually returned from the join.  I can "solve" this by using an applied filter at the dashboard but it's inelegant.

[mmastropaolo]

Agreed! Furthermore, given that the join itself (to the alias of FND_LOOKUP_VALUES) includes a filter, the results shown in the dashboard filter drop down should also be filtered in the SAME manner.

[StefanWenc]

Seconding the comment regarding join filters having an impact on the filter drop down list values for these kinds of lookup tables - this would be a big help to reduce the amount of available extraneous values presented to the user will tall lookup tables.