What Changed for SAP PS in S/4HANA

·4 min read
What Changed for SAP PS in S/4HANA

With the end of mainstream maintenance for SAP ECC at the end of 2027, most companies running SAP Project System (PS) are planning or executing their move to SAP S/4HANA. A question we hear often from PS consultants and key users is simple: what actually changes for us?

The short answer: the PS module itself is very familiar, but much of what happens underneath it, in finance, master data and the user interface, has changed. This article walks through the main differences.

Advertisement

1. SAP PS is still there, and it looks familiar

SAP Project System is part of S/4HANA. Its core concepts are unchanged: project definitions, WBS elements, networks, activities and milestones (see Project Structures), and the main transactions such as the Project Builder (CJ20N), cost planning (CJ40) and budgeting (CJ30) are still available. Most of the PS configuration you know from ECC, such as project profiles, network profiles, budget profiles and settlement profiles, is still maintained in the same way.

This is good news for experienced PS consultants: your knowledge of the module remains highly relevant. The changes are mainly in the surrounding areas.

2. Finance underneath: the Universal Journal

The biggest change for PS comes from finance. In S/4HANA, financial accounting and controlling postings are stored in a single table, the Universal Journal (ACDOCA). Actual costs and revenues posted to WBS elements and networks end up there, together with the G/L account, the profit center and other dimensions. Plan data is stored in a similar line-item table (ACDOCP).

What this means in practice:

  • One source of truth: no more reconciliation between FI and CO for project postings.

  • Cost elements are G/L accounts: primary and secondary cost elements are now maintained as G/L accounts with a cost element category.

  • Reporting: classic tables such as COSP, COSS and COEP are still readable through compatibility views, so many existing reports keep working, but new reports should be built on ACDOCA. See our SAP PS tables page.

  • Profitability analysis: margin analysis, the account-based approach to CO-PA, is the default in S/4HANA, which affects how project revenues and costs flow into profitability reporting.

3. Revenue recognition: event-based as an alternative to results analysis

In ECC, revenue recognition for customer projects is typically done at period-end with results analysis (see Period-End Closing). S/4HANA introduced event-based revenue recognition, where revenue is recognized in real time with each relevant posting (for example a cost posting or a billing document), instead of waiting for the period-end run.

Event-based revenue recognition gives project managers up-to-date margins during the period, but it is a different way of working and needs to be designed carefully, especially for fixed-price and time-and-material projects. Results analysis remains available, so the choice is a design decision for each implementation.

4. The user experience: SAP Fiori

In S/4HANA, users work through the SAP Fiori launchpad. Classic PS transactions are still available, either in SAP GUI or as SAP GUI for HTML tiles in the launchpad, alongside Fiori apps for monitoring projects, WBS elements and networks. New functionality is delivered first, and sometimes only, as Fiori apps. See SAP PS Fiori apps for examples and tips to find the apps for your release.

Advertisement

5. Master data changes that affect projects

  • Business Partner: customer and vendor master data are maintained through the Business Partner in S/4HANA. This affects every project process that involves customers (sales orders, billing) or suppliers (purchasing for networks and WBS elements).

  • Longer material numbers: material numbers can have up to 40 characters, which may matter for interfaces and custom developments around material components.

  • Material Ledger: the Material Ledger is mandatory for inventory valuation in S/4HANA, which is relevant when projects use valuated project stock.

6. Simplifications and deprecated functions

As with every module, some older or rarely used functions were simplified, replaced or moved to the compatibility scope in S/4HANA. SAP documents all of them in the Simplification List for each S/4HANA release, with dedicated items for the Project System area.

Before any project, check the Simplification List items for PS, and run the SAP Readiness Check on your ECC system: it shows which simplification items actually apply to your data and custom code. Do not rely on generic lists, since what applies depends on your release and on which PS functions you use today.

7. Cloud editions

The full PS functionality described above applies to SAP S/4HANA on-premise and S/4HANA Cloud Private Edition, which is the typical target for companies moving with RISE with SAP. S/4HANA Cloud Public Edition takes a more standardized approach to project management, built around predefined processes such as enterprise projects and project-based services, so a public cloud move usually means adopting SAP's standard processes rather than carrying over a classic PS design.

What it means for SAP PS consultants

Your PS expertise remains valuable, but the role is evolving. The skills that make the biggest difference on S/4HANA projects are:

  • a solid understanding of the Universal Journal and S/4HANA finance, since PS is closely tied to it;

  • knowledge of event-based revenue recognition for customer projects;

  • familiarity with Fiori apps and the launchpad, to support users;

  • experience with the migration tools and approaches (see our ECC to S/4HANA migration guide for PS consultants);

  • the SAP Activate methodology used on S/4HANA projects.

S/4HANA evolves with each release. Always check the SAP documentation, Simplification List and SAP Notes for the release you are working on.

Advertisement
Looking for the reference pages? See the SAP PS transaction codes, database tables and module overview.