Chapter 7. Accounting
서울시립대학교인공지능연구실
G201549028조찬연
https://github.com/lovebube/1/31
The Data Warehouse Toolkit
2/31
Contents
ü What is accounting?ü Four-Step Dimensional Design Processü General Ledger
ü Chart of accountsü Budget process
ü Hierarchyü Consolidated fact table
What is accounting?
3/31
Accounting/ə|kaʊntɪŋ/ noun.
Accounting is the activity of keeping detailedrecords of the amounts of money a business or
person receives and spends.
4/31
Four-Step Dimensional Design Process
Select the Business Process
Declare the Grain
Identify the Dimensions
Identify the Facts
Case Study and Bus Matrix
5/31
ü Early decision support solutions focused on the analysis of financial data.ü Because finance was an early adopter of technology.
ü Managers need the ability to analyze performance trends, variances, and anomalies with relative speed and minimal effort.
Case Study
Case Study and Bus Matrix
6/31
Bus Matrix
Bus matrix rows for accounting process
Business Process
Dimension
General Ledger Periodic Snapshot
7/31
Ledger/ledʒər/ noun.
A ledger is a book in which a company ororganization writes down the amounts of
money it spends and receives.
General Ledger Periodic Snapshot
8/31
The general ledger consists of journal entries.
Chart of Accounts
9/31
ü The cornerstone of the general ledger.ü Series of identifier.
ü The first set of digits may identify the account, account type.ü So, you’d include the account type as a dimension attribute rather than
forcing users to filter on the first digit of the account number.
Chart of Accounts
10/31
Periodic Close
11/31
ü At the end of each period, the finance organization is responsible for finalizing the financial results.ü It often produces countless reports and responds to countless
variations on the same questions each month.ü This chapter focuses on easily analyzing the closed financial results, rather
than facilitating the close.
General ledger periodic snapshot
12/31
Year-to-Date Facts
13/31
ü It would be helpful to store quarter-to-date or year-to-date additive totals on each fact row so they don’t need to calculate them.ü To-date column produce nonsensical, overstated results.
General Ledger Journal Transactions
14/31
ü Analysts want to look at the detailed transactions to sort through the issue. ü You can complement the periodic snapshot with a detailed journal entry
transaction schema.
General Ledger Journal Transactions
15/31
General ledger journal entry transactions.
General Ledger Journal Transactions
16/31
Drilling Down Through a Multilevel Hierarchy
17/31
ü Division < Department < Enterpriseü To model this hierarchy is by introducing the parent snapshot’s fact
table surrogate key in the fact table.ü So, you can define a parent/child relationship between rows.
Drilling Down Through a Multilevel Hierarchy
18/31
Design for drilling down through multiple ledgers.
Financial Statements
19/31
ü One of the primary functions of a general ledger system is to produce the organization’s official financial reports.ü Such as, the balance sheet and income statement.ü So, DW teams create complementary aggregated data that provides
simplified access to report information.
Budgeting Process
20/31
ü Budgeting is seldom simply a once-per-year event. And series of event.ü Reflecting changes in business conditions or the realities of actual
spending versus the original budget.ü As the year unfolds, commitments to spend the budgeted monies are
made.
Budgeting Process
21/31
Budgeting Process
22/31
Budget schema
Ragged Variable Depth Hierarchies
23/31
Organization rollup structure Organization dimension joined to fact table
The classic way to represent parent/child tree
24/31
Classic parent/child recursive design
But, SQL did not provide a way to evaluate these recursive pointers.
Organization map bridge table
25/31
Lower portion is omittedBuild a special kind of bridge table that is independent from
the primary dimension table
Joining organization map bridge table to fact table
26/31
Joining organization map bridge table to fact table
Modifying Ragged Hierarchies
27/31
The organization map bridge table can easily be modified
Alternative Ragged Hierarchy Modeling Approaches
28/31
There is no bridge table. But there are two disadvantages
ü The definition of the hierarchy cannot easily be replaced
ü These schemes are vulnerable to a relabeling disaster in a large part of the tree due to a small change
Path-string approach
Modified preordered tree traversal approach
29/31
Each node have the names Left and Right
ü Then all the nodes in tree can be found with the constraint
ü Left and right differ by 1, meaning there aren’t any children
Advantages of the Bridge Table Approach
30/31
ü Alternative rollup structures to be selected at query time.ü Time varying ragged hierarchies.ü Limited impact when the tree structure is changed.
Consolidated Fact Tables
31/31
Combine metrics from multiple business process.
ü Consolidated fact table can be useful, both in terms of performance and usability.
ü “Least common denominator”