JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 27, 2026 · 10 min read

SAP PS Project Definition

The Project Definition is the header master data object that represents the entire project in SAP Project System. It stores the project-level control parameters, scheduling dates, and organizational assignments that cascade down to every WBS Element and Network beneath it. Created from a Project Profile (Phase 1 Customizing), the Project Definition acts as the mandatory root of the PS master data hierarchy — nothing in Phase 2 or Phase 3 can exist without it. The rest of this article covers its types, org-level scope, field-by-field detail, and integration with CO and FI.

Part 1: Project Definition — Core Concepts (All Modules)#

1.1 What Is the Project Definition?#

The Project Definition is a single header record that identifies and controls a project as a whole — it is not a cost object in itself, but it sets the rules under which all cost objects (WBS Elements, Networks, Activities) underneath it operate. Every project in SAP PS has exactly one Project Definition.

1.2 Project Types#

The Project Type, inherited from the Project Profile, determines the business scenario the project serves and activates or restricts certain downstream functions. Choosing the wrong type at the start forces a project deletion and re-creation — it cannot be changed after WBS Elements are created.

Design principle: Project Type is locked once WBS Elements are created. Determine the correct type in the blueprint phase and enforce it via Project Profile assignment.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Controlling Area 1000
   │
   └── Project Definition PROJ-2026-001
          Plant Expansion — Line 3 Capacity Increase
          Type: Investment (01), 2026-01-01 – 2027-06-30
          │
          ├── WBS Element PROJ-2026-001.1
          │      Civil Works — Profit Center PC-1000-MFG
          │      ── linked via ──> Network Activity (below)
          │
          └── Network 4500001234
                 Mechanical Installation
                 │
                 └── Activity 0010
                        Install Conveyor Frame
                        ── assigned to ──> WBS Element PROJ-2026-001.1
                        │
                        ├── Activity Element 0010/1
                        │      Torque Verification Checklist
                        │
                        ├── Milestone MS-010
                        │      Customer Acceptance Checkpoint
                        │
                        └── ── consumes ──> BOM Item 0010 (Component RM-2001)

1.4 Integration with Other Master Data Objects#

The Project Definition does not stand alone — it derives its control parameters from the Project Profile and propagates constraints downward to every WBS Element and Network it governs.

Part 2: PS-Specific Field Details#

2.0 Scope of PS Ownership#

Legend: ◎ = Owner / Critical

2.1 Basic Data#

Basic Data fields identify the project and assign its primary organizational responsibility. The project number is the key that links all PS objects and appears as the root of every WBS code — a well-designed naming convention here pays dividends across the entire project lifecycle.

2.2 Control Data#

Control Data fields drive the behavioral characteristics of the project — they determine which planning functions are available, whether budget checks are enforced, and which user statuses the project can pass through. Most of these default from the Project Profile but can be overridden at the Project Definition level for exceptional cases.

2.3 Dates#

The Project Definition holds the outermost date frame for the entire project. WBS Element and Network dates must fall within this frame — the system issues a warning (configurable to an error) if child object dates exceed the Project Definition’s boundary dates. Accurate date maintenance at header level is therefore critical for scheduling integrity.

2.4 Organizational Assignment#

Organizational Assignment fields link the project to the SAP system’s financial and controlling structure. These fields are typically inherited from the Project Profile and locked as soon as WBS Elements are created — changing them later requires a new project.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction