Domain catalogue Reference data

Calendars and time profiles

Factory, fiscal and planning calendars as governed reference data: working days, periods, weeks and buckets that every plan and report agrees on.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPWorkdayHCM · financeSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN CALENDARS AND TIME PROFILESCalendars and time profilesone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the calendars and time profiles record comes from, how it is assembled, and who reads it. Other systems have their own page.
1 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
2
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today the ERP's factory calendar, the planning tool's weekly buckets and finance's 4-4-5 periods each define the month differently, and the same demand lands in different buckets.

With Lima the calendars are read where they live, matched on calendar id and type + country + year, assembled field by field and published as one golden record per real calendars, with every source key underneath. The facts that fell into a period under each calendar are one click away, because the transactions sit in the same bed.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Calendarid, type (factory, fiscal, planning), country, time zone
wins: reference owner
Days and shiftsworking days, holidays, shifts by site
wins: sites and HR
Periodsfiscal years and periods, planning weeks, 4-4-5 or calendar months
wins: finance and planning
Mappingsday → period per calendar type
wins: generated
How records match

The keys, in order

calendar idtype + country + year

Calendars are dimensions in the bed, so pivots can switch between fiscal periods and planning weeks on the same facts.

Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Fiscalyear → quarter → period → day
Planningyear → planning month → week → day

A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columna date exists
a period number is inside the year's count
Rowevery day of a year belongs to exactly one period per calendar
a holiday belongs to a country or a site
Businessfiscal periods cover the year with no gap and no overlap
sites with production have a factory calendar for the planning horizon
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Demand and supply by dateplanning
Postings by periodGL
working days per perioddemand by week vs by periodsites lacking a calendar

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the facts that fell into a period under each calendar.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Finance edits fiscal calendars; sites edit their factory calendars; planners read. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/calendar/bucket
{
  "calendar": "PLAN-WK",
  "date": "2026-10-01"
}
response
200 OK
{
  "bucket": "2026-W40",
  "fiscal_period": "2026-P10",
  "working_day": true
}

The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.

A planning organisation aligned three calendars in the bed. A demand review that used to argue about which week a promotion belonged to now switches the pivot's time axis and sees both.

illustrative scenario · Calendars and time profiles
Terms on this page

Factory calendarThe working days and shifts of a site.
4-4-5A fiscal pattern of 13-week quarters split into 4, 4 and 5 weeks.
BucketThe time unit a plan or report aggregates to: day, week, period.
Golden recordThe one record for a real calendars, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.

How long to the first golden view?

One working day for the first two sources; 1 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Industrial manufacturing, Consumer goods, High-tech and semiconductor, Life sciences. The industry pages show the domains each starts with.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.