JinJin48

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

June 24, 2026 · 9 min read

SAP CO Operating Concern

The Operating Concern is the top-level organizational unit for SAP CO-PA (Profitability Analysis) that defines the dimensions and measures used to analyze company profitability. It is configured once per SAP system (or per business scope) and forms the analytical framework for all CO-PA reporting: which dimensions you can slice and dice by (Characteristics such as Customer, Product, Region, Sales Channel), and which financial measures you can analyze (Value Fields such as Revenue, Discounts, Cost of Goods Sold, Marketing Costs, Margin). The Operating Concern design is one of the most strategic and high-impact Customizing decisions in a CO-PA implementation.

Part 1: Operating Concern — Core Concepts (All Modules)#

1.1 What Is the Operating Concern?#

The Operating Concern is the analytical framework object of CO-PA. It defines the “data model” of Profitability Analysis: what dimensions exist, what measures are tracked, and which organizational entities are included. Every CO-PA line item (actual, plan, and statistical) references an Operating Concern and carries values for all defined Characteristics and Value Fields. The Operating Concern is assigned to a Controlling Area, linking it to the CO master data (Cost Centers, Profit Centers, Cost Elements) already defined.

1.2 Account-Based vs. Costing-Based CO-PA#

This is the most fundamental design decision in a CO-PA implementation.

Design principle: In S/4HANA, implement Account-Based CO-PA as the primary reporting basis. Implement Costing-Based CO-PA only if there is a specific, documented business requirement that cannot be met with Account-Based CO-PA (typically: the need for cost component split reporting in a format that differs from the Cost Component Structure). The reconciliation and maintenance overhead of Costing-Based CO-PA in addition to Account-Based is substantial — confirm the requirement with the CFO and management reporting team before committing to both types.

1.3 Organizational Levels and Data Hierarchy#

Operating Concern sits at the top of the CO organization, above the Controlling Area. One Operating Concern can carry multiple Controlling Areas (1 : N).

Data hierarchy with a concrete example

Operating Concern "S001"       CO-PA scope · 1 : N CO Areas
   │
   └── Controlling Area "1000"     CoA · Fiscal-Year Variant · JPY
          ├── Company Code "1000"   Japan HQ
          └── Company Code "2000"   Japan Sub

Design principle: One Operating Concern per corporate group is the common design — sharing it across every Controlling Area keeps CO-PA reporting consistent group-wide. Split into multiple Operating Concerns only when business units genuinely need different Characteristics or currencies for profitability analysis.

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 Operating Concern Definition (TKE1)#

2.2 Characteristics and Value Fields#

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction