Scenario modelling and trade-offs
Tools to evaluate alternative investment scenarios and understand the impact of different funding, timing, and prioritization decisions.

Capital allocation and reallocation
The ability to assign capital across the portfolio and adjust allocations dynamically as priorities, constraints, and project performance change.

Forecasting (cash and accrual)
Forward-looking visibility of financial outcomes, including both accounting-based forecasts and actual cashflow requirements.

Governance across the lifecycle
Defined processes, approvals, and controls that ensure investment decisions are consistent, transparent, and aligned from initial idea through to execution.

What These PPM Capabilities Enable

When these capabilities are in place, organizations can:

• Compare investments on a consistent basis
• Understand trade-offs across the portfolio
• Allocate capital with confidence
• Maintain control from idea through to execution

Each of these capability areas is explored in more detail in the supporting articles linked in the "Explore Each Area in More Detail" section below.

Where the PPM Gaps Emerge in SAP Environments

The capabilities required for effective Project Portfolio Management span the full investment lifecycle, from initial idea through to execution and financial control.

In SAP environments, these capabilities are not delivered within a single, continuous process.

SAP is designed to operate once projects have been approved and formally structured. It provides strong support for execution, including budgeting, procurement, and the tracking of actual costs and commitments.

However, the activities that define Project Portfolio Management occur before SAP becomes the system of record.

• Investment ideas and proposals are identified before projects exist in SAP
• Business cases are developed and assessed outside the system
• Investment decisions are made prior to formal project creation

As a result, critical planning and decision-making processes are typically managed across spreadsheets, documents, and disconnected tools.

This creates a separation between how investment decisions are made and how projects are executed.

The gap is not caused by a lack of capability within SAP, but by the fact that Project Portfolio Management requires functionality that sits upstream of where SAP is designed to operate.

The following sections outline where this gap becomes visible across key Project Portfolio Management capabilities.

Where SAP Falls Short in Project Portfolio Management

The following gaps illustrate where the capabilities required for effective Project Portfolio Management are not fully supported within typical SAP environments, and where a dedicated capital planning layer becomes essential. SAP PPM nominally addresses some of these gaps, this module is rarely deployed, and will be excluded from consideration in the below.

Gap 1: Limited Visibility Before Project Creation

• PPM requires: visibility of investment pipeline and early-stage demand
• In SAP environments: only approved and structured projects (WBS, internal orders) are typically visible
• Why this creates a gap: there is no consolidated view of proposed or in-flight investment ideas
• What fills the gap: structured demand capture and portfolio visibility before projects enter SAP

Limited visibility across the portfolio is explored further in how organizations achieve project portfolio visibility in SAP.

Gap 2: No Structured Project Comparison

• PPM requires: consistent evaluation criteria to compare projects on value, risk, and strategic alignment
• In SAP environments: project evaluation is typically performed in spreadsheets or disconnected tools
• Why this creates a gap: inconsistent inputs make it difficult to compare or prioritize investments
• What fills the gap: standardized business cases and scoring frameworks across all projects

This challenge is explored further in how organizations compare investments, including approaches to scoring and ranking projects.

Gap 3: No Portfolio-Level Prioritization

• PPM requires: prioritization of projects within capital and resource constraints
• In SAP environments: projects are managed individually rather than as part of a constrained portfolio
• Why this creates a gap: capital is allocated without full visibility of trade-offs or opportunity cost
• What fills the gap: portfolio-level prioritization based on strategic objectives and constraints

Gap 4: No Scenario Modelling

• PPM requires: the ability to model alternative investment scenarios and trade-offs
• In SAP environments: reporting reflects the current state, not alternative or future scenarios
• Why this creates a gap: organizations cannot test or compare "what-if" investment decisions before committing
• What fills the gap: scenario modelling to evaluate funding, timing, and prioritization options

Gap 5: Limited Capital Reallocation

• PPM requires: dynamic reallocation of capital as priorities and project performance change
• In SAP environments: budget changes require manual adjustments and structural updates
• Why this creates a gap: organizations are slow to respond to shifting priorities or emerging opportunities
• What fills the gap: continuous capital reallocation based on portfolio performance and constraints

Gap 6: Forecasting vs Actual Disconnect

• PPM requires: consistent, forward-looking forecasts aligned to actual performance
• In SAP environments: strong visibility of actuals and commitments, but forecasting is externalized in the analytics layer
• Why this creates a gap: forecasts are manual, inconsistent, and difficult to validate
• What fills the gap: structured forecasting aligned to project and portfolio-level assumptions

This disconnect is explored further in capital forecasting and financial planning in SAP environments.

Gap 7: No Cashflow Forecasting Capability

• PPM requires: visibility of when cash will be spent across the portfolio
• In SAP environments: financial tracking is primarily accrual-based
• Why this creates a gap: treasury and funding decisions lack reliable cashflow insight
• What fills the gap: portfolio-level cashflow forecasting across all investments

Gap 8: Fragmented Planning and Execution

• PPM requires: a connected process from idea through to execution
• In SAP environments: planning occurs outside SAP, while execution occurs within it
• Why this creates a gap: data is duplicated, fragmented, and difficult to reconcile
• What fills the gap: integration between planning and execution into a single portfolio view

Gap 9: Over-Reliance on Spreadsheets

• PPM requires: controlled, auditable, and consistent data structures
• In SAP environments: spreadsheets become the default planning layer
• Why this creates a gap: version control, auditability, and consistency are compromised
• What fills the gap: a structured, single source of truth, and governed environment for capital planning

This reliance on spreadsheets is explored further in why organizations continue to depend on spreadsheets for capital planning despite the limitations.

Gap 10: Heterogeneous System Landscapes

• PPM requires: a unified view across all investments and business units
• In SAP environments: Project, procurement, resourcing and fixed asset data is often split across multiple systems and instances
• Why this creates a gap: organizations lack a consolidated portfolio view
• What fills the gap: a central planning layer that aggregates data across systems

Gap 11: User Experience and Accessibility

• PPM requires: broad accessibility for stakeholders involved in planning and decision-making
• In SAP environments: access is often limited by licensing, complexity, and usability constraints
• Why this creates a gap: business users are excluded from effective participation in planning processes
• What fills the gap: intuitive, accessible interfaces designed for cross-functional collaboration

Gap 12: Cost and Complexity of Customization

• PPM requires: flexibility to adapt processes as organizational needs evolve
• In SAP environments: customization requires technical development and significant cost
• Why this creates a gap: organizations rely on workarounds instead of evolving their processes
• What fills the gap: configurable, no-code environments for capital planning

Gap 13: Limited Workflow for Portfolio Decisions

• PPM requires: structured workflows for evaluation, approval, and governance
• In SAP environments: workflows are typically focused on discrete project procurement Authorization for Expenditure (AFE) requests rather than portfolio-level decisions
• Why this creates a gap: approval processes are fragmented and inconsistent with loss of visibility around project substitutions, trade-off and prioritization
• What fills the gap: end-to-end workflows for investment evaluation and approval

Gap 14: No Portfolio Impact Analysis

• PPM requires: understanding the financial impact of investment decisions at a portfolio level
• In SAP environments: focus is on individual project cost tracking rather than portfolio outcomes
• Why this creates a gap: organizations cannot assess the combined impact of investment decisions on financial performance
• What fills the gap: portfolio-level modelling of financial outcomes, including ongoing cost (incl depreciation), revenue, and taxation impacts

Why SAP Environments Create This Separation

The separation between capital planning and execution in SAP environments is structural, not incidental.

These gaps are not caused by missing functionality, but by how SAP and Project Portfolio Management operate across different stages of the lifecycle.

SAP is designed to support execution and financial control. Its strengths are grounded in:

• Financial control
  Managing budgets, tracking actual costs, and ensuring financial accuracy
• Transaction processing
  Recording procurement, invoices, and operational activity at a detailed level
• Execution tracking
  Monitoring project progress, commitments, and spend once work is underway

These capabilities become critical once an investment has been approved and formalized, ensuring projects are delivered in a controlled and auditable manner.

However, Project Portfolio Management operates in a different part of the lifecycle.

It requires capabilities that are inherently forward-looking and decision-driven, including:

• Evaluating investment options before commitment
• Comparing projects using consistent criteria
• Modelling scenarios and trade-offs across the portfolio
• Allocating capital based on strategic priorities and constraints

These activities take place before projects are created and executed. They focus on deciding what should happen, rather than managing what has already been approved.

As a result, the capabilities required for effective Project Portfolio Management sit upstream of where SAP is designed to operate.

This creates a structural separation:

• SAP provides control over execution and financial outcomes
• Project portfolio management requires visibility and control over investment decisions

These functions exist in different layers of the lifecycle. Without a dedicated capital planning layer to connect them, organizations rely on spreadsheets, manual processes, and disconnected tools to bridge the gap.

Why SAP Modules Do Not Fully Address Project Portfolio Management

SAP provides a range of modules that support aspects of capital planning and project management. These tools are often assumed to deliver full Project Portfolio Management capability.

In practice, they address specific parts of the process, but do not provide a complete framework for evaluating, comparing, and prioritizing investments across the portfolio.

SAP Investment Management (IM)

• Strength: supports top-down budget control and appropriation management
• Limitation: does not provide structured scoring, ranking, or comparability across investment options

SAP Project Portfolio Management (PPM module)

• Strength: provides a program-level structure for managing projects and prospective items
• Limitation: limited support for business case development, collaborative evaluation and impact analysis

SAP Project Systems (PS)

• Strength: enables detailed project execution, tracking, and financial control
• Limitation: not designed for dynamic planning or portfolio-level decision-making

SAP Analytics Cloud (SAC)

• Strength: provides advanced project financial reporting and analytics capabilities
• Limitation: does not support workflow, structured evaluation, or integrated decision processes

SAP Business Technology Platform (BTP)

• Strength: allows organizations to build customized solutions
• Limitation: requires significant cost, time, and technical resources to replicate planning capabilities

These tools play important roles within SAP environments, but they do not eliminate the separation between capital planning and execution.

They support components of the process, rather than delivering an integrated approach to project portfolio management.

The Missing Layer in Project Portfolio Management

The Role of a Capital Planning Layer

The gaps identified in SAP environments point to a missing layer in how Project Portfolio Management is executed.

This layer sits between early-stage investment planning and project execution. It is responsible for structuring how decisions are made before projects are approved and delivered.

A capital planning layer operates outside SAP, connecting the full investment lifecycle:

• Idea generation
• Evaluation and business case development
• Prioritization and approval
• Execution and financial control

By linking these stages, it ensures that investment decisions are consistent, comparable, and aligned before they enter execution systems.

To perform this role effectively, a capital planning layer provides a set of core capabilities:

• Standardized business cases
  Ensuring all investments are defined using consistent assumptions, metrics, and evaluation criteria
• Portfolio prioritization
  Enabling organizations to rank and select projects based on value, risk, and strategic alignment
• Scenario modelling
  Allowing decision-makers to assess alternative investment options and understand trade-offs
• Forecasting
  Providing forward-looking visibility across both financial outcomes and cashflow requirements
• Governance workflows
  Structuring evaluation, approval, and control processes across the investment lifecycle

This layer does not replace SAP. It complements it.

SAP remains the system of record for executing and controlling approved projects. The capital planning layer ensures that the right projects are selected, prioritized, and defined before they reach that stage.

Together, they create a connected approach to project portfolio management, linking decision-making with execution across the full lifecycle of capital investment.

Solutions such as Stratex Online are designed to operate in this role, enabling organizations to evaluate, prioritize, and govern capital investments before they move into SAP for execution.

Summary

Project Portfolio Management in SAP environments is defined by a structural separation between planning and execution:

• Project Portfolio Management is a decision-making discipline
• SAP environments support execution, not full investment decision-making
• The gap exists before project creation, where planning and prioritization occur
• As a result, planning is often fragmented across spreadsheets and disconnected tools
• A capital planning layer connects decision-making with execution across the lifecycle
• Solutions such as Stratex Online are designed to support this layer within SAP environments

Explore Each Area in More Detail

Project Portfolio Management spans multiple capabilities. The following resources expand on key areas of Project Portfolio Management within SAP environments, including visibility, prioritization, forecasting, and governance.

Portfolio Visibility and Performance

• Capital Project Portfolio Visibility in SAP: Connecting Demand, Delivery, and Outcomes
• How to Gain Real-Time Global CapEx Visibility in SAP
• Visualizing CapEx KPIs in SAP: Dashboards That Drive Success

Investment Evaluation and Prioritization

• How to Score and Rank Budget Appropriation Requests
• The Value of Capital Budgeting for Effective CAPEX Management
• Growth vs Maintenance Capex: The Complete Guide and Formula

Forecasting and Financial Planning

• 7 Success Factors for Financial Planning and Budgeting in Project Forecasting
• Preparing a Capital Expenditure Budget – Commitment or Cash?
• 9 Key Differences Between Project Budgeting and Cost Forecasting

Capital Planning Challenges in SAP

• Why do 85% of SAP customers rely on Spreadsheets for Capital Planning?
• Budgeting vs Planning Capital Expenditure SAP
• SAP Capital Budgeting: Streamline Capital Expenditure Management

SAP Investment Management and Governance

• Why are you NOT making use of SAP Investment Management?
• The Pros and Cons of SAP Investment Management in S/4HANA
• Key Considerations when Structuring Your SAP Investment Program

Strategy, Risk and Outcomes

• Why CapEx Projects Fail
• How Capital Projects Fail
• Risk Mitigation Strategies for Capital Projects

AI and the Future of CapEx

• Harnessing AI in CapEx Management for Better Results

FAQs on Project Portfolio Management in SAP