Complex Parameter Validation and Defaulting

You must use the Advanced Required Parameters feature, which accepts a logical expression. For your ‘either-or’ requirement, the expression would be entered as: `:Customer_Name is not null or :Account_Number is not null`. This logic is evaluated at run-time, and if the condition is not met, an error message is displayed.

Parameters are referenced by their names (in the installed base language, usually US), prefixed with a colon (`:`). Any spaces or other non-word characters in the name must be replaced with a single underscore.

Yes, you can specify a custom message text directly in the Advanced Required Parameters field. Otherwise, the system defaults to FND message `XXEN_REPORT_INSUFFICIENT_PARAM` or `XXEN_REPORT_ONE_PARAM_REQUIRED` if it detects that at least one parameter entry is required.

You define dependencies using the syntax `:$flex$.parameter_or_lov_name`. For example, to inherit the Operating Unit value and add ‘suppliers’, your default value SQL could be: `select :$flex$.operating_unit|| suppliers from dual`. This dependency syntax is used in both LOV queries and default values.