The capital rollforward, current every morning
Capital lives in three states, and the questions live in the movements between them: what went into service, what is aging in flight, what is waiting for approval. The rollforward is those movements as one table, and it should not wait for quarter end to be assembled.
Note: Capital, the asset-planning part of Planning, Oracle's budgeting and forecasting module, tracks assets from request through construction into service. This page is the rollforward, the one table that shows all three states across time.
The whole module is mapped on the Planning index.
◆ The table, column by column, the footed 74.0M, and what each column answers.
The FY26 position in the sample world, footed: 74.0M of capital, which is 41.5M in service plus 27.3M in flight plus 5.2M requested and not yet approved, with 6.8M of new-asset depreciation flowing to the plan P&L.
| Rollforward column | What it answers |
|---|---|
| Opening in service | What was already depreciating when the year began. |
| Placed in service | What moved from in flight during the period, and the date it moved, because the in-service date is when depreciation starts, per the Capital process described in the module reference. |
| In flight, closing | The 27.3M under way, aging visibly: a project in flight for three periods longer than planned is a schedule problem, visible first in the finance numbers. |
| Requested | The 5.2M waiting for approval. Its size against remaining budget is the real capacity conversation. |
| Depreciation | The 6.8M the year's new assets add to the P&L, tying this report to the expense plan. |
The comparison that keeps it honest lives on the objects page: plan rows beside the fixed-asset register, on the shared entity tree, so the plan's in-service list reconciles to assets that exist.
The problem: Asset states live on separate forms, and the quarter-end rollforward is assembled by hand.
What we build: The three states, requested, in flight, in service, land nightly as one table with dates, on the shared entity tree.
What you get: The 74.0M rollforward is a standing view, current every morning, with depreciation flowing from in-service dates.
- in-service date
- When depreciation starts. The date that matters most.
- in-flight aging
- Time in construction against plan. A schedule signal.
- requested
- The 5.2M waiting. Its size against budget is the capacity talk.
- the register check
- Plan in-service rows reconciled to real assets.