In this article
In this article
SAP can tell you how much a capital project was approved for. It can tell you what’s committed, what’s been spent, and what’s left. It can tell you the cost center, the WBS element, the asset.
What it can’t tell you is whether the project should have been approved at all, or whether the promise it was approved on ever came true.
That reasoning, the CapEx business case behind the decision, is the most important information in your entire capital process. And in most SAP-run organizations, it has no system of record. It’s homeless.
The Capital Project that was Approved to Fail
You know the scene. A capital project lands over budget and behind schedule. The review zeroes in on delivery. The project manager carries the blame. The organization decides it needs tighter delivery controls.
Now rewind. That project was probably over budget the day it was approved, signed off on the most optimistic numbers in the room and carried by the most persuasive sponsor at the table. No amount of delivery discipline saves a decision that was wrong from the start.
The failure didn’t happen in execution. It happened in the business case. And the business case is the one thing nobody kept.
It Isn’t a Project Management Problem
When capital outcomes disappoint, the instinct is to fix the tooling. It usually points the wrong way.
Execution tools, whether SAP’s own Project System, Primavera, or Microsoft Project, run work that’s already approved. They were never built to decide what gets funded. That choice belongs to project portfolio management, the discipline that sits above execution and decides which investments are selected, sequenced, and funded. A dedicated portfolio platform gets closer, but parked beside your ERP it becomes one more planning silo, making confident calls on numbers it can’t reconcile with SAP.
None of that is your real problem. Your real problem is upstream, and it’s one of the most common challenges with project portfolio management in SAP: how the decision got made, and whether anyone can reconstruct it a year later.
What Is a CapEx Business Case?
A CapEx business case is the structured reasoning behind a capital investment decision: the problem it solves, the options considered, the assumptions under the numbers, the expected benefits, the risks accepted, the financial justification, and who is accountable for the outcome.
It is not the form that releases the funds. A CapEx request asks for approval to spend. A CapEx business case explains why that spend should be approved, how it compares with other uses of your capital, and how the result will be judged later.
And while the keyword here is CapEx, the discipline doesn’t stop at capital. The same reasoning governs the operating expenditure that sits right alongside CapEx and is increasingly becoming more important. The real system of record is for strategic expenditure that includes every significant commitment of capital and operating spend, judged the same way in one model. CapEx is simply where the pain shows first.
Most organizations capture part of this once, to clear a gate, then file it. The difference between a document that wins funding and a business case that improves decisions is whether it is structured, comparable, and kept alive through the life of the project. Almost no one treats it as the asset it is.
Why Capital Projects Keep Failing Before They’re Built
That blamed-project-manager scene isn’t bad luck at your company. It’s one of the most consistently documented patterns in capital investment.
Oxford’s Bent Flyvbjerg, who holds the largest dataset of major projects in the world, calls it the Iron Law of Megaprojects: over budget, over time, under benefits, again and again. Nine in ten megaprojects bust their budgets, a pattern that has held for more than 70 years across over a hundred countries.
The cause isn’t weather or bad luck. It’s two things, and both live in the business case. Optimism bias, the honest human tendency to underestimate cost and overestimate benefit. And strategic misrepresentation, the incentive to shade the numbers to win funding. Put them together and you get what Flyvbjerg calls “survival of the unfittest”: the projects that win approval aren’t the best ones, they’re the ones that look best on paper, which are exactly the ones with the most optimistic numbers baked in. That is your most persuasive sponsor, winning again. It’s how good CapEx projects fail despite competent delivery: the flaw was set upstream.
Public finance has known this for twenty years. HM Treasury’s Green Book, the UK’s appraisal standard, states plainly that appraisers are systematically over-optimistic, and it requires them to add explicit uplifts to cost and time, for some project types more than 50%. The catch: those uplifts must be empirically based, drawn from how past projects actually turned out.
That is the whole argument in one line. The proven fix for over-optimistic decisions is a structured record of what really happened last time. That record is the business case, kept and compared. And it is the one thing SAP doesn’t hold.
The Part of Capital Project Control SAP Will Never Hold
Here is the uncomfortable part. SAP is an outstanding system of record for execution and financial control. That is exactly why it is not a system of record for decisions. It captures the request and the number. It does not capture the reasoning, and the reasoning is what tells you whether the capital was well spent.
| What SAP Records | What the Business Case Holds and SAP Doesn’t |
|---|---|
| The approved amount, commitments, and actuals | The assumptions the numbers were built on |
| Cost center, WBS element, asset | The alternatives considered and rejected, and why |
| What’s been spent and what remains | The benefit promised and whether it was ever realized |
| The appropriation request and its approval | The risks accepted, and who accepted them |
| The transaction trail | Who promised what, and on what basis |
| A complete audit of the money | A standard structure that makes one case comparable to the next |
The left column is essential, and SAP does it better than almost anything. The right column is where capital decisions are actually won or lost. So in most organizations the reasoning , the options compared, the assumptions made, the benefit promised versus the benefit realized, ends up scattered across slide decks and the spreadsheets that still run most capital planning, then lost the moment funding is approved. That is the column where capital decisions are actually won or lost, and it’s the column with no system of record.
“But we already do this in SAP”
Many of SAP customers point to Appropriation Requests or capital expenditure management in SAP Investment Management and say it’s handled.
Those tools record that a request was raised, classified, approved, and funded. What they were never built to hold is the why and the what-if: the options you compared, the assumptions you made, the benefit you projected versus the benefit you got, the way the case changed as it moved through the gates. SAP Investment Management can tell you a project was approved for a number. It can’t tell you whether that number was ever credible, or whether the investment delivered. That isn’t a flaw. It’s simply not what a transactional ERP is for.
CapEx Selection Is a Project Portfolio Management Problem
A project can look sound on its own and still be the wrong use of your capital. The harder discipline is choosing across the whole portfolio.
When you have more good projects than money, and you always do, the textbook rule of capital budgeting, fund every positive-return project, falls apart. Under capital rationing, as Aswath Damodaran puts it, selection becomes a constrained optimization: you can only back a subset, so scoring and ranking competing capital projects matters more than any single business case. And you cannot rank what you cannot compare. If every case is written in a different shape, on different assumptions, prioritization collapses into politics, and the loudest voice wins again. The quality of your portfolio is capped by the comparability of the cases beneath it.
A CapEx Business Case You Keep Becomes Context, Memory, and a Boardroom Asset
Keep each business case alive through delivery and something compounds. You build a record of what you promised, what you assumed, what changed, and what you actually got, across every capital decision you have made.
That record is what makes better forecasting possible. Flyvbjerg’s fix for optimism bias, reference-class forecasting, built on Daniel Kahneman’s Nobel-winning work and now used by treasuries from the UK to the Netherlands, means estimating a new project from how similar past projects really turned out, instead of from a hopeful bottom-up guess. It is measurably more accurate. And it is impossible without a body of past cases to draw on. So is the Green Book’s empirical uplift. The single most effective technique for fixing capital estimates depends on having a memory of past projects, and that memory is exactly what you throw away when the business case dies at approval.
This is what makes a unified capital planning system, holding every business case in one consistent, comparable place, your single source of truth for investment decisions, the way SAP is your single source of truth for transactions. It is also what finally gives the board the view it has never had: portfolio health, spend integrity against plan, strategic alignment, and benefit realization, all read off the same record rather than reassembled from slide decks every quarter.
Additionally, it’s also what turns AI in CapEx management from a party trick into something useful. AI can draft detailed professional business cases in minutes. The real value is a structured history it can reason against, to flag the assumptions that always slip, the sponsors who always run hot, and the cash-flow curves that never hold and to answer a board’s question with a grounded number and the chart behind it. Without that context and memory there is nothing to learn from. With it, every decision sharpens the next and the assistant earns its seat at the table.
SAP Isn’t the Villain, It’s Where Execution Belongs
None of this is an argument against SAP. The opposite.
SAP should stay the system of record for execution, commitments, actuals, and assets. The mistake is asking it to also be where decisions get made, argued, compared, and remembered, the same line that separates budgeting and planning capital expenditure in SAP from deciding what to fund at all. Bolt the decision process onto the transaction layer and you get a brittle version of both. The decision layer belongs in front of SAP and connected to it, so the case you approved, the money you commit and the outcome you deliver finally sit on one line instead of three.
What to Look for in Capital Planning Software for SAP
If you want better capital outcomes, the test isn’t whether software can track a project. It’s whether you can:
- standardize the business case for capital projects before they exist in SAP
- compare and rank competing projects under real funding constraints
- model funding scenarios as budgets and conditions shift
- record why each project was approved, deferred, or rejected, with a versioned trail
- carry the case through delivery and measure actual benefits against the ROI you promised
- do all of it connected natively to SAP, not in a standalone tool you feed by hand and reconcile forever
That last point is where most organizations come unstuck, and it’s one of the gaps in how project portfolio management is executed in SAP. A decision is only as good as the data under it. Made beside your ERP, on numbers re-keyed or lagged, it’s a decision made on faith. Connected properly to reconciled data, the same discipline gives you capital project portfolio visibility across demand, delivery, and outcomes that a standalone tool can’t.
Bridging the Project Portfolio Management Gap in SAP with Stratex Online
This is the layer Stratex Online was built for. It gives finance and leadership one place to build, compare and challenge the business case behind every capital and strategic expenditure decision, prioritize under real constraints, and keep each decision and its rationale alive through the life of the project. Approved cases flow into SAP for execution, so the decision and the delivery finally connect.
One gap runs through everything above: SAP-run organizations have a complete record of what they spent, but not of why they chose it or whether it paid off. That’s the gap Stratex Online closes, and it’s the record that lets the boardroom allocate capital on evidence instead of advocacy.
Choose Before You Commit
Once a project exists in SAP, the biggest decision is already behind you. The capital is committed, the assumptions are baked in and watching the spend more closely won’t rescue a poor choice.
The question that matters comes earlier, and it lives in the business case. Should we fund this? Is it still the best use of our capital? Are the assumptions honest? What are we choosing not to do instead? Could we defend this in a year?
Go back to that over-budget project and the manager who took the blame. The honest post-mortem doesn’t end in the field. It ends in the room where the business case was approved, on numbers no one kept. SAP will faithfully record what you decided. It will never tell you whether you decided well. That part is yours, and it’s the most important capital work you do.
Related Posts
If you enjoyed reading this, then please explore our other articles below:
