Quick Answer
SAP PS configuration sets up the profiles that control how every project behaves. In order: confirm the FICO prerequisites, then define the project profile (OPSA), the coding mask (OPSJ), status profiles, network types and the network profile (OPUU), and the planning profile. After those come the budget profile (OPS9) and the settlement profile (OKO7), plus results analysis and investment settings where needed. The project profile ties them together, so each project type picks up the right settings automatically. SaiSatwik configures SAP PS around real project types, not generic defaults.
What does SAP PS configuration involve?
Definition: SAP PS configuration is the setup, in the implementation guide under Project System, of the profiles, number ranges, statuses and control keys that decide how projects are structured, planned, budgeted and settled. End users never see it directly. They feel it in every field default and every error message.
Good configuration is invisible. A project administrator picks a project profile and gets the right numbering, budget rules and settlement receivers without thinking. Poor configuration shows up as daily workarounds and manual corrections at month end.
What must be in place before configuring SAP PS?
SAP PS sits on top of the finance and logistics structures, so several objects must exist first. Missing one stops project creation in testing.
- Finance structures. Company code, controlling area, profit centers and cost elements. The SAP PS and FICO integration guide explains each one.
- Logistics structures. Plants, and work centers with activity types and rates if networks will carry internal labour.
- Overhead and settlement basics. Costing sheets and secondary cost elements for overhead and settlement.
- A project-type list. Agreed with the business: capital, customer, internal, maintenance or R&D.
How do you configure SAP PS, step by step?
SAP PS configuration is best done in a fixed order, because later profiles are assigned inside earlier ones. This is the sequence SaiSatwik follows on new implementations.
- Coding mask (OPSJ). Define the project number pattern and separators, such as C-2026-001 for capital projects.
- Status profiles. Add user statuses where the business needs approval gates beyond the standard system statuses.
- Network types and network profile (OPUU). Set scheduling defaults, control keys and the default network type.
- Planning profile. Choose planning methods, time frame and whether plans run bottom-up or top-down.
- Budget profile (OPS9). Set budget time frame, availability control activation and tolerance limits.
- Settlement profile (OKO7). Define allowed receivers and the allocation structure.
- Results analysis settings. For customer projects: results analysis keys, versions and valuation methods.
- Investment profile. For capital projects that settle to assets under construction.
- Project profile (OPSA). Bring it all together: assign the profiles above and set organisational defaults.
- Templates. Build standard WBS and standard networks for each project type.
What does each SAP PS profile control?
Each profile owns one area of behaviour. Knowing which profile owns what saves hours when something behaves unexpectedly in testing.
| Profile | Transaction or area | Controls |
|---|---|---|
| Project profile | OPSA | Defaults for each project type and the profiles it uses |
| Coding mask | OPSJ | Project and WBS numbering pattern |
| Network profile | OPUU | Network defaults, scheduling and control keys |
| Planning profile | IMG: Costs, Planned Costs | Planning methods, time frame, plan rules |
| Budget profile | OPS9 | Budget time frame and availability control |
| Settlement profile | OKO7 | Allowed receivers and allocation structure |
| Status profile | IMG: Status Management | User statuses and allowed business transactions |
Planning, budgeting and settlement each have their own guide in this series: cost planning, budgeting and availability control and settlement.
How many project profiles should a company have?
Fewer than most implementations end up with. One project profile per genuinely different project type is the rule. Capital, customer, internal and maintenance projects usually need separate profiles. Two capital projects that differ only by plant do not.
Profile sprawl is expensive later. Every extra profile multiplies test cases, training variants and reporting exceptions. The SAP EPPM best practices for capital projects make the same point about templates.
Why does SAP PS configuration quality matter?
Configuration decides whether SAP PS controls projects or just records them. McKinsey found large projects typically run 20 percent late and up to 80 percent over budget. Budget profiles with live availability control and settlement profiles that close cleanly are the system side of preventing that.
Control systems are also how complex programmes stay auditable. The GAO Cost Estimating and Assessment Guide treats documented, repeatable cost control as basic discipline. In SAP PS, that discipline lives in configuration.
How does SaiSatwik configure SAP PS?
SaiSatwik starts SAP PS configuration with a project-type workshop, not the IMG. Finance, project controls and operations agree the types, then each gets one project profile, one set of templates and one settlement path. Configuration is documented per profile, so the next consultant can read why each setting exists.
The same approach runs on SAP S/4HANA and ECC through the SaiSatwik SAP practice. Official configuration documentation is on the SAP Help Portal. For a quick lookup of these and other codes, see the SAP PS transaction codes cheat sheet.
Related SaiSatwik Reading
More from the SAP PS series:
- What is SAP PS? A beginner guide. The objects this configuration controls.
- SAP PS in S/4HANA: key differences. What changes in configuration on S/4HANA.
- SAP PS Work Breakdown Structure explained. Designing structures the profiles support.
FAQs about SAP PS configuration
What is the first step in SAP PS configuration?
Confirm the finance and logistics prerequisites: company code, controlling area, profit centers, cost elements, plants and work centers. Within Project System itself, start with the coding mask and the profiles that the project profile will later reference.
What does the project profile control in SAP PS?
The project profile, maintained in OPSA, sets defaults for a project type and links the other profiles: planning, budget, settlement, network and status. Choosing a project profile when creating a project applies all of them at once.
Can SAP PS configuration be changed after go-live?
Yes, but carefully. Some settings apply only to new projects, while others affect existing ones immediately. Budget profile changes, for example, may need availability control reactivated with CJBV. Test every change on copies of live projects first.
How long does SAP PS configuration take?
It depends on the number of project types and integrations. A focused set of three or four project types typically takes a few weeks of configuration inside a larger implementation, with most effort spent on design workshops and testing, not on the settings themselves.
0 Comments