User Views are not a logical modeling concept. They are included to allow analysts to document logical views of the data which can be used by the physical database.
The aim of a user view is to provide access to a file in a sequence other than the primary key and logical views created as a result of relationships. User views will generate logical views when a database build is performed on an entity.
For example, a logical view sequenced by Customer Name will not ordinarily be created for the Customer entity, as there are no relationships involving Customer Name and it is not part of the key of Customer. However, an end user may wish to view Customer information in Customer Name sequence. A user view can be created to support this requirement.
User views can only be specified for entities which become physical files when they are built. For example, Data and Variant objects may have user views. User views become logical files in the repository when the entity is built. You may add user views as a means of creating logical files which may be needed for reporting or other operations.
This is described in: