SAP LO-VC / AVC

SAP LO-VC (Logistics – Variant Configuration) is the SAP module that enables product configuration at sales order time, deriving order-specific bills of materials from a configurable product model built on characteristics Characteristics (ˌker-ik-tə-ˈris-tiks) n. pl. In variant configuration, a characteristic is a named property with a defined set of values — the core building block used to model variation points in configurator systems. , variant classes, and variant rules. It is the primary tool used in SAP environments to implement Configure To Order (CTO) Configure To Order (CTO) (kən-ˈfi-gyər tü ˈȯr-dər) n. In Configure To Order (CTO), a product is assembled from predefined options upon customer order — no custom engineering, fast delivery, controlled variety. for complex product families. AVC (Advanced Variant Configuration) is its successor in SAP S/4HANA, offering improved performance, an updated user interface, and enhanced classification capabilities.

The LO-VC configuration model

The configuration model in SAP LO-VC is built from several interconnected objects:

Configurable material (KMAT) The SAP KMAT SAP KMAT (ˌes-ˌā-ˈpē ˌkā-ˈmat) n. abbr. A KMAT is SAP's configurable material — the LO-VC object representing a product family around which characteristics, variant BOMs, and configuration rules are organized. is the central object — the material master record that represents the configurable product family. All configuration-relevant objects are linked to the KMAT.

Characteristics and classes Characteristics Characteristics (ˌker-ik-tə-ˈris-tiks) n. pl. In variant configuration, a characteristic is a named property with a defined set of values — the core building block used to model variation points in configurator systems. define the variation points of the product — properties with defined value sets (e.g., Engine type: {Petrol, Diesel, Electric}). Characteristics are grouped into classes, which are then assigned to the KMAT. Together, characteristics and their values represent the option space customers can configure.

Configuration profile Attached to the KMAT, the configuration profile governs how the configuration session is presented: the sequence of characteristics displayed, which are pre-filled, and which user interface is used. It also links to the constraint net.

Variant conditions and dependency nets The constraint logic of the configuration model is defined in dependency nets: preconditions (when is a characteristic displayed?), selection conditions (which BOM items apply for a given configuration?), procedures (how are characteristics computed from other values?), and constraints (which value combinations are forbidden?).

Configurable BOM The configurable BOM attached to the KMAT is the 150% BOM 150% BOM (ˌwən-ˌfif-tē pər-ˈsent ˌbil əv mə-ˈtir-ē-əlz) n. A 150% BOM lists all possible components across all product variants, serving as the master structure for subtractive configuration in variant management. equivalent in SAP: it lists all possible components across all variants. Each BOM item has a selection condition — a procedural variant rule Procedural Variant Rule (prə-ˈsē-jər-əl ˈver-ē-ənt ˈrül) n. Procedural variant rules govern feature models and variant BOMs by executing IF-THEN logic in sequence. Unlike constraints, the result depends on which rules fire first. — that determines whether it is included in a specific configuration.

Configurable routing In addition to the BOM, the production routing can be made configuration-dependent: specific operations are included or excluded based on the configuration, enabling variant-specific production processes.

How configuration works at order time

When a sales order for a configurable product is created in SAP, the system opens a configuration session:

1. The salesperson (or customer, via a connected CPQ system) selects values for the relevant characteristics.
2. Dependency nets propagate selections: choosing one value may automatically set others, restrict available options, or trigger constraints.
3. On completion, the configuration is validated: all mandatory characteristics must be filled; no active constraints may be violated.
4. The configured sales order is saved; the system derives the order-specific BOM by evaluating the selection conditions of each BOM item against the stored characteristic values.
5. The derived BOM is transferred to production as the manufacturing order.

LO-VC versus AVC

SAP introduced Advanced Variant Configuration (AVC) as part of SAP S/4HANA. The key differences:

Aspect	LO-VC (ECC)	AVC (S/4HANA)
Performance	Rule evaluation at order time	Pre-compiled models, faster evaluation
UI	Classic SAP GUI / IPC	Fiori-based configuration UI
Variant tables	Supported	Enhanced with table-driven logic
Integration	SAP CRM / SD	SAP CPQ, Sales Cloud
Cardinality	Single instance per position	Multi-instance (repeated subassemblies)

Most companies running SAP ECC use LO-VC. Migration to AVC occurs as part of S/4HANA transitions. The underlying concepts — KMAT, characteristics, selection conditions, configurable BOM — carry over.

Role in variant management

SAP LO-VC / AVC is the primary implementation vehicle for variant management in SAP-centric manufacturing companies. A well-implemented LO-VC configuration model:

• Enforces the variant space: only valid configurations can be ordered
• Automates BOM derivation: no manual BOM preparation per order
• Links characteristics to pricing (variant conditions) and production routing
• Integrates with the PLM system for product structure and engineering change management

The quality of the LO-VC model reflects the quality of the underlying variant management: an incomplete characteristic model, missing selection conditions, or unvalidated constraints in LO-VC are symptoms of unresolved variant management problems, not just IT issues.

Frequently asked questions

Do we need SAP LO-VC if we already have a CPQ system?

CPQ and SAP LO-VC serve overlapping but distinct purposes. A CPQ system manages the customer-facing configuration and quoting process — guided selling, pricing, proposal generation. SAP LO-VC manages the ERP-side configuration — BOM derivation, production order creation, and materials management. In many implementations, CPQ and LO-VC run in parallel: CPQ handles the sales process and hands the configured order to SAP, where LO-VC derives the manufacturing BOM. Eliminating LO-VC in favor of CPQ-only requires the CPQ system to fully drive BOM derivation and ERP integration — which is technically possible but increases the integration complexity.

How complex can an LO-VC configuration model become?

Production LO-VC models at major manufacturers often contain hundreds of characteristics, thousands of characteristic values, and tens of thousands of BOM items with selection conditions. Dependency nets with hundreds of interdependent rules are common. At this scale, managing the model — keeping it consistent with engineering changes, validating that it produces correct BOMs for all valid configurations, and testing new rules without breaking existing ones — is a significant ongoing engineering discipline, not a one-time setup task.