Understanding Oracle Business Analytics Warehouse Exceptions
Using Oracle Business Analytics Warehouse Exception Reports
E.1.3 Products Without a Cost List
During the ETL process, the costs of the products are calculated based on the Cost List
table. If the cost lists are not defined correctly, the cost of the products cannot be
calculated correctly in the Oracle Business Analytics Warehouse. This exception
mapping queries the product table and looks for a minimum of one cost list to be
defined. The products with no cost list definition are flagged as exceptions.
E.1.4 Exchange Rate Exceptions
The Oracle Business Analytics Warehouse supports transactions in many different
currencies. Oracle Business Intelligence converts all currencies in the Oracle Business
Analytics Warehouse to a single currency for analysis purposes. The ETL Base
Exchange Currency parameter in System Preferences, indicates the currency to which
all the financial amounts will be converted. The Exchange rates are derived from the
Exchange Rate tables in the Oracle Business Analytics Warehouse. If the currency
exchange rates do not change for a period of 30 days, then Oracle Business Intelligence
flags it as an exception.
If there are time period gaps in the exchange rate data, the ETL process defaults to the
most recent recorded exchange rate. If the actual exchange rate is significantly more or
less favorable than what is recorded in the database, the outdated exchange rate
distorts the true value of currency amounts in the Oracle Business Analytics
E.1.5 Invalid Hierarchy Exceptions
Accounts, divisions, products, and opportunities can all have hierarchical
relationships. These entities are denormalized within the Oracle Business Analytics
Warehouse database to a fixed number of levels. Oracle Business Intelligence supports
up to ten hierarchies levels in the Oracle Business Analytics Warehouse. If the depth of
hierarchies extends beyond this number, results become inconsistent or incomplete.
E.1.6 Circular Hierarchy Exceptions
Circular Hierarchies arise when the parent-child relationship has circular references.
for an example.
Oracle Business Intelligence flags exceptions for two levels. Circular references over
two hierarchies are not flagged. See
for an example.
Exchange rates are derived from records that are of type 'Daily'
in the Oracle Business Analytics Warehouse. If any other types have
been defined, they are not handled without some customization.
Circular Hierarchy Example 1
Circular Hierarchy Example 2