A list of values is used when the end user is prompted to select a value for a specific dimension such as region, for example. Usually, LOVs are assigned with a dimension because they are used in filters. The LOV will generate a query to display the distinct values for the associated dimension.
Tip
We should create LOVs for dimensions with less than 100 distinct values in order to make sure that they are user friendly and easy to navigate.
It is not recommended that you create an LOV for any business object based on the fact table. We should use the dimension table instead. For example, if you have the country code, which is stored in the Customers fact table as a foreign key and in the Country dimension as a primary key, we should then build an LOV on top of the country code stored in the Country dimension table.
It is not recommended that you build an LOV for attributes or measures because it will generate a nonsense LOV, for example, a list of PO box numbers is nonsense while...