Integration Server does not distinguish between tables and views in data sources. You can use them (and user-defined tables) when building OLAP models.
Creating views, tables, user-defined tables, or synonyms can provide security and make the transition from data sources to multidimensional databases easier. By creating views, tables, or user-defined tables, the structure in the data source remain unchanged.
Create views, new tables, or user-defined tables for these takss:
Build an Essbase hierarchy down to a specific level in a recursive table (see Building Essbase Hierarchies from Recursive Tables).
Create aliases in Essbase databases from data stored in multiple columns in source data tables (see Creating Aliases for Dimensions and Members).
Consider creating views, tables, or user-defined tables if source tables meet any of these criteria:
The source tables contain unions. Integration Server does not generate SQL for unions. See Removing Unions.
The source tables have columns you want to transpose to rows. See Transposing Columns and Rows.
The source tables are in a packaged application. You may not know which tables contain the data that you need because the table names provided by the application may not be meaningful in your environment. You may need to ask an application specialist to create the required tables and views (with meaningful names) in a staging area in the target data source. See Deciding to Create Staging Areas.
The source tables are highly normalized. Normalized data is appropriately grouped and does not include redundant data. Consider denormalizing data. See Denormalizing Source Data Tables.