Explanation/Reference:
Intelligent Bursting and Output Tool (iBot).
iBot is an utility available in OBIEE which is used for reports scheduling as well as Alerts sent to the required recipients on different web accessible / communication devices.

Explanation/Reference:
Oracle Essbase developers creating planning and budgeting applications have been keenly aware of the advantages and disadvantages of the two different storage types available to them:
* Block storage option (BSO) databases support a wide range of calculations, including forecasts, allocations, and aggregations through procedural calculation scripts. The results of these calculations can be written back to the database, but applications that use BSO storage are limited to about 10 dimensions and member counts in the low hundreds of thousands.
* Aggregate storage option (ASO) databases can support about 20 dimensions and member counts in the millions. ASO databases use multidimensional functions rather than procedural scripts to perform calculations, but the results of queries cannot be stored back in the database, making ASO unsuitable for most financial management applications.

Explanation
Creating Logical Time Dimensions
Compared to modeling an ordinary dimension, the time dimension requires just two additional steps: selecting the Time option in the Logical Dimension dialog, and designating a chronological key for every level of every dimension hierarchy.
Note: Time dimensions and chronological keys. You can identify a dimension as a time dimension. At least one level of a time dimension must have a chronological key. The following is a list of some guidelines you should use when setting up and using time dimensions:
* At least one level of a time dimension must have a chronological key.
* All time series measures using the AGO, TODATE, and PERIODROLLING functions must be on time levels. AGO, TODATE, and PERIODROLLING aggregates are created as derived logical columns.

Explanation/Reference:
There are two types of session variables:
System - A session variable that the Oracle BI Server and Oracle BI Presentation Services use for specific purposes.
System session variables have reserved names that cannot be used for other kinds of variables (such as static or dynamic repository variables and non-system session variables).
Non-system - A system variable that the administrator creates and names. For example, the administrator might create a SalesRegion non-system variable that initializes the name of a user's sales region.
The administrator creates non-system session variables using the Oracle BI Administration Tool.
Note: Session Variables
A session variable is a variable that is initialized at login time for each user. When a user begins a session, the Oracle BI Server creates a new instance of a session variable and initializes it.
There are as many instances of a session variable as there are active sessions on the Oracle BI Server. Each instance of a session variable could be initialized to a different value.

Explanation
Initialization blocks are used to initialize dynamic repository variables, system session variables, and nonsystem session variables.