SAP PS in S/4HANA: Key Differences from ECC Explained

SAP

October 23, 2026

Quick Answer

SAP PS in S/4HANA keeps the same core objects and most of the same transactions as ECC: project definitions, WBS elements, networks, CJ20N and the period-end close. The differences sit around the module. Finance postings land in the Universal Journal. Cost elements become G/L accounts. Detailed planning moves toward SAP Analytics Cloud. Event-based revenue recognition joins results analysis, and Fiori apps add new screens. SaiSatwik helps project-driven businesses move SAP PS to S/4HANA without redesigning projects that already work.

Does SAP PS still exist in SAP S/4HANA?

Yes. SAP Project System is part of SAP S/4HANA on-premise and private cloud. Project definitions, WBS elements, networks, activities and milestones work as they did in ECC, and CJ20N remains the main working transaction.

That continuity is deliberate. Thousands of companies run capital and customer projects on SAP PS. A forced redesign would have stalled migrations. The SAP PS beginner guide describes the objects that carry over unchanged.

What are the key differences for SAP PS in S/4HANA?

The changes that affect SAP PS teams most come from finance, planning and the user interface. The table summarises them.

AreaSAP ECCSAP S/4HANA
Finance dataSeparate FI and CO tables, reconciledOne Universal Journal (table ACDOCA)
Cost elementsSeparate CO master dataG/L accounts with a cost element category
Detailed planningClassic planning transactions such as CJR2SAP Analytics Cloud positioned as the strategic planning tool
Revenue recognitionResults analysis at period endResults analysis or event-based revenue recognition
Customer and vendor masterSeparate customer and vendor recordsBusiness partner model
User interfaceSAP GUISAP GUI plus SAP Fiori apps
MRPClassic MRPMRP Live, much faster on HANA
SAP PS in ECC vs SAP PS in S/4HANA

How does the Universal Journal change SAP PS?

The Universal Journal puts every financial posting, including project costs, in one line-item table. A supplier invoice on a WBS element is one record carrying the G/L account, cost element, profit center and project together.

For project controllers, reports get faster and FI to CO reconciliation disappears. For migration teams, the cost element change is the bigger job. Secondary cost elements used for settlement, overhead and results analysis must exist as G/L accounts first. The SAP PS and FICO integration guide covers those flows.

What changes for planning and revenue recognition?

Planning and revenue recognition are where SAP PS in S/4HANA asks for real decisions. Both have a classic option and a newer one.

  • Cost planning. Easy Cost Planning and network costing work as before. For detailed financial planning, SAP positions SAP Analytics Cloud as the strategic tool. See the SAP PS cost planning guide.
  • Revenue recognition. Classic results analysis still runs on-premise. Event-based revenue recognition posts recognised revenue as costs and billings occur. The results analysis guide compares the two.

Neither choice has to be made on day one. Many companies convert with classic planning and results analysis, then move to the newer options as a later phase.

Which SAP PS functions need checking before migration?

SAP publishes a Simplification List for each S/4HANA release. It names functions that changed, moved or are not part of the target architecture. A few older Project System add-ons appear on it, and the list changes by release.

Run SAP Readiness Check against your ECC system before planning the conversion. It reports which simplification items apply to the functions you actually use. Release-specific guidance is on the SAP Help Portal.

Why is the timing of SAP PS migration important?

The ECC deadline sets the clock. SAP’s maintenance announcement commits mainstream maintenance for ECC until the end of 2027, with optional extended maintenance to 2030. S/4HANA maintenance runs to at least 2040.

Project-heavy businesses carry extra migration risk because projects run across the cutover. McKinsey and Oxford found large IT projects run 45 percent over budget on average. Open projects, budgets and assets under construction all need a clear conversion plan.

How should you migrate SAP PS to S/4HANA?

An SAP PS migration follows the wider S/4HANA conversion, with a few project-specific steps. The order below is how SaiSatwik plans them.

  1. Run Readiness Check. Identify simplification items that touch Project System.
  2. Clean up projects. Close finished projects, settle balances and archive what you can.
  3. Prepare cost elements. Map secondary cost elements to G/L accounts.
  4. Decide planning and revenue recognition. Keep classic first, or move now.
  5. Test full cycles. Plan, budget, procure, confirm, bill and settle on converted projects.
  6. Train on Fiori. Introduce the new apps alongside CJ20N, not instead of it.

How does SaiSatwik handle SAP PS in S/4HANA projects?

SaiSatwik treats SAP PS as its own workstream inside an S/4HANA conversion. Open projects are listed and classified months before cutover. The project team decides which close, which convert, and which need a fresh structure.

That work is part of every conversion run by the SaiSatwik SAP practice. For the full platform picture, see the SAP ECC to S/4HANA migration guide and SAP EPPM in SAP S/4HANA: what changed.

FAQs about SAP PS in S/4HANA

Is SAP PS replaced in SAP S/4HANA?

No. SAP Project System continues in SAP S/4HANA with the same core objects and transactions. What changes are the surrounding finance, planning and interface layers, plus newer options such as event-based revenue recognition.

Does CJ20N still work in SAP S/4HANA?

Yes. CJ20N runs in SAP S/4HANA as the main transaction for building and changing projects. SAP Fiori apps add monitoring and reporting views alongside it.

What happens to cost elements for SAP PS in S/4HANA?

Cost elements become G/L accounts with a cost element category in the chart of accounts. Secondary cost elements used for overhead, results analysis and settlement must be set up as G/L accounts during conversion.

Can open SAP PS projects be converted to S/4HANA?

Yes. A system conversion carries open projects, budgets, commitments and assets under construction across. Clean-up before conversion, such as closing finished projects and settling balances, makes it much smoother.

You May Also Like…

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *