The possible ways to solve a fan trap problem are:
Use a combination of aliases and contexts
Avoid the fan trap scenario
Aliases and Contexts
Create an alias for the first table on the many end of the join. Use the Detect Contexts tool to detect and propose a context for the alias table and a context for the original table. Define the SELECT statement for any objects from the aliased table to refer to the aliased table.
Fan Trap Avoidance
You can avoid the scenario in the first place by relating all measure objects in the universe to the same table in the universe structure. Avoid placing a measure on anything other than the most detailed table in a table path, which is usually the last table with the many cardinality attached to it.
In the Motors universe, the Sales Revenue measure is not based on the SALES_TOTAL figure in the SALE table, but on a number of columns from the SALE, SALE_MODEL, and MODEL tables, which are held in the database at the same level of granularity as the number of cars sold. Therefore, no fan trap exists and the correct result is obtained.