I am creating a view where a main table Initiatives (init_id, topic_cd, sector_cd) is linked to 2 children table init_topic (init_id, topic_id, topic_nm) and init_sector (init_id, sector_id, sector_nm)

Now, when I create a report that only takes init_id, topic_cd ad topic_nm, the SQL that is fired still include the table init_sector which is not there in the report.
This then creates duplicates, unless if I use the distinct or distinct count option.

Is there a way to build the view of set up yellowing so that tables that are not called in the front end are not triggered in the SQL