English version
Moving a report query into a view can improve organization and reuse. It does not, by itself, make the query faster.
Correction to my original post: I described a special 'View-Based Rendering Optimization', a fixed execution plan, and a possible 40% improvement. I could not substantiate those claims in Oracle's documentation, so they should not be treated as APEX guarantees.
A normal view is a query definition
Oracle may merge a view into the surrounding query or apply other optimizer transformations. The resulting work depends on the SQL, statistics, data, predicates, indexes, and optimizer decisions—not simply whether the region names a view. See Oracle's explanation of view merging.
A view is still valuable when it gives a stable, understandable interface to repeated joins or business definitions. Keep application filters selective and inspect the actual plan.
A materialized view is a different decision
A materialized view stores results. That can reduce repeated aggregation work, but creates questions about freshness, storage, refresh cost, and eligibility for fast refresh. REFRESH FAST ON COMMIT is not a universal setting that works for every aggregate query.
Compare equivalent workloads
Measure the same report with the same binds and data volume. Capture elapsed time and the actual execution plan. Include refresh overhead when assessing materialized data.
Use a view for a clearer interface. Choose a materialized view when a measured workload and an acceptable freshness policy justify it.
