SAP VC Material Variants: From Configuration to Production

A configurable material isn't a product you can build. It's a template.

When a customer configures a bike — red frame, 150cc engine, disc brakes — you don't want to build each sales order from scratch. You want to capture that specific combination as a material variant, a unique material master with a material number, that production can plan, pick, and manufacture against.

Material variants are the bridge between configuration and manufacturing.

Source: This article is based on SAP Community blog "SAP VC Material Variants: Creation, Usage in Sales Order" (2012, 76 kudos), available at SAP Community. Concepts updated for S/4HANA.

What is a material variant?

A material variant is a standard material master (MM01) that inherits all the master data of its configurable parent — BOM, routing, classification — but has its characteristics pre-assigned to specific values.

Property	Configurable Material	Material Variant
Material type	KMAT	Any (usually finished product or semi-finished)
BOM	Super BOM with selection conditions	Same BOM, items selected per configuration
Classification	Class type 300	Same class, values pre-set
Created by	MM01/MM02	VA01 configuration → CU51 or direct CU51
Used in	Sales orders, production	Production orders, deliveries

When to create a material variant

Two common scenarios:

Scenario 1: Sales order → MTO production

1. Customer orders a configured bike (VA01)
2. Sales order configures the KMAT material
3. You create a material variant (CU51) from the completed configuration
4. Production order references the variant, not the KMAT

Scenario 2: Pre-configured stock variants

1. You know you'll sell 100 red bikes with disc brakes per month
2. Create material variants in advance (CU51 without sales order)
3. Plan production against these variants
4. Sales order directly references the variant material number

Creating a material variant

Method 1: From a sales order configuration (VA01 → CU51)

1. Create a sales order (VA01) with the configurable KMAT material
2. In the item detail, complete the configuration (characteristic values)
3. From the configuration screen, choose Extras → Create Material Variant (or switch to transaction CU51)
4. CU51 copies the KMAT master data and assigns the selected characteristic values
5. Assign a material number — either let the system assign it or enter a meaningful number

The new variant material appears in MM03 with:

• Base data copied from the KMAT
• Classification values pre-filled
• BOM exploded with selection conditions already evaluated

Source: Transaction CU51 — Material Variant Create. Also accessible from Configuration Simulation environment.

Method 2: Direct creation (CU51 standalone)

1. Transaction CU51
2. Enter the configurable material and class type (300)
3. Select characteristic values
4. Save — system creates the material variant

Use this when you know exactly which variants you need without a sales order trigger.

Material variant in production

Once you have a material variant, you can:

1. Create a production order (CO01) referencing the variant material directly
2. Run MRP — it treats the variant as any other material
3. Pick components — BOM items are already selected based on the configuration

The key point: the production planner never needs to see the configuration screen. All decisions are already baked into the variant.

Source: Transaction CO01 — Production Order Create. Enter the material variant number — the BOM is pre-exploded based on configuration.

Multi-level configuration and variants

For complex products (e.g., a car with a configured engine and configured interior), each configurable sub-assembly can also produce its own material variant.

Example structure:

CONFIGURABLE_CAR (KMAT)
  ├── ENGINE_2000CC (material variant of configurable engine)
  └── INTERIOR_LEATHER (material variant of configurable interior)

Each sub-assembly gets its own CU51, and from there production works independently.

What about AVC?

Material variants work with both LO-VC and AVC. The difference:

• In LO-VC: CU51 reads the configuration from the configuration profile and creates the variant
• In AVC: Same CU51 transaction, but the configuration was processed by the AVC inference engine. The variant creation itself is identical.

SAP Note: When using AVC, the material variant stores the final characteristic values as determined by the constraint engine.

Common pitfalls

Problem	Cause	Fix
Variant not found in production	No BOM exploded for variant	Check BOM usage and alternative, re-create variant with proper plant
Variant shows wrong components	BOM selection conditions not updated	Re-explode BOM for variant, check dependency logic
"Material variant does not exist"	Transport issue	Move KMAT + variant together, check material type
Inconsistent configuration	Characteristic values changed after variant creation	Use ECM to track changes, freeze variant

Best practices

1. Naming convention: Use a meaningful pattern e.g., BIKE-RED-150-DISC so the material number tells you the config
2. Group variants: Use material groups to categorize variants by product family
3. Don't over-create: Each variant is a material master. Creating 10,000 variants creates database overhead. Create only what you need for production planning.
4. Use engineering records: In S/4HANA, Engineering Records can track variant changes and revisions

Source: SAP Community — SAP VC Material Variants (2012, 76 kudos). Available at SAP Community.

Summary

Material variants are a simple concept with big impact: take a configured product and stamp it as a buildable material number. They decouple configuration from production — the sales guy configures, the plant builds, and the two sides meet through the variant.

The workflow: KMAT → Configure → CU51 → Material Variant → CO01 → Production.