コンテンツへスキップ

SAP EPPM (Enterprise Portfolio & Project Management)

― Enterprise Portfolio and Project Management ―

PS / PPM / Commercial Project Management / Investment Management / CATS

July 2026

This paper provides a systematic explanation of SAP EPPM (Enterprise Portfolio and Project Management) — the framework that integrates SAP’s project-oriented processes — covering its constituent components, functions, evolution under S/4HANA, and application scenarios. It is aimed primarily at manufacturing practitioners who manage accounting, logistics, and resources around “projects,” including capital expenditure (CAPEX), order-based projects (Revenue), R&D, and maintenance projects.

Chapter 1 What Is SAP EPPM

SAP EPPM (Enterprise Portfolio and Project Management) is not a single product; rather, it is an umbrella term for a set of components that support project-oriented processes from the accounting, logistics, and resource perspectives. It covers all scenarios — CAPEX (capital expenditure), OPEX (expense projects), and Revenue (order-based projects).

It is important to note that EPPM does not refer to “PPM alone.” In addition to the core PPM (Portfolio and Project Management), it also includes PS (Project System), CPM (Commercial Project Management), IM (Investment Management), and CATS (time recording), all of which run on S/4HANA.

Component Role Main Use
PS (Project System) Execution-level project management using WBS and networks Cost/schedule/revenue management for CAPEX, EPC, maintenance, and R&D
PPM (Portfolio and Project Mgmt) Portfolio management and decision-making Selection, prioritization, and resource allocation across multiple projects
CPM (Commercial Project Mgmt) Commercial management of order-based projects Estimating, cost planning, progress billing, and change/issue management
IM (Investment Management) Investment budget management Investment programs, budget allocation, and approval
CATS (Cross Application Time Sheet) Time recording Time entry against projects/cost centers

* “EPPM” does not equal “PPM.” EPPM is an “umbrella” under which execution-oriented PS, portfolio-oriented PPM, and commercial-oriented CPM are used according to their respective roles. The “portfolio management tool” often discussed in the context of AI engineering and similar fields refers to the PPM within this umbrella.

Chapter 2 Detailed Look at the Components

2-1 PS (Project System) ― Execution-Level Project Management

PS is the core execution-level module in S/4HANA that plans, executes, and manages projects using the WBS (Work Breakdown Structure) and networks (activities). It provides integrated management of cost, budget, labor hours, procurement, and revenue on a per-project basis.

・WBS elements: Break the project down hierarchically to serve as the aggregation unit for cost, budget, and actuals

・Networks/activities: Define the sequence of work, duration, resources, and subcontracting, and perform schedule planning (scheduling)

・Budget/actuals management: Compare budget allocation (BCS) against actuals, and control overruns through Availability Control

・Revenue recognition/progress billing: Revenue recognition via Results Analysis / percentage-of-completion (POC), and milestone billing

・Procurement integration: Subcontracting orders and material requirements from networks (integrated with MM/PP)

2-2 PPM (Portfolio and Project Management) ― Portfolio Management

PPM sits above individual project execution (PS) and manages multiple projects across the organization. It supports decisions on “which projects to invest in” from the perspectives of strategic fit, ROI, risk, and resources. Its predecessors were cProjects and xRPM (Resource and Portfolio Management), which were integrated to form PPM.

・Portfolio management: Listing, scoring, prioritizing, and gate review of projects/initiatives

・Resource management: Capacity planning for engineers and staff, and allocation across multiple projects

・Project planning: Project planning of phases, tasks, checklists, and deliverables

・Financial integration: Link PPM projects with PS cost projects to manage plan and actuals end-to-end

2-3 CPM (Commercial Project Management) ― Commercial Management of Order-Based Projects

CPM supports the lifecycle of “customer-facing commercial projects” such as engineer-to-order production, EPC, and engineering services. In S/4HANA, it has become a native capability (previously an add-on).

・Project Cost and Revenue Planning: Plan multi-level estimates, costs, and revenue in a workbench

・Project Progress: Manage progress and earned value (EVM), and calculate EAC/ETC

・Project Issue and Change Management: Manage issues, change requests, and their cost impact

2-4 IM (Investment Management) and CATS (Time Recording)

・IM (Investment Management): Budget planning, approval, and allocation for investment programs. Used to control CAPEX budgets

・CATS (Cross Application Time Sheet): Records time against projects, networks, and cost centers, providing visibility into cost and staff utilization

Chapter 3 The Evolution of EPPM under S/4HANA

Under S/4HANA, each EPPM component has been substantially renewed in terms of its accounting foundation, UX, and analytics.

・Integration with the Universal Journal: Project finances are posted not to separate CO tables but to the Universal Journal (ACDOCA), managed as a single source of truth

・Move to Fiori: The front end has shifted from SAP GUI to SAP Fiori, giving project management, progress entry, and analytics a modern UI

・Embedded Analytics: Real-time analysis on live data rather than nightly extracts (Embedded Analytics)

・Native CPM: CPM has become part of the platform rather than an add-on

* EPPM is available in both the Public and Private editions of S/4HANA Cloud. The greatest advance is that, with project finances integrated into ACDOCA, FI, CO, PS, and PPM now reconcile in real time on the same ledger.

Chapter 4 Application Scenarios and Industries

Scenario Description Primary Components Used
CAPEX (capital expenditure) Investment management for new plant construction and equipment upgrades IM + PS
R&D / new product development Cost/labor/gate management for R&D projects PPM + PS + CATS
Revenue (order-based) EPC, engineer-to-order production, engineering services CPM + PS
Maintenance projects Large-scale overhauls and periodic repairs (integrated with PM) PS (+ PM)

For manufacturers, CAPEX (IM + PS) and order-based projects (CPM + PS) are the two most important scenarios. In the engineering and plant industries, a typical configuration manages EPC projects with CPM + PS, while resource optimization across multiple projects is handled with PPM.

Chapter 5 Integration with Other Tools and Key Implementation Points

・Microsoft Project: Schedule analysis via Copilot integration. Can be integrated with SAP PS via Power Platform integration

・Primavera P6: For large-scale infrastructure and construction. Monte Carlo completion-probability analysis. Has a track record of integration with PS

・Use of AI: Since 2025, PPM has been expanded with AI functions for delay prediction and resource optimization, natively referencing PS data

⚠ Key implementation point: Everything comes down to designing “which component handles which scenario” in EPPM. Relying on PS alone prevents overall optimization across multiple projects, while relying on PPM alone means execution-level costs cannot be controlled. Clearly dividing roles — IM + PS for CAPEX, CPM + PS for order-based projects, and PPM for cross-project optimization — is the condition for success.

Chapter 6 Configuration (Specific Configuration Steps)

EPPM configuration is divided by component. The following, assuming S/4HANA (on-premise / Private Edition), organizes the main configuration steps (SPRO menu paths and representative transactions) in the order PS → IM → PPM → CPM/CATS. This corresponds to the configuration areas covered in the SAP Learning Journey (S4120–S4123: Master Data / Configuration for Project Control in Logistics and Financials).

6-1 Main Configuration for PS (Project System)

PS starts from the “Project Profile,” which defines the numbering scheme, budget, and settlement rules.

Configuration Item SPRO / Overview Representative T-Code
Project Profile Project System > Structures > Operative Structures > WBS. Consolidates default values for budget/planning/organization/settlement OPSA
Project Coding Mask Defines the project numbering scheme (mask) OPSJ
Network Profile Network > Settings for Networks. Defaults for scheduling and confirmation OPUV / OPUU
Status Profile Defines user statuses (approval, freeze, etc.) OK02 / BS02
Budget Profile & Availability Control Costs > Budget. Availability Control that governs budget overruns OPS9
Settlement Profile Settlement rules to AUC / assets / cost centers OKO7
Key Execution Transactions Project Builder / Budget / Settlement / Structure Reports CJ20N / CJ30 / CJ88 / CN41N

6-2 Configuration of IM (Investment Management)

・Defining investment program types: Configure program types and budget categories (SPRO > Investment Management) T:OIT1

・Creating investment programs and budget allocation: Program definition (IM01) → Budget (IM32) → Allocation to WBS/orders

・Automatic AUC (asset under construction) generation: Define AUC generation and settlement rules in the investment profile; the asset remains AUC during the period and is capitalized to the final asset upon completion

6-3 Configuration of PPM (Portfolio and Project Management)

PPM configuration covers the portfolio structure, items, decision flow, and scoring. The figure below shows the structure of PPM (portfolio / bucket / item / project).

Figure: Structure of SAP PPM ― Portfolio / Bucket / Item / Project (Source: quoted from SAP EPPM materials, p.6)

・Portfolio type / bucket structure: Defines the hierarchy of strategic buckets (R&D, IT, customer projects, etc.)

・Item Type: Configures the types of portfolio items along with field control and status

・Decision Flow / phase-gate: Defines gate reviews for Strategy→Idea→Concept→Development→Scale Up→Launch

・Scoring model / questionnaire: Configures an evaluation model that quantifies risk assessment, commercial success probability, and technical feasibility

・Financial / capacity planning categories: Defines categories for financial planning (NPV, ECV, ROI, etc.) and resource planning

・PPM ⇔ PS integration: Assigns portfolio items to PS cost projects, managing plan and actuals end-to-end

6-4 Configuration of CPM / CATS

・CPM: Configuration of the project workspace and financial planning templates (multi-level cost and revenue planning), and progress/earned value (EVM)

・CATS: Configure the data entry profile for time recording (T:CAC1) and approval (CATS_APPR_LITE), recording time against WBS/networks/cost centers

⚠ Edition differences: In S/4HANA Public Cloud, configuration is done not via SPRO but through the Fiori-based configuration environment (Configuration/Manage Your Solution). Private Edition/on-premise is centered on SPRO. Since the configuration method and scope of change vary by edition, design should be based on the target edition.

Chapter 7 Customer Implementation Case Studies (with Screen Images)

7-1 John Deere ― Large-Scale R&D Project Management

John Deere, a major agricultural machinery manufacturer, manages its R&D projects with SAP EPPM (PPM/PS). According to publicly available SAP materials, the customer’s system holds approximately 8 million project tasks, and 15,000 users use it to review tasks. The SAP HANA platform is said to have dramatically improved the responsiveness of dashboard operations such as querying open tasks, setting status, and saving tasks.

Figure: John Deere ― R&D Project Management (approximately 8 million tasks, 15,000 users, accelerated by HANA) (Source: quoted from SAP EPPM materials, p.21)

【Takeaway】 EPPM has the scalability to withstand task management for large-scale R&D, and the HANA platform underpins the responsiveness of operations on large task volumes (open → set → save). The larger a manufacturer’s portfolio, the greater the benefit of platform performance.

7-2 Application Models by Project Type

The application of SAP EPPM varies according to the nature of the project. The reference materials organize the modules used and capitalization destinations across three types: investment, customer, and cost.

Figure: Project Types in SAP (Investment / Customer / Cost) and the Modules Used (Source: quoted from SAP EPPM Demo materials, p.5)

Project Type Example Modules Used Capitalization/Revenue
Investment project Fixed asset acquisition, office construction (e.g., Godrej) IM / PS / CO / PPM / CPM AUC → capitalized to asset
Customer project Order-based SAP implementation, MTO (make-to-order) PS / SD / CO / PPM / CPM Revenue recognized to product/project
Cost project R&D, plant shutdown maintenance PS / CO / PPM / CPM Transferred to cost center

* The examples shown in the materials ― Godrej’s real estate/office construction (an investment project), an SAP implementation engagement (a customer project), and plant shutdown maintenance (a cost project) ― concretely demonstrate that “even within the same EPPM, module configuration changes according to the nature of the project.”

7-3 Decision Support and Portfolio Analysis in Practice

In PPM portfolio operations, soft information (risk, probability of commercial success, technical feasibility) is quantified using questionnaires and scoring models, and rankings and what-if comparisons are performed on dashboards.

Figure: Decision Support ― Scoring Dashboard (Ranking / What-If Scenarios) (Source: quoted from SAP EPPM materials, p.9)

In portfolio analysis, a KPI monitor (planned/actual schedule, cost/budget, risk, NPV, ROI) is used to check the alignment between strategic goals and the allocation of capital/operating expenditure, and to compare demand against available capacity.

Figure: Portfolio Analysis ― KPI Monitor (Schedule / Cost / Risk / NPV / ROI) (Source: quoted from SAP EPPM materials, p.17)

* The essence of EPPM (PPM) lies in the cycle of “quantifying soft information (scoring) → getting an overview via portfolio KPIs → selecting/discarding at gate reviews.” The configuration described in the previous chapter (scoring model, decision flow) forms the foundation that makes this operation possible.

Chapter 8 Conclusion

SAP EPPM is an integrated umbrella that supports project-oriented processes from the accounting, logistics, and resource perspectives, with PS (execution), PPM (portfolio), and CPM (commercial) at its core. The decisive difference from before is that, integrated into the Universal Journal under S/4HANA, FI, CO, PS, and PPM now reconcile in real time on the same ledger.

* Final message: Do not mistake EPPM for merely another name for PPM. Dividing roles among PS, PPM, and CPM under the umbrella, and unifying finances through the Universal Journal, is the key to achieving both visibility and control in project management.

(This paper was prepared based on publicly available SAP information (S/4HANA EPPM / PS / PPM / CPM) and literature from 2025–2026. The scope of functionality varies by edition and release.)

About the author — Tsujita (Supply Chain)

Focuses on supply/demand planning and project-based business processes, with expertise in global SCM integration design.

Have a question about this article?

Ask the author directly — no sales pitch, just an answer.

Ask about this article →