Table Organization in OBAW (Oracle Business Analytics Warehouse)

OBAW Table Format: Prefix + _ + Table_Name + _ + Suffix

Prefix Values

Prefix Descriptions

W_

Warehouse Table

WS

Staging Tables for Usage Accelerator

Suffix Values

Suffix Descriptions

_A

Aggregate

_D

Dimension

_DS

Staging for dimension

_DH

Dimension Hierarchy

_DHL

Dimension Helper Table

_DHLS

Staging for Dimension Helper

_F

Fact

_FS

Staging for Fact

_G, _GS, _S

Internal Table

_H

Helper table

_M

Map dimension

_MD

Mini dimension

_UD

Unbounded dimension

_TMP

Pre staging temporary table

Descriptions:
Aggregate tables (_A)

Contain summed (aggregated) data.

Dimension tables (_D)

Star analysis dimensions.

Staging tables for Dimension (_DS)

Tables used to hold dimension information that have
not been through the final ETL transformations.

Staging tables for Usage Accelerator (WS_)

transformations.
Dimension Hierarchy tables (_DH)
structure.
Dimension Helper tables (_DHL)
joining dimension tables.

Tables containing the necessary columns for the ETL

Tables that store the dimensions hierarchical

Tables that store M:M relationships between two

Staging tables for Dimension Helper (_DHLS)

between two joining dimension tables.
Fact tables (_F)

Staging tables for storing M:M relationships

Contain the metrics being analyzed by dimensions.

Fact Staging tables (_FS)

Staging tables used to hold the metrics being analyzed
by dimensions that have not been through the final ETL transformations.
Internal tables (_G, _GS, _S)
Internal tables are used primarily by ETL mappings for
data transformation and controlling ETL runs. Not even administered through DAC.
Helper tables (_H)

Helper tables are inserted between the fact and

dimension tables to support a many-to-many (M:M) relationship between fact and dimension
records.
Map dimension tables (_M)
the external data ID and the internal ID.

Tables that store cross-referencing mappings between

Mini dimension tables (_MD)

Include combinations of the most queried attributes of
their parent dimensions. The database joins these small tables to the fact tables.
Primary extract tables (_PE)
Tables that are used to support the soft delete feature.
The table includes all the primary key columns (integration ID column) from the source system.
When a delete event happens, the full extract from the source compares the data previously
extracted in the primary extract table to determine if a physical deletion was done in the
transactional database. The soft delete feature is disabled by default. Therefore, the primary
extract tables are not populated until you enable the soft delete feature.
Unbounded dimension tables
Tables containing information that is not bounded in
transactional database data but should be treated as bounded data in the OBAW.

A fact table in the Oracle Business Analytics Warehouse has a surrogate key only if the records in
the fact table need to be updated or if the fact table has an aggregate table on top of it.

Importance of ROW_WID column

Dimension Class Tables are physical tables that store multiple logical entities that have similar
attributes.

Unique numeric key generated as part of dimension load process.

Used to join dimension tables to any fact/other tables.

ROW_WID value of zero is always reserved for Unspecified.

Classic example is W_XACT_TYPE_D which is a single physical table representing a dimension in

OBAW that houses all logical entities like sales order types, sales invoice types, purchase order
types etc.

Mini Dimension Tables is a smaller subset of dimension tables based on frequency of usage to
speed up the query performance. Mini Dimensions can be views/materialized views on top of
large dimensions or Dimension Class tables depending on refresh schedules of the parent
dimensions. Example: W_RESPONSE_D dimension has W_RESPONSE_MD, W_AGREE_MD,
W_ASSET_MD, W_OPTY_MD etc.

Types of hierarchical tables in OBAW are structured hierarchy and parent-child hierarchy tables.
While the former has defined number of levels, the later does not.

Name
W_PARAM_G
W_DUAL_G
W_ETL_RUN_S

W_COSTLST_G
W_EXCH_RATE_G
W_LOV_G

W_LST_OF_VAL_G

W_LOV_EXCPT_G

W_UOM_CONVERSION_G

S_ETL_COSTLST

S_ETL_EXCH_RATE

Purpose
Location
Stores parameters and defaults Data warehouse
that are used in ETL processes.
Used to generate records for
Data warehouse
the Day dimension.
Stores a record for every ETL run Data warehouse
with a status of running when
the ETL is running and
Completed when the ETL
finishes successfully.
Stores cost lists.
Data warehouse
Stores exchange rates.
Data warehouse
Stores lists of values in a way
Data warehouse
that translations can be done
effectively using SQL.
Stores the list of values. A
Data warehouse
temporary table that is built
during every ETL run and used
to populate W_LOV_D.
Stores the list of values for the Data warehouse
LOV types in whichthe ETL
process finds exceptions.
Stores a list of From and To
Data warehouse
UOM codes and their
conversion rates.
Mirror table of W_COST_LST_G. Transactional database
Used by real-time Analytics
processes.
Mirror table of W_COST_LST_G. Transactional database
Used by real-timeAnalytics

S_ETL_CTRYREGN

S_ETL_CURR_RUN

S_ETL_RUN
S_ETL_TIME_DAY

S_ETL_DAY
S_ETL_ERRHLP

S_ETL_ERRLOG
S_ETL_INDUS_VER

S_ETL_LOV
S_ETL_PARAM

S_ETL_PRD_ATTR
S_ETL_PRD_REL

processes.
Mirror table of
Transactional database
W_EXCH_RATE_G. Used byrealtime Analytics processes.
Stores the last ETL run date for Transactional database
which forecasts wereextracted
and the current ETL run date
when forecasts are being
extracted.
Mirror table of W_ETL_RUN_S. Transactional database
A seeded table. The date from Transactional database
this table is extractedand loaded
into W_TIME_DAY_D. Also used
by real-time Analytics processes.
Mirror table of W_DAY_D. Used Transactional database
by real-time Analytics processes.
A seeded table. Stores the error Transactional database
messages displayed in exception
reports.
Stores exceptions.
Transactional database
A seeded table. Stores the
Transactional database
vertical for every SIC industry
code. This table is used to load
W_INDUSTRY_D and also used
in real-time Analytics processes.
Mirror table of W_LOV_D. Used Transactional database
by real-time Analytics processes.
Mirror table of W_PARAM_G. Transactional database
Used to extract and convert
exchange rates to the data
warehouses currency.
Stores all possible attributes for Transactional database
a given product.
Stores class inheritance of a
Transactional database
product.

Column Format Descriptions (Prefix+ _ + Column_Name + _ + Suffix)

Prefix/Suffix
Description
In Table Types
W_
Domain value columns
_D
_CD
Code Field
_D, _DS, _FS, _G, _GS
_DT
Date Field
_D, _DS, _FS, _G, _DHL, _DHLS
_I
Language Independent Code.
_D, _MD
_ID
_ID columns are used in _FS
_FS
tables. They correspondto the

_FLG
_WID

_NAME

_DESC

_WID columns of the

corresponding _F table.
Indicator or Flag.

_D, _DHL, _DS, _FS, _F,

_G,_DHLS
Identifier generated by Oracle BI _F, _A, _DHL
linking dimension and fact
tables, except for ROW_WID.
Name corresponding to the
_D, _F, _A
code column (columns ending
with _CODE)
Long Description corresponding _D, _F, _A
to the code column (columns
ending with _CODE)