JinJin48

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

June 27, 2026 · 13 min read

SAP PS Activity

The Activity (table AFVC) is the individual work package within a Network. Where the Network defines the overall framework for scheduling and cost collection, the Activity holds the operational detail — the Control Key that governs its processing type, the Work Center that supplies capacity, the planned duration and dates, and the predecessor/successor relationships that form the project schedule. Every internal manufacturing operation, external service purchase, and cost-only posting in a network-based project flows through an Activity. This article covers Activity concepts applicable across all SAP modules that consume PS Networks, then dives into the field-level detail that PS consultants configure and maintain.

Part 1: Activity — Core Concepts (All Modules)#

1.1 What Is the Activity?#

An Activity is the atomic scheduling and cost-collection unit within an SAP PS Network. While the Network groups activities into a schedulable sequence, the Activity itself specifies what work is done, by whom (Work Center), how long it takes (duration), and how it is processed (Control Key). Activities carry predecessor and successor relationships that drive the critical-path calculation performed by the PS scheduling engine.

1.2 Activity Types by Control Key#

The Control Key is the most critical configuration decision for an Activity. It determines whether work is performed internally (using a Work Center), procured externally (generating a Purchase Requisition automatically), or tracked as a cost-only entry. Selecting the wrong Control Key causes incorrect procurement behavior and scheduling errors.

Design principle: Define the Control Key assignment rules in the blueprint phase. PS02 (External) activities require purchasing master data (vendor, PIR, or contract) to be available at release time; missing source data causes the PR to be created without a source, triggering manual buyer intervention.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Network 4500001234
   Line 3 Expansion — Mechanical Installation
   │
   ├── Activity 0010
   │      Install Conveyor Frame
   │      Control Key PS01 (Internal)
   │      ── assigned to ──> Work Center MECH-INST-01
   │      (inherits WBS Element from Network header)
   │
   ├── Activity 0020
   │      Align & Torque Conveyor Drive
   │      Control Key PS01 (Internal)
   │      ── assigned to ──> Work Center MECH-INST-01
   │      ── assigned to ──> WBS Element PROJ-2026-001.2 (override)
   │      │
   │      └── Activity Element 0020/1
   │             Torque Verification Checklist
   │
   └── Activity 0030
          Final Assembly Complete
          Control Key PS04 (Cost Activity — no Work Center)
          ── assigned to ──> WBS Element PROJ-2026-001.1

1.4 Integration with Other Master Data Objects#

The Activity integrates with a broad set of PS, CO, PP, and MM master data objects. Each integration point must be designed and tested during the blueprint and realization phases.

Part 2: PS-Specific Field Details#

2.0 Scope of PS Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Basic Data (Control Key, Description, Work Center)#

Basic Data defines the identity and processing type of the Activity. These fields are set when the Activity is first created and drive all downstream behavior — scheduling, procurement, and costing.

2.2 Scheduling Data (Duration, Dates, Relationships)#

Scheduling Data defines the time dimension of each Activity and the dependency chain that drives the network’s critical path calculation. These fields are the primary inputs for PS project scheduling (CN24, CN25).

2.3 Cost Data (Activity Type, Planned Costs)#

Cost Data links each Activity to the CO framework for planned and actual cost calculation. PS owns the Activity Type assignment; CO owns the rates and cost center planning.

2.4 External Processing Data (Purchase Data)#

External Processing Data applies only to PS02 (External Processing) and PS03 (Service) Activities. These fields control the automatic Purchase Requisition generated at Network release.

2.5 Account Assignment (WBS Element, Network)#

Account Assignment determines where actual costs (confirmations, goods receipts, invoices) are posted in the CO/PS module. The default is the parent Network, but activities can redirect costs to specific WBS Elements for granular project controlling.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction