SAP Variant Configuration (VC) is one of the most powerful — and most misunderstood — features in SAP. I've spent over a decade working with it across multiple global companies and projects, and I still see the same confusion: people either think it's too complex to learn, or they underestimate what it takes to build a good model.
This guide is for the first group. Let's explain VC in plain English.
The Problem VC Solves
Imagine you manufacture elevators. Every customer wants a different combination:
- 10 floors vs 20 floors
- Standard speed vs high speed
- Stainless steel doors vs painted doors
- With or without emergency phone
- Different voltage requirements per country
Without VC, you'd need to create a separate material number for every possible combination. For even a moderately complex product, that's thousands of material numbers. Thousands of BOMs. Thousands of routings. Thousands of cost estimates.
With Variant Configuration, you build a single "Super BOM" that contains all possible components. You define rules (called dependencies) that control which components are selected, which options are compatible, and how prices are calculated.
The result: one material number, one BOM, infinite combinations.
Industries That Use VC
| Industry | Example |
|---|---|
| Automotive | Car options (color, engine, trim) |
| Elevators | TK Elevator, KONE, Schindler |
| Furniture | Configurable furniture sets |
| Machinery | Custom pumps, compressors, industrial equipment |
| High Tech | Server configurations, computer builds |
Core Concepts in Plain English
Characteristics
A characteristic is a feature the customer
can choose. Examples: COLOR,
HEIGHT_MM, MATERIAL_TYPE. Each
characteristic has a name, a data type (character, numeric,
currency, date), and a list of allowed values.
Tip: Keep characteristic names simple. Use CHAR and NUM data types as much as possible. Let dependencies handle the complex logic.
Classes
A class is a group of characteristics that belong together. Class type 300 is used for configurable materials, type 200 for class nodes in multi-level BOMs. Think of a class as a "folder" that holds the characteristics relevant to a product family.
Configurable Material (KMAT)
This is the product being configured. It's a material master record (created via MM01) with a special flag marking it as configurable, plus a configuration profile that ties everything together.
Configuration Profile
The configuration profile is the control center of the VC model. It defines which class applies, which dependencies (rules) control the configuration, how the BOM is exploded, and whether it's used in sales, production, or both.
Without a configuration profile, the configurable material is just a material number.
Super BOM
A special BOM that contains all possible components. Components are either selected by dependencies (selection conditions) or class nodes that are resolved during configuration.
Object Dependencies (OD)
These are the rules that make VC work. There are several types:
| Type | Purpose | When It Runs |
|---|---|---|
| Procedure | Sets values (defaults, pricing) | Every time user changes a value |
| Selection Condition | Filters BOM items | During BOM explosion |
| Precondition | Validates or hides value choices | At each user input |
| Constraint | Restricts combinations | Continuously during configuration |
| Dependency Net | Groups constraints | Modular approach |
LO-VC vs AVC: The Two Flavors of VC
SAP Variant Configuration comes in two versions:
LO-VC (Logistics Variant Configuration) — The original, introduced in the 1990s. Based on SAP GUI transactions (CU50, CU41). Stable, well-understood, but no longer enhanced by SAP.
AVC (Advanced Variant Configuration) — Introduced in SAP S/4HANA (2018). Features a Fiori UI (PMEVC), improved constraint solver, enhanced table handling, and better tracing. Actively developed by SAP.
If you're moving to S/4HANA Cloud, AVC is mandatory. For on-premise, you can keep LO-VC — but you'll be running on a platform SAP is no longer enhancing.
Why This Matters Now
With the massive wave of ECC to S/4HANA migrations underway, understanding Variant Configuration — and especially the migration from LO-VC to AVC — is becoming a critical skill for SAP consultants. Companies that invested heavily in LO-VC models need expertise to plan, execute, and validate their migration.
This is where hands-on experience matters. Not just knowing the theory, but understanding how object dependencies behave differently in AVC, how to refactor temporary parameters, and what testing strategy catches the subtle bugs before they hit production.