Version, the drafts of a lane
Working is where numbers move, Final is what was approved, and everything between is a what-if copy you delete once it has answered its question. Approvals ride the scenario-version pair, which makes version discipline approval discipline.
Note: In Planning, Oracle's budgeting and forecasting module, a Version is a draft within a lane: working numbers, what-if copies, the final. Approvals ride a scenario and version pair. This page is version discipline.
The whole module is mapped on the Planning index.
◆ The three kinds of version, working, what-if, final, and the copy moment.
| Version | Discipline |
|---|---|
| Working | Where numbers change. Approvals ride scenario plus version, per the actions doc, so each approval unit, an entity in a scenario and version, promotes through Budget-Working in the sample world. |
| What-if copies | Cheap to make, expensive to keep. Every kept copy doubles the cells rules touch; the aggregation page counts that cost. |
| Final | Copied once from Working at sign-off, then read-only in practice. The copy moment is the audit boundary: what was approved is what Final holds. |
The discipline that pays: one Working per lane, what-ifs deleted when decided, Final copied exactly once. In the sample world the June forecast's 851.4M lives in Forecast-Working; the 842.0M the variance is measured against lives in Budget-Final, and the accuracy report is version-against-version arithmetic the app never holds still.
The problem: Which number was actually approved becomes a debate three months later.
What we build: Final is snapshotted into your warehouse at sign-off, with the approval record stored beside it.
What you get: The approved number is provable at any later date, with who approved it and when.
- Working
- Where numbers change. What approvals promote.
- what-if
- A copy for a question. Delete it once answered.
- Final
- The approved copy. Made once, then read-only in practice.
- the pair
- Scenario plus version. What an approval unit rides.