SAP SD MADE SIMPLE

Material Classification | Bill of Material (BOM) | Variant Configuration

A beginner-friendly, no-jargon guide explaining what these are,

why SAP needs them configured, and what breaks if you skip a step.

What you'll learn in this guide:

1. What "Configuration" actually means in SAP (in plain English)

2. Material Classification — tagging materials so the system can find/use them
3. Bill of Material (BOM) — the "recipe" of what goes into a product
4. Variant Configuration — how one material number can become 1000s of
custom products
5. Side-by-side differences between all three
6. A real-life example tying everything together (a made-to-order laptop)
7. Quick-reference T-code cheat sheet

SAP SD Guide — Classification, BOM & Variant Configuration | Page 1

 0. What Does "Configuration" Even Mean in SAP?
Before we touch Classification, BOM, or Variant Configuration, let's fix one word that confuses every
beginner: "Configuration." In normal English it means "setting something up." In SAP, it means exactly that
too — but at two very different levels. Don't mix them up.

Two meanings of "Configuration" in SAP

Type What it means Who does it Example

1. System / IMG Setting up the RULES of how SAP behaves for SAP Functional Deciding that Item
Configuration your company — done once, in the background, Consultant Category "TAN"
(a.k.a. "Customizing") using transaction SPRO. should not check
credit, or that
Sales Org 1000
uses Pricing
Procedure ZPR01.

2. Variant Building a PRODUCT that a customer can Consultant sets it A customer orders
Configuration customize at the time of sale (choose color, up; then a laptop and picks
(a product feature) size, RAM, etc.). Sales/Customer "16GB RAM, Black
uses it daily. color, 1TB SSD" in
the sales order
screen.

This guide covers both — Material Classification and BOM mostly rely on system configuration (rules set
up in the background), while Variant Configuration is itself a feature that is built using configuration steps.

Why does SAP need configuration at all?

SAP is delivered as a blank, generic system — like a brand-new smartphone before you set your language,
Wi-Fi, and apps. It works for EVERY industry (a chemical company, a car maker, a hospital, a bank), which
means, out of the box, it doesn't know anything specific about YOUR business.

■ Think of it like this: SAP without configuration is like a huge empty building with all electricity
and plumbing installed, but no rooms, no labels on doors, no furniture. Configuration is the work of
building rooms, putting name-plates, and deciding "this room is for accounts, this one for sales" —
so people (transactions/users) know where to go and what to do.

■ WHY THIS IS NEEDED

Configuration tells SAP things like: which company codes exist, how pricing should be calculated,
what data is mandatory before a sales order can be saved, how a product's components should be
assembled, and how a customer can customize a product. Without this, SAP simply does not know
YOUR business rules — it can't guess them.

■ WHAT HAPPENS IF YOU MISS / SKIP THIS

SAP SD Guide — Classification, BOM & Variant Configuration | Page 2

If a required configuration step is missing, SAP will usually not silently "guess" and move on. Instead
you get one of these three outcomes: (1) a hard error / red message stopping the transaction
completely (most common), (2) the system lets you proceed but with wrong or blank data (dangerous
— errors show up later, e.g. wrong billing, wrong shipment), or (3) a needed screen/field/button simply
does not appear at all, so users think a "feature is missing" when it's actually just not configured.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 3

 1. Material Classification

1.1 What is it?

Every material (product) in SAP has basic fields like material number, description, weight, etc. But what if
you want to search or group materials by things SAP didn't originally think of — like "color = Red", "voltage =
220V", "fabric = Cotton", or "shelf life = 12 months"? That's exactly what Classification does. It lets you
attach your OWN custom tags (called Characteristics) to materials, and group similar materials into a
Class.

■ Think of it like this: Classification is exactly like adding hashtags/labels to photos in your phone
gallery. Your phone doesn't natively know a photo is "a photo of a birthday cake" — but if you tag it
#birthday #cake, you can later search "birthday" and instantly find all such photos, even though
they have different file names. In SAP, Characteristics = the tags, and Class = the tag-group/folder.

1.2 The Building Blocks

• Characteristic (CT04) — a single custom attribute, e.g. "COLOR", "VOLTAGE", "FABRIC_TYPE".
You define what values are allowed (e.g. COLOR = Red / Blue / Green).

• Class (CL01/CL02) — a group/folder that bundles multiple Characteristics together, and has a "Class
Type" that tells SAP where this class can be used (Class Type 001 = Material Classification, Class
Type 200 = Batch, Class Type 300 = Variant Configuration).

• Classification assignment (done in MM01/MM02 "Classification" view, or CL20N) — this is

where you actually pick a class for a specific material and fill in real values (e.g. this exact material's
COLOR = Red).

1.3 Configuration Steps (in order)

Step What you do T-code

1 Create Characteristics — define the attribute name, data type, and allowed values CT04

2 Create a Class of Type 001 — group the characteristics under one class CL01

3 Assign the Class to the Material — go into the material master, Classification MM01 / MM02
view, and link it

4 Enter actual values for that material against each characteristic MM02 / CL20N

5 (Optional) Use classification in search helps, batch search, variant pricing, or MM60, CL30N
reporting

■ WHY THIS IS NEEDED

SAP SD Guide — Classification, BOM & Variant Configuration | Page 4

 Classification is the foundation for: searching/filtering materials by attributes (instead of remembering
thousands of material numbers), grouping materials for reporting and analytics, batch management
(e.g. classifying a batch of chemicals by purity %), and — very importantly — it is the SAME
underlying technology used to build Variant Configuration (Section 3). If you skip classification basics,
you cannot do Variant Configuration at all, because configurable characteristics are built the exact
same way.

■ WHAT HAPPENS IF YOU MISS / SKIP THIS

If characteristics/classes are not created or not assigned to a material: users cannot search materials
by attributes (they'll have to know exact material codes — painful in a plant with 50,000 materials);
batch classification and batch-specific reporting will not work; any downstream feature relying on
classification — like Variant Configuration or class-based pricing — will simply not function, since
there is nothing to "read" values from; and reports that group by classification data (e.g. "show all Red
products sold this month") will return blank or incomplete results.

1.4 Small Example

Material "SHIRT-001" is assigned to Class "Z_APPAREL" (Class Type 001) which has Characteristics
COLOR and SIZE. For this specific material, COLOR is set to "Blue" and SIZE is set to "L". Now a sales
user can go to MM60 (or a custom report) and search: "show me all materials where COLOR = Blue" — and
SHIRT-001 shows up, along with any other material tagged Blue, even if their material numbers look nothing
alike.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 5

 2. Bill of Material (BOM)

2.1 What is it?

A Bill of Material (BOM) is simply a structured LIST of everything that goes into making one finished
product — the components, sub-parts, and quantities needed. It answers the question: "If I want to build/sell
ONE unit of this finished product, what exactly do I need?"

■ Think of it like this: A BOM is a cooking recipe. To make "1 Chocolate Cake" (finished product),
the recipe lists: 2 cups flour, 1 cup sugar, 3 eggs, 1 cup cocoa powder (components + quantities).
SAP's BOM works exactly the same way, except the "cake" is your finished material and the
"ingredients" are component materials, each with its own material number and quantity.

2.2 Types of BOM relevant to SD

BOM Type Purpose Where it's used

Material BOM Standard production recipe — used by Production Orders, MRP

manufacturing/PP to build the finished product in-house.

Sales Order BOM A BOM that is exploded (broken into components) right Make-to-order scenarios, kits,
(item category TAQ) inside the SALES ORDER itself — each component bundles
becomes its own order line, can be priced/delivered
separately.

Sales BOM / "Set" A commercial "bundle" of items sold together as one Bundled product sales
(item category TAE entry, e.g. a gift hamper — main item is not
or similar) delivery-relevant, sub-items are.

Super BOM A BIG master BOM containing ALL possible Variant Configuration (Section
components across ALL variants of a configurable 3)
product; Object Dependencies later filter it down to the
correct components for one specific configuration.

2.3 Configuration Steps (in order)

Step What you do T-code

1 Define BOM Usage (e.g. "Production", "Sales and Distribution", "Universal") — OS20 / SPRO
controls which module can use this BOM

2 Create the actual BOM header + line items (components + quantities) for the CS01
finished material

3 Assign the correct Item Category Group to the finished material master (e.g. MM02, Material
ERLA for sales BOM, LUMF for structure explosion at delivery) Master "Sales:
Gen/Plant" view

SAP SD Guide — Classification, BOM & Variant Configuration | Page 6

 Step What you do T-code

4 Maintain Item Category Determination so SAP knows which item category to VOV4 (SPRO)
propose for the BOM header item and sub-items in a sales order (e.g. TAQ, TAE)

5 Set BOM explosion / structure scope relevant settings on Schedule Line VOV6 (SPRO)
Category (availability check per component or header)

■ WHY THIS IS NEEDED

BOM tells SAP exactly what physical components must be picked, packed, and shipped for one sales
order line, and in what quantity. Without a properly configured BOM: pricing cannot be calculated
correctly at the component level, delivery/picking will not know which individual parts to pull from the
warehouse, and availability checks (stock check) will be wrong because the system will check stock
for the wrong material (the "bundle" instead of the real components).

■ WHAT HAPPENS IF YOU MISS / SKIP THIS

If the BOM is missing, incomplete, or the item category/BOM usage settings are wrong: the sales
order may create only ONE line for the whole bundle with no component breakdown — meaning
warehouse staff won't know which individual parts to pick; delivery documents will be incomplete or
wrong (missing components), leading to customer complaints or partial shipments; pricing may be
calculated at the wrong level (e.g. one blanket price instead of summing accurate component prices),
causing revenue leakage or overcharging; and for configurable products (Section 3), if the Super BOM
is missing or not linked, Variant Configuration cannot determine which components to include AT ALL
— the configuration profile will show characteristics, but nothing will explode into the order or
production order.

2.4 Small Example

Finished product "GIFT-HAMPER-01" has a Sales BOM with 3 components: 1x Chocolate Box, 1x Wine
Bottle, 1x Greeting Card. When a customer orders 2 Gift Hampers, the sales order explodes this into 2x
Chocolate Box, 2x Wine Bottle, 2x Greeting Card as sub-items — each can be priced, checked for stock,
and delivered individually, even though the customer just typed "Gift Hamper" once in the order.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 7

 3. Variant Configuration (VC)

3.1 What is it?

Variant Configuration lets ONE material number represent THOUSANDS of possible product variations.
Instead of creating a separate material master for "Laptop-Black-8GB", "Laptop-Black-16GB",
"Laptop-White-8GB"... you create ONE configurable material (called a KMAT), and let the customer (or
sales person) pick options at the time of the sales order. SAP then calculates the right price, pulls the right
BOM components, and routes it to production correctly — all from that ONE material.

■ Think of it like this: Think of ordering a custom pizza online. There isn't a separate "item" in the
menu for every single topping combination (that would be millions of items!). Instead there is ONE
item called "Build Your Own Pizza", and you pick: size, crust type, toppings. The system then
works out the price and the kitchen ticket (ingredients list) based on YOUR choices. That's Variant
Configuration — the pizza is the KMAT, and size/crust/toppings are Characteristics.

3.2 The Building Blocks (all pieces must work together)

Component What it does T-code

Characteristics Individual options the customer can choose — Color, RAM, CT04
Size, etc. (same concept as Section 1, reused here).

Class (Type 300) Groups the characteristics that apply to this configurable CL01/CL02
product.

Configurable Material The single material number representing the whole MM01 (material type
(KMAT) customizable product family. KMAT)

Configuration Profile Links the KMAT material to the Class 300, and controls how CU41
the selection screen behaves.

Super BOM Contains ALL possible components across every variant — CS01
object dependencies filter it down.

Object Dependencies The "IF-THEN" business rules: Preconditions, Selection CU01 or embedded in
Conditions, Constraints, Procedures — decide which CT04/CS01
components/values are valid or forced together.

Variant Pricing Condition records (variant condition type e.g. VA00) so each VK11
characteristic value can add/change price.

Variant Tables Excel-like tables to store valid combinations, useful for LOVC / LOVCC
(optional) complex rule sets.

3.3 Configuration Steps (in order — this is the full chain)

SAP SD Guide — Classification, BOM & Variant Configuration | Page 8

 Step What you do

1 Create all Characteristics needed (Color, RAM, Storage, etc.) with allowed values — CT04

2 Create a Class of Type 300 and assign these characteristics to it — CL01

3 Create the KMAT material master (material type KMAT) for the configurable product — MM01

4 Create a Configuration Profile linking the KMAT to the Class 300 — CU41

5 Build the Super BOM under the KMAT containing every possible component across all variants —
CS01

6 Write Object Dependencies (constraints/preconditions/procedures) so the system auto-selects/filters

the correct BOM components and characteristic values based on customer choices

7 Maintain Variant Pricing condition records so each option correctly adds to/changes the price — VK11

8 Test end-to-end: create a sales order (VA01) for the KMAT, pick characteristic values, confirm correct
BOM explosion, correct price, and correct routing to production

■ WHY THIS IS NEEDED

Without Variant Configuration, a company selling customizable products would need to create a
SEPARATE material master for every single possible combination (imagine a laptop with 4 colors x 5
RAM options x 4 storage options x 3 processors = 240 separate material numbers to maintain
manually, and that's a SIMPLE example). Variant Configuration collapses this into ONE material and
lets the business rules + customer choices decide the rest — massively reducing master data
maintenance and letting sales offer true mass customization.

■ WHAT HAPPENS IF YOU MISS / SKIP THIS

If any single link in the VC chain is missing or wrong, the whole feature breaks in different ways:
missing Configuration Profile → the KMAT won't even show the characteristic selection screen in the
sales order; missing/incomplete Object Dependencies → invalid combinations get allowed (e.g. a
processor that isn't compatible with a motherboard), or the system fails to auto-select mandatory
components, resulting in incomplete/wrong BOM explosion and wrong shipments or wrong production
orders; missing Super BOM link → nothing explodes into production/delivery at all, so the factory
doesn't know what parts to assemble; missing Variant Pricing condition records → the order may price
at zero or at the base price only, ignoring the cost of options selected (direct revenue loss); and if
characteristics were never created properly in Classification (Section 1) in the first place, none of this
is even possible, since Variant Configuration is BUILT on top of the classification system.

3.4 Small Example

KMAT material "LAPTOP-CONFIG" has characteristics RAM (8GB/16GB/32GB) and COLOR
(Black/Silver). An Object Dependency says: "IF RAM = 32GB THEN COLOR must = Black" (because only
the black chassis supports that board). A customer orders LAPTOP-CONFIG in VA01, selects RAM = 32GB
— the system automatically restricts COLOR to Black only, pulls the correct Super BOM components (32GB
RAM stick + correct motherboard + black chassis), and adds the RAM upgrade price automatically via the
variant pricing condition.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 9

 4. Classification vs BOM vs Variant Configuration
— Side by Side

Aspect Material Classification BOM Variant Configuration

Core Question it "What attributes/tags does "What components make "How can ONE material
Answers this material have?" up this product?" become many
customer-chosen versions?"

Basic Unit Characteristic + Class Header material + KMAT + Class(300) + Super

Component lines BOM + Dependencies

Standalone use? Yes — useful on its own for Yes — useful on its own for No — DEPENDS on
search/reporting/batch kits/bundles/production Classification and usually a
Super BOM

Main T-codes CT04, CL01, MM02 CS01, CS02, MM02, VOV4 CT04, CL01, CU41, CS01,
VK11

What breaks if Search/reporting/batch Wrong/incomplete delivery, Wrong config screen, wrong

missing grouping fails pricing, availability check BOM explosion, wrong price,
invalid product builds

Analogy Hashtags on photos A recipe's ingredient list A "build your own" product
configurator (custom pizza /
custom PC)

Key relationship to remember: Variant Configuration is not a separate island — it is built by COMBINING
Classification (characteristics/classes) with a Super BOM (components) and adding Object Dependencies
(business rules) and Variant Pricing (cost impact) on top. If you understand Sections 1 and 2 well, Section 3
is really just "Classification + BOM + Rules + Pricing," wired together.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 10

 5. Putting It All Together — One Real Example
Let's follow one product, a configurable office chair, through all three concepts in a single flow, so you can
see how they connect.

Step A — Classification
We create Characteristics FRAME_COLOR (Black/Grey) and ARMREST (Fixed/Adjustable), grouped into
Class "Z_CHAIR_OPTIONS". This class will later be reused as the Class Type 300 base for Variant
Configuration — so classification work is not wasted, it's the foundation.

Step B — BOM
We create a Super BOM under material "CHAIR-CONFIG" (KMAT) listing every possible component: Black
Frame, Grey Frame, Fixed Armrest, Adjustable Armrest, Seat Cushion (common to all), Gas Lift (common to
all).

Step C — Variant Configuration

We build a Configuration Profile linking CHAIR-CONFIG to Class Z_CHAIR_OPTIONS. We write an Object
Dependency: "IF ARMREST = Adjustable THEN add Adjustable Armrest component AND add price
surcharge of $25 (via VK11)". We test in VA01: the sales user picks FRAME_COLOR = Grey, ARMREST =
Adjustable. The system automatically pulls Grey Frame + Adjustable Armrest + Seat Cushion + Gas Lift into
the BOM explosion, adds the $25 surcharge to the price, and the delivery later ships exactly these 4 physical
components — nothing more, nothing less.

What if ONE step was skipped?

• No Characteristics created → Can't even start; nothing to select.

• Class created but not linked via Configuration Profile → KMAT behaves like a plain material; no
selection screen appears in the sales order at all.

• Super BOM missing components → Order gets priced and confirmed, but delivery/production has
no idea what to physically pick — shipment will be wrong or incomplete.

• Object Dependency missing → System might allow invalid or nonsensical combinations, or fail to
add mandatory components automatically, causing rework or wrong builds.

• Variant Pricing (VK11) missing → Chair ships correctly, but the $25 surcharge for Adjustable
Armrest is NEVER charged to the customer — silent revenue loss that's hard to detect until someone
audits margins.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 11

 6. Quick Reference T-Code Cheat Sheet

T-code Used For

CT04 Create/change Characteristics

CL01 / CL02 / CL03 Create / Change / Display Class

CL20N / CL24N Assign objects (materials/batches) to a class

MM01 / MM02 Create / Change Material Master (incl. Classification view)

CS01 / CS02 / CS03 Create / Change / Display Bill of Material

OS20 Define BOM Usage (Customizing)

VOV4 Item Category Determination (Customizing)

VOV6 Schedule Line Category settings (Customizing)

CU41 / CU42 / CU43 Create / Change / Display Configuration Profile

CU01 / CU02 Maintain Object Dependencies

VK11 / VK12 Create / Change Condition Records (Variant Pricing)

LOVC / LOVCC Maintain Variant Tables

VA01 / VA02 / VA03 Create / Change / Display Sales Order (where everything comes together)

Golden Rule to Remember

Classification = Tags.
BOM = Ingredients list.
Variant Configuration = Tags + Ingredients + Rules + Pricing, combined into a
"build-your-own" product.

Every missing configuration step doesn't just cause an "error message" — it breaks a real
downstream business process: wrong search, wrong shipment, wrong price, or an invalid product
being sold. That is why configuration in SAP is never "optional polish" — it IS the business logic.

SAP SD Guide — Classification, BOM & Variant Configuration | Page 12