JinJin48

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

June 26, 2026 · 10 min read

SAP PM Characteristic

A Characteristic is the atomic unit of the SAP Classification System — it defines a single named attribute, its data type, and the rules governing what values it may hold. In Plant Maintenance, Characteristics are assigned to Classes of type 002 (Equipment) or type 003 (Functional Location), and their values are populated on individual Equipment and Functional Location records to enable attribute-based search, grouping, and reporting. This article covers the full structure of a Characteristic from general data through value restriction settings, and explains the field-level decisions PM consultants make in CT04.

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

1.1 What Is the Characteristic?#

A Characteristic is a metadata template that declares an attribute — its name, data type, unit of measure, and permissible values — without yet being attached to any specific object. Once created, it is assigned to one or more Classes, and those Classes in turn are assigned to technical objects (Equipment, Functional Locations) or other SAP objects (Material, Batch, Variant). The value is filled at the object level, not inside the Characteristic itself.

1.2 Characteristic Data Types#

The data type chosen at Characteristic creation is permanent — it cannot be changed after values have been assigned to objects. Selecting the wrong type causes mismatches in search and reporting logic, so this decision must be made deliberately during blueprint.

Design principle: For PM Equipment attributes that need range-based search (e.g., “all pumps with max pressure between 50 and 100 MPa”), always use Numeric type with a unit of measure — Character type cannot support range queries.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Client
   │
   ├── Class "PUMP_TYPE"
   │      Class Type 002 (Equipment)
   │      │
   │      └── Characteristic "MAX_PRESSURE"
   │             Numeric, Unit MPa — contained in the Class above
   │             │
   │             └── Allowed Values
   │                    Optional restriction — e.g. permitted value list
   │
   ├── Equipment 10001234
   │      Centrifugal Pump #3, Cooling Water Circuit
   │      ── assigned to ──> Class "PUMP_TYPE"
   │      MAX_PRESSURE = 6.5 MPa
   │
   └── Functional Location 1000-A-01
          Pump House, Line 1
          ── assigned to ──> Class "PUMP_TYPE"
          MAX_PRESSURE = 6.0 MPa

1.4 Integration with Other Master Data Objects#

A Characteristic does not stand alone — its value is only meaningful in the context of an object to which a Class containing that Characteristic has been assigned. The integration chain is Characteristic → Class → Object.

Part 2: PM-Specific Field Details#

2.0 Scope of PM Ownership#

Legend: ◎ = Owner / Critical

2.1 Basic Data#

The Basic Data tab in CT04 contains the structural definition of the Characteristic. These fields control how values are stored and how the Characteristic behaves across all systems that use it.

2.2 Values#

The Values tab (only active when the Characteristic has “With Allowed Values” checked) defines the fixed list of permissible entries. For Numeric Characteristics, a value range (from/to) can be set instead of a discrete list.

2.3 Descriptions#

The Descriptions tab stores multilingual text for the Characteristic itself. This text appears as the label in classification views on Equipment and Functional Location screens.

2.4 Restrictions#

The Restrictions tab controls which Class types and object types may use this Characteristic. Without restrictions, a Characteristic created for PM Equipment can inadvertently be used in Variant Configuration or Batch Management, polluting those domains.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction