Laravel is it correct to set up a Model to get data from SQL's views?

Imagine I have my DB structure with tables A, B, C ... N Tables have their relations. Nothing new...

Could it be a good a idea to set up a model that implement a group of methods to retrieve views of my DB (related to a concept e.g. statistics). So this model will not be directly connected to a real table, but it is a bunch of query joins on 2 or more tables...(with subqueries to other tables), or calls to stored func/procedures SQL views...

Or it is more stylish to stick to classical model setup, so have a model for each table and place around these models my (stats) methods ?

Or Maybe in laravel5 there's some functionality/sw-layer to implement this kind of cross tables non standard complex queries?

via Chebli Mohamed