JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 11 min read

Cover: SAP PP Class — master data defining the classification hierarchy that connects Characteristics to Materials

SAP PP Class

The Class is the master data object that defines a classification category and groups SAP objects — primarily materials — by shared properties. It acts as the container in the Classification System (CA), holding Characteristics that describe the attributes relevant to a given group. In Production Planning, Classes are used to enable material search by attribute, manage variant configuration for make-to-order products, and support reporting groupings beyond the standard material type hierarchy. This article covers Class core concepts across all modules in Part 1, and PP-specific field details in Part 2.


Part 1: Class — Core Concepts (All Modules)

1.1 What Is the Class?

Hub-and-spoke diagram showing Class at center, connected to Characteristic, Material Master, Variant Configuration, Batch, Customer, and Equipment

A Class is a named category that bundles a set of Characteristics and can be assigned to SAP objects such as materials, batches, customers, equipment, or documents. The Classification System (transaction CL01) is a cross-application framework used throughout S/4HANA; its scope far exceeds PP, but PP is the module that most commonly establishes Classes as part of production master data setup.

AspectDetails
RoleGroups SAP objects by shared attributes; enables attribute-based search, variant configuration, and reporting
Modules using itPP (Classification setup, variant configuration), MM (material search, batch classification), QM (inspection characteristics), PM (equipment/functional location classification), SD (customer classification, variant configuration)
TransactionsCL01 (Create) / CL02 (Change) / CL03 (Display) / CL20N (Assign class to objects) / CL30N (Find objects in class)
Key TablesKLAH (Class header), KSML (Characteristic assignment to class), AUSP (Characteristic values on objects), INOB (Object — class link)
S/4HANA noteClassification data model is unchanged from ECC. Fiori app “Manage Classes” (F2286) is available for basic maintenance; complex variant configuration work still uses transaction-based tools (CU41, CU50).

1.2 Class Types

Matrix comparing the principal SAP class types: 001 (Material), 010 (Batch), 022 (Equipment), 023 (Functional Location), 300 (Variant Configuration)

The Class Type determines which SAP object category can be assigned to the class and which business scenarios are enabled. Selecting the wrong Class Type creates an incompatible assignment that the system will reject at object classification time.

Class TypeCodeUse CaseKey Behavior
Material Class001Classify materials for search, grouping, and variant configurationMost common in PP/MM. Objects assigned are material numbers (MARA). Enables material attribute search (CL30N) and VC configuration profiles.
Batch Classification010Classify batch-managed materials with batch-specific attribute valuesUsed in QM, PP, and MM for batch-level traceability. Characteristics can carry values at the individual batch level, not just at the material level.
Equipment Class022Classify PM equipment objectsCommon in PM and asset management. Enables equipment attribute search and structured maintenance data.
Functional Location Class023Classify PM functional locationsUsed alongside Equipment Class to organize plant topology.
Variant Configuration Class300Define configurable product structures in SD/PPSpecial class type for VC. Configuration profiles (CU41) reference Class 300 to determine which characteristics are relevant for order configuration. Not interchangeable with Class Type 001.

Design principle: Class Type must be aligned with the object category during blueprint. A Class of Type 001 can never be assigned to a batch; Class Type 010 is required for that purpose. For variant configuration, Class Type 300 must be created in addition to — not instead of — Type 001 material classes.


1.3 Organizational Levels and Data Hierarchy

Hierarchy diagram showing Class containing a Characteristic, with Material assigned to the Class

Data hierarchy with a concrete example

Client
   │
   ├── Class "STEEL_GRADE"
   │      Class Type 001 (Material)
   │      │
   │      ├── Characteristic "TENSILE_STRENGTH"
   │      │      Numeric, Unit MPa
   │      ├── Characteristic "MATERIAL_GRADE"
   │      │      Character, S355
   │      └── Characteristic "COATING_TYPE"
   │             Character, Galvanized
   │
   └── Material RM-2001
          Steel Coil, Grade S355
          ── assigned to ──> Class "STEEL_GRADE"
          TENSILE_STRENGTH = 355 MPa
          MATERIAL_GRADE = S355
          COATING_TYPE = Galvanized

1.4 Integration with Other Master Data Objects

Hub-and-spoke showing Class at center connected to Characteristic, Material Master, Production Version, Variant Configuration Profile, and Batch

The Class does not stand alone. It is the container that links Characteristics to SAP objects, and its design decisions cascade into variant configuration, material search, and quality management.

ObjectRelationshipPractical Notes
Characteristic (CT04)Characteristics are assigned to the Class via KSMLA Class without Characteristics carries no attribute information. The Characteristic defines the data type, allowed values, and search behavior; the Class determines which object category uses them together.
Material MasterMaterials are classified into a Class via CL20N or MM02 (Classification view)The Classification view in the Material Master (MM02) is the most common entry point for assigning a material to one or more classes. A material can belong to multiple classes of the same or different types.
Production VersionIn variant configuration, the configuration profile references a Class 300The VC configuration profile (CU41) links the configurable material to a Class 300 object class, from which the system derives the dependency rules governing BOM item and Routing operation selection.
Batch Master (MSC1N)Batch Classification uses a Class of Type 010 to store batch-level valuesIn pharmaceutical or process industries, batch characteristics (e.g., potency, expiry date) are stored as classification values on the individual batch, enabling batch-level traceability and search.
QM Inspection CharacteristicsQM can map inspection results to classification characteristicsAllows quality results to be stored in a structured, searchable form rather than free text — enabling cross-batch or cross-material quality reporting.

Part 2: PP-Specific Field Details

2.0 Scope of PP Ownership

Checklist showing PP consultant ownership across Class data sections: Class Header, Characteristic Assignment, Material Assignment, and Classification Values

Data SectionPP InvolvementNotes
Class Header (KLAH)◎ OwnerClass name, type, status, validity, and description are defined by PP during Classification setup
Characteristic Assignment (KSML)◎ OwnerPP defines which Characteristics belong to the class; Characteristics themselves are maintained in the companion article PP-A06-02
Material Assignment◎ OwnerPP assigns materials to classes during master data migration and ongoing maintenance
Classification Values (AUSP)◎ OwnerPP populates characteristic values on each classified material
Batch Classification○ Shared with QM / MMBatch-level classification design is shared with QM (inspection) and MM (batch management); PP provides production-context requirements
Variant Configuration○ Shared with SDClass 300 for VC is co-owned by PP (production BOM/Routing dependency rules) and SD (sales order configuration); requires joint blueprint

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


2.1 Class Header (KLAH)

Checklist of key KLAH class header fields: Class Name, Class Type, Status, Validity, Description, Keywords, Same Classification flag

The Class Header is the top-level definition of the classification category. It must be created and released before any Characteristics can be assigned or objects classified.

FieldDescriptionPractical Usage
Class NameAlphanumeric key identifying the classActs as the primary identifier. Naming conventions are critical at blueprint — common patterns are functional prefix + running number (e.g., PP_MACH_001 for machine-type materials). Poor naming conventions create maintenance debt in large classification landscapes.
Class TypeNumeric code determining which object category this class applies toSee Section 1.2. Must be set at creation and cannot be changed afterward. For PP standard classification, Type 001 (Material) is the default. For VC, Type 300 must be used separately.
StatusLifecycle status of the class (1 = Released, 0 = In Preparation)Only Released classes can be used in object assignment and search. A common go-live issue is migration data loading into classes still in status 0. Set to 1 before production data migration.
Valid From / Valid ToDate range for class validityControls the period during which the class can be used for classification. Leave Valid To blank for open-ended classes. Use date ranges only when a classification scheme is planned to be retired and replaced.
DescriptionShort text description of the classDisplayed in classification screens and search results. Should be self-explanatory to business users — not just system architects. Translations to local languages (e.g., Japanese) can be maintained for user-facing display.
KeywordsAdditional search terms associated with the classEnables finding the class by synonym or alternative terminology in CL30N searches. Useful when business teams use different names for the same concept across departments or plants.
Same ClassificationFlag controlling whether multiple assignments of the same object are allowedWhen checked, the same object (e.g., same material) can be classified in the same class multiple times with different characteristic values. Rarely used in PP standard classification; relevant for batch or document classification scenarios.

2.2 Characteristic Assignment (KSML)

Stack layered diagram grouping characteristic assignment fields by category: Characteristic identity, display order, required indicator, and search relevance

The Characteristic Assignment section defines which Characteristics are bundled into this Class and in what order they appear on classification screens. This is maintained in transaction CL02 (change class) under the “Characteristics” tab.

FieldDescriptionPractical Usage
Characteristic NameInternal name of the Characteristic to be includedReferences the Characteristic master defined in CT04 (see PP-A06-02). Only Characteristics with status “Released” can be added. Attempting to add an unreleased Characteristic causes a system error at save.
Sort PositionDisplay order of the Characteristic within the class screenDetermines the left-to-right / top-to-bottom sequence on the classification entry screen. Group related characteristics together (e.g., all dimensional attributes before weight attributes) to reduce user errors and improve data entry speed.
Required EntryFlag marking the Characteristic as mandatory for classificationWhen set, the system prevents saving an object classification record unless a value is provided for this Characteristic. Use for attributes that are genuinely critical — over-use of required flags creates maintenance friction during mass data uploads.
SearchableFlag enabling this Characteristic to be used as a search criterion in CL30NControls whether business users can filter objects by this attribute in the Find Objects in Class transaction. Set for all Characteristics that will drive operational search (e.g., material type, dimension range). Characteristics not flagged as searchable still store values but cannot be used as filter criteria.

2.3 Material Assignment

Comparison two-column layout showing Material Assignment via MM02 Classification view versus CL20N batch assignment

Material Assignment records which specific materials belong to this Class. In PP, this is the step that makes a material searchable by its classification attributes and eligible for variant configuration.

FieldDescriptionPractical Usage
Object TypeCategory of the SAP object being classified (e.g., MARA = Material)Always MARA for material classification. The class type (001) enforces this — the system only accepts material numbers for Type 001 classes.
Object Key (Material Number)The MATNR of the material being assigned to the classEntry point via MM02 (Classification view) or CL20N (mass assignment). For initial data migration, CL20N or LSMW/BAPI_OBJCL_CREATE is used for bulk assignment — individual MM02 entry is impractical for large material catalogs.
Multiple Class AssignmentA material can belong to more than one classA material may be assigned to a process-capability class, a dimensional class, and a material-type class simultaneously. Each assignment stores its own characteristic values. Avoid redundant overlapping classes that store the same attribute in multiple places — this creates data inconsistency risk.
Validity (if applicable)Date-range on the object assignmentAvailable for certain class types. For standard Material Class 001, assignment is typically open-ended (no validity date). For Batch Classification, the batch’s own shelf-life dates govern validity rather than the class assignment.

2.4 Classification Values (AUSP)

Checklist showing classification value entry fields: Characteristic value types (single, multiple, numeric range), value source (direct entry vs. table lookup), and inheritance behavior

Classification Values are the actual attribute values stored on each classified material — for example, “Color = RED” or “Weight = 2.5 kg.” They are maintained on the individual material’s Classification view in MM02, or in bulk via CL20N.

FieldDescriptionPractical Usage
Characteristic Value (Single)A single allowed value for a Characteristic on this materialFor Characteristics defined with a fixed value list (e.g., Surface Finish = POLISHED / MATTE / RAW), enter one of the predefined allowed values. The system validates against the allowed value list defined in CT04 — entries outside the list are rejected.
Characteristic Value (Multiple)Multiple allowed values assigned simultaneouslyA Characteristic can hold more than one value on a single object if the Characteristic is defined as multi-value (CT04 setting). Example: a material certified for multiple industry standards can carry each standard code as a separate value.
Numeric Value / RangeNumeric entry with optional upper/lower boundFor Characteristics with numeric data type (e.g., Diameter = 50 mm). Numeric range assignment (e.g., 45–55 mm) is possible when the Characteristic allows interval values. Used in CL30N to filter materials by dimensional range — a key scenario in make-to-order environments.
Characteristic Value InheritanceValues can be inherited from a superior class in a class hierarchyWhen a class hierarchy is defined (CLHI), lower-level classes can inherit characteristic values from parent classes. Relevant in complex variant configuration or equipment hierarchy scenarios; less common in standard PP Classification.
Value Language DependencyDescription text of the value is language-dependentThe value key itself (e.g., RED) is language-independent, but the description displayed on screen is maintained per logon language. Ensure all relevant languages are maintained before go-live in multi-language deployments (e.g., JP + EN).

L1) Big Picture

IDCategoryTitle
pp-001OverviewWhat is SAP PP?

L2-A) Master Data

IDCategoryTitle
pp-a01OverviewSAP PP Master Data: Overview, Hierarchy & Relationships
pp-a02-01Master DataSAP PP Material Master
pp-a02-02Master DataSAP PP MRP Controller
pp-a03-01Master DataSAP PP Work Center
pp-a04-01Master DataSAP PP Bill of Materials (BOM)
pp-a04-02Master DataSAP PP Routing
pp-a05-01Master DataSAP PP Production Version
pp-a06-01Master DataSAP PP Class 📍
pp-a06-02Master DataSAP PP Characteristic

L2-B) Transaction

IDCategoryTitle
pp-b01OverviewSAP PP Transactions: Process Flow, Hierarchy & Relationships