The View dimension, periodic to year to date
The same account, the same month, gives two honest answers: what happened this period, and where the year stands so far. This dimension holds both, and one storage decision behind it decides whether your grids open in seconds or minutes.
Every cell in a consolidation cube answers several questions at once, and each dimension carries one of them. This page is the question of over what span a number is read, this month alone or the year so far. What happened inside the period lives on Movement, and the whole reference is mapped on the FCCS index.
◆ The three readings— periodic, quarter to date, year to date, and which numbers live naturally in each.
| Member | What it reads, and what belongs there |
|---|---|
| FCCS_Periodic | The period alone, this month's activity with the prior months stripped away. Flows read naturally here: revenue, expenses, the month's movements. The income statement's home view. |
| FCCS_QTD | The quarter so far, the periods of the quarter accumulated. The reading an earnings release is written in, and the one quarter-end review meetings argue about. |
| FCCS_YTD | The year so far, an as-of reading. Balances are inherently as-of, so the balance sheet reads naturally here, and a year-to-date income statement is the year's story in one column. |
The pairing is the insight: flows are periodic creatures, balances are as-of creatures, and the dimension lets each be read either way on purpose. Read the wrong way by accident and the number is still correct, just not the answer to the question that was asked, which is the most expensive kind of correct.
◆ The storage decision— who pays for the to-date views, the symptom of each choice, and the middle path.
| Choice | The tradeoff |
|---|---|
| Store the views | Quarter and year to date written at consolidation time. Consolidation runs longer and the application grows, and every retrieve afterwards is a read, not a computation. Heavy reporting months earn this. |
| Compute at retrieve | Rule members assemble the to-date reading every time someone opens a grid. The application stays lean, consolidation stays fast, and the cost lands on the person waiting for the spreadsheet. The tell: grids that are quick on periodic and crawl on year to date. |
| The middle path | Recalculate stored views only for the entities that changed, so a late adjustment to one country does not reprice the whole application. The practical setting for most groups once the entity count grows. |
The slow-grid diagnosis method, the Activity Report and the five causes, lives on Smart View performance, and computed to-date views are cause five. In the owned warehouse, the star schema we recommend building beside FCCS on your own cloud, mapped here, land periodic at level zero and derive the to-date readings in the query, one stored view of the truth, the accumulations computed where computation is cheap, and never sum across views, they contain each other by design. Member behavior verified against Oracle's documentation, July 2026.
- view
- The span a number is read over. Same cell, three readings.
- as-of reading
- Where things stand, not what just happened. The balance sheet's nature.
- stored views
- To-date readings written at consolidation. Size and time for speed.
- rule members
- The computed alternative, assembled at retrieve. Lean, and slower to open.