SAP ConsultingProjects and engineering
SAP VC - Variant Configuration and PLM
SAP VC (Variant Configuration) lets you sell and build many versions of a product without a separate material for each. The product is modeled once as a configurable material; values picked on the sales order drive price, BOM and routing. PLM tracks the model's changes and documents.
Product family
Process
Configure-to-order in SAP VC
The model is built once and reused on every order; changes come in through PLM with a valid-from date.
- 01ModelingPMEVC · CU41 · CU01
Characteristics, super BOM
- 02SimulationCU50 · F2570
Does the BOM explode right
- 03Order configurationVA01 · variant conditions
Consistency, completeness
- 04PlanningMRP · CU51 · F4770
Super BOM exploded by MRP
- 05ProductionProduction order
Chosen parts and operations
- 06Engineering changeCC01 · F2097 · CV01N
Effective from a set date
Comparison
Classic VC or AVC
Both engines can run in one system, chosen per configuration profile; the choice affects modeling, UI and licensing.
Classic VC (LO-VC)
Core scope in the FSD
- No new actions; old ones still run
- Simulation in CU50
- Table mode: Classic or Mixed
- Classic tables: ranges, multiple values
Advanced VC (AVC)
Since 1709, Enhanced LoB
- Constraint solver on SAP HANA
- Single and multi-level models
- Simulation in F2570, Fiori UI
- Table mode: AVC or Mixed; wildcard (*)
Shared by both
One system, per profile
- Models maintained in PMEVC
- Engine set by the profile's mode
- Only Mixed tables link to a DB table
- Copy and compare tools for migration
Scope
Building blocks we set up in SAP VC and PLM
Configuration model
Characteristics, a class type 300 variant class, KMAT, super BOM and super routing, with class nodes for selection.
Dependency strategy
Preconditions, selection conditions, procedures, constraints: rules as AVC constraints, one-off settings as procedures.
Variant tables
Pricing and technical lookup tables; Mixed mode with one value per cell if they must link to a database table.
Variant pricing
Variant conditions tied to the chosen values, so the price builds up with the configuration on the sales order.
Moving from classic to AVC
Copying dependencies, migrating material variants and comparing both engines' results on real orders.
Changes and documents
Change numbers, change record approval workflow (F3402), document info records and product structure management.
Current state
SAP VC and PLM after the move to S/4HANA
- New actions cannot be created, and classification can no longer serve as a selection condition on BOM items. Existing models still run; new ones use procedures, constraints and class nodes.
- PMEVC replaces CU80 and CUMODEL, and CU51 replaces CU51E, CU52 and CU52E. Classification runs in CL20N, CL22N and CL24N; renaming characteristics is no longer possible.
- Engineering change requests and orders (ECR/ECO) are gone in S/4HANA; the change record takes their place. Interim PLM Web UI Engineering Record: end-2030 on-premise, end-2033 under RISE.
- SAP's 2023 feature scope description puts classic VC and product structure management in the core. AVC and change records sit under Enhanced LoB, which may need a separate license.
Localization
Configured products in Türkiye
e-Invoice and e-Dispatch lines
A configured product is invoiced under one material number. If the chosen options must show on the document line, output and e-document mapping need their own design.
E-InvoiceCustoms codes and variants
The customs tariff number (GTİP) is kept per material. If variants of one KMAT fall under different numbers, a material variant or a separate material may be needed.
Import and Export PackageDocument control in defense
In defense projects, document and change control can be tracked in SAP through revision levels, document versions and change records.
From the field
Field notes on SAP VC models
- Every variant a material, or everything a KMAT. The first means thousands of material masters; the second means make-to-order even for variants you could stock. We draw the line with sales and stock data: frequent variants become material variants, the rest stays KMAT.
- Long procedure chains give odd results. Procedures run once, in the order the modeler sets; the longer the chain, the more one changed value can surprise at the end. We move rule-like relationships into constraints, the main tool in AVC.
- The AVC move is taken for a conversion. The tools copy dependencies and compare both engines' results, but AVC evaluates dependencies differently, and in bundle (SET) models $root and $parent references are encapsulated. We test each model on real orders.
- Licensing comes up after the design. AVC and change records are Enhanced LoB, and in Private Edition the VC scope items are on the additional-license list. We settle the engine and change management choice together with a license check.
FAQ
SAP VC and PLM: frequent questions
What is SAP VC?
SAP VC (Variant Configuration) is the S/4HANA function for managing many product versions with one configurable material, characteristics and rules. Values chosen on the sales order determine price, bill of materials and routing, so you do not need a material per variant.
What is the difference between classic VC and AVC?
AVC (Advanced Variant Configuration) is the configuration engine introduced in S/4HANA 1709. It works as a constraint solver and uses a Fiori interface. Classic LO-VC still works, and both engines can run side by side in one system, chosen per profile. SAP's feature scope description places AVC in the section that may need a separate license.
What is a super BOM?
A bill of materials holding every component that any version of the configurable product might use. Selection conditions or class nodes decide, based on the order's values, which components are actually used. The same logic applies to operations through a super routing.
How are engineering changes managed in S/4HANA?
A change number ties changes to BOMs, materials and routings to a date or parameter effectivity. For an approval-driven process S/4HANA uses the change record, which can bundle materials, BOMs, documents, routings and inspection plans. The ECR/ECO objects from ECC do not exist in S/4HANA.
Do ECC variant models still work in S/4HANA?
In general, yes. Existing actions and classification used as a selection condition keep working, but you cannot create new ones. PMEVC replaces CU80 and CUMODEL. Moving to AVC is a separate decision and means retesting the models.
Sources12 sourcesSAP Help Portal, SAP Support, SAP Fiori Apps Library +1
SAP Help Portal
- SAP S/4HANA 2023 Feature Scope Description help.sap.com (opens in a new tab)
- Simplification List for SAP S/4HANA 2022 - Initial Shipment, Feature Pack Stack 1 & 2 help.sap.com (opens in a new tab)
- Pricing Relevant Scope Items - SAP S/4HANA Cloud Private Edition 2023 FP2 with SAP Best Practices help.sap.com (opens in a new tab)
- Advanced Variant Configuration - What's New in SAP S/4HANA 1709 help.sap.com (opens in a new tab)
- Conversion Tools for Advanced Variant Configuration - What's New in SAP S/4HANA 1709 FPS01 help.sap.com (opens in a new tab)
- Processing Mode - Variant Configuration (LO-VC) help.sap.com (opens in a new tab)
- Glossary for Advanced Variant Configuration help.sap.com (opens in a new tab)
SAP Support
SAP Fiori Apps Library
SAP
Sources checked as of October 2026. SAP Notes require an SAP for Me account.
SAP Consulting
Turn your product range into one model
Your portfolio shows which variants to configure and which to stock.