The Movement dimension, opening to closing

Every balance has a story: what it opened at, what happened, what translation did, what it closed at. This dimension is that story built into the database, the rollforward every disclosure schedule is made of.

Every cell in a consolidation cube answers several questions at once, and each dimension carries one of them. This page is the question of what happened to a number this period. What it is lives on the Account page, how it consolidates on Consolidation, and the whole reference is mapped on the FCCS index.

RuleLoad activity into movement detail under the movements subtotal, and let the system own opening, FX, and closing. Your job is the middle of the story; the engine writes the ends.

Neverload into opening balance, closing balance, or the FX members. The engine computes those, and a load landing there is a double count that surfaces as period one refusing to tie.

◆ The load-bearing members— who owns each part of the story, verified against Oracle's troubleshooting reference.

Member	Who writes it, and what it carries
FCCS_OpeningBalance, under FCCS_Total OpeningBalance	The system's. Computed from the prior period's close, including the retained earnings rollover machinery. When this is wrong, the cause is almost never here, it is the account hierarchy or a member that was moved, the first check on the known-issues list.
FCCS_Mvmts_Subtotal	Yours. Your movement members live under it, additions, disposals, transfers, charges, whatever detail your rollforwards and disclosures need. This is the only region a data load should target.
The members under FCCS_Mvmts_FX_Total	The system's. Translation effects computed during consolidation land here, and from here the CTA story is built. Repurpose one and every FX number downstream inherits the error, silently.
FCCS_ClosingBalance	The system's. Opening plus movements plus FX. The balance the balance sheet shows, and it ties by construction, which is what the dimension is for.

◆ What the dimension buys you— rollforwards for free, the cash flow, and the tie that holds by construction.

Payoff	Why it falls out of the design
Disclosure rollforwards, free	Fixed assets, equity, provisions, debt: the schedules that show opening, activity, closing are a query on this dimension, not a quarterly spreadsheet project. Design the movement members to match the disclosure lines and the schedule writes itself.
The cash flow statement	Built from movement, not balances. The consolidated cash flow on the 10-K page exists because this dimension carries the year's activity by type; without movement detail, cash flow reverts to a derivation project every quarter.
A tie that cannot drift	Closing equals opening plus movements plus FX because the engine computes it that way. The audit question changes from does it tie to which movement carries the difference, a better question with a findable answer.
In the warehouse	dim_movement on the consolidated fact of the owned star we recommend building beside FCCS, on your own cloud, movement members at level zero, and the same overlap warning as the consolidation belt: closing already contains the movements, so summing closing with movement members double counts. Filter to one view of the story at a time.

Member roles verified against Oracle's consolidation troubleshooting reference, July 2026. The companion trap list, opening balances off, FX inaccuracies, lives on known consolidation issues.

Rollforwards still built in spreadsheets?

We map your movement members to your disclosure lines, fix the loads that target the wrong members, and the schedules become queries.

Talk to us

Terms on this page

rollforward: Opening, activity, closing. The story shape of every disclosure schedule.
movement detail: Your members under the movements subtotal. The only load target.
FX members: Where computed translation effects live. System-owned, CTA feeds from here.
ties by construction: Closing is computed from the parts, so the tie cannot drift, only decompose.