Você está na página 1de 33

1 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Confidential – Oracle Internal


Oracle Business Analytics
Warehouse Overview
BI Applications Workshop

Fanny Cai
Platform Technology Solutions

2 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Agenda

 After completing this lesson, you should be


able to:
– Describe the contents of the Oracle Business Analytics
Warehouse
– Describe the warehouse tables

3 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
BI Applications Data Model Features

 Dimensional Modeling – Model designed for Analytics and Reporting


 Maintain Aggregation – Store summary data for better performance
 Universal Data Warehouse and Staging
 Multiple Source – Data Source Num and Warehouse Code Standardization
 Transaction data stored in most granular fashion
 History Tracking – Slowly Changing Dimension support

4 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
BI Applications Data Model Features

 Dimension Hierarchy tables – Flatten Tree Hierarchies from OLTP


 Enforce Conforming Dimension Tables
 Multiple Currency Support
 Multiple Calendar Support
 Multiple Tenant Support
 Implemented and optimized for Oracle

5 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Star Schema

 Is a denormalized format that is more effective for query processing


 Is populated by ELT processes
 Is composed of
- One fact table
- A set of dimension tables
- The joins that relate the dimension tables to the fact table

6 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Selected Star Schemas in OBAW

7 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Sample Data Model
W_ORDER_F and W_ORDERITEM_F

8 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Fact Tables

 Are central tables in star schema


 Typically contain numeric measurements
 It has multiple joins to the dimension tables surrounding it
 Transaction data stored in most granular fashion
 Are identified with suffix _F

9 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Types of Fact Tables
 Cycle Lines Facts
 Transactional Facts
– Derived from multiple fact tables,
– Mirror of transactional data from
the source typically store process cycle times
– Sales Order Cycle Lines,
– E.g. Order Lines Fact, Account
Receivable Transactions Purchase Cycle Lines
 State Transition Facts
 Snapshot Facts
– Required for specialized transition
– Snapshot of balances across
time count metrics
– Customer State transitions (#
– E.g. Inventory & Account
Balances, AR and AP aging New, # Inactive, # Dormant
snapshots & Opportunity customers, etc)
Pipeline  Aggregate Facts
– Performance enhancement on key
metrics
10 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Dimension Tables

 A surrogate key (ROW_WID) for each dimension table is generated during


the SIL process.
 ROW_WID is a numeric column, which is used to join to fact tables
 In some cases, the ROW_WID is shared between the dimension and
dimension hierarchy tables
 In every dimension table, the ROW_WID value of zero is reserved for
unspecified
 Are identified with the suffix _D

11 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Dimension Hierarchy Tables
 Tree hierarchies are flattened and stored in
separate tables with level indicators Level 3
(top)
A

 It supports fixed levels of hierarchy


Level 2 B C
 Some prebuilt hierarchy tables:
- W_GEO_REGION_DH Level 1 D E

- W_INDUSTRY_DH
- W_INT_ORG_DH Level 0
(base)
F G

- W_OPTY_DH
- W_ORG_DH Base (Level 0) Others Level 1 Level 2 Top
A … A A A
- W_PERIOD_DH
B … B B A
- W_POSITION_DH
C … C C A
- W_PRODUCT_DH D … D B A

- W_PRODCAT_DH E … E B A
F … D B A
- W_REGN_DH
G … D B A
 Identified with the suffix _DH

12 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Aggregate Tables
Base Fact Table
 Detail level facts are DayTime_ID

summarized Store_ID 5 Million Rows


Customer_ID
 Can dramatically improve Sales_$
query performance
 Identified with the suffix _A
 Use Rolled-up Dimensions
Aggregated Table
- Dimensions created from base Month_ID
dimension tables Region_ID 100,000 Rows
Customer_Category_ID
- Examples:
Sales_$
• W_GEO_D

13 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Aggregate Tables

 OBAW contains pre-built


aggregate tables

14 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Staging Tables

 Normally populate with the incremental data from transactional database


 Always truncate before each load
 Are loaded by the extract (SDE) process
- A single table may be populated by one or more SDE processes during
a ETL run
 Are the source tables for load (SIL) process
 The staging table in BI Apps is independent of source data and closely
resembles the structure of the data warehouse tables
 Universal adapters are available to load the staging tables
 Are identified with the suffix _DS, _FS, _DHS

15 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Other Table Types
 Subset Dimension  Mini-Dimension
– The data are extracted from – The dimension tables that include a
dimension tables using a filter on combination of frequently queried
attributes of the original dimension attributes
table – It improves the query performance
– It contains all columns from the since the fact table can avoid joining
original dimension tables to the big parent dimension tables
– Is used in conjunction with – Some tables exist in BI Apps:
aggregate tables  W_RESPONSE_MD
– BI Apps does not directly deliver  W_AGREE_MD
the Subset dimensions  W_ASSET_MD
– The deploying organization can  W_OPTY_MD
create subset dimension to  W_ORDER_MD
optimize their performance
 W_SRVREQ_MD

16 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Table Types and the Table Naming Convention
– Fact Table (W_XXX_F)  ETL tables
– Dimension Table (W_XXX_D) – General Tables (W_XXX_G), such
– Dimension Hierarchy Table as exchange rate
(W_XXX_DH) – Temporary Tables (W_XXX_TMP)
– Aggregated Fact Table (W_XXX_A) – support Multi-staging
– Staging Tables for each type:  Prefix with OLTP source when
appropriate
 Fact Staging (W_XXX_FS)
 Ex. W_ORA_XXX_TMP
 Dimension Staging (W_XXX_DS)
 Dimension Hierarchy Staging – Tables for support Soft Delete
(W_XXX_DHS)  W_XXX_F_PE
– Mini-Dimension (W_XXX_MD)  W_XXX_F_DEL

17 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Slowly Changing Dimension

 The attributes of a dimension may change overtime, but changes are not
frequent. For example, the marital status of your employees or customers.
 Here are the industry standard ways to handle this problem:
- Type 1: Overwrite the dimension record with the latest values, therefore
losing history
- Type 2: Create a new dimension record for the new values
- Type 3: Create a new field in the dimension table to hold both the
current and the previous values

18 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Slowly Changing Dimension Support

 Slowly changing dimension Type II can be enabled/disabled at a per


dimension group using the parameter TYPE2_FLG
 Every new record in the dimension will have the surrogate key
(ROW_WID) generated in the data warehouse
 The fact table performs range-join to the specific dimension record that is
effective at the time of the transaction
 Out of the box, certain dimensions are enabled for slowly changing
 Only a small set of columns are considered historically significant.
Customization is required to add or remove columns
 Modifying the Type-II tracking logic is the only change that you should
make to shipped logic.

19 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Conforming Dimensions

 A dimension is used to describe the measures in the fact table. A


conformed dimension is a dimension that can be used to describe multiple
facts table and the dimension has exactly the same meaning and context
when being referred from different fact tables
- For example, a customer dimension may be used with the sales fact as
well as with the service fact.
 Conforming dimensions is a way to enable drill across information

20 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Conforming Dimensions
 Fact tables share the same dimension tables
 Conforming across CRM & ERP
 Conforming across Multiple Sources
 Ensure Cross Fact Analysis

Dimension Fact Dimension

Dimension Fact Dimension

21 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Conformed Dimensions
 Time Dimensions
 Customer Dimensions
 Product Dimensions
 Supplier Dimensions
 Internal Organization Dimensions
 Employee Dimensions
 Business Location Dimensions
 Accounts Dimensions
- GL Account
- Cost Center
- Profit Center

22 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Time Dimensions
DIMENSION PHYSICAL TABLES DESCRIPTION

• W_DAY_D, W_MONTH_D, • Store the date and Gregorian calendar


• Date
W_QTR_D, W_YEAR_D hierarchy information

• W_MCAL_DAY_D • Store the fiscal calendar hierarchy


W_MCAL_WEEK_D information
W_MCAL_PERIOD_D
• Fiscal W_MCAL_QTR_D • These dimension tables are mainly
W_MCAL_YEAR_D used in Financial subject area
• Aggregate facts against these tables

• Store the time interval at the


• Hour of the Day • W_TIME_OF_DAY_D
granularity of seconds
• Store the hours of a day
• Time of the Day • W_HOUR_OF_DAY_D
• One record per hour

• Marketing Period
• Period • W_PERIOD_D, W_PERIOD_DH
• Not a conformed dimension today

23 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Account Dimensions

DIMENSION PHYSICAL TABLES DESCRIPTION

• Stores information of all General


Ledger accounts and account
• GL Account • W_GL_ACCOUNT_D
hierarchy such as GL Account
Number, Name, Account Group etc.

• W_PROFIT_CENTER_D • Stores profit center information such


• Profit Center
• W_HIERARCHY_D as Number, Name and Hierarchy etc.

• W_COST_CENTER_D • Stores cost center information such as


• Cost Center
• W_HIERARCHY_D Number, Name and Hierarchy etc

24 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Multiple Currency Support

 Data model stores multiple currencies in each fact


- Document Currency - Actual Transaction Currency
- Local Currency - Local Country / Region Currency
- Global Currency – Up to 5 Corporate Reporting Currencies
 Support for up to 5 exchange rate types
 Global currency code and exchange rate types are configured in BIACM
 Currency conversions are done as part of ETL
 Conversions come from OLTP system (for example Oracle EBS -
GL_DAILY_RATES)

25 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Multiple Calendar Support

 Supports Gregorian and Multiple Fiscal Calendars out of the box


 Configuration to support Multiple Fiscal Calendars depends on user profile
- Requires Initialization block to read user profile
- Dynamically use the appropriate calendar table

26 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Multi-Source Load
 INTEGRATION_ID: Stores the primary key or the unique identifier of
the record from the OLTP
- The transaction sources may use the same ID for identifying
different objects which may share the same target table
 DATASOURCE_NUM_ID: Source the data source from which the
data is extracted.
- All warehouse tables have the DATASOURCE_NUM_ID as part
of the unique user key
- OOTB, it is used in resolving the FK from fact to dimension
- The value is predefined in BIACM when configuring the source
system

27 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Multi-Source Loads
 Segregation and Lineage captured in data model
 Source data keys, comprised of:
+
Integration ID Data Source Num
Part no. Plant id
+ +
‘MT27907b’ ‘NW3’ ‘1’ (Siebel OLTP)
Integration_id for Product dimension from other sources:
Oracle EBS ‘item_id ~ organization_id

28 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Business Process Conformance

 Native source specific transaction types are transformed to


standardized warehouse codes
 Standardized warehouse codes are superset of all
supported sources
 Native source specific transaction types are retained for
source specific analysis

29 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Business Process Conformance

Standard Warehouse Code Oracle PeopleSoft

Invoice Invoice and Payment Schedules Invoice items

CR Memo/DR Memo CR Memo and DR Memo CR Memo and DR Memo items

Payments Cash Receipts etc. Payments/ Deposits

Payment Applications Cash/CR Memo Payment Item Activities


applications/Adjustments

Other All other types of transactions BI/AR: All other types of items

30 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Incremental Extraction and Load
 A variety of strategies used to optimize incremental extracts and loads
 Overall Philosophy – Extract incrementally if possible, else load
incrementally
- Siebel Source
 Use a combination of a date window and rowid comparisons
- Oracle
 Use a date window and last update date for extraction
 Also use dates/record images to control updates on target
- PeopleSoft
 Use a date window and last update dates for extraction
wherever possible

31 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Summary

 In this lesson, you should have learned


how to:
– Describe the contents of the Oracle Business Analytics
Warehouse
– Describe the warehouse tables

32 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal
Q&A

33 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal

Você também pode gostar