SAP PS explained: Project Systems

SAP PS (Project Systems) is the SAP area that makes a project a business object in its own right: a project structure — WBS and networks — carrying dates, capacities, materials, costs and revenues from budget approval to settlement. It serves companies whose product is a project — plant construction, shipbuilding, engineer-to-order — and any company running capital investment projects.

What sits inside Project Systems

The classic component codes still describe the split; a job advert usually names a few of them, never all of them:

Structures (PS-ST) — project definition, WBS elements, networks with activities and milestones, and the coding mask.
Dates (PS-DAT) — basic, forecast and actual dates, and the scheduling that derives them from activity durations.
Resources and material (PS-CRP, PS-MAT) — capacity behind internal activities, project stock, and requisitions reaching Procurement with a WBS account assignment.
Costs (PS-COS) — planning by structure or unit costing, the budget, and availability control that warns or blocks a commitment over tolerance.
Revenues and earnings (PS-REV) — billing plan, milestone billing, results analysis and work in process, then settlement to Controlling or an asset under construction.
Progress and reporting (PS-PRG, PS-IS) — degree of processing and earned value, read back against the plan in the information system.
Confirmations, claims, versions (PS-CON, PS-CLM, PS-VER) — time confirmed on activities, claims when scope moves, versions preserving the original plan.

Is SAP PS the same as project management?

No — PS is where a project's structure, money and materials live in the system, not the tooling for running an SAP implementation (how those are structured is a separate topic). It does not replace the scheduling tool engineers prefer: many schedule elsewhere and let PS hold dates and costs. The consultant's work is accounting-grade — what a WBS element means, what may be posted to it, where its cost lands.

What gets frozen at design, and what surfaces at period end

A PS project alternates between engineers thinking in deliverables and controllers thinking in cost elements.

Design and configuration weeks: How deep the structure goes and what each level means — contract, phase, deliverable. Coding mask, profiles, the status profile gating what may be posted to a node, and the settlement profile are fixed here; reversing them once actuals exist is expensive.
Test and migration weeks: The hard part is projects mid-flight: legacy actuals, consumed budget, open commitments and work in process must arrive as an opening position that reconciles.
Period-end and hypercare: The first close — overhead, progress, results analysis, settlement — then the calls when a settlement lands somewhere unexpected, before handover to AMS and support work.

Who PS hires, and the structure they ask you to defend

From project control — cost engineers and controllers who already argue about accruals and change orders; the usual domain route in.
From Controlling — consultants who already own overhead, results analysis and settlement.
From a live system — the planner colleagues ask before they raise a ticket (the key-user route).
From logistics — MM or PP consultants who followed the project account assignment upstream.
From delivery — people who have run projects, though configuring them stays a different craft from the SAP project manager role.

What gets someone hired is a structure they can defend: a WBS design and why it goes that deep, availability control that stopped an overspend without stopping the business, a settlement rule that put cost on the right asset. Interviews go straight there — billing element versus account assignment element, why a budget check fired (what interviews test).

Which areas PS pairs with, and why

CO is the default second area, and the division is exact: PS owns the settlement rule, CO owns the receivers it lands on — cost centres, internal orders. SD meets PS on customer projects, where the billing plan turns a milestone into an invoice; FI on capital projects, where an asset under construction holds cost until capitalisation; Asset management where turnarounds run as projects. MM and PP sit under the account assignment (which combinations work).