Lesson 5 of 6
EPPM and the cloud direction
9 min
Listen to this lesson
SAP groups its project capabilities under Enterprise Portfolio and Project Management (EPPM). What that means in practice depends on the edition. In SAP S/4HANA Private Edition and on-premise, classic Project System remains, alongside Portfolio and Project Management and Commercial Project Management. In SAP S/4HANA Cloud Public Edition, projects are modeled differently, with enterprise projects and project financial control, and SAP keeps adding capabilities each release.
What lives where
| Capability | Private Edition / on-premise | Public Edition |
|---|---|---|
| Project structures | Project System: project definition, WBS, networks | Enterprise projects with WBS-based structures |
| Financial control | PS planning, budget, AVC, settlement, results analysis | Project financial control, with event-based revenue recognition |
| Portfolio management | Portfolio and Project Management (PPM) | Portfolio capabilities within EPPM |
| Customer and commercial projects | Commercial Project Management (project workspace, cost and revenue planning) | Customer projects for professional services |
| Resource management | Depends on add-ons | SAP Project and Resource Management alongside the ERP |
For a Private Edition customer like Contoso, the practical message is: Project System is not going away in the near term, so converted projects keep working, but new capabilities, especially user experience, AI features and resource management, arrive first in cloud products and in the newer project apps. SAP's 2608 early release series for EPPM in Public Edition, for example, highlights a Project Setup Agent and updates to SAP Project and Resource Management, such as planning, scheduling and a project grid. Treat specific features as release-dependent and verify them in the release notes.
Commercial Project Management
Commercial Project Management (CPM) adds a commercial layer to projects: a project workspace for project managers, project cost and revenue planning that can span WBS elements and sales documents, and issue and change management. It suits professional services and engineering firms that sell projects. Contoso's customer projects are few and product-centered, so it did not adopt CPM in the conversion; a supplier that sells engineering services would look at it closely.
What changes for testers
| Area | Private Edition (PS) | Public Edition (enterprise projects) |
|---|---|---|
| Upgrades | Customer-scheduled; regression owned by the customer | Quarterly releases (2602, 2608, ...); regression on SAP's cadence |
| Revenue recognition | Results analysis or EBRR | EBRR |
| Configuration | IMG, project profiles, budget profiles | Configuration apps within scope items |
| Test focus | Converted data, AVC, settlement, period-end | Scope item processes, release changes, integrations |
How project testing differs by edition.
What would you do?
Grace's steering group hears that "PS is legacy" and asks whether Contoso should rebuild its projects in a new cloud product during the conversion. What is the best advice?
What goes wrong in testing
- Assuming a cloud feature seen in a demo exists in your Private Edition release.
- Comparing results analysis results with EBRR results without accounting for timing differences by design.
- Forgetting that Public Edition releases change project apps every quarter, so test cases need maintenance.
- Treating PPM portfolio data as financial truth when budgets are actually controlled in PS.
Portfolio management in practice
Portfolio and Project Management (PPM) sits above individual projects. It collects proposals, scores them, decides which go ahead within a budget envelope, and tracks the portfolio. At Contoso, capital requests such as the Toledo distribution center are approved in an annual capital review, today in a spreadsheet. A portfolio tool would hold the same decision with its scoring and approval history, then create the PS project once approved, so that the approved figure becomes the original budget without retyping.
| Layer | Question it answers | Contoso today |
|---|---|---|
| Portfolio | Which projects should we do with the money we have? | Annual capital review, spreadsheet |
| Project | How do we deliver this one, on time and budget? | Project System in SAP S/4HANA |
| Financial control | What did it cost, and where do the costs go? | PS budget, AVC, settlement |
| Resources | Who is available to do the work? | Department planning outside SAP |
The layers EPPM covers and where Contoso stands.
For testers, the integration points matter most: an approved portfolio item must create a project with the right profile, and the approved amount must arrive as budget, once, in the right currency. Those are the cases to test when a portfolio layer is added.
One more practical point: in Private Edition, newer project apps and older transactions often coexist for the same object. A project created in CJ20N can be displayed in a Fiori app, and both must show the same structure and values. When a release adds a new app for a task, add a short comparison test: same project, same period, same figures in the old and the new view, before users are told to switch.
- EPPM is SAP's umbrella for project and portfolio capabilities.
- Private Edition keeps Project System, plus PPM and Commercial Project Management.
- Public Edition uses enterprise projects, project financial control and EBRR.
- Verify features per edition and release; cloud features arrive first.
Check your understanding · not graded
Lesson check
1. Is classic Project System available in SAP S/4HANA Private Edition?
2. Which revenue method do Public Edition customer projects use?
3. What does Commercial Project Management add?
4. Why record the release checked when deciding on a project feature?