JinJin48

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

June 24, 2026 · 6 min read

SAP CO Activity Type Group

The Activity Type Group is the hierarchical grouping structure that organizes Activity Types for reporting and allocation cycle definitions in SAP Controlling. Activity Types represent the services a Cost Center provides — machine hours, labor hours, kilowatt-hours, setups — and the Activity Type Group organizes these types into logical categories for management reporting, planning, and cycle sender definitions. A well-designed Activity Type Group hierarchy makes activity-based cost allocation reports readable and simplifies period-end cycle configuration.

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

1.1 What Is the Activity Type Group?#

The Activity Type Group is a set object in SAP CO that aggregates Activity Types under a shared label. Like Cost Element Groups and Cost Center Groups, it uses the SETHEADER/SETLEAF/SETNODE framework. Activity Type Groups are used primarily in CO-CCA reports (to show planned and actual activity quantities by category), in activity price planning (bulk price entry by group), and in allocation cycle definitions.

1.2 Group Structure Types#

Design principle: Keep Activity Type Groups simple. Unlike Cost Center Groups (which have a mandatory Standard Hierarchy), Activity Type Groups are entirely optional — create only what is needed for specific reporting or cycle requirements. Over-engineering the Activity Type Group hierarchy creates maintenance burden without proportional reporting benefit.

1.3 Organizational Levels and Data Hierarchy#

Activity Type Group is scoped at the Controlling Area level, consistent with the Activity Types it groups.

Data hierarchy with a concrete example

Controlling Area 1000
   │
   ├── AT Group "AT-PROD"          Production AT
   │
   └── Cost Center "C1100"         Press Line
          ├── Activity Type "MH-01"   Machine hrs
          └── Activity Type "LH-01"   Labor hrs

Design principle: Activity Type Groups aren’t mandatory — only create them when you need group-level reporting or a cycle sender/receiver definition spanning multiple Activity Types. For implementations with fewer than 20 Activity Types total, selecting them individually in reports is often simpler than maintaining groups.

1.4 Integration with Other Master Data Objects#

Part 2: CO-Specific Field Details#

2.0 Scope of CO Ownership#

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

2.1 Group Header#

2.2 Group Members#

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction