TutorialKart.comSAP PS (Project System) is an SAP application component used to plan, execute, monitor, and close projects. It brings project structures, dates, resources, procurement, costs, budgets, revenues, and settlement into the same business system used for finance, logistics, sales, maintenance, and human resources.
This SAP PS tutorial explains the project structure, core master data, planning and execution flow, integration points, commonly used transactions, and configuration areas. The available functions and screen names can differ between SAP ERP and SAP S/4HANA releases, so system-specific steps should be checked against the documentation for the installed product.
What is SAP PS Project System?
SAP PS is designed for business activities that have a defined objective, organizational responsibility, schedule, and financial scope. A project can be divided into hierarchical and operational elements so that planners can assign work, estimate costs, procure materials or services, record progress, and compare actual results with approved plans.
SAP PS is used for projects such as plant construction, equipment installation, research and development, capital investment, engineering services, customer projects, shutdown work, and complex internal initiatives. The applicable design depends on whether the project primarily controls costs, produces an asset, bills a customer, coordinates operational work, or combines several of these purposes.
SAP provides official documentation for Project System in SAP S/4HANA and a learning course covering the basics of SAP S/4HANA Project System.
SAP PS project structure: project definition, WBS, networks, and activities
An SAP PS project is represented through related structural objects. Each object has a specific planning and control purpose.
| SAP PS object | Purpose | Typical information |
|---|---|---|
| Project definition | Identifies the overall project and provides project-wide control data | Project profile, company code, controlling area, organizational assignments, dates, and status |
| Work Breakdown Structure element | Divides the project into hierarchical deliverables, phases, or responsibility areas | Responsible organization, planned costs, budget, account assignment, billing relevance, and settlement rules |
| Network | Models the operational sequence of project work | Network profile, scheduling parameters, relationships, capacity requirements, and costing data |
| Network activity | Represents a task or work package within a network | Duration, work, work center, control key, materials, services, costs, and confirmations |
| Activity element | Adds detailed internal, external, service, or cost-related planning to an activity | Resources, purchasing information, quantities, values, and dates |
| Milestone | Marks a significant project event or decision point | Milestone date, usage, progress relevance, and linked business functions |
The Work Breakdown Structure, or WBS, answers what the project contains and how responsibility or financial control is divided. Networks and activities answer how and when the work will be performed. A project may use only a WBS for financial control or combine the WBS with networks for detailed scheduling and execution.
SAP PS Work Breakdown Structure and WBS elements
The Work Breakdown Structure organizes a project into levels. The top level may represent the complete project, while lower levels represent phases, deliverables, locations, disciplines, or responsibility units. The structure should support both operational reporting and financial control without becoming more detailed than the business process requires.
A WBS element can act as an account-assignment object. Costs from purchasing, inventory movements, internal activities, invoices, and other postings can be assigned to it when the relevant controls permit. Depending on the project design, a WBS element may also carry budget, receive revenue, support billing, or settle accumulated values to another object.
Common WBS control indicators include:
- Planning element: permits planning at the WBS element where applicable.
- Account assignment element: permits actual postings to the WBS element.
- Billing element: identifies an element relevant to billing in an appropriately configured customer-project process.
- Statistical indicator: controls whether the WBS is used for statistical reporting rather than as the real cost object.
The available indicators and their effects depend on the project type and system configuration. They should be defined as part of the project template or creation procedure rather than changed without understanding the accounting consequences.
SAP PS networks, activities, and relationships
A network describes the operational flow of project work. Its activities may represent internal work, externally processed work, purchased services, or general cost activities. Control keys and related configuration determine which business functions apply to each activity.
Relationships connect activities and establish their logical order. Common relationship types include finish-to-start, start-to-start, finish-to-finish, and start-to-finish. Time intervals can be added where the business process requires a delay or overlap.
For example, foundation work may need to finish before equipment installation begins. Electrical work might start after part of the installation has progressed rather than waiting for the complete activity. Correct relationships allow scheduling to calculate feasible dates and identify dependencies.
SAP PS project profiles, coding masks, and templates
SAP PS uses profiles and organizational settings to provide default values and control project behavior. Important design elements include:
- Project profile: supplies default organizational data and links to planning, scheduling, budgeting, settlement, and status settings.
- Coding mask: defines the permitted format and hierarchy rules for project and WBS identifiers.
- Network profile: provides defaults and controls for networks and their processing.
- Standard project structure: provides a reusable WBS template.
- Standard network: provides a reusable template for activities and relationships.
- Project version: stores a project snapshot for comparison when version management is configured and used.
Templates reduce inconsistent project structures and repeated data entry. They should reflect stable project patterns while still allowing project-specific dates, quantities, responsibilities, and account assignments.
SAP PS project planning and execution lifecycle
A typical SAP PS process moves through project definition, planning, approval, execution, monitoring, and closure. The exact sequence depends on the project category and integrated modules.
- Create the project structure: Create the project definition, WBS elements, networks, activities, and milestones manually or from approved templates.
- Assign organizational data: Define the responsible company code, controlling area, profit center, plant, business area, responsible cost center, and project organization as required.
- Plan dates and resources: Enter basic dates, activity durations, relationships, work centers, work quantities, and capacity requirements.
- Plan costs and revenues: Estimate costs by value, activity, material, service, unit costing, or other supported planning methods. Plan revenues for applicable customer projects.
- Approve budget: Enter, distribute, release, supplement, transfer, or return budget according to the configured budgeting process.
- Release project objects: Apply the required system or user statuses so that operational postings and procurement can begin.
- Execute project work: Purchase materials and services, issue stock, confirm activities, record time, post invoices, and process other integrated transactions.
- Monitor progress and financials: Compare planned, committed, actual, and forecast values while reviewing dates, milestones, capacity, and exceptions.
- Settle project costs: Allocate eligible values to assets, cost centers, profitability segments, other projects, or supported receivers according to settlement rules.
- Close the project: Complete remaining procurement, finalise settlement, resolve open commitments, and set the appropriate completion or closure statuses.
SAP PS scheduling and milestone control
SAP PS scheduling calculates activity and network dates from durations, relationships, factory calendars, work center calendars, and scheduling parameters. Depending on the scenario, scheduling can be performed forward from a start date, backward from a finish date, or according to the configured planning method.
Basic dates are commonly maintained at project or WBS level, while networks provide detailed operational dates. Scheduling results may include earliest and latest dates, floats, and critical activities. Planners should review conflicts between manually entered dates and dates calculated from the network logic.
Milestones identify events such as design approval, procurement completion, site handover, or customer acceptance. Depending on configuration, milestones can support progress analysis or trigger related business functions. A milestone date should represent a defined and verifiable event rather than a loosely described phase.
SAP PS cost planning, budgeting, and availability control
Cost planning and budgeting are related but serve different purposes in SAP PS.
| Financial value | Meaning in SAP PS |
|---|---|
| Planned cost | The expected cost of performing the project work |
| Budget | The approved financial limit made available to the project |
| Commitment | A future obligation created by transactions such as purchase requisitions or purchase orders |
| Actual cost | A value already posted through goods movements, invoices, activity allocations, payroll-related processes, or other transactions |
| Assigned value | A value used by availability control, generally derived from actual costs and commitments according to configuration |
A project can be planned at different levels and through different methods. Detailed planning may originate from network activities, materials, services, work, and unit costing. Higher-level planning may use overall or annual values assigned directly to WBS elements.
Availability control compares assigned values with the available budget according to a configured tolerance profile. When thresholds are reached, the system can issue warnings or errors. Its behavior depends on activation, budget profile, tolerance limits, transaction groups, and other configuration; it should therefore be tested with each relevant posting process.
SAP PS procurement and material requirements
Project work often requires materials, external processing, and purchased services. SAP PS integrates these requirements with procurement and inventory processes.
- A material component can be assigned to a network activity where the process supports it.
- A requirement may be covered from existing stock or through project-specific procurement.
- External processing can create purchasing requirements for work performed by a vendor.
- Service activities can support procurement and recording of externally supplied services.
- Purchase requisitions, purchase orders, goods receipts, service entries, and invoices can create commitments or actual costs for project objects.
The chosen procurement method affects stock ownership, account assignment, valuation, material availability, and settlement. It must be aligned with the organization’s materials management and accounting design.
SAP PS confirmations and project progress tracking
Activity confirmations record the progress of operational work. A confirmation can include actual work, remaining work, actual dates, forecast dates, and completion information. Depending on integration and configuration, it may also result in internal activity allocation or other cost-related updates.
Progress should not be assessed from a single measure. A project can be financially under budget while operationally late, or show completed activities while invoices and commitments remain open. Effective monitoring combines:
- Basic and scheduled dates
- Activity confirmations and remaining work
- Milestone achievement
- Planned and actual costs
- Budget consumption
- Open commitments
- Material and service availability
- Revenue and billing status for customer projects
- Settlement and closure status
SAP PS status management and transaction control
Statuses control which business transactions are permitted for a project object. SAP PS uses system statuses set by standard processes and may also use configured user statuses.
Examples of lifecycle states include created, released, technically completed, closed, and deletion-related states. A project may need to be released before certain postings are permitted. Technical completion can restrict further operational processing while still allowing selected closing activities. Final closure generally requires open business transactions to be resolved.
User status profiles can add organization-specific controls, such as requiring an approval before procurement or preventing budget changes after a defined gate. Because status rules can block accounting and logistics transactions, their permitted and prohibited business processes should be documented and tested.
SAP PS settlement and capital investment projects
Settlement transfers eligible project costs from a sender object to one or more receivers. The receiver depends on the business purpose and configuration. Examples can include a cost center, fixed asset, asset under construction, profitability segment, sales order item, or another supported controlling object.
A settlement rule identifies the receiver, allocation method, share, and validity. Periodic settlement may transfer values during project execution, while final settlement completes the allocation at project closure. Errors can occur when settlement rules are missing, receivers are invalid, source costs are not eligible, or previous accounting steps are incomplete.
Capital investment projects commonly integrate SAP PS with Investment Management and Asset Accounting. Costs may first accumulate on WBS elements and then settle to an asset under construction or final fixed assets according to the approved accounting design.
SAP PS integration with other SAP modules
SAP PS does not operate as an isolated project-planning tool. Its main value in an SAP landscape comes from integrated operational and financial postings.
| SAP area | Typical SAP PS integration |
|---|---|
| Financial Accounting and Controlling | Actual costs, overhead, commitments, cost allocation, reporting, and settlement |
| Materials Management | Material requirements, purchase requisitions, purchase orders, goods movements, services, and vendor invoices |
| Sales and Distribution | Customer-project assignment, sales-related requirements, revenue planning, and billing processes |
| Production Planning | Production requirements and project-related manufacturing scenarios |
| Plant Maintenance | Coordination of maintenance work with project structures where the business process requires it |
| Human Capital or resource processes | Personnel-related planning, time recording, and labor-cost integration where implemented |
| Asset Accounting and Investment Management | Investment programs, capital budgets, assets under construction, capitalization, and settlement |
Difference between SAP PS and SAP PPM
SAP PS and SAP Portfolio and Project Management address different levels of project control, although an organization may integrate them.
| Comparison area | SAP PS | SAP PPM |
|---|---|---|
| Primary focus | Detailed operational and financial execution of projects | Portfolio selection, prioritization, governance, and higher-level project management |
| Core structures | Project definitions, WBS elements, networks, activities, and milestones | Portfolio items, initiatives, buckets, projects, phases, tasks, and related portfolio structures depending on the solution |
| Financial processing | Integrated costs, commitments, budgets, procurement, and settlement | Portfolio-level financial planning, comparison, and decision support |
| Operational logistics | Direct integration with purchasing, inventory, confirmations, and accounting | Generally focuses on portfolio and project-management functions rather than replacing detailed PS logistics processing |
In a combined design, SAP PPM can support the decision about which proposals or projects should proceed, while SAP PS can control detailed execution and accounting. Product scope and integration options vary by release and licensed solution.
Common SAP PS transaction codes
The following transaction codes are commonly associated with classic SAP PS processing. Their availability and recommended use depend on the installed release, authorizations, activated functions, and whether SAP Fiori applications are used.
| Transaction code | Typical purpose |
|---|---|
| CJ20N | Create and maintain project structures in Project Builder |
| CJ01, CJ02, CJ03 | Create, change, or display a project definition |
| CJ11, CJ12, CJ13 | Create, change, or display a WBS structure |
| CN21, CN22, CN23 | Create, change, or display a network |
| CJ30, CJ31, CJ32 | Maintain, display, or change project budget functions according to the available process |
| CJ40 | Cost planning for projects in applicable classic scenarios |
| CN25 | Display a project overview in supported systems |
| CN41N | Display project structures and related overview information |
| CN43N | Display project definitions through the relevant overview report |
| CN48N | Display confirmations for project network activities |
| CJ88 | Perform individual project settlement |
| CJ8G | Perform collective project settlement |
Transaction lists should not be treated as a process design. A transaction may expose functions that are restricted by status, configuration, or authorization. Users should follow the organization’s documented role and procedure.
SAP PS configuration areas
SAP PS configuration should begin with defined business scenarios rather than isolated settings. Important configuration areas commonly include:
- Project and WBS coding masks
- Project profiles and default organizational assignments
- Network types, network profiles, control keys, and scheduling parameters
- Field selection and screen controls
- User status profiles and business transaction controls
- Planning profiles and cost-planning settings
- Budget profiles, availability control, and tolerance limits
- Settlement profiles, allocation structures, and settlement strategies
- Progress analysis, milestone usage, and project versions
- Material, external-processing, and service procurement integration
- Revenue, sales-order, and billing integration for customer projects
- Investment profiles and asset-accounting integration for capital projects
Configuration changes can affect financial postings and cross-module processes. They should be tested with complete scenarios covering project creation, release, procurement, confirmations, actual postings, settlement, and closure.
SAP PS reporting and project-control checks
SAP PS reporting can present project structures, dates, costs, revenues, budgets, commitments, and statuses. Reports and SAP Fiori applications available to a user depend on the product release, activated content, authorizations, and analytical design.
A project review should answer specific control questions:
- Are the current forecast dates consistent with the required completion date?
- Which activities have zero progress, insufficient confirmation, or negative float?
- Which milestones are overdue or forecast late?
- How do planned costs compare with commitments and actual costs?
- Is sufficient budget available for pending procurement and postings?
- Which purchase requisitions, purchase orders, goods receipts, invoices, or service entries remain open?
- Are settlement rules complete and are any costs still unsettled?
- Can the project be technically completed or closed without blocking required follow-up work?
SAP PS learning path for consultants and project users
A practical SAP PS learning sequence should combine structure, scheduling, logistics, and accounting:
- Learn the purpose of the project definition, WBS elements, networks, activities, relationships, and milestones.
- Create a small project from a standard template and review inherited profile settings.
- Plan dates, work, materials, services, costs, and revenues for a controlled example.
- Study project statuses and observe which transactions become permitted after release.
- Create procurement requirements and trace commitments through purchase order, receipt, and invoice processing.
- Confirm operational activities and compare scheduled dates with actual progress.
- Enter and release a budget, then test availability control with approved scenarios.
- Review planned, committed, and actual values through project reports.
- Create valid settlement rules and run periodic and final settlement in a test environment.
- Complete the project while checking open commitments, balances, statuses, and accounting requirements.
- Continue with customer projects, investment projects, progress analysis, SAP Fiori applications, and configuration relevant to the target role.
SAP PS module FAQs
What does PS mean in SAP?
PS means Project System. SAP PS is used to structure projects and control their schedules, resources, procurement, costs, budgets, revenues, progress, and settlement within an integrated SAP environment.
What is a WBS element in SAP PS?
A WBS element is a node in the project’s Work Breakdown Structure. It can represent a phase, deliverable, location, responsibility area, or financial control point. Depending on its settings, it can receive plans, budgets, commitments, actual costs, revenues, and settlement rules.
What is the difference between a WBS element and a network activity?
A WBS element structures the project by scope, responsibility, or financial control. A network activity represents operational work with duration, relationships, resources, material requirements, confirmations, and scheduling information. Activities can be assigned to WBS elements.
What is the difference between SAP PS and SAP PPM?
SAP PS focuses on detailed project execution and integration with finance and logistics. SAP PPM focuses more broadly on portfolio selection, prioritization, governance, and higher-level project management. Organizations may integrate them instead of treating them as direct substitutes.
Which SAP modules integrate with SAP PS?
SAP PS commonly integrates with Financial Accounting, Controlling, Materials Management, Sales and Distribution, Production Planning, Plant Maintenance, Asset Accounting, Investment Management, and resource or time-recording processes. The exact integration depends on the project scenario and system design.
SAP PS tutorial editorial QA checklist
- Verify that project definitions, WBS elements, networks, activities, activity elements, and milestones are described as distinct SAP PS objects.
- Keep planned cost, budget, commitment, actual cost, and assigned value separate in all financial explanations.
- Confirm each SAP PS transaction code against the target SAP ERP or SAP S/4HANA release before publishing procedural instructions.
- State whether each process applies to internal, customer, investment, maintenance, or other project types.
- Check that status instructions explain the effect on procurement, postings, confirmations, settlement, and closure.
- Validate SAP PS integration steps end to end with the relevant FI, CO, MM, SD, PP, PM, AA, or IM process owner.
- Verify availability-control examples against the configured budget profile, tolerance limits, and transaction groups.
- Check settlement guidance for valid receivers, allocation structures, settlement profiles, source structures, and accounting periods.
- Distinguish SAP PS operational execution from SAP PPM portfolio-level planning and governance.
- Test all configuration and transaction steps in a non-production system using the same release and business scenario described in the tutorial.