Explanation
A data warehouse is a database used for reporting and data analysis. It is a central repository of data which is created by integrating data from multiple disparate sources. Data warehouses store current as well as historical data and are commonly used for creating trending reports for senior management reporting such as annual and quarterly comparisons.

Query environment can be managed by setting query limits (governors) in the Repository (RPD) for particular Application Roles. You should always set query limits for particular application roles rather than for individual users. Steps:
1.Login to Repository using OBIEE Admin Tool
2.Navigate to Manage > Identity
3.Go to Application Role tab, choose the role and double click on it to open.

4. Click on Permissions tab

5. Set the Query Limits. You can limit queries by the number of rows received, by maximum run time, and by restricting to particular time periods. You can also allow or disallow direct database requests or the Populate privilege.

Explanation/Reference:
Dynamic Repository Variables:
You initialize dynamic repository variables in the same way as static variables, but the values are refreshed by data returned from queries. When defining a dynamic repository variable, you will create an initialization block or use a pre-existing one that contains a SQL query. You will also set up a schedule that the Oracle BI Server will follow to execute the query and periodically refresh the value of the variable.
Note: The value of a static repository value is initialized in the Variable dialog box. This value persists, and does not change until an Oracle BI Administrator decides to change it.

The Oracle BI Presentation Services Administration page provides the Manage Map Data link. This link displays the Manage Map Data page, where you can manage the logical and display versions of the data from various physical data sources. This defines the layers that content designers use when creating map views. The data that is available for managing maps and data is stored in Oracle Database as part of MapViewer.
Using this page, you provide:
*(A) Logical names to prevent any existing BI column mappings and map analyses from breaking because of changes to the physical data or to the data source.
*Display names so that the geographic data is meaningful to end users.
Note: Administering Maps Using Administration Pages
For (C) -layers, see 3-7 below.
For (D) -import images, see 11-12 below.
To administer maps using Administration pages:
Click OK when you have finished selecting layers that are appropriate for the subject area with
which you are working.
Click OK when you have finished editing the layer.
You use this tab to associate layers with BI data. If you use the City column in multiple subject
areas, then you must associate it with a layer for each subject area.
The connection that you select for the main map can be different from the connection for the
layers or images.
Click OK when you have finished selecting main maps.
Click OK when you have finished editing the map.
Click OK when you have finished selecting images.
Reference: Oracle Fusion Middleware System Administrator's Guide for Oracle Business
Intelligence Enterprise Edition, Configuring Mapping and Spatial Information