Hi Malcolm,
I'd say, that depends... e.g. if you are using aggregations in the view.
But I'd say it's a good workaround if applicable, so I understand instead of passing a filter value to the view in form of an input parameter, you're adding the (to be filtered) field to the projection list and leave the filtering to the consumer, right?
Question is, how will you consume the view? If it's Open SQL you can of course use a default value (in the Open SQL) or the given filter value in case it's given... same holds for IDA ALV, you can pass the default in the ABAP coding.
Cheers,
Jasmin