The FCCS data model, eight questions become eight tables

Every dimension page in this reference answered one question about a number. The star is those answers as tables: one fact of periodic amounts, eight dimensions around it, and four gates that keep it tied to the ledger.

The capstone of the FCCS reference. The slice that fills it comes from the consolidated data export, the general pattern lives on the warehouse model, and the whole reference is mapped on the FCCS index.

RuleBuild the star from the export slice, level zero and periodic, and let every to-date, subtotal, and rollup derive in the query. One stored truth, computed views where computation is cheap.

Neverpublish a load the gates have not passed. A star that almost ties answers every question almost correctly, which is worse than not answering.

◆ The star— one fact, eight dimensions, each one a page of this reference.

◆ What each table carries— the column that matters most in each, and why it is there.

Table	The column that matters
dim_entity	Levels of the tree, currency, and the ledger and balancing segment mapping, the row that lets every consolidated number tie back to a ledger somebody closed.
dim_account	The hierarchy as level columns, the rate type, and the intercompany and plug tags, so the warehouse knows why an account translated and eliminated the way it did.
dim_movement	Your detail and the system's opening, FX, and closing members, kept distinct. Rollforwards and the cash flow read from here.
dim_partner	The counterparty. With entity and account it completes the trio that decomposes any elimination, and makes matching a morning query.
dim_source	Loaded, journaled, or computed. The auditor's first question as a filter.
dim_currency	One currency per fact row, entity and each reporting currency as separate rows, never mixed, never summed across.
dim_ownership	Percentage and method per parent and child, with from and to dates. Who owned what, when, as a query, and the NCI rollforward's backbone.
journal_story	Labels, approvers, statuses, and dates, joined to journal amounts on label and period. Amounts with no story is the finding this join exists to catch.

◆ The four gates— what runs before anything publishes, every night.

Gate	What it proves
Rows arrived	Counts against expectation per file. Catches the empty export a dynamic parent produces, the silent failure with no error.
Statuses were OK	Every entity OK for the period before the export ran, from the status check. Stale data never enters.
The trial balance ties	Exported rows summed per entity equal the application's consolidated trial balance, entity by entity. The gate the whole model answers to.
The movement equation holds	Opening plus movements plus FX equals closing, per entity and account. When it fails, the difference names its own movement member.

This star is the owned warehouse this reference has pointed at from every page: built beside FCCS on your own cloud, filled by the export slice, gated nightly, and queryable forever. Our read-only console runs on precisely this model, it computes nothing and writes nothing. Fixed price, about ten days, and you own all of it. Structures verified against Oracle's documentation throughout, July 2026.

Twenty-one pages of theory, one model to own?

We build this star beside your FCCS, wire the four gates, and hand over the code, the model, and the runbook. Yours, on your cloud.

Talk to us

Terms on this page

the star: One fact, eight dimensions. The dictionary as a database.
the gates: Row counts, status, the trial balance tie, the movement equation.
owned: Your cloud, your code, your runbook. The word the whole catalog is about.