Classification: characteristics that make objects findable

Master record fields cover what every object has in common. But a compressor has a rated pressure, a motor has a power rating, and a winding machine has a maximum wire gauge. SAP's classification system adds those object-specific attributes without custom fields. You define characteristics (such as POWER_KW or RATED_PRESSURE_BAR), group them in a class (such as MOTOR or COMPRESSOR), and assign the class to the technical object, where users fill in the values.

Class types

Classes belong to a class type, which decides which kind of object they can classify. In the standard system, equipment classes and functional location classes use separate class types (commonly 002 for equipment and 003 for functional locations); check the class types configured in your system before you build test data. Classes are maintained with CL01 and CL02, characteristics with CT04. On the technical object, the class sits in the General view, and the characteristic values are entered there.

Why it matters

• Search: find every compressor rated above 10 bar, or every 15 kW motor, without knowing their numbers.
• Reporting: compare breakdowns by manufacturer or power class rather than by individual machine.
• Spare parts: identify interchangeable units, such as motors with the same frame size and voltage.
• Consistency: characteristic value checks stop users from typing "15kw", "15 KW" and "fifteen".

Classification is master data like any other, and it decays the same way. A class that nobody fills in is worse than no class at all, because searches return incomplete results that look complete. Contoso's rule is to classify only the object types where planners actually search by attribute: motors, compressors and pumps. Each class has an owner in Rosa's team.

Classification in day-to-day work

Planners mostly meet classification through search. In the equipment value help and list reports, they can search by class and characteristic values rather than by number or description. A planner who needs a replacement motor during a breakdown opens the search, selects class MOTOR, enters POWER_KW = 15 and FRAME_SIZE = 160M, and gets a list of every matching motor, installed or in stock. Combined with the usage list, that tells her which units are free.

Characteristics can carry rules as well as values: allowed value lists, numeric ranges, units, and whether a value is required. Use them. A required characteristic with a value list catches a missing or wrong entry at the moment the record is saved, which is far cheaper than finding it during an audit or a breakdown. When testing, include at least one negative check: try to save a motor with an invalid power value and confirm the system refuses it.

Classification also matters in a conversion because it lives in its own tables. Contoso's mock conversions showed that classification values came across correctly, but one custom report that read characteristic values directly from the database needed adapting by Kenji's team. That is the kind of finding a field-by-field sample comparison is designed to catch.

Walkthrough: making motors findable

1. Create characteristics with CT04: POWER_KW (numeric, 5 digits, 2 decimals, unit kW, required), VOLTAGE (value list 230, 400, 480), FRAME_SIZE (character, value list).
2. Create class MOTOR with CL02 in the equipment class type and assign the three characteristics.
3. Assign class MOTOR to the in-scope motor records in their General view and fill in the values; for many records, use a mass maintenance or migration approach rather than typing.
4. Search: in the equipment list (IH08) or value help, select by class MOTOR with POWER_KW = 15 and FRAME_SIZE = 160M. Compare the hit list with Rosa's manual count.
5. Negative test: try to save a motor with VOLTAGE = 500. The value check must refuse it.