The Data Source dimension, who put this here
A number arrives in the cube one of three ways: it was loaded, someone journaled it, or the system computed it. This dimension keeps the three apart forever, and that separation is the audit trail.
Every cell in a consolidation cube answers several questions at once, and each dimension carries one of them. This page is the last of the eight, the question of how a number got here. Who traded it lives on Intercompany, how it consolidates on Consolidation, and the whole reference is mapped on the FCCS index.
◆ The members, by family— the input side, the elimination side, and the subtotal between them.
| Family | What lives there |
|---|---|
| The input side | Loaded data in its own member, journal adjustments in theirs, kept apart so a trial balance can always be split into what the ledger sent and what people changed. Both roll into FCCS_TotalInputAndAdjusted, the everything-we-put-in subtotal the engine reads from. |
| The elimination side | System intercompany entries land in FCCS_Intercompany Eliminations, with the detail readable by entity, account, and partner. User-built elimination rules post to their own members, and FCCS_Total Eliminations subtotals the lot. |
| The ownership entries | Since release 23.04, system ownership adjustments write to FCCS_AcquisitionsDisposals, unless a substitution variable holds them in the old intercompany member. Half-migrated settings split entries across both, the fifth row on the known-issues checklist. |
◆ What the separation buys— three questions this dimension answers in one filter.
| Question | How the dimension answers it |
|---|---|
| Was this loaded or adjusted? | Filter the cell by source. The load member holds what the ledger sent, the journal member holds what people changed, and the difference between a balance and its loaded value is, by definition, the adjustments. No forensic project required. |
| What did the eliminations do? | Open the elimination members for any group number and the entries are there, decomposable by the audit trio. Paired with the Intercompany dimension, every removed amount names its trade. |
| Why did period one change after the upgrade? | When ownership entries moved members in 23.04, applications with a half-set variable found the same entries split across two homes. This dimension is where that shows, and where it gets fixed. |
In the owned warehouse, the star schema we recommend building beside FCCS on your own cloud, mapped here, source lands as its own dimension on the consolidated fact, so adjustment analysis is a filter, journals only, by entity and period, and the input members overlap their subtotal by design, the same never-sum rule as everywhere else in this module. Member names and the 23.04 behavior verified against Oracle's documentation, July 2026.
- source
- How a number got into the cube. Loaded, journaled, or computed.
- FCCS_TotalInputAndAdjusted
- Everything put in, loads plus journals. What the engine consolidates.
- FCCS_Intercompany Eliminations
- Where system elimination entries land, decomposable by the audit trio.
- FCCS_AcquisitionsDisposals
- The home of system ownership entries since 23.04.