Wrong tool for the need: a dashboard prompt isn’t Google or a search engine.

And could you just write all the requirements you are trying to cover at once? Because it’s now the 3rd version of the requirements, changing things around.

It sounds like a XY problem: you believe you know what you need but your real needs are actually different.

There are workarounds for everything, but you need to express all your needs at once.

This one is fairly simple, not simple to do but simple to cover: you either take the possible workarounds or forget that requirement (because that's really a search engine approach).

Multiple fields for multiple words: that's the only way you can easily deal with multiple words, doesn't matter the order as it will not be something you can check.

If you want a single field, then only multiple words in exact order can work, but users will need to write SQL operators as their search, this means it will work as long as users follow the rules, but they never do.

For your "upper case", "lower case", "accents" etc. management you should consider dealing with that at the data preparation level: because the tool isn't a search engine, you should have a version of the column you want to search on which you do the whole preparation job: you can take the string, turn it all lower case and remove any accent, the database or your ETL has functions doing these things.

Of course users will then need to follow the rules: searching only using lower case words and not writing accents.

In the end the key point is really that the tool isn't a search engine, it's just running queries on a database. You can do a step towards your users by making it easier to query freely, but they also must accept the limits and stick to the defined rules.

Of course you can also cover all your exact needs if you want: implement a search engine indexing your column, query it by javascript, add a fake prompts on top of OBIEE prompts to use your query engine and then set, in a hidden way, the real OBIEE prompt with all the matched occurrences.

Is it possible? Sure, technically doable. Is it worth it? Well, it maybe takes you 1 month of custom coding, that will stop working with the next patch because OBIEE changed and you will need to support it. Not worth it at all, train users instead: it's cheaper.