The journal export, adjustments with their story
A journal is two things: an amount in the cube, and a story around it, who wrote it, who approved it, when it posted. An export that carries only the amount has lost the half the auditor came for.
Second export page of the FCCS reference, companion to the consolidated data export. The journal lifecycle itself lives on the Journals page, and the whole reference is mapped on the FCCS index.
◆ The two halves, and where each comes from— amounts from the cube, the story from the listing.
| Half | How it exports |
|---|---|
| The amounts | The same export job as the consolidated slice, filtered to the journal input member of the Data Source dimension. Every posted adjustment by entity, account, movement, and period, in rows the warehouse already knows how to receive. Only posted journals exist in the cube; drafts are invisible here by design. |
| The story | The journal listing carries what the cube cannot: label, description, status, who created, who approved, who posted, and when. Export it from the application alongside the data run, same cadence, same dated filenames, and the drafts and rejected journals appear here even though they never touched a number. |
| The join | Label plus scenario, year, and period ties the story to its amounts. A journal in the listing with no rows in the cube is unposted or rejected, working as intended. Rows in the journal input member with no listing entry is the finding, and the join is how it surfaces. |
◆ What the export makes possible— three questions that stop requiring a login.
| Question | Answered by |
|---|---|
| What did people change this period, and why? | Journal rows by entity and account, each carrying its label and description. The adjustment analysis the Journals page calls a filter, running outside the application, any morning. |
| Who approved the big ones? | The story half, sorted by amount, with approver and timestamp. The audit sample selects itself, and the answer arrives without anyone screen-sharing a journal list in a meeting. |
| Did the auto-reversals land? | Each accrual's label paired against its next-period reversal, amounts netting to zero across the boundary. The year-end check from the lifecycle rules, as a query. |
In the owned warehouse, the star schema we recommend building beside FCCS on your own cloud, mapped here, journal amounts land as source-tagged fact rows and the story lands as its own table, joined on label and period, gated by the same row-count and tie-out checks as the main export. Cube storage behavior and journal lifecycle verified against Oracle's documentation, July 2026.
- the two halves
- Amounts in the cube, story in the listing. An audit answer needs both.
- journal input slice
- The Data Source member holding posted adjustment amounts.
- the join
- Label plus scenario, year, and period. Story meets amount here.
- the finding
- Amounts with no story. The join surfaces it before the auditor does.