Analytics Catalog/Workday/Financials/Assets and expenses/Data model
Explore the catalogModulesAssets and expensesThe ledger starThe register
Workday · Financials · Model

Two facts that remember every month

This star stores months, not balances. One row per asset per month makes the register, the run, and every as-of answer a filter or a subtraction, and one row per coded expense line keeps the worktags the ledger never sees.

RuleModel the module as two facts on shared dimensions: one row per asset per month, one row per coded expense line, everything else derived.
Neverstore computed balances as if they were facts. Net book value is a subtraction; store the months and the subtraction stays honest.
fct_asset_monthone row per asset per month fct_expense_lineone row per coded report line dim_assetwhat depreciates, versioned dim_accountthe ledger’s chart dim_worktagthe ledger’s tags dim_employeewho spent, shared with payroll dim_datein service, filed, posted
Two red facts, five teal dimensions, three of them borrowed. The asset rows keep every month; the expense lines keep their worktags.
◆ The two factsthe book and the trips.
FactGrainCarries
fct_asset_monthone row per asset per monthCost, life, monthly charge, depreciation to date, and status, kept for every month since landing.
fct_expense_lineone row per coded report lineAmount, category, traveler, worktags, filed and approval dates, joined to the program bill it substantiates.

The register is the latest asset month; the run is one of its columns; the roll-forward and the as-of page are subtractions between stored months.

◆ Borrowed dimensions, third timethe wave’s habit holds.

dim_account and dim_worktag are the ledger star’s own tables, dim_employee is the workforce modules’ people dimension, and dim_asset is this module’s one contribution, versioned like every who-and-what dimension in the catalog. The supplier and customer stars sit beside this one on the same keys.

Use case
Problem
Asset reporting rebuilds balances from a live register and expense analytics greps card statements, so history rewrites itself and travel never learns its worktags.
What we build
Two facts on shared keys: asset months stored so balances are subtractions, expense lines coded so travel is a grouping, dimensions borrowed instead of copied.
What you get
A module where nothing recomputes history: the register filters, the run divides, the as-of store remembers, and travel finally answers by cost center.
Want the asset book and travel on one star?
We build the two facts on the ledger’s own keys.
Talk to us
Terms on this page
asset month
One stored row per asset per month; the module’s memory.
expense line
One coded line from a filed report.
borrowed dimension
Another star’s table reused, never copied.
versioned
Old values kept with their dates when a row changes.